[Touch-packages] [Bug 1475084] [NEW] Gallery app appears to scan all folders for images
Public bug reported: The gallery app appears to scan all user folders for images, as a result album art for music collection is shown in the gallery. It should just show images in the 'Pictures' folder. ** Affects: gallery-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1475084 Title: Gallery app appears to scan all folders for images Status in gallery-app package in Ubuntu: New Bug description: The gallery app appears to scan all user folders for images, as a result album art for music collection is shown in the gallery. It should just show images in the 'Pictures' folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1475084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474720] Re: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed:
And r2749 built with clang looks similar: [1437014933.264840] mirserver: Selected driver: dummy (version 0.15.0) [1437014933.280540] mirserver: Using software cursor [1437014933.281941] mirserver: Mir version 0.15.0 [1437014933.282095] mirserver: GL vendor: [1437014933.282104] mirserver: GL renderer: [1437014933.282107] mirserver: GL version: [1437014933.282109] mirserver: GLSL version: [1437014933.282113] mirserver: GL max texture size = 0 [1437014933.282115] mirserver: GL framebuffer bits: RGBA=, depth=0, stencil=0 ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: ( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1474720 Title: [regression] Mir servers crash on start-up. dummy graphics driver selected and then: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: [1437011956.469215] mirserver: Selected driver: dummy (version 0.15.0) [1437011956.492673] mirserver: Using software cursor [1437011956.493899] mirserver: Mir version 0.15.0 ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475129] [NEW] HP EliteBook 9480m and others crash when sleeping docked and resuming undocked
Public bug reported: I've seen this bug on multiple versions of Ubuntu (14.04 and 15.04) and with multiple hardware (HP EliteBook 9470m, HP EliteBook 9480m, and HP EliteBook 820). Not surprising since they appear to share a bios core. They are all running latest BIOS. Sleep/resume normally works fine, but if I allow it to sleep while in the docking station, and then I undock it and resume it, it appears to try to resume, then after half a second or so, it flashes back to POST screen and boots fresh. It looks to me like the resume operation crashes somehow and it reboots. Observations: It does not matter if there are any monitors pluged into the docking station. I've tried toggling deep-sleep in bios, no effect. I've tried toggling USB3 in bios, no effect. I can't find any indication of a crash or a reason for the reboot in any of the logs. I added the dmesg from EliteBook 820 because it's the simpler installation. I have Bluetooth, Camera, and audio turned off in bios for various reasons. It is also docked in a monitor-less dock (I use it for charging). Please let me know what other information I can provide. ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Attachment added: dmesg.txt from EliteBook 820 and 14.04.2 https://bugs.launchpad.net/bugs/1475129/+attachment/4429759/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1475129 Title: HP EliteBook 9480m and others crash when sleeping docked and resuming undocked Status in pm-utils package in Ubuntu: New Bug description: I've seen this bug on multiple versions of Ubuntu (14.04 and 15.04) and with multiple hardware (HP EliteBook 9470m, HP EliteBook 9480m, and HP EliteBook 820). Not surprising since they appear to share a bios core. They are all running latest BIOS. Sleep/resume normally works fine, but if I allow it to sleep while in the docking station, and then I undock it and resume it, it appears to try to resume, then after half a second or so, it flashes back to POST screen and boots fresh. It looks to me like the resume operation crashes somehow and it reboots. Observations: It does not matter if there are any monitors pluged into the docking station. I've tried toggling deep-sleep in bios, no effect. I've tried toggling USB3 in bios, no effect. I can't find any indication of a crash or a reason for the reboot in any of the logs. I added the dmesg from EliteBook 820 because it's the simpler installation. I have Bluetooth, Camera, and audio turned off in bios for various reasons. It is also docked in a monitor-less dock (I use it for charging). Please let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1475129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475133] Re: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1475133 Title: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました Status in sudo package in Ubuntu: New Bug description: bagu no kaksyou wa nai ubuntu14.04 to debinan8.1 dualboot de tukatteimasu debian de synaptic to gparted dewa rootpasward ga toru noni tannmatu de touranai dakara komatuteimasu sudo o tukauto rootpasword gatoutainodesu ProblemType: Package DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: sudo: Remove sudo-ldap: Install sudo-ldap: Configure Architecture: amd64 Date: Tue Jul 14 17:03:39 2015 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1.1:サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました ErrorMessage: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました InstallationDate: Installed on 2015-02-01 (164 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Build amd64 LIVE Binary 20140422-09:40 SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: 正しく構文解析されました /etc/sudoers.d/README: 正しく構文解析されました To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1475133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474891] Re: USC crash on multimonitor unplug [std::exception::what: error during hwc prepare()]
** Summary changed: - USC crash on multimonitor unplug + USC crash on multimonitor unplug [std::exception::what: error during hwc prepare()] ** Changed in: mir Milestone: None = 0.15.0 ** Tags added: android multimonitor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1474891 Title: USC crash on multimonitor unplug [std::exception::what: error during hwc prepare()] Status in Mir: In Progress Status in Unity System Compositor: New Status in mir package in Ubuntu: New Bug description: I've a slightly customized USC built in Silo0. On top of that, a multimonitor-aware unity8 is running. http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu/landing-000 On Android devices, Nexus 4 7, I occasionally get a crash on external monitor unplug. Here is the relevant log: ERROR: /build/mir-UAyS26/mir-0.13.4+15.04.20150709.2/src/platforms/android/server/real_hwc_wrapper.cpp(123): Throw in function virtual void mir::graphics::android::RealHwcWrapper::set(const std::arrayhwc_display_contents_1*, 3u) const Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: error during hwc prepare(). rc = To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474720] Re: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed:
Uh, of course the problem was staring at me right there on the first line: [1437014933.264840] mirserver: Selected driver: dummy (version 0.15.0) That's not a driver that will work. :) ** Summary changed: - [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: + [regression] Mir servers crash on start-up. dummy graphics driver selected and then: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: ** Description changed: All Mir demo servers are now crashing on start-up, with very little explanation: + [1437011956.469215] mirserver: Selected driver: dummy (version 0.15.0) + [1437011956.492673] mirserver: Using software cursor + [1437011956.493899] mirserver: Mir version 0.15.0 ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1474720 Title: [regression] Mir servers crash on start-up. dummy graphics driver selected and then: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: [1437011956.469215] mirserver: Selected driver: dummy (version 0.15.0) [1437011956.492673] mirserver: Using software cursor [1437011956.493899] mirserver: Mir version 0.15.0 ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475133] [NEW] package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました
Public bug reported: bagu no kaksyou wa nai ubuntu14.04 to debinan8.1 dualboot de tukatteimasu debian de synaptic to gparted dewa rootpasward ga toru noni tannmatu de touranai dakara komatuteimasu sudo o tukauto rootpasword gatoutainodesu ProblemType: Package DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: sudo: Remove sudo-ldap: Install sudo-ldap: Configure Architecture: amd64 Date: Tue Jul 14 17:03:39 2015 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1.1:サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました ErrorMessage: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました InstallationDate: Installed on 2015-02-01 (164 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Build amd64 LIVE Binary 20140422-09:40 SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: 正しく構文解析されました /etc/sudoers.d/README: 正しく構文解析されました ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1475133 Title: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました Status in sudo package in Ubuntu: New Bug description: bagu no kaksyou wa nai ubuntu14.04 to debinan8.1 dualboot de tukatteimasu debian de synaptic to gparted dewa rootpasward ga toru noni tannmatu de touranai dakara komatuteimasu sudo o tukauto rootpasword gatoutainodesu ProblemType: Package DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: sudo: Remove sudo-ldap: Install sudo-ldap: Configure Architecture: amd64 Date: Tue Jul 14 17:03:39 2015 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1.1:サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました ErrorMessage: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました InstallationDate: Installed on 2015-02-01 (164 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Build amd64 LIVE Binary 20140422-09:40 SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: 正しく構文解析されました /etc/sudoers.d/README: 正しく構文解析されました To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1475133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473800] Re: systemd update causes screen to lock
This seems to happen on systemctl try-restart systemd-logind.service. ** Changed in: systemd (Ubuntu) Status: Confirmed = Triaged ** Changed in: systemd (Ubuntu) Importance: Low = Medium ** Summary changed: - systemd update causes screen to lock + restarting logind during systemd update causes screen to lock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1473800 Title: restarting logind during systemd update causes screen to lock Status in systemd package in Ubuntu: Triaged Bug description: When systemd is updated (through the update manager), the screen/session locks when processing the update. I've had this happen twice I think, and the only suspicious packages are the systemd ones. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 222-1ubuntu3 ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7 Uname: Linux 4.0.0-4-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 13 09:49:47 2015 InstallationDate: Installed on 2015-01-31 (162 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-4-generic root=UUID=4c827ac5-3a87-4443-86eb-a55dca9626ad ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: FM2A88X Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/31/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1473800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475094] Re: Warning because an already existing user is tried to be created
http://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=daf17c2 ** Changed in: systemd (Ubuntu) Status: Triaged = Fix Committed ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1475094 Title: Warning because an already existing user is tried to be created Status in systemd package in Ubuntu: Fix Committed Bug description: I'm using Ubuntu 15.10 dev with systemd/udev 222-1ubuntu4 and on the last upgrades I have noticed that these packages are trying to create users which already exists. On reinstalling them udev shows on setting up addgroup: The group `input' already exists as a system group. Exiting. and systemd shows on setting up addgroup: The group `systemd-journal' already exists as a system group. Exiting. and addgroup: The group `systemd-journal-remote' already exists as a system group. Exiting.. Maybe it could be checked if a user exists to avoid showing a warning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474289] Re: QThread: fix race when setting the eventDispatcher
here is my complete patchset against qt4 version in ubuntu trusty https://github.com/qtproject/qt/commit/0db65e148dcb4d5e5b98475f207d41a287c401a1.patch https://github.com/qtproject/qt/commit/45693cc638d10890f2816a38d38de6ddaf04ffd3.patch https://github.com/qtproject/qt/commit/64a2bc8cebe36ed4e7ad430a23fc4bb536f790e1.patch https://github.com/qtproject/qt/commit/753321eb459d2c988d66cc6c8905d75a0ba769bb.patch https://github.com/qtproject/qt/commit/7fcb100bbf6e8482039f915a9df93d951f7d52e6.patch https://github.com/qtproject/qt/commit/80e3108f5cd1e1850ec81a21100d79a0946addd7.patch https://github.com/qtproject/qt/commit/97b85f4f4e7fc14ff47cd92e4525f7a56864bff4.patch https://github.com/qtproject/qt/commit/c830cfab4f9b264c26c0111fe923562b82f72fed.patch https://github.com/qtproject/qt/commit/fa81aa6d027049e855b76f5408586a288f160575.patch https://github.com/qtproject/qt/commit/fb7fa2918b558381dd98aff3d3250786300d8a3b.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1474289 Title: QThread: fix race when setting the eventDispatcher Status in qt4-x11 package in Ubuntu: New Bug description: Please see here: https://bugreports.qt.io/browse/QTBUG-29452 this patch: https://codereview.qt-project.org/#/c/105574/ should be included to avoid random crash when using QThread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1474289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1466790] Re: dhclient does not remain running on boot
** Package changed: ifupdown (Ubuntu) = systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: New = In Progress ** Changed in: systemd (Ubuntu) Importance: Undecided = High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1466790 Title: dhclient does not remain running on boot Status in systemd package in Ubuntu: In Progress Bug description: Not sure whether this is a systemd or ifupdown issue. I just happened to notice today for a Wily VM (set up from server iso) that I failed to get a DNS resolution for a VM I started earlier the day. DNS updates in my case are related to DHCP updates. And on the DHCP/DNS server I noticed that the IP address had been removed at some point. Looking at the VM, I find no dhclient being started. When I manually run ifdown and ifup on the interface this does happen. But not whenever I boot. Curious about this I also checked a Vivid VM (also server install) and this looks the same. However for Vivid this seems fixed in the latest versions. Network config in /etc/network/interfaces: auto eth0 iface eth0 inet dhcp Expected result: dhclient running for eth0 Actual result after boot: No dhclient process is running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1466790] Re: dhclient does not remain running on boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1466790 Title: dhclient does not remain running on boot Status in systemd package in Ubuntu: In Progress Bug description: Not sure whether this is a systemd or ifupdown issue. I just happened to notice today for a Wily VM (set up from server iso) that I failed to get a DNS resolution for a VM I started earlier the day. DNS updates in my case are related to DHCP updates. And on the DHCP/DNS server I noticed that the IP address had been removed at some point. Looking at the VM, I find no dhclient being started. When I manually run ifdown and ifup on the interface this does happen. But not whenever I boot. Curious about this I also checked a Vivid VM (also server install) and this looks the same. However for Vivid this seems fixed in the latest versions. Network config in /etc/network/interfaces: auto eth0 iface eth0 inet dhcp Expected result: dhclient running for eth0 Actual result after boot: No dhclient process is running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455194] Re: error booting
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1455194 Title: error booting Status in xorg package in Ubuntu: Expired Bug description: goes to a purpule screen at boot ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8.4 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: Thu May 14 11:52:13 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b9] InstallationDate: Installed on 2001-01-25 (5222 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Apple Inc. MacBookPro5,5 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) 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.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed May 13 14:17:50 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455127] Re: [xorg-edgers] screen freezes while audio playback is still active
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1455127 Title: [xorg-edgers] screen freezes while audio playback is still active Status in xorg package in Ubuntu: Expired Bug description: The issue seems to occur randomly and has been experienced 5 times over last ~3 weeks. If it does there's no reaction for 10 minutes (then I usually force a reboot). Changing the tty with kbdCtrl/kbd+kbdAlt/kbd+kbdF[N]/kbd doesn't work while the audio playback (in `vlc` 2.2.0) continues over the whole 10 minutes. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 Uname: Linux 4.0.1-040001-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde kein Wert zugewiesen CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 14 17:26:04 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3904] InstallationDate: Installed on 2015-04-02 (41 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: LENOVO 20221 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.0.1-040001-generic root=UUID=0d646fdd-bb34-4e1c-9271-86a59deb3bf9 ro rootflags=subvol=@ SourcePackage: xorg SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60+git20150416.0d78b37b-0ubuntu0ricotz2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150505.5054e227-0ubuntu0sarvatt~vivid version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu May 14 17:02:38 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5557 vendor CMN xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] Headphone out on docking station doesn't work
Confirmed bug - HP EliteBook 9470m and 9480m. Works fine in WIndows. US UltraSlim docking station (2013 model) Although I can no longer test it, I believe this issue was also in 14.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1470730 Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] Headphone out on docking station doesn't work Status in alsa-driver package in Ubuntu: New Bug description: When I plug in external speakers to headphone out on the laptop the internal speakers are turned off but when I plug the speakers into the docking station (HP UltraSlim Dock 2013 EURO, D9Y32AA) music keeps playing in the internal speakers. ### Expected behaviour Plugging in external speakers to docking station should turn off sound from laptop internal speakers. ### Current behaviour Sound keeps playing in internal speakers when plugging in external speakers to docking station. ### Hardware Laptop: HP EliteBook 840 G2 Product number: H9W19EA#AK8 Docking station: HP UltraSlim Dock 2013 EURO Product number: D9Y32AA ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chol 2001 F pulseaudio /dev/snd/controlC0: chol 2001 F pulseaudio /dev/snd/controlC1: chol 2001 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 2 08:16:15 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-05 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.04 dmi.board.name: 2216 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.54 dmi.chassis.asset.tag: 5CG5093YZ7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009D410303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G2 dmi.product.version: A3009D410303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1470730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453894] Re: Trackpad and External mouse non-responsive.
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1453894 Title: Trackpad and External mouse non-responsive. Status in xorg package in Ubuntu: Expired Bug description: -Based on wiki.ubuntu.com, I should file this against HAL. -This problem went away for the past year, but as of ~last week, the trackpad stops responding all together after minutes of having booted or returning from sleep (and often times neither of those things brings the trackpad back to life). -The problem is not (no longer?) intermittent; if the trackpad is functioning, I can count on it to stop functioning after ~minutes of use. Once it's dead, I can only hope that a reboot/sleep will resurrect it. -This has been a recurrent issue with my particular machine, a Lenovo U300s; it was so bad to begin with that I had a technician come twice to check/replace the hardware. -External mice have almost never worked on either USB port (even though lsusb properly identifies the manufacturer/device). -**Two things have occurred that may have triggered this**, with the first being the most suspicious: 1) I accidentally let the battery drain completely from the laptop 2) There were a series of kernel upgrades that happened this month. Both of these things occurred at/around the time when this problem started again, but because I have reason to suspect both things, I don't know what might actually be at fault. I will try draining the battery entirely again (leaving the boot select menu open in the BIOS screen), as well as physically disconnecting the battery. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 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: Mon May 11 13:15:59 2015 DistUpgraded: 2014-04-24 07:47:06,026 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3975] InstallationDate: Installed on 2013-12-05 (522 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 1080 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=b8983716-7cb8-479d-85b4-b876ca2da340 ro quiet splash elevator=noop vt.handoff=7 SourcePackage: xorg SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to trusty on 2014-04-24 (382 days ago) dmi.bios.date: 04/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 56CN43WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U300s dmi.board.vendor: LENOVO dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad U300s dmi.modalias: dmi:bvnLENOVO:bvr56CN43WW:bd04/03/2012:svnLENOVO:pn1080:pvrLenovoIdeaPadU300s:rvnLENOVO:rnU300s:rvr1.0:cvnLENOVO:ct10:cvrLenovoIdeaPadU300s: dmi.product.name: 1080 dmi.product.version: Lenovo IdeaPad U300s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon May 11 08:53:19 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4916 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to:
[Touch-packages] [Bug 1455715] Re: en terminal
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1455715 Title: en terminal Status in xorg package in Ubuntu: Expired Bug description: no se ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 15 22:36:28 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-53-generic, i686: installed GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:019c] Subsystem: Acer Incorporated [ALI] Device [1025:019c] MachineType: Acer Aspire one ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=95ad651a-75cb-4dac-9df7-8ab79aaba701 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire one dmi.board.vendor: Acer dmi.board.version: V1.05 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd02/20/2009:svnAcer:pnAspireone:pvrV1.05:rvnAcer:rnAspireone:rvrV1.05:cvnAcer:ct1:cvrV1.05: dmi.product.name: Aspire one dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.60+git20150416.0d78b37b-0ubuntu0ricotz2~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150423.125574d1-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150423.125574d1-0ubuntu0ricotz~trusty version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150505.5054e227-0ubuntu0sarvatt~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2 xserver.bootTime: Fri May 15 17:13:24 2015 xserver.configfile: default xserver.errors: intel: Failed to load module present (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21838 vendor SEC xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452519] Re: Xorg freeze
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1452519 Title: Xorg freeze Status in xorg package in Ubuntu: Expired Bug description: This happens at log out. Reboot and shutdown work fine but any attempt to log out will freeze X. I can't even switch to a tty. The screen freezes for about 30 seconds then drops to the shell but is still frozen. The only way to correct the problem is a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-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 CurrentDesktop: Unity Date: Wed May 6 20:30:30 2015 DistUpgraded: 2015-04-21 21:43:42,239 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-16-generic, x86_64: installed focaltech, 1.5, 3.19.0-16-generic, x86_64: installed nvidia-349, 349.16, 3.19.0-16-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2015-04-22 (14 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. N550JX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to vivid on 2015-04-22 (14 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JX.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JX.202:bd01/08/2015:svnASUSTeKCOMPUTERINC.:pnN550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60+git20150416.0d78b37b-0ubuntu0ricotz2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150423.125574d1-0ubuntu0ricotz version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150505.5054e227-0ubuntu0sarvatt~vivid version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20150318.d29d8baa-0ubuntu0sarvatt xserver.bootTime: Wed May 6 20:22:55 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SDC xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1452519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450911] Re: Xorg freeze
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1450911 Title: Xorg freeze Status in xorg package in Ubuntu: Expired Bug description: ubuntu-bug ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic i686 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 1 23:39:23 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 14.200, 3.13.0-49-generic, i686: installed fglrx, 14.200, 3.13.0-51-generic, i686: installed GpuHangFrequency: I don't know GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e244] InstallationDate: Installed on 2015-04-12 (19 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-51-generic root=UUID=32a7f783-bc9a-43e1-b5a1-22dd6c7c1df5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/28/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri May 1 23:34:35 2015 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputA4TECH USB DeviceKEYBOARD, id 8 inputA4TECH USB DeviceMOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1450911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475129] Re: HP EliteBook 9480m and others crash when sleeping docked and resuming undocked
as a clarification, the 820 has the BT, audio, and camera turned off in the bios, but the 9480m does not. Those three items are not a variable in this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1475129 Title: HP EliteBook 9480m and others crash when sleeping docked and resuming undocked Status in pm-utils package in Ubuntu: New Bug description: I've seen this bug on multiple versions of Ubuntu (14.04 and 15.04) and with multiple hardware (HP EliteBook 9470m, HP EliteBook 9480m, and HP EliteBook 820). Not surprising since they appear to share a bios core. They are all running latest BIOS. Sleep/resume normally works fine, but if I allow it to sleep while in the docking station, and then I undock it and resume it, it appears to try to resume, then after half a second or so, it flashes back to POST screen and boots fresh. It looks to me like the resume operation crashes somehow and it reboots. Observations: It does not matter if there are any monitors pluged into the docking station. I've tried toggling deep-sleep in bios, no effect. I've tried toggling USB3 in bios, no effect. I can't find any indication of a crash or a reason for the reboot in any of the logs. I added the dmesg from EliteBook 820 because it's the simpler installation. I have Bluetooth, Camera, and audio turned off in bios for various reasons. It is also docked in a monitor-less dock (I use it for charging). Please let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1475129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475129] Re: HP EliteBook 9480m and others crash when sleeping docked and resuming undocked
I had the wrong package selected. But I'm not sure if this is a pm-utils issue or a kernel issue. ** Package changed: alsa-driver (Ubuntu) = pm-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1475129 Title: HP EliteBook 9480m and others crash when sleeping docked and resuming undocked Status in pm-utils package in Ubuntu: New Bug description: I've seen this bug on multiple versions of Ubuntu (14.04 and 15.04) and with multiple hardware (HP EliteBook 9470m, HP EliteBook 9480m, and HP EliteBook 820). Not surprising since they appear to share a bios core. They are all running latest BIOS. Sleep/resume normally works fine, but if I allow it to sleep while in the docking station, and then I undock it and resume it, it appears to try to resume, then after half a second or so, it flashes back to POST screen and boots fresh. It looks to me like the resume operation crashes somehow and it reboots. Observations: It does not matter if there are any monitors pluged into the docking station. I've tried toggling deep-sleep in bios, no effect. I've tried toggling USB3 in bios, no effect. I can't find any indication of a crash or a reason for the reboot in any of the logs. I added the dmesg from EliteBook 820 because it's the simpler installation. I have Bluetooth, Camera, and audio turned off in bios for various reasons. It is also docked in a monitor-less dock (I use it for charging). Please let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1475129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474944] Re: Settings Display results from SCOPE is not translated
** Changed in: savilerow Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1474944 Title: Settings Display results from SCOPE is not translated Status in Canonical System Image: Confirmed Status in The Savilerow project: Invalid Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: Since keyword support was added, agg scopes automatically get user settings to enable/disable child scopes. PROBLEM: Theses always display in English for me. I flashed with a --wipe: ubuntu-device-flash --wipe --channel=ubuntu-touch/rc-proposed/bq-aquaris.en On first boot welcome wizard I chose Spanish/Spain. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 67 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-07-15 16:17:29 version version: 67 version ubuntu: 20150715 version device: 20150529-8e13c5f version custom: 20150709-814-29-21-vivid See screenshot of Video agg. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1474944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474720] Re: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed:
I am sure because I bisected the issue meaning that I verified r2741 works and r2742 doesn't. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1474720 Title: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474720] Re: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed:
The error appears to originate in gl_program_family.cpp, so could be driver specific. I'm using Intel i915. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1474720 Title: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474720] Re: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed:
And crashing again in r2749 :( [1437011956.469215] mirserver: Selected driver: dummy (version 0.15.0) [1437011956.492673] mirserver: Using software cursor [1437011956.493899] mirserver: Mir version 0.15.0 ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: Verified r2748 does not have the crash: [1437011965.849147] mirserver: Selected driver: mesa-kms (version 0.15.0) [1437011966.168966] mirserver: Using hardware cursor [1437011966.169684] mirserver: Mir version 0.15.0 [1437011966.174499] mirserver: GL vendor: Intel Open Source Technology Center [1437011966.174518] mirserver: GL renderer: Mesa DRI Intel(R) Haswell Desktop [1437011966.174525] mirserver: GL version: OpenGL ES 3.0 Mesa 10.5.9 [1437011966.174531] mirserver: GLSL version: OpenGL ES GLSL ES 3.00 [1437011966.174540] mirserver: GL max texture size = 8192 [1437011966.174556] mirserver: GL framebuffer bits: RGBA=8880, depth=0, stencil=0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1474720 Title: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474720] Re: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed:
It might be related to bug 1416482 which was around the same area. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1474720 Title: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475094] [NEW] Warning because an already existing user is tried to be created
Public bug reported: I'm using Ubuntu 15.10 dev with systemd/udev 222-1ubuntu4 and on the last upgrades I have noticed that these packages are trying to create users which already exists. On reinstalling them udev shows on setting up addgroup: The group `input' already exists as a system group. Exiting. and systemd shows on setting up addgroup: The group `systemd- journal' already exists as a system group. Exiting. and addgroup: The group `systemd-journal-remote' already exists as a system group. Exiting.. Maybe it could be checked if a user exists to avoid showing a warning. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm using Ubuntu 15.10 dev with systemd/udev 222-1ubuntu4 and on the last upgrades I have noticed that these packages are trying to create users which already exists. On reinstalling them udev shows on setting up addgroup: The group `input' already exists as a system group. Exiting. and systemd shows on setting up addgroup: The group `systemd- journal' already exists as a system group. Exiting. and addgroup: The group `systemd-journal-remote' already exists as a system group. - Exiting.. Maybe it could be checked if a users exists to avoid showing - a warning. + Exiting.. Maybe it could be checked if a user exists to avoid showing a + warning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1475094 Title: Warning because an already existing user is tried to be created Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: I'm using Ubuntu 15.10 dev with systemd/udev 222-1ubuntu4 and on the last upgrades I have noticed that these packages are trying to create users which already exists. On reinstalling them udev shows on setting up addgroup: The group `input' already exists as a system group. Exiting. and systemd shows on setting up addgroup: The group `systemd-journal' already exists as a system group. Exiting. and addgroup: The group `systemd-journal-remote' already exists as a system group. Exiting.. Maybe it could be checked if a user exists to avoid showing a warning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240909] Re: [performance] Restore support for double-buffering by default
Apparently the fix got reverted in the 0.14 branch. It's still present in 0.15 but sounds like it will need fixing. ** Changed in: mir Milestone: 0.14.0 = 0.15.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1240909 Title: [performance] Restore support for double-buffering by default Status in Mir: Fix Committed Status in Mir 0.5 series: Won't Fix Status in mir package in Ubuntu: Triaged Bug description: We really should restore support for double-buffering where possible. Presently we're on triple-buffering all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1240909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475094] Re: Warning because an already existing user is tried to be created
** No longer affects: udev (Ubuntu) ** Changed in: systemd (Ubuntu) Status: New = Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1475094 Title: Warning because an already existing user is tried to be created Status in systemd package in Ubuntu: Triaged Bug description: I'm using Ubuntu 15.10 dev with systemd/udev 222-1ubuntu4 and on the last upgrades I have noticed that these packages are trying to create users which already exists. On reinstalling them udev shows on setting up addgroup: The group `input' already exists as a system group. Exiting. and systemd shows on setting up addgroup: The group `systemd-journal' already exists as a system group. Exiting. and addgroup: The group `systemd-journal-remote' already exists as a system group. Exiting.. Maybe it could be checked if a user exists to avoid showing a warning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474720] Re: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed:
Fix committed: Reverted r2742 in r2746. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1474720 Title: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437912] Re: SMS not stored
@Sebastien Bacher (seb128) There is a duplicate here : #1448492 from Ilario Gelmetti ** Description changed: Hi, - I tried to receive a SMS with code number. The SMS his send by a robot + I tried to receive a SMS with code number. The SMS is send by a robot and I supposed it's a SMS class 0. I got a notification and a new entry in message list. I can see the beginning of the SMS. When I click on the sender, it displays nothing and the notification in message list (1 green) stay. Edit : And the SMS is not readable entirely. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1437912 Title: SMS not stored Status in messaging-app package in Ubuntu: New Bug description: Hi, I tried to receive a SMS with code number. The SMS is send by a robot and I supposed it's a SMS class 0. I got a notification and a new entry in message list. I can see the beginning of the SMS. When I click on the sender, it displays nothing and the notification in message list (1 green) stay. Edit : And the SMS is not readable entirely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1437912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452320] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: mir (Ubuntu) Importance: Undecided = Critical ** Changed in: mir (Ubuntu) Status: New = Confirmed ** Changed in: mir (Ubuntu) Milestone: None = ubuntu-15.07 ** Changed in: mir (Ubuntu Vivid) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1452320 Title: please drop build-dependency on g++-4.9 Status in Mir: Fix Committed Status in mir package in Ubuntu: Confirmed Status in mir source package in Vivid: Won't Fix Bug description: The mir package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1452320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452327] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: indicator-network (Ubuntu) Importance: Undecided = Critical ** Changed in: indicator-network (Ubuntu) Status: New = Confirmed ** Changed in: indicator-network (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1452327 Title: please drop build-dependency on g++-4.9 Status in indicator-network package in Ubuntu: Confirmed Bug description: The indicator-network package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1452327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452336] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: platform-api (Ubuntu) Importance: Undecided = Critical ** Changed in: platform-api (Ubuntu) Status: New = Confirmed ** Changed in: platform-api (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1452336 Title: please drop build-dependency on g++-4.9 Status in platform-api package in Ubuntu: Confirmed Bug description: The platform-api package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/platform-api/+bug/1452336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452332] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: mediascanner2 (Ubuntu) Importance: Undecided = Critical ** Changed in: mediascanner2 (Ubuntu) Status: New = Confirmed ** Changed in: mediascanner2 (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1452332 Title: please drop build-dependency on g++-4.9 Status in mediascanner2 package in Ubuntu: Confirmed Bug description: The mediascanner2 package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1452332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452324] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: indicator-location (Ubuntu) Importance: Undecided = Critical ** Changed in: indicator-location (Ubuntu) Status: New = Confirmed ** Changed in: indicator-location (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1452324 Title: please drop build-dependency on g++-4.9 Status in indicator-location package in Ubuntu: Confirmed Bug description: The indicator-location package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1452324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452319] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = Critical ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1452319 Title: please drop build-dependency on g++-4.9 Status in indicator-datetime package in Ubuntu: Confirmed Bug description: The indicator-datetime package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1452319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452329] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: location-service (Ubuntu) Importance: Undecided = Critical ** Changed in: location-service (Ubuntu) Status: New = Confirmed ** Changed in: location-service (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1452329 Title: please drop build-dependency on g++-4.9 Status in location-service package in Ubuntu: Confirmed Bug description: The location-service package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1452329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452321] Re: [connectivity-service] please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: indicator-network (Ubuntu) Importance: Undecided = Critical ** Changed in: indicator-network (Ubuntu) Status: New = Confirmed ** Changed in: indicator-network (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1452321 Title: [connectivity-service] please drop build-dependency on g++-4.9 Status in indicator-network package in Ubuntu: Confirmed Bug description: The connectivity-api package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1452321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1230366] Re: Please provide Ubuntu camera service that integrates with trust-store
** Changed in: canonical-devices-system-image Assignee: John McAleely (john.mcaleely) = Manuel de la Peña (mandel) ** Changed in: qtubuntu-camera (Ubuntu) Assignee: (unassigned) = Manuel de la Peña (mandel) ** Changed in: qtubuntu-camera (Ubuntu RTM) Assignee: (unassigned) = Manuel de la Peña (mandel) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1230366 Title: Please provide Ubuntu camera service that integrates with trust-store Status in Canonical System Image: Triaged Status in qtubuntu-camera package in Ubuntu: Triaged Status in qtubuntu-camera package in Ubuntu RTM: Invalid Bug description: Currently Ubuntu Touch is using the android camera-service and that is the plan for 13.10. Going forward in 14.04, the android camera-service will no longer be used and camera access is going to move to the Ubuntu side. There was discussion of either using HAL directly (direct access to devices) or using a camera-service type thing in Ubuntu. Using devices directly causes at least a few problems: * can't prevent more than one user from accessing the device at a time * enumerating camera devices for apparmor policy is extra maintenance for porters * can't provide a contextual runtime prompt for access (like we (will) do with online accounts, location, microphone). This is particularly important for application confinement. Instead of direct hardware access, an out of process helper (in relation to the app) can be used to address all of these problems, similar to what pulseaudio does for audio. This service can ensure only one user can access the device at a time and since the service accesses the the device files on the app's behalf, we don't need to enumerate devices in /dev in policy. Furthermore, when an app accesses the service (ideally over DBus), the service can contact trust-store, the trust-store will prompt the user (Foo wants to access the camera. Is this ok? Yes|No), then optionally cache the result and return the result to the service. In this manner the user is given a contextual prompt at the time of access by the app. By using caching this decision can be remembered the next time. If caching is used, there should be a method to change the decision in system settings. If direct hardware access is needed for performance reasons, it is possible to use fd delegation in AppArmor and have the service open the device and pass the fd to the app without having to enumerate the /dev devices. Please talk to jjohansen if pursuing this option. Lastly, bug #1230391 discusses providing a visual cue during background recording for audio. We will need to do the same for video recording. Feel free to add a task to bug #1230391 if there is work to integrate this new service with that visual cuing. This should be implemented in time for shippable devices to address the application confinement concern. https://wiki.ubuntu.com/AccountPrivileges#permission-prompt: On the phone, if an app tries to access your ... camera ... or video recording, this should be subject to permission... To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1230366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473873] Re: ucstylehints.cpp problem with Qt 5.5
Qt 5.5 will not land in vivid. ** No longer affects: ubuntu-ui-toolkit (Ubuntu Vivid) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1473873 Title: ucstylehints.cpp problem with Qt 5.5 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: https://launchpadlibrarian.net/211515806/buildlog_ubuntu-wily-amd64 .ubuntu-ui- toolkit_1.3.1549%2B15.10.20150710.1-0ubuntu2~wily1~test1~qt550_BUILDING.txt.gz Looks similar to https://code.launchpad.net/~ubuntu-sdk-team/ubuntu- ui-toolkit/stateSaverUrlType/+merge/262319 https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1473873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1466484] Re: UITK Components install_plugins_qmltypes fails with Qt 5.5
Qt 5.5 will not land in vivid. ** No longer affects: ubuntu-ui-toolkit (Ubuntu Vivid) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1466484 Title: UITK Components install_plugins_qmltypes fails with Qt 5.5 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: With the bug #1461897 fix included, the next failure with Qt 5.5 is install_plugins_qmltypes failing: https://launchpadlibrarian.net/209420305/buildlog_ubuntu-wily-amd64 .ubuntu-ui- toolkit_1.3.1517%2B15.10.20150523-0ubuntu4~wily1~test1~qt550beta%2Bfix1_BUILDING.txt.gz --- make[4]: Entering directory '/build/buildd/ubuntu-ui-toolkit-1.3.1517+15.10.20150523/modules/Ubuntu/Components' ALARM_BACKEND=memory /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump -notrelocatable Ubuntu.Components 0.1 ../../ 2/dev/null /build/buildd/ubuntu-ui-toolkit-1.3.1517+15.10.20150523/debian/tmp//usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/plugins.qmltypes Makefile.ComponentModule:333: recipe for target 'install_plugins_qmltypes' failed make[4]: *** [install_plugins_qmltypes] Error 3 --- More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1466484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452347] Re: please drop build-dependency on g++-4.9
** Changed in: unity-system-compositor Assignee: (unassigned) = Daniel van Vugt (vanvugt) ** Changed in: unity-system-compositor Status: New = Incomplete ** Changed in: unity-system-compositor Status: Incomplete = In Progress ** Changed in: unity-system-compositor Importance: Undecided = Critical ** Branch linked: lp:~vanvugt/unity-system-compositor/fix-1452347 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1452347 Title: please drop build-dependency on g++-4.9 Status in Unity System Compositor: In Progress Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: The unity-system-compositor package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1452347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474763] [NEW] gallery-app fails to display on Qt 5.5
Public bug reported: Shows just white screen, upstart log attached. More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: gallery-app (Ubuntu) Importance: High Status: New ** Tags: qt5.5 ** Attachment added: application-click-com.ubuntu.gallery_gallery_2.9.1.1209.log https://bugs.launchpad.net/bugs/1474763/+attachment/4429275/+files/application-click-com.ubuntu.gallery_gallery_2.9.1.1209.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1474763 Title: gallery-app fails to display on Qt 5.5 Status in gallery-app package in Ubuntu: New Bug description: Shows just white screen, upstart log attached. More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1474763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474695] Re: Video playback broken with Qt 5.5
** Also affects: mediaplayer-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: application-legacy-mediaplayer-app-.log https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1474695/+attachment/4429277/+files/application-legacy-mediaplayer-app-.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1474695 Title: Video playback broken with Qt 5.5 Status in mediaplayer-app package in Ubuntu: New Status in qtvideo-node package in Ubuntu: New Bug description: Video playback is broken with Qt 5.5 (tested on mako). Eg sintel trailer just shows a black screen, and no audio. Pure music playback does work elsewhere. More information at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1474695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471475] [NEW] Add a Folder-wise View Mode
You have been subscribed to a public bug: I'd also be very nice, if you could somehow manage to add a View Mode for the app, that will just show all the folders that the app monitors and allow you to look through your pictures just like in a normal browser (showing only pictures and folders). ** Affects: gallery-app (Ubuntu) Importance: Wishlist Status: New -- Add a Folder-wise View Mode https://bugs.launchpad.net/bugs/1471475 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 592434] Re: ssh -X user@machine hangs when using exit to terminate
still there on 14.04. Is anybody looking into that? I understand its not a huge bug, but it is pretty annoying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/592434 Title: ssh -X user@machine hangs when using exit to terminate Status in D-Bus: Confirmed Status in dbus package in Ubuntu: Triaged Bug description: ssh -X user@server hangs when using exit to terminate Steps to reproduce: user@client:~$ ssh -X user@server user@server:~$ gedit At this point gedit from server will run locally. Closing the program and returning to the terminal you run: user@server:~$ exit logout At this point the terminal hangs on the echo logout, but does not return to the client prompt. The action has been consistent when connecting to a server running opensolaris or ubuntu 8.04. The client is using Ubuntu 10.04 and the server is using 8.04, and using default password authentication. As you will see in the video attached I can confirm the issue when using a clean Ubuntu 10.04 as a client and Ubuntu 8.04 as the server, using default password authentication. Workaround -- -When logging out with exit and it hangs, press Ctrl-C -If you would like to simply use gedit on another computer use the following command: $ dbus-launch gedit Date: Thu Jun 10 17:34:26 2010 To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/592434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473890] Re: UITK API addition in Qt 5.5
I will unassign myself from this, since I only know how to update the components.api and that's not wanted as is. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Timo Jyrinki (timo-jyrinki) = (unassigned) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1473890 Title: UITK API addition in Qt 5.5 Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: There's a change in Qt 5.5 that affects API of UITK too: https://launchpadlibrarian.net/211518910/buildlog_ubuntu-wily-i386 .ubuntu-ui- toolkit_1.3.1549%2B15.10.20150713.1-0ubuntu1_BUILDING.txt.gz --- https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1473890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409332] Re: Mouse cursor freezes, when using e.g. youtube in chromium, and stays that way
** Changed in: xorg (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1409332 Title: Mouse cursor freezes, when using e.g. youtube in chromium, and stays that way Status in xorg package in Ubuntu: New Bug description: I can not make this happen, if I use Firefox, but it happens, if I use Chromium browser and play youtube video. Visible mouse cursor stops moving. Still I can move mouse and use it, but it is hard, when you don't see where the cursor effectively is. This seems to happen only, if I have hardware acceleration enabled in advanced settings. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.04.1.1064 ProcVersionSignature: Ubuntu 3.13.0-43.72-lowlatency 3.13.11.11 Uname: Linux 3.13.0-43-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 10 22:23:29 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (111 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-09-28T10:04:54.426898 --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: [ 373.553548] perf samples too long (2509 2500), lowering kernel.perf_event_max_sample_rate to 5 DRM.card0.VGA.1: edid-base64: AP///wAebW9DLDQEABEPAQNuIht46i7lpFdKnCURUFSla4AxT0VPYU+BgAEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4Sx5TDgAKICAgICAg/ABMMTcxNVMKICAgICAg/AAKICAgICAgICAgICAgAJg= dpms: On modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 640x480 640x480 720x400 enabled: enabled status: connected Desktop-Session: 'ubuntustudio' '/etc/xdg/xdg-ubuntustudio:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share' DetectedPlugins: DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2014-09-21 (180 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. OptiPlex 745 Package: xorg PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-lowlatency root=UUID=d012c1bd-7e56-4035-b321-38d20cb14421 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-46.79-lowlatency 3.13.11-ckt15 Tags: trusty Uname: Linux 3.13.0-46-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-09-28T10:04:54.426899 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1409332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452322] Re: please drop build-dependency on g++-4.9
confirmed, prevents building in the silo 16 with GCC 5. ** Changed in: dbus-cpp (Ubuntu) Importance: Undecided = Critical ** Changed in: dbus-cpp (Ubuntu) Status: New = Confirmed ** Changed in: dbus-cpp (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1452322 Title: please drop build-dependency on g++-4.9 Status in dbus-cpp package in Ubuntu: Confirmed Bug description: The dbus-cpp package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1452322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452337] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: process-cpp (Ubuntu) Importance: Undecided = Critical ** Changed in: process-cpp (Ubuntu) Status: New = Confirmed ** Changed in: process-cpp (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to process-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1452337 Title: please drop build-dependency on g++-4.9 Status in process-cpp package in Ubuntu: Confirmed Bug description: The process-cpp package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/process-cpp/+bug/1452337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474690] Re: Keyboard doesn't work with Qt 5.5
** Description changed: Possibly related to bug #1447190, the keyboard simply does not show when used with Qt 5.5 (no crash file created). Qt 5.5 final is now testable on the phone, more information at https://wiki.ubuntu.com/Touch/QtTesting maliit-server.log contents: Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:55:22: QML CheckBox: Theme.createStyleComponent() is deprecated. Use ThemeSettings instead. WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString, Maliit::HandlerState) libubuntu-keyboard-plugin.so en is not enabled WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:74: TypeError: Cannot read property of null + + Since this affects being able to unlock the screen if passphrase is set, + it's useful to know: gdbus call --session --dest + com.canonical.UnityGreeter --object-path / --method + com.canonical.UnityGreeter.HideGreeter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1474690 Title: Keyboard doesn't work with Qt 5.5 Status in ubuntu-keyboard package in Ubuntu: New Bug description: Possibly related to bug #1447190, the keyboard simply does not show when used with Qt 5.5 (no crash file created). Qt 5.5 final is now testable on the phone, more information at https://wiki.ubuntu.com/Touch/QtTesting maliit-server.log contents: Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:55:22: QML CheckBox: Theme.createStyleComponent() is deprecated. Use ThemeSettings instead. WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString, Maliit::HandlerState) libubuntu-keyboard-plugin.so en is not enabled WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:74: TypeError: Cannot read property of null Since this affects being able to unlock the screen if passphrase is set, it's useful to know: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method com.canonical.UnityGreeter.HideGreeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1474690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450346] Re: Camera black with Qt 5.5
** Attachment added: application-click-com.ubuntu.camera_camera_3.0.0.572.log https://bugs.launchpad.net/ubuntu/+source/qtvideo-node/+bug/1450346/+attachment/4429278/+files/application-click-com.ubuntu.camera_camera_3.0.0.572.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1450346 Title: Camera black with Qt 5.5 Status in camera-app package in Ubuntu: New Status in qtvideo-node package in Ubuntu: New Bug description: The camera app is simply black on Qt 5.5. More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting --- ApportVersion: 2.17.2-0ubuntu1 Architecture: armhf DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-04-28 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20150428-033424) Package: qtvideo-node PackageArchitecture: armhf Tags: third-party-packages vivid Uname: Linux 3.4.0-6-mako armv7l UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1450346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333027] Re: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090 try hdajackretask to change node 0x1a to speaker ** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1333027 Title: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: Incomplete Bug description: I tried to fix the alsa-base.conf, however I am not sure what the default configuration should be.Either way, I do hear the test tone but it doesnt alternate between speakers/channels. It just sounds one constant tone. The same happens when i do a speaker-test, i get pink noise through the same output, even though it reads front-left, front- right, center, lfe it plays sound while displaying those 4, however the sound comes through the lfe from what it sounds like (the sound only plays through one output). If you have a preferred alsa-base.conf or a way for me to overwrite it, let me know and we can proceed. I modified it due to this problem. Since installing Ubuntu I have not had the sound working properly so I have been trying configuration edits (with no success so far). I noticed no subdevices are displayed. I am not sure how the card decides where to send sound to but the interesting thing is that when testing in Pulseaudio I get sound playing when clicking front-left, front-right but nothing from clicking subwoofer. And again, the front-left and front-right all play the tone through the same speaker..theres no difference and apparently my guess is not all of my speakers are being detected as available options because I also only have (1) speaker control in Alsamixer. Surely there must be some way to get 2.1 speakers correctly configured? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: phallix1713 F pulseaudio /dev/snd/controlC0: phallix1713 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 22 16:04:53 2014 InstallationDate: Installed on 2014-06-15 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2014 dmi.bios.vendor: Alienware dmi.bios.version: A07 dmi.board.name: 01W2J2 dmi.board.vendor: Alienware dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A07 dmi.modalias: dmi:bvnAlienware:bvrA07:bd04/23/2014:svnAlienware:pnAlienware18:pvrA07:rvnAlienware:rn01W2J2:rvrA02:cvnAlienware:ct8:cvrA07: dmi.product.name: Alienware 18 dmi.product.version: A07 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-06-22T16:04:27.421233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1333027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471474] Re: Make View Mode on Start-up Configurable
** Project changed: gallery-app = gallery-app (Ubuntu) ** Changed in: gallery-app (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1471474 Title: Make View Mode on Start-up Configurable Status in gallery-app package in Ubuntu: New Bug description: It's not so important, but still, it is somehow annoying, that you would always have to change the view mode after start-up if you just don't like the 'Event' view mode. Could you make it configurable somehow? That'd be nice. (Just put it on the wishlist.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1471474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371977] Re: [Alienware 17, Realtek ALC668, Speaker, Internal] No sound at all
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090 try hdajackretask to change node 0x1a as speaker ** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1371977 Title: [Alienware 17, Realtek ALC668, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: First this was the problem and i did as it was given in some others report and the sound was working but after installing some other softwares it stopped working again ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max2163 F pulseaudio /dev/snd/controlC1: max2163 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 21 01:57:56 2014 InstallationDate: Installed on 2014-08-19 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max2163 F pulseaudio /dev/snd/controlC1: max2163 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Alienware 17, Realtek ALC668, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2014 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd02/25/2014:svnAlienware:pnAlienware17:pvrA09:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA09: dmi.product.name: Alienware 17 dmi.product.version: A09 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-09-20T13:56:34.698572 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447182] Re: u1db-qt FTBFS with Qt 5.5
Weirdly, the same problem seems back again now with Qt 5.5.0 final: https://launchpadlibrarian.net/211685937/buildlog_ubuntu-wily-amd64 .u1db- qt_0.1.5%2B15.04.20150327-0ubuntu2~wily1~test1~qt550%2B1_BUILDING.txt.gz ** Changed in: u1db-qt (Ubuntu) Status: Fix Released = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to u1db-qt in Ubuntu. https://bugs.launchpad.net/bugs/1447182 Title: u1db-qt FTBFS with Qt 5.5 Status in u1db-qt package in Ubuntu: Triaged Bug description: u1db-qt fails to build with Qt 5.5. Build log: https://launchpadlibrarian.net/204005182/buildlog_ubuntu-vivid-amd64 .u1db- qt_0.1.5%2B15.04.20150327-0ubuntu2~vivid1~test1~qt550alpha1_BUILDING.txt.gz -- documentation/CMakeFiles/doc.dir/build.make:60: recipe for target 'documentation/overview.html' failed -- More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u1db-qt/+bug/1447182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474775] [NEW] ubuntu-ui-extras fails running a test on Qt 5.5
Public bug reported: Fails as follows: https://launchpadlibrarian.net/211692813 /buildlog_ubuntu-wily-amd64.ubuntu-ui- extras_0.2%2B15.04.20150311-0ubuntu2~wily1~test1~qt550%2B1_BUILDING.txt.gz --- 3/3 Test #3: tst_PhotoEditorPhotoImageProvider ...***Failed0.06 sec Error: Upper boundary of data for directory Panasonic, entry 0x0061 is out of bounds: Offset = 0x2110, size = 148, exceeds buffer size by 62 Bytes; truncating the entry Error: Offset of directory Panasonic, entry 0x8010 is out of bounds: Offset = 0x21a4; truncating the entry Error: Upper boundary of data for directory Panasonic, entry 0x0061 is out of bounds: Offset = 0x2110, size = 148, exceeds buffer size by 62 Bytes; truncating the entry Error: Offset of directory Panasonic, entry 0x8010 is out of bounds: Offset = 0x21a4; truncating the entry --- More information at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: ubuntu-ui-extras (Ubuntu) Importance: High Status: New ** Tags: qt5.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-extras in Ubuntu. https://bugs.launchpad.net/bugs/1474775 Title: ubuntu-ui-extras fails running a test on Qt 5.5 Status in ubuntu-ui-extras package in Ubuntu: New Bug description: Fails as follows: https://launchpadlibrarian.net/211692813 /buildlog_ubuntu-wily-amd64.ubuntu-ui- extras_0.2%2B15.04.20150311-0ubuntu2~wily1~test1~qt550%2B1_BUILDING.txt.gz --- 3/3 Test #3: tst_PhotoEditorPhotoImageProvider ...***Failed0.06 sec Error: Upper boundary of data for directory Panasonic, entry 0x0061 is out of bounds: Offset = 0x2110, size = 148, exceeds buffer size by 62 Bytes; truncating the entry Error: Offset of directory Panasonic, entry 0x8010 is out of bounds: Offset = 0x21a4; truncating the entry Error: Upper boundary of data for directory Panasonic, entry 0x0061 is out of bounds: Offset = 0x2110, size = 148, exceeds buffer size by 62 Bytes; truncating the entry Error: Offset of directory Panasonic, entry 0x8010 is out of bounds: Offset = 0x21a4; truncating the entry --- More information at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-extras/+bug/1474775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474313] Re: Needs to b-d on libqt5xcbqpa5 to be able to run tests under xvfb
** Description changed: Qt 5.5 packaging currently introduces a new package libqt5xcbqpa5, which is required to be installed during build time for being able to run tests under X(vfb). + + The change cannot be landed other than together with Qt 5.5, so there + are no actions except for preparing the branch. Another possibility + would probably be to switch to Mir's mirvfb. ** Description changed: Qt 5.5 packaging currently introduces a new package libqt5xcbqpa5, which is required to be installed during build time for being able to run tests under X(vfb). - The change cannot be landed other than together with Qt 5.5, so there - are no actions except for preparing the branch. Another possibility - would probably be to switch to Mir's mirvfb. + The change cannot be landed other than together with Qt 5.5, or after it + for packages that do not require a rebuild. So, there are no actions + except for preparing the branch. Another possibility would probably be + to switch to Mir's mirvfb. ** Changed in: webbrowser-app (Ubuntu) Importance: Undecided = Low ** Also affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: signon-ui (Ubuntu) Importance: Undecided Status: New ** Also affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided = Low ** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided = Low ** Changed in: signon-ui (Ubuntu) Importance: Undecided = Low ** Changed in: messaging-app (Ubuntu) Importance: Undecided = Low ** Changed in: camera-app (Ubuntu) Importance: Undecided = Low ** Description changed: Qt 5.5 packaging currently introduces a new package libqt5xcbqpa5, which is required to be installed during build time for being able to run tests under X(vfb). The change cannot be landed other than together with Qt 5.5, or after it for packages that do not require a rebuild. So, there are no actions except for preparing the branch. Another possibility would probably be to switch to Mir's mirvfb. + + Packages that need to be fixed together with Qt 5.5: webbrowser-app + + Packages that can be fixed afterwards (but it'd be useful to run the + tests before to see if they actually pass): camera-app messaging-app + signon-ui ubuntu-system-settings ubuntu-system-settings-online-accounts + + Information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting ** Description changed: Qt 5.5 packaging currently introduces a new package libqt5xcbqpa5, which is required to be installed during build time for being able to run tests under X(vfb). The change cannot be landed other than together with Qt 5.5, or after it for packages that do not require a rebuild. So, there are no actions except for preparing the branch. Another possibility would probably be to switch to Mir's mirvfb. Packages that need to be fixed together with Qt 5.5: webbrowser-app Packages that can be fixed afterwards (but it'd be useful to run the tests before to see if they actually pass): camera-app messaging-app signon-ui ubuntu-system-settings ubuntu-system-settings-online-accounts Information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting + + Test rebuilds against landing-012 have been made at + https://launchpad.net/~canonical- + qt5-edgers/+archive/ubuntu/qt5-beta2/+packages?field.name_filter=field.status_filter=publishedfield.series_filter=wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1474313 Title: Needs to b-d on libqt5xcbqpa5 to be able to run tests under xvfb Status in camera-app package in Ubuntu: New Status in messaging-app package in Ubuntu: New Status in signon-ui package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Qt 5.5 packaging currently introduces a new package libqt5xcbqpa5, which is required to be installed during build time for being able to run tests under X(vfb). The change cannot be landed other than together with Qt 5.5, or after it for packages that do not require a rebuild. So, there are no actions except for preparing the branch. Another possibility would probably be to switch to Mir's mirvfb. Packages that need to be fixed together with Qt 5.5: webbrowser-app Packages that can be fixed afterwards (but it'd be useful to run the tests before to see if they actually pass): camera-app messaging-app signon-ui
[Touch-packages] [Bug 1474720] Re: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed:
Bisected the issue. It was introduced in: revno: 2742 [merge] author: Cemil Azizoglu cemil.azizo...@canonical.com committer: Tarmac branch nick: development-branch timestamp: Tue 2015-07-14 10:05:04 + message: Use command line options during platform probe. Approved by PS Jenkins bot, Chris Halse Rogers, Alexandros Frantzis. ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New = Invalid ** Changed in: mir Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1474720 Title: [regression] Mir servers crash on start-up: ERROR: Dynamic exception type: St13runtime_error - std::exception::what: Link failed: Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: All Mir demo servers are now crashing on start-up, with very little explanation: ERROR: Dynamic exception type: St13runtime_error std::exception::what: Link failed: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1474720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461897] Re: UITK FTBFS with Qt 5.5 'cdata-QQmlContextData::url' does not have class type
Qt 5.5 will not land in vivid.
** No longer affects: ubuntu-ui-toolkit (Ubuntu Vivid)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1461897
Title:
UITK FTBFS with Qt 5.5 'cdata-QQmlContextData::url' does not have
class type
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Bug description:
This build failure is new with Qt 5.5 beta (UITK built with Qt 5.5
alpha). Build logs:
https://launchpadlibrarian.net/208258644/buildlog_ubuntu-wily-amd64.ubuntu-ui-toolkit_1.3.1517%2B15.10.20150523-0ubuntu2~vivid1~test1~qt550beta1_BUILDING.txt.gz
https://launchpadlibrarian.net/208259100/buildlog_ubuntu-wily-armhf.ubuntu-ui-toolkit_1.3.1517%2B15.10.20150523-0ubuntu2~vivid1~test1~qt550beta1_BUILDING.txt.gz
---cut---
ucstatesaver.cpp: In member function 'QString
UCStateSaverAttachedPrivate::absoluteId(const QString)':
ucstatesaver.cpp:85:20: error: 'cdata-QQmlContextData::url' does not have
class type
QString path = cdata-url.path().replace('/', '_') + ':'
^
---cut---
More information about Qt 5.5 at
https://wiki.ubuntu.com/Touch/QtTesting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1461897/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471474] [NEW] Make View Mode on Start-up Configurable
You have been subscribed to a public bug: It's not so important, but still, it is somehow annoying, that you would always have to change the view mode after start-up if you just don't like the 'Event' view mode. Could you make it configurable somehow? That'd be nice. (Just put it on the wishlist.) ** Affects: gallery-app (Ubuntu) Importance: Wishlist Status: New -- Make View Mode on Start-up Configurable https://bugs.launchpad.net/bugs/1471474 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471475] Re: Add a Folder-wise View Mode
** Project changed: gallery-app = gallery-app (Ubuntu) ** Changed in: gallery-app (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1471475 Title: Add a Folder-wise View Mode Status in gallery-app package in Ubuntu: New Bug description: I'd also be very nice, if you could somehow manage to add a View Mode for the app, that will just show all the folders that the app monitors and allow you to look through your pictures just like in a normal browser (showing only pictures and folders). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1471475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1469803] Re: Connecting to some sites via glib-networking is broken due to removed certificates
This bug was fixed in the package ca-certificates - 20150426ubuntu1 --- ca-certificates (20150426ubuntu1) wily; urgency=medium * mozilla-1024/*, Makefile: Since version 20140927 of the ca-certificates package, containing the 2.1 version of the nss database, CA certificates with 1024-bit RSA keys have been removed. Unfortunately, older versions of libraries such as OpenSSL, GnuTLS and glib-networking are unable to automatically find alternative trust chains to continue connecting to certain sites. This update restores the certificates until all libraries have been updated to properly handle alternative trust chains. See mozilla-1024/certdata.txt for a list of the exact certificates that were added back. (LP: #1469803) -- Marc Deslauriers marc.deslauri...@ubuntu.com Mon, 13 Jul 2015 11:10:03 -0400 ** Changed in: ca-certificates (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1469803 Title: Connecting to some sites via glib-networking is broken due to removed certificates Status in ca-certificates package in Ubuntu: Fix Released Bug description: See https://bugzilla.redhat.com/show_bug.cgi?id=1166614 and https://rt.openssl.org/Ticket/Display.html?id=3621user=guestpass=guest - this situation still exists in the wild (e.g. Facebook's CDN), but our ca-certificates package has dropped these certs, as of 20150426. For example run the attached script on wily or try to use Facebook in epiphany. Fedora have kept some of these certificates and called them legacy - I suggest that we could do the same, at least until glib-networking is fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1469803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471213] Re: [SKL] noise in unity dash, torcs
This bug was fixed in the package mesa - 10.5.9-2ubuntu1 --- mesa (10.5.9-2ubuntu1) wily; urgency=medium * Merge from Debian unstable. -- Timo Aaltonen tjaal...@debian.org Fri, 10 Jul 2015 14:02:38 +0300 ** Changed in: mesa (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1471213 Title: [SKL] noise in unity dash, torcs Status in mesa package in Ubuntu: Fix Released Status in mesa-lts-vivid package in Ubuntu: Invalid Status in mesa-lts-vivid source package in Trusty: New Status in mesa source package in Vivid: New Bug description: 10.5.x suffers from noise seen in transparent unity dialogs, also visible in torcs for instance Need to backport four patches from 10.6.0: commit c02c4b567ce001f6605c46e71e089692b837bf26 Author: Neil Roberts n...@linux.intel.com Date: Wed Mar 4 14:13:40 2015 + i965: Store the GPU revision number in brw_context commit bc4b18d2977a94a6fb513bf5955236a0e92298ca Author: Neil Roberts n...@linux.intel.com Date: Thu Mar 19 18:18:49 2015 + i965: Refactor SIMD16-to-2xSIMD8 checks. commit 484f9f4fcd53fcaa768e63934a5f74346bfb46a9 Author: Dave Airlie airl...@redhat.com Date: Mon Mar 23 09:54:52 2015 +1000 i965: define I915_PARAM_REVISION commit 706b916960c898cfc24110f14fa4def84caaba93 Author: Kenneth Graunke kenn...@whitecape.org Date: Wed Mar 4 12:53:45 2015 -0800 i965/skl: Break down SIMD16 3-source instructions when required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1471213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5
Meizu MX4 Operator : Free Sens = ok Receive = faile -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1439101 Title: impossible receive MMS any operator on bq aquaris E4.5 Status in Canonical System Image: Confirmed Status in Ubuntu Mobile Phone: Incomplete Status in messaging-app package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition For information, my operator is Free even if it seems it doesn't matter. In the same time, let me tell you than I had detect than MMS didn't sent when WIFI is ON. I've read some other people who send the same information so it's seems to be a real bug. Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if ON, and in all of case we don't receive MMS :-(( Thank's to you for fix it faster. Sorry for my approximativ english. Fabien To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1469611] Re: QQuickPixmapReader::asyncResponseFinished segfaults if a QQuickAsyncImageProvider returns an error response
qtdeclarative-opensource-src (5.4.1-1ubuntu8) vivid; urgency=medium
* debian/patches/Add-QQuickAsyncImageProvider.patch:
- Fix segfault by importing https://codereview.qt-project.org/#/c/115522/
and https://codereview.qt-project.org/#/c/120638/
(LP: #1469611)
-- Timo Jyrinki timo-jyri...@ubuntu.com Tue, 07 Jul 2015 11:50:57
+
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1469611
Title:
QQuickPixmapReader::asyncResponseFinished segfaults if a
QQuickAsyncImageProvider returns an error response
Status in qtdeclarative-opensource-src package in Ubuntu:
Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
Fix Released
Bug description:
While working on the new thumbnailer, we've been using the new
QQuickAsyncImageProvider API. The API allows us to report errors by
overriding the errorString() method on QQuickImageResponse to return a
non-empty string. However, if I do so the application crashes.
Loading up the symbols to get a stack trace shows this to be a bug in
the logic of QQuickPixmapReader::asyncResponseFinished:
QQuickTextureFactory *t = 0;
QQuickPixmapReply::ReadError error = QQuickPixmapReply::NoError;
QString errorString;
QSize readSize;
if (!response-errorString().isEmpty()) {
error = QQuickPixmapReply::Loading;
errorString = response-errorString();
} else {
t = response-textureFactory();
}
mutex.lock();
if (!cancelled.contains(job))
job-postReply(error, errorString, t-textureSize(), t);
mutex.unlock();
If errorString() is not empty, then t will still be NULL. It is then
dereferenced to call t-textureSize() resulting in a segfault.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libqt5quick5 5.4.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 29 14:53:49 2015
InstallationDate: Installed on 2013-10-29 (607 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64
(20131016.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: Upgraded to wily on 2015-06-13 (15 days ago)
Test case (on desktop):
- bzr branch lp:~jamesh/thumbnailer/no-fallback-albumart
- sudo apt-get build-dep thumbnailer
- sudo apt install libleveldb-dev cmake-extras libapparmor-dev
libboost-filesystem-dev libboost-regex-dev libqtdbustest1-dev libunity-api-dev
python3-tornado qml-module-qttest xvfb
- cd no-fallback-albumart
- cmake .
- make
- ctest -R qml --verbose
- check if crash (Segmentation fault (core dumped)) or no crash (don't mind
tests pass/fail)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1469611/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452346] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided = Critical ** Changed in: unity-scopes-api (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1452346 Title: please drop build-dependency on g++-4.9 Status in unity-scopes-api package in Ubuntu: Fix Committed Bug description: The unity-scopes-api package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1452346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452344] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: unity-scope-mediascanner (Ubuntu) Importance: Undecided = Critical ** Changed in: unity-scope-mediascanner (Ubuntu) Status: New = Confirmed ** Changed in: unity-scope-mediascanner (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1452344 Title: please drop build-dependency on g++-4.9 Status in unity-scope-mediascanner package in Ubuntu: Confirmed Bug description: The unity-scope-mediascanner package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1452344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452347] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: unity-system-compositor (Ubuntu) Importance: Undecided = Critical ** Changed in: unity-system-compositor (Ubuntu) Status: New = Confirmed ** Changed in: unity-system-compositor (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1452347 Title: please drop build-dependency on g++-4.9 Status in Unity System Compositor: New Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: The unity-system-compositor package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1452347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452348] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: unity8 (Ubuntu) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu) Status: New = Confirmed ** Changed in: unity8 (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1452348 Title: please drop build-dependency on g++-4.9 Status in unity8 package in Ubuntu: Confirmed Bug description: The unity8 package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1452348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452342] Re: please drop build-dependency on g++-4.9
raising importance, prevents build using GCC 5, which will become the default at the end of July ** Changed in: unity-api (Ubuntu) Importance: Undecided = Critical ** Changed in: unity-api (Ubuntu) Status: New = Confirmed ** Changed in: unity-api (Ubuntu) Milestone: None = ubuntu-15.07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-api in Ubuntu. https://bugs.launchpad.net/bugs/1452342 Title: please drop build-dependency on g++-4.9 Status in unity-api package in Ubuntu: Confirmed Bug description: The unity-api package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-api/+bug/1452342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1230366] Re: Please provide Ubuntu camera service that integrates with trust-store
** Changed in: qtubuntu-camera (Ubuntu RTM) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1230366 Title: Please provide Ubuntu camera service that integrates with trust-store Status in Canonical System Image: Triaged Status in qtubuntu-camera package in Ubuntu: Triaged Status in qtubuntu-camera package in Ubuntu RTM: Invalid Bug description: Currently Ubuntu Touch is using the android camera-service and that is the plan for 13.10. Going forward in 14.04, the android camera-service will no longer be used and camera access is going to move to the Ubuntu side. There was discussion of either using HAL directly (direct access to devices) or using a camera-service type thing in Ubuntu. Using devices directly causes at least a few problems: * can't prevent more than one user from accessing the device at a time * enumerating camera devices for apparmor policy is extra maintenance for porters * can't provide a contextual runtime prompt for access (like we (will) do with online accounts, location, microphone). This is particularly important for application confinement. Instead of direct hardware access, an out of process helper (in relation to the app) can be used to address all of these problems, similar to what pulseaudio does for audio. This service can ensure only one user can access the device at a time and since the service accesses the the device files on the app's behalf, we don't need to enumerate devices in /dev in policy. Furthermore, when an app accesses the service (ideally over DBus), the service can contact trust-store, the trust-store will prompt the user (Foo wants to access the camera. Is this ok? Yes|No), then optionally cache the result and return the result to the service. In this manner the user is given a contextual prompt at the time of access by the app. By using caching this decision can be remembered the next time. If caching is used, there should be a method to change the decision in system settings. If direct hardware access is needed for performance reasons, it is possible to use fd delegation in AppArmor and have the service open the device and pass the fd to the app without having to enumerate the /dev devices. Please talk to jjohansen if pursuing this option. Lastly, bug #1230391 discusses providing a visual cue during background recording for audio. We will need to do the same for video recording. Feel free to add a task to bug #1230391 if there is work to integrate this new service with that visual cuing. This should be implemented in time for shippable devices to address the application confinement concern. https://wiki.ubuntu.com/AccountPrivileges#permission-prompt: On the phone, if an app tries to access your ... camera ... or video recording, this should be subject to permission... To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1230366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437192] Re: FTBFS with Qt 5.5: cannot find -linput
** Changed in: appmenu-qt5 (Ubuntu) Importance: Undecided = High ** Branch linked: lp:~timo-jyrinki/appmenu-qt5/build_dep_libinput- dev_qt55 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1437192 Title: FTBFS with Qt 5.5: cannot find -linput Status in appmenu-qt5 package in Ubuntu: New Status in qtubuntu package in Ubuntu: Fix Released Bug description: There seems to be some sort of new dependency, even though none were added in Qt 5.5's own build dependencies: --- g++ -std=c++11 -Wl,-no-undefined -Wl,-Bsymbolic-functions -Wl,-z,relro -shared -o libqpa-ubuntumirclient.so backingstore.o clipboard.o glcontext.o input.o integration.o nativeinterface.o platformservices.o plugin.o screen.o theme.o window.o moc_clipboard.o moc_input.o moc_plugin.o moc_screen.o moc_window.o -lmirclient -lmircommon -lubuntu_application_api -lQt5PlatformSupport -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -linput -lxkbcommon -ludev -lmtdev -lEGL -lQt5Gui -lQt5Sensors -lQt5DBus -lQt5Core -lGLESv2 -lpthread /usr/bin/ld: cannot find -linput --- That is, qtubuntu and appmenu-qt5 should apparently have a build dependency on 'libinput-dev': https://launchpad.net/ubuntu/+source/libinput More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting appmenu-qt5: https://launchpadlibrarian.net/202748418/buildlog_ubuntu-vivid-amd64.appmenu-qt5_0.3.0%2B15.04.20150121-0ubuntu4~vivid1~test1~qt550alpha1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1437192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448492] Re: Can't open SMS from my operator
*** This bug is a duplicate of bug 1437912 *** https://bugs.launchpad.net/bugs/1437912 ** This bug has been marked a duplicate of bug 1437912 SMS not stored -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1448492 Title: Can't open SMS from my operator Status in messaging-app package in Ubuntu: New Bug description: When I receive a SMS from my mobile operator, that has SMS sender number the text Orange, the messaging app does show the preview but then it doesn't show me the full message. In the attached screenshot you can see how I see the SMS existence from the homepage of the app and then opening the conversation I can't see any message. Thanks, Ilario ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: messaging-app 0.1+15.04.20150218~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Sat Apr 25 17:47:57 2015 InstallationDate: Installed on 2015-04-10 (14 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150410-232623) SourcePackage: messaging-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1448492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437912] Re: SMS not stored
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: messaging-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1437912 Title: SMS not stored Status in messaging-app package in Ubuntu: Confirmed Bug description: Hi, I tried to receive a SMS with code number. The SMS is send by a robot and I supposed it's a SMS class 0. I got a notification and a new entry in message list. I can see the beginning of the SMS. When I click on the sender, it displays nothing and the notification in message list (1 green) stay. Edit : And the SMS is not readable entirely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1437912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450346] Re: Camera black with Qt 5.5
Qt 5.5 final is now testable on the phone and the bug persists. ** Changed in: qtvideo-node (Ubuntu) Importance: Undecided = Critical ** Changed in: camera-app (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1450346 Title: Camera black with Qt 5.5 Status in camera-app package in Ubuntu: New Status in qtvideo-node package in Ubuntu: New Bug description: The camera app is simply black on Qt 5.5. More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting --- ApportVersion: 2.17.2-0ubuntu1 Architecture: armhf DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-04-28 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20150428-033424) Package: qtvideo-node PackageArchitecture: armhf Tags: third-party-packages vivid Uname: Linux 3.4.0-6-mako armv7l UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1450346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373696] Re: Android overlay mode ping-pongs constantly with touchspots or software cursor enabled, causing stuttering and lag
Hmm, no. The bug is still happening in proving server :P -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1373696 Title: Android overlay mode ping-pongs constantly with touchspots or software cursor enabled, causing stuttering and lag Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: Bypass/overlay mode ping-pongs constantly during touches with touchspots enabled, or when using a mouse (software cursor on Android). This visibly means the screen is stuttering and jerky. This is a lesser form of bug 1373689, which has a workaround about to land... $ bin/mir_demo_server_minimal --enable-touchspots --compositor-report=log # (and also start a fullscreen client from elsewhere) [1411611407.207459] (II) compositor: Started [1411611407.230898] (II) compositor: Added display 0x1123d48: 768x1280 +0+0 [1411611407.236148] (II) compositor: Display 0x1123d48 bypass OFF [1411611410.060412] (II) compositor: Display 0x1123d48 bypass ON [1411611410.996746] (II) compositor: Display 0x1123d48 averaged 56.652 FPS, 11.493 ms/frame, latency 0.741 ms, 57 frames over 1.006 sec, 98% bypassed [1411611411.998852] (II) compositor: Display 0x1123d48 averaged 59.875 FPS, 10.765 ms/frame, latency 0.305 ms, 60 frames over 1.002 sec, 100% bypassed [1411611412.584721] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.599981] (II) compositor: Display 0x1123d48 bypass ON [1411611412.677534] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.683699] (II) compositor: Display 0x1123d48 bypass ON [1411611412.771628] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.783500] (II) compositor: Display 0x1123d48 bypass ON [1411611412.874756] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.883577] (II) compositor: Display 0x1123d48 bypass ON [1411611412.972513] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.983714] (II) compositor: Display 0x1123d48 bypass ON To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1373696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474690] [NEW] Keyboard doesn't work with Qt 5.5
Public bug reported: Possibly related to bug #1447190, the keyboard simply does not show when used with Qt 5.5 (no crash file created). Qt 5.5 final is now testable on the phone, more information at https://wiki.ubuntu.com/Touch/QtTesting maliit-server.log contents: Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:55:22: QML CheckBox: Theme.createStyleComponent() is deprecated. Use ThemeSettings instead. WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString, Maliit::HandlerState) libubuntu-keyboard-plugin.so en is not enabled WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:74: TypeError: Cannot read property of null ** Affects: ubuntu-keyboard (Ubuntu) Importance: Critical Status: New ** Tags: qt5.5 ** Description changed: Possibly related to bug #1447190, the keyboard simply does not show when - used with Qt 5.5. + used with Qt 5.5 (no crash file created). Qt 5.5 final is now testable on the phone, more information at https://wiki.ubuntu.com/Touch/QtTesting maliit-server.log contents: Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:55:22: QML CheckBox: Theme.createStyleComponent() is deprecated. Use ThemeSettings instead. WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString, Maliit::HandlerState) libubuntu-keyboard-plugin.so en is not enabled WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:74: TypeError: Cannot read property of null -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1474690 Title: Keyboard doesn't work with Qt 5.5 Status in ubuntu-keyboard package in Ubuntu: New Bug description: Possibly related to bug #1447190, the keyboard simply does not show when used with Qt 5.5 (no crash file created). Qt 5.5 final is now testable on the phone, more information at https://wiki.ubuntu.com/Touch/QtTesting maliit-server.log contents: Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:55:22: QML CheckBox: Theme.createStyleComponent() is deprecated. Use ThemeSettings instead. WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString, Maliit::HandlerState) libubuntu-keyboard-plugin.so en is not enabled WARNING: file:///usr/share/maliit/plugins/com/ubuntu/keys/LanguageMenu.qml:74: TypeError: Cannot read property of null To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1474690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474684] Re: caffeine-plus crased with xlib.eror.DisplayConnectionError in_init_():Can't connect to display:0:b'No protocol specified\n'
*** This bug is a duplicate of bug 1343770 *** https://bugs.launchpad.net/bugs/1343770 ** This bug has been marked a duplicate of bug 1343770 caffeine don't work on Ubuntu 14.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1474684 Title: caffeine-plus crased with xlib.eror.DisplayConnectionError in_init_():Can't connect to display:0:b'No protocol specified\n' Status in indicator-bluetooth package in Ubuntu: New Bug description: It does not start caffeine-plus. Attached start the output of the command in the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1474684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474695] [NEW] Video playback broken with Qt 5.5
Public bug reported: Video playback is broken with Qt 5.5 (tested on mako). Eg sintel trailer just shows a black screen, and no audio. Pure music playback does work elsewhere. More information at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: qtvideo-node (Ubuntu) Importance: Critical Status: New ** Tags: qt5.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtvideo-node in Ubuntu. https://bugs.launchpad.net/bugs/1474695 Title: Video playback broken with Qt 5.5 Status in qtvideo-node package in Ubuntu: New Bug description: Video playback is broken with Qt 5.5 (tested on mako). Eg sintel trailer just shows a black screen, and no audio. Pure music playback does work elsewhere. More information at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtvideo-node/+bug/1474695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460149] Re: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7.
Comment #30 is also being resolved... Work in progress in the attached egl-pixel-format branch. ** Branch linked: lp:~vanvugt/mir/egl-pixel-format -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1460149 Title: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7. Status in Mir: In Progress Status in libsdl2 package in Ubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: https://github.com/pseuudonym404/neverball-touch/issues/2 Install neverball or neverputt from the click store:- https://uappexplorer.com/app/neverputt.lb https://uappexplorer.com/app/neverball.lb Note they work fine on krillin and arale, however there's corruption making the games unusable on Nexus 4 and Nexus 7. Simpler test cases are provided at the above linked github issue. Attaching them to this bug for persistence. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1460149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474684] [NEW] caffeine-plus crased with xlib.eror.DisplayConnectionError in_init_():Can't connect to display:0:b'No protocol specified\n'
Public bug reported: It does not start caffeine-plus. Attached start the output of the command in the terminal ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Attachment added: caffeine-plus https://bugs.launchpad.net/bugs/1474684/+attachment/4429170/+files/caffeine-plus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1474684 Title: caffeine-plus crased with xlib.eror.DisplayConnectionError in_init_():Can't connect to display:0:b'No protocol specified\n' Status in indicator-bluetooth package in Ubuntu: New Bug description: It does not start caffeine-plus. Attached start the output of the command in the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1474684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470777] Re: Favorites Tab - Frequently called contacts overlay 'create a new contact...'
** Changed in: address-book-app (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1470777 Title: Favorites Tab - Frequently called contacts overlay 'create a new contact...' Status in address-book-app package in Ubuntu: Triaged Bug description: If no favorite contacts are selected the frequently called contacts overlay the 'create a new contact by swiping up form the bottom of the sceen.' text. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1470777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474962] Re: Amount of SMS's used to send a message is not shown
The 253 in the mockup would be the number of characters the user typed. The 306 would be the character limit for the amount of SMS's already started (which is 160 for 1 message in the GSM 7-bit alphabet, and 153 per message in Concatenated SMS using the GSM 7-bit alphabet). ** Attachment added: Mockup for indicator of amount of SMS's https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1474962/+attachment/4429555/+files/messaging-mockup.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1474962 Title: Amount of SMS's used to send a message is not shown Status in messaging-app package in Ubuntu: New Bug description: For people who don't have an unlimited amount of SMS's or who pay per SMS, it is useful to know if they are about to send a message that needs more than one SMS, using Concatenated SMS. I would propose to show this information above the Send button, as in the attached mockup. As in the mockup, an info button could be provided. It would open an information screen informing the user that the message has to be sent using multiple SMS's, and that they probably will be charged multiple messages by the provider. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1474962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474962] [NEW] Amount of SMS's used to send a message is not shown
Public bug reported: For people who don't have an unlimited amount of SMS's or who pay per SMS, it is useful to know if they are about to send a message that needs more than one SMS, using Concatenated SMS. I would propose to show this information above the Send button, as in the attached mockup. As in the mockup, an info button could be provided. It would open an information screen informing the user that the message has to be sent using multiple SMS's, and that they probably will be charged multiple messages by the provider. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: No indicator is shown to warn me I am about to send 2 SMS's https://bugs.launchpad.net/bugs/1474962/+attachment/4429553/+files/messaging-mockup.png ** Attachment removed: Mockup of indicator for multiple SMS's https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1474962/+attachment/4429553/+files/messaging-mockup.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1474962 Title: Amount of SMS's used to send a message is not shown Status in messaging-app package in Ubuntu: New Bug description: For people who don't have an unlimited amount of SMS's or who pay per SMS, it is useful to know if they are about to send a message that needs more than one SMS, using Concatenated SMS. I would propose to show this information above the Send button, as in the attached mockup. As in the mockup, an info button could be provided. It would open an information screen informing the user that the message has to be sent using multiple SMS's, and that they probably will be charged multiple messages by the provider. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1474962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267680] Re: package gdb-arm-none-eabi (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218
I've attached a debdiff with the first patch mentioned above, applied to the package in 14.04. I've built this locally in my trusty vm (amd64) and I no longer get a conflict when attempting to install the package. Not done any testing beyond this. Two questions/concerns for the review: 1. The version number. I checked out the source code for 7.6.50.20131218-0ubuntu1+1, but from the binary produced I ended up building 7.7.1-0ubuntu5~14.04.2+1ubuntu0.1. I haven't fully understood how the version number is constructed, but the prefix matches the gdb version number so I believe it is taken from there somehow. The version number does indicated a much larger jump than I had intended, so I guess this has rebuilt with the latest gdb sources or something. I don't know whether this is ok for an SRU. 2. The other patch. As mentioned above, http://anonscm.debian.org/cgit/collab-maint/gdb-arm-none-eabi.git/log/ also contains another patch related to manpages. I have not included it yet (mostly because I don't fully understand its consequences). Someone should take a look at Workaround for upstream manpages stripped and decide whether that needs to be included as well. ** Patch added: patch.debdiff https://bugs.launchpad.net/ubuntu/+source/gdb-arm-none-eabi/+bug/1267680/+attachment/4429557/+files/patch.debdiff ** Tags added: patch ** Description changed: Was makin sure every thing worked and install properly for ya peeps from Synaptic Package Manager and found a few errors in the process got 2 uploaded along with this report also uploaded info to the error tracker which is named: 077cac62-1be5-11e3-88e6-e4115b0f8a4a which is what i also got while installing hope this helps ya =) peace + + + SRU + + [Impact] + Currently it is not possible to install this package alongside gdb. See also comments #8 and #9. + + [Test case] + Attempt to install `gdb-arm-none-eabi` where `gdb` is already installed. + + [Regression potential] + The patch used is one available in a newer version of the package. + There is some confusion regarding the version number and how much changes has actually gone into this rebuild, see comment #9. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gdb-arm-none-eabi (not installed) Uname: Linux 3.13.0-999-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 Date: Thu Jan 9 21:39:21 2014 DuplicateSignature: package:gdb-arm-none-eabi:(not installed):trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1 InstallationDate: Installed on 2013-12-10 (30 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131209) SourcePackage: gdb-arm-none-eabi Title: package gdb-arm-none-eabi (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1267680 Title: package gdb-arm-none-eabi (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1 Status in gdb package in Ubuntu: Confirmed Status in gdb-arm-none-eabi package in Ubuntu: Confirmed Bug description: Was makin sure every thing worked and install properly for ya peeps from Synaptic Package Manager and found a few errors in the process got 2 uploaded along with this report also uploaded info to the error tracker which is named: 077cac62-1be5-11e3-88e6-e4115b0f8a4a which is what i also got while installing hope this helps ya =) peace SRU [Impact] Currently it is not possible to install this package alongside gdb. See also comments #8 and #9. [Test case] Attempt to install `gdb-arm-none-eabi` where `gdb` is already installed. [Regression potential] The patch used is one available in a newer version of the package. There is some confusion regarding the version number and how much changes has actually gone into this rebuild, see comment #9. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gdb-arm-none-eabi (not installed) Uname: Linux 3.13.0-999-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 Date: Thu Jan 9 21:39:21 2014 DuplicateSignature: package:gdb-arm-none-eabi:(not installed):trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1
[Touch-packages] [Bug 1461593] Re: No data connection switching from 2G only to 3G
** Branch linked: lp:~phablet-team/network-manager/lp1461593-wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1461593 Title: No data connection switching from 2G only to 3G Status in Canonical System Image: Fix Released Status in network-manager package in Ubuntu: In Progress Status in network-manager package in Ubuntu RTM: Fix Released Bug description: Test case. - Open System Settings. - Go to Cellular. - Switch from 3G to 2G, check that indicator network shows 2G only connection. - Switch from 2G only to 3G. Expected result. - Indicator network shows 3G connection, and user can use data connection. Actual result. - Data connection is lost. Tested in single SIM and dual SIM mode, with two different SIM cards from different operators. current build number: 23 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452327] Re: please drop build-dependency on g++-4.9
** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) ** Changed in: indicator-network (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1452327 Title: please drop build-dependency on g++-4.9 Status in indicator-network package in Ubuntu: In Progress Bug description: The indicator-network package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1452327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452327] Re: please drop build-dependency on g++-4.9
** Branch linked: lp:~charlesk/indicator-network/lp-1452327-drop-g++-4.9 -build-dep -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1452327 Title: please drop build-dependency on g++-4.9 Status in indicator-network package in Ubuntu: In Progress Bug description: The indicator-network package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1452327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452319] Re: please drop build-dependency on g++-4.9
** Branch linked: lp:~charlesk/indicator- datetime/lp-1452319-drop-g++-4.9-build-dep -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1452319 Title: please drop build-dependency on g++-4.9 Status in indicator-datetime package in Ubuntu: In Progress Bug description: The indicator-datetime package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1452319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444883] Re: Emergency numbers other than 112 and 911 (and 999 for the UK) are not available in emergency mode
** Branch linked: lp:~tiagosh/telephony-service/use-libphonenumber ** Branch linked: lp:~tiagosh/dialer-app/emergency-calls-libphonenumber ** Branch linked: lp:~tiagosh/telepathy-ofono/use-libphonenumber -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1444883 Title: Emergency numbers other than 112 and 911 (and 999 for the UK) are not available in emergency mode Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: New Status in ofono package in Ubuntu: Invalid Status in telephony-service package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu RTM: Confirmed Bug description: arale device, r177, ubuntu-touch/vivid-proposed Steps 1. Emergency mode (e.g. Lock phone with a passcode, slide left, tap on Emergency Call) 2. try input 911, 112 == OK 2. try input 110, 119 == Dial button is inactive after number is input Expect Allow these numbers in emergency mode To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474984] [NEW] installing multipath-tools 0.5.0 on trusty leaves the system unable to boot
Public bug reported: In order to test the fix for bug #1468897 on trusty on a POWER8 system (PowerNV mode), Mike installed the multipath-tools package from wily. This results in a system that fails to boot, dropping to the initramfs. The reproducible failure is: Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Loading multipath modules ... Success: loaded module dm-multipath. Failure: failed to load module dm-emc. done. Begin: Discovering multipaths ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/mpath0-part2 does not exist. Dropping to a shell! [ 220.162333] hidraw: raw HID events driver (C) Jiri Kosina [ 220.164232] usbcore: registered new interface driver usbhid [ 220.164277] usbhid: USB HID core driver BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Debugging info: (initramfs) cat /proc/cmdline root=/dev/mapper/mpath0-part2 ro (initramfs) /sbin/multipath -v 3; echo $? Jul 15 18:21:52 | libdevmapper version 1.02.99 (2015-06-20) Jul 15 18:21:52 | DM multipath kernel driver v1.7.0 Jul 15 18:21:52 | loading /lib/multipath/libcheckdirectio.so checker Jul 15 18:21:52 | loading /lib/multipath/libprioconst.so prioritizer Jul 15 18:21:52 | sr0: blacklisted, udev property missing Jul 15 18:21:52 | sda: udev property SCSI_IDENT_LUN_T10 whitelisted Jul 15 18:21:52 | sda: not found in pathvec Jul 15 18:21:52 | sda: mask = 0x3f Jul 15 18:21:52 | sda: dev_t = 8:0 Jul 15 18:21:52 | sda: size = 554287104 Jul 15 18:21:52 | sda: vendor = IBM Jul 15 18:21:52 | sda: product = IPR-0 5EC25900 Jul 15 18:21:52 | sdb: udev property SCSI_IDENT_LUN_T10 whitelisted Jul 15 18:21:52 | sdb: not found in pathvec Jul 15 18:21:52 | sdb: mask = 0x3f Jul 15 18:21:52 | sdb: dev_t = 8:16 Jul 15 18:21:52 | sdb: size = 554287104 Jul 15 18:21:52 | sdb: vendor = IBM Jul 15 18:21:52 | sdb: product = IPR-0 5EC25900 Jul 15 18:21:52 | sdc: udev property SCSI_IDENT_LUN_T10 whitelisted Jul 15 18:21:52 | sdc: not found in pathvec Jul 15 18:21:52 | sdc: mask = 0x3f Jul 15 18:21:52 | sdc: dev_t = 8:32 Jul 15 18:21:52 | sdc: size = 554287104 Jul 15 18:21:52 | sdc: vendor = IBM Jul 15 18:21:52 | sdc: product = IPR-0 5EC25900 Jul 15 18:21:52 | sdd: udev property SCSI_IDENT_LUN_T10 whitelisted Jul 15 18:21:52 | sdd: not found in pathvec Jul 15 18:21:52 | sdd: mask = 0x3f Jul 15 18:21:52 | sdd: dev_t = 8:48 Jul 15 18:21:52 | sdd: size = 554287104 Jul 15 18:21:52 | sdd: vendor = IBM Jul 15 18:21:52 | sdd: product = IPR-0 5EC25900 Jul 15 18:21:52 | sde: udev property SCSI_IDENT_LUN_T10 whitelisted Jul 15 18:21:52 | sde: not found in pathvec Jul 15 18:21:52 | sde: mask = 0x3f Jul 15 18:21:52 | sde: dev_t = 8:64 Jul 15 18:21:52 | sde: size = 554287104 Jul 15 18:21:52 | sde: vendor = IBM Jul 15 18:21:52 | sde: product = IPR-0 5EC25900 Jul 15 18:21:52 | sdf: udev property SCSI_IDENT_LUN_T10 whitelisted Jul 15 18:21:52 | sdf: not found in pathvec Jul 15 18:21:52 | sdf: mask = 0x3f Jul 15 18:21:52 | sdf: dev_t = 8:80 Jul 15 18:21:52 | sdf: size = 554287104 Jul 15 18:21:52 | sdf: vendor = IBM Jul 15 18:21:52 | sdf: product = IPR-0 5EC25900 Jul 15 18:21:52 | sdg: udev property SCSI_IDENT_LUN_T10 whitelisted Jul 15 18:21:52 | sdg: not found in pathvec Jul 15 18:21:52 | sdg: mask = 0x3f Jul 15 18:21:52 | sdg: dev_t = 8:96 Jul 15 18:21:52 | sdg: size = 554287104 Jul 15 18:21:52 | sdg: vendor = IBM Jul 15 18:21:52 | sdg: product = IPR-0 5EC25900 Jul 15 18:21:52 | sdh: udev property SCSI_IDENT_LUN_T10 whitelisted Jul 15 18:21:52 | sdh: not found in pathvec Jul 15 18:21:52 | sdh: mask = 0x3f Jul 15 18:21:52 | sdh: dev_t = 8:112 Jul 15 18:21:52 | sdh: size = 554287104 Jul 15 18:21:52 | sdh: vendor = IBM Jul 15 18:21:52 | sdh: product = IPR-0 5EC25900 Jul 15 18:21:52 | loop0: blacklisted, udev property missing Jul 15 18:21:52 | loop1: blacklisted, udev property missing Jul 15 18:21:52 | loop2: blacklisted, udev property missing Jul 15 18:21:52 | loop3: blacklisted, udev property missing Jul 15 18:21:52 | loop4: blacklisted, udev property missing Jul 15 18:21:52 | loop5: blacklisted, udev property missing Jul 15 18:21:52 | loop6: blacklisted, udev property missing Jul 15 18:21:52 | loop7: blacklisted, udev property missing Jul 15 18:21:52 | ram0: blacklisted, udev property missing Jul 15 18:21:52 | ram1: blacklisted, udev property missing Jul 15 18:21:52 | ram10: blacklisted, udev property missing Jul 15 18:21:52 | ram11: blacklisted, udev property missing Jul 15 18:21:52 | ram12: blacklisted, udev property missing Jul 15 18:21:52 | ram13: blacklisted, udev property missing Jul 15 18:21:52 | ram14: blacklisted, udev property missing Jul 15 18:21:52 | ram15:
[Touch-packages] [Bug 1452319] Re: please drop build-dependency on g++-4.9
** Branch unlinked: lp:~charlesk/indicator- network/lp-1452327-drop-g++-4.9-build-dep -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1452319 Title: please drop build-dependency on g++-4.9 Status in indicator-datetime package in Ubuntu: In Progress Bug description: The indicator-datetime package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1452319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267680] Re: package gdb-arm-none-eabi (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218
It looks like the version in the new changelog entry should probably be `2` instead of having an ubuntu prefix, since the prefix is already built into the version number. Beyond that, it looks like the patch is just removing all of the man pages that would normally be copied to the staging directory, so that they don't make it into the final deb. I don't see anything in your patch that would be causing it to build a much newer version of gdb. Did it build the older version of gdb before you applied your patch? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1267680 Title: package gdb-arm-none-eabi (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1 Status in gdb package in Ubuntu: Confirmed Status in gdb-arm-none-eabi package in Ubuntu: Confirmed Bug description: Was makin sure every thing worked and install properly for ya peeps from Synaptic Package Manager and found a few errors in the process got 2 uploaded along with this report also uploaded info to the error tracker which is named: 077cac62-1be5-11e3-88e6-e4115b0f8a4a which is what i also got while installing hope this helps ya =) peace SRU [Impact] Currently it is not possible to install this package alongside gdb. See also comments #8 and #9. [Test case] Attempt to install `gdb-arm-none-eabi` where `gdb` is already installed. [Regression potential] The patch used is one available in a newer version of the package. There is some confusion regarding the version number and how much changes has actually gone into this rebuild, see comment #9. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gdb-arm-none-eabi (not installed) Uname: Linux 3.13.0-999-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 Date: Thu Jan 9 21:39:21 2014 DuplicateSignature: package:gdb-arm-none-eabi:(not installed):trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1 InstallationDate: Installed on 2013-12-10 (30 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131209) SourcePackage: gdb-arm-none-eabi Title: package gdb-arm-none-eabi (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/gdb.1.gz', which is also in package gdb 7.6.50.20131218-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1267680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456328] Re: Need a development framework on Vivid overlay
** Changed in: canonical-devices-system-image Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1456328 Title: Need a development framework on Vivid overlay Status in Canonical System Image: Fix Released Status in click package in Ubuntu: In Progress Bug description: While we continue to develop on top of 15.04 using the overlay, we will need to add new APIs. Normally this would occur in the new release, like Wily, but as Wily is moving to snap it probably does not make sense there. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1456328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474934] [NEW] package libfluidsynth1:amd64 1.1.6-2 failed to install/upgrade: package libfluidsynth1:amd64 is already installed and configured
Public bug reported: libreoffice intalation ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libfluidsynth1:amd64 1.1.6-2 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1 Architecture: amd64 Date: Wed Jul 15 12:38:37 2015 DuplicateSignature: package:libfluidsynth1:amd64:1.1.6-2:package libfluidsynth1:amd64 is already installed and configured ErrorMessage: package libfluidsynth1:amd64 is already installed and configured InstallationDate: Installed on 2015-07-13 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: fluidsynth Title: package libfluidsynth1:amd64 1.1.6-2 failed to install/upgrade: package libfluidsynth1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fluidsynth (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/1474934 Title: package libfluidsynth1:amd64 1.1.6-2 failed to install/upgrade: package libfluidsynth1:amd64 is already installed and configured Status in fluidsynth package in Ubuntu: New Bug description: libreoffice intalation ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libfluidsynth1:amd64 1.1.6-2 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1 Architecture: amd64 Date: Wed Jul 15 12:38:37 2015 DuplicateSignature: package:libfluidsynth1:amd64:1.1.6-2:package libfluidsynth1:amd64 is already installed and configured ErrorMessage: package libfluidsynth1:amd64 is already installed and configured InstallationDate: Installed on 2015-07-13 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: fluidsynth Title: package libfluidsynth1:amd64 1.1.6-2 failed to install/upgrade: package libfluidsynth1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1474934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474090] Re: growpart breaks ppc64 images / sfdisk changes partition type
Just for clarity, this can be marked fix-released in util-linux when we get any upstream release 2.26.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1474090 Title: growpart breaks ppc64 images / sfdisk changes partition type Status in cloud-utils package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Confirmed Bug description: rebooting a wily cloud image under ppc64 qemu fails to come back up. also power off then start causes this issue. It ends in a SLOF prompt after showing: Trying to load: from: disk ... No DOS disk-label found. E3404: Not a bootable device! Trying to load: from: disk1 ... No DOS disk-label found. E3404: Not a bootable device! Trying to load: from: cdrom ... No medium ! E3405: No such device Trying to load: from: net ... Bootloader 1.6 Reading MAC address from device: 52:54:00:12:34:56 Requesting IP address via DHCP: 10.0.2.15 Requesting file via TFTP from 10.0.2.2 Receiving data: 0 KBytes E3010 (net) TFTP access violation the reason for this is that growpart used sfdisk to resize the disk, and sfdisk changed the partition type of the PReP partition to the default Linux partition type. The bootloader then did not consider this a partition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1474090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470557] Re: content picker shows a black line between header and page
** No longer affects: address-book-app (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1470557 Title: content picker shows a black line between header and page Status in Canonical System Image: Fix Released Status in content-hub package in Ubuntu: Fix Released Bug description: While selecting an application to share/export the contact the area between the header and the application list appear with a black color. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452319] Re: please drop build-dependency on g++-4.9
** Branch linked: lp:~charlesk/indicator-network/lp-1452327-drop-g++-4.9 -build-dep ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1452319 Title: please drop build-dependency on g++-4.9 Status in indicator-datetime package in Ubuntu: In Progress Bug description: The indicator-datetime package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1452319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
