[Touch-packages] [Bug 1389084] Re: networkmanager QtBearer backend does not support dual sim
https://codereview.qt-project.org/98774 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1389084 Title: networkmanager QtBearer backend does not support dual sim Status in “qtbase-opensource-src” package in Ubuntu: New Bug description: Currently, the networkmanager plugin assumes one modem. It needs to support dual sim properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1389084/+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 1366743] Re: Ubuntu 14.04 only prints LibreOffice Docs
Sorry, but that printout file is still the Poppler created one. I'm afraid I'm going to need Till's input on this as my knowledge of cups is limited (and now exhausted) - I only really do the Ghostscript end of things.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1366743 Title: Ubuntu 14.04 only prints LibreOffice Docs Status in “cups” package in Ubuntu: Incomplete Bug description: I use Ubuntu 14.04, a Logilink Fast Ethernet Printserver and a HP Color Laserjet 2550L. Under Ubuntu 12.10 everything worked fine and I could print any file. The printer is connected via a USB to the Printserver and adressed via HP Jet Direct. As already said, everything worked fine under 12.10 and I didn't change any settings on the printserver. I use the ubuntu tool for installing the printer, as a normal user not su. Searching the network, for network printers offers me three possibilities for adressing the printer. HP Jet Direct, IPP and LPD/LPR. I tried all of them with the same result. I use the drivers from the Database, not surprisingly HP/Color Laserjet 2550/HP Color Laserjet 2550 Series Postscript [en] (recommended). After installing the printer the first thing that fails is the Testpage. The ubunut printer spooler tells me that the job is in progress and the printer starts to blink to tell me that he is receiving input. Unfortunatly the job never starts or gets finished. After blinking quite a while the printer stops an nothing happes. Interestingly, after canceling the job on my computer and a restart of the printer, the printserver and my computer, I can open libre office writing Hello World go to print and the printer starts immediately and prints the correct result. But this only works for libreoffice and only with text, as soon as there is an image in the document it doesn't work. I can't print any pdf or even from gedit. Nothing works. Always the same as with the Testpage. Printer starts to blink but nothing happens. lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 Thanks for Help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1366743/+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 1386109] Re: [TOPBLOCKER] com.ubuntu.connectivity1.NetworkingStatus.Status is always online
The thing is that status is not requested by apps, apps have a QML binding to that value and it's the value that should change itself and send a signal, otherwise you're going to end up with polling. -- 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/1386109 Title: [TOPBLOCKER] com.ubuntu.connectivity1.NetworkingStatus.Status is always online Status in dekko: Confirmed Status in Network Menu: Invalid Status in Libqtelegram - a qt library to access telegram.: Confirmed Status in “network-manager” package in Ubuntu: In Progress Bug description: qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status always returns online on the phone, no matter if i'm connected to wifi or not or in Flight mode or not. To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1386109/+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 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)
Same problem here. Xubuntu 14.10 64bit Intel HD 4600 I am having the _xgeWireToEvent: Unknown extension 148, this should never happen. logged due to steam. My ~/.cache/upstart/startxfce4.log and /tmp/dumps/user_stdout.txt are showing this message and these files grow several GB due to this message. -- 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/1369113 Title: Steam game began crashing 2014-09-12 (cross-post Source bugtracker) Status in “steam” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Confirmed Bug description: I am cross-posting this issue, which I reported to Valve's Source GIT issue tracker, because it was suggested that the regression may be due to Ubuntu Xorg changes rather than changes on the Steam end. Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822 Symptom -- DoD:Source loads normally. But after a few minutes of playing (not a specific time as far as I can tell), the game freezes in place. A short clip (maybe a quarter of a second) of the last audio that played then repeats over and over on a loop. The process has to be killed manually with a QUIT or HUP signal for good measure. This is a new issue that just arose today. I have included system info, kernel log, and output when game is run from terminal and crashes. X info -- X.Org X Server 1.16.0 Release Date: 2014-07-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug Build Date: 10 September 2014 01:10:01PM xorg-server 2:1.16.0-1ubuntu1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.32.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. System -- OS: Ubuntu 14.10 (latest updates) Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Model: HP Envy x360 lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4) 00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI mode 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) 08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) Kernel log excerpt (from game start through crash end) -- Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open] Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open] Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] [CONNECTOR:14:?] Sep 12 19:11:25 kernel: [ 4447.852796] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP VDD on Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 0x8008 PP_CONTROL: 0xabcd000f Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 00e04c Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 00e04c Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA
[Touch-packages] [Bug 1388068] Re: sysctl.conf is not loaded by 'sysctl --system'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: procps (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1388068 Title: sysctl.conf is not loaded by 'sysctl --system' Status in “procps” package in Ubuntu: Confirmed Bug description: As described in the sysctl man page, /etc/sysctl.conf should be loaded by running 'sysctl --system': --system Load settings from all system configuration files. /run/sysctl.d/*.conf /etc/sysctl.d/*.conf /usr/local/lib/sysctl.d/*.conf /usr/lib/sysctl.d/*.conf /lib/sysctl.d/*.conf /etc/sysctl.conf This patch seems to have broken that, by loading it only in the case of an *error* from stat() on /etc/sysctl.conf, rather than success. http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/procps/trusty/revision/77/.pc/ignore_eaccess.patch/sysctl.c See the new line 643 in that patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1388068/+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 1366743] Re: Ubuntu 14.04 only prints LibreOffice Docs
Something seems to be going wrong with the -o pdftops-renderer- default=gs. Please follow the instructions of the section CUPS error_log on https://wiki.ubuntu.com/DebuggingPrintingProblems while printing the job again. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1366743 Title: Ubuntu 14.04 only prints LibreOffice Docs Status in “cups” package in Ubuntu: Incomplete Bug description: I use Ubuntu 14.04, a Logilink Fast Ethernet Printserver and a HP Color Laserjet 2550L. Under Ubuntu 12.10 everything worked fine and I could print any file. The printer is connected via a USB to the Printserver and adressed via HP Jet Direct. As already said, everything worked fine under 12.10 and I didn't change any settings on the printserver. I use the ubuntu tool for installing the printer, as a normal user not su. Searching the network, for network printers offers me three possibilities for adressing the printer. HP Jet Direct, IPP and LPD/LPR. I tried all of them with the same result. I use the drivers from the Database, not surprisingly HP/Color Laserjet 2550/HP Color Laserjet 2550 Series Postscript [en] (recommended). After installing the printer the first thing that fails is the Testpage. The ubunut printer spooler tells me that the job is in progress and the printer starts to blink to tell me that he is receiving input. Unfortunatly the job never starts or gets finished. After blinking quite a while the printer stops an nothing happes. Interestingly, after canceling the job on my computer and a restart of the printer, the printserver and my computer, I can open libre office writing Hello World go to print and the printer starts immediately and prints the correct result. But this only works for libreoffice and only with text, as soon as there is an image in the document it doesn't work. I can't print any pdf or even from gedit. Nothing works. Always the same as with the Testpage. Printer starts to blink but nothing happens. lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 Thanks for Help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1366743/+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 1384286] Re: add directory allowing scopes and apps to share data
currently, ~/.local/share/@{APP_PKGNAME} is used as the click
*installation* directory
There's something mixed up here I think. This is, for apps as well as
scopes, where data is stored, wheras installations are in
/opt/click.ubuntu.com/ .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1384286
Title:
add directory allowing scopes and apps to share data
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
Confirmed
Bug description:
Summary says it all, just need to decide on the directory. I propose using
this rule:
# Allow scopes to share data with the app shipped in the same click
owner @{HOME}/.local/share/@{APP_PKGNAME}/rw,
owner @{HOME}/.local/share/@{APP_PKGNAME}/** mrwkl,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286/+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 1385619] Re: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev
the url you gave is another ubuntu bug, not an upstream one -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1385619 Title: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev Status in The Linux Mint Distribution: New Status in “gtk+3.0” package in Ubuntu: New Bug description: The static libraries are missing in libgtk-3-dev 3.10.8~6+qiana. Upstream (Ubuntu) also has this issue, but since this is a specialized qiana build, I felt I should also report this here. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1385619/+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 1385622] Re: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev
*** This bug is a duplicate of bug 1385619 *** https://bugs.launchpad.net/bugs/1385619 ** This bug has been marked a duplicate of bug 1385619 libgtk-3.a and libgdk-3.a missing in libgtk-3-dev -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1385622 Title: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev Status in “gtk+3.0” package in Ubuntu: New Bug description: In one of the latest releases, you removed the static libraries from libgtk-3-dev. (They were still there in 3.4.2 and are missing in 3.10.8-0ubuntu1.) Please consider re-adding them. I have read in https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1101157 that you removed them on purpose, but I must object to the claim that static builds of gtk have so many issues that it is justified to remove the static libraries at all. I admittetly build my static version of gtk with `--disable-modules`, but with that build flag, I haven't experienced any issues with statically linked gtk applications so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1385622/+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 1378184] Re: RTM r3 why is Nepali Unicode texts not displaying in browser app
Confirmed for ubuntu-touch-meta and marked invalid for webbrowser-app as it’s not specific to the browser, it potentially affects all applications trying to display nepali text. ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New = Confirmed ** Changed in: webbrowser-app (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1378184 Title: RTM r3 why is Nepali Unicode texts not displaying in browser app Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Status in “webbrowser-app” package in Ubuntu: Invalid Bug description: In browser app including facebook and google+ web app nepali unicode texts are displayed as rectangle boxes instead of actual texts. Doesn't it support unicode? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1378184/+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 1389044] [NEW] Error while reading from descriptor: Broken pipe
You have been subscribed to a public bug: In my dmesg output I see this error in red: [9.665694] init: Error while reading from descriptor: Broken pipe No idea what it means and to what it is referring to. The attached extra debug information should tell you a bit more. Thanks for investigating! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael-heuberger 2171 F pulseaudio /dev/snd/controlC1: michael-heuberger 2171 F pulseaudio /dev/snd/controlC0: michael-heuberger 2171 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 4 15:29:19 2014 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: upstart (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages utopic -- Error while reading from descriptor: Broken pipe https://bugs.launchpad.net/bugs/1389044 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart 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 1378184] Re: RTM r3 why is Nepali Unicode texts not displaying in browser app
I have requested landing the addition of fonts-lohit-deva to the touch seed for RTM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1378184 Title: RTM r3 why is Nepali Unicode texts not displaying in browser app Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Status in “webbrowser-app” package in Ubuntu: Invalid Bug description: In browser app including facebook and google+ web app nepali unicode texts are displayed as rectangle boxes instead of actual texts. Doesn't it support unicode? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1378184/+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 1385619] Re: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev
Since Mint is based on Ubuntu I'd consider their version of the package upstream from Mint's. The bug lies in the packaging, not gtk itself, so there's nowhere further upstream from them.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1385619 Title: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev Status in The Linux Mint Distribution: New Status in “gtk+3.0” package in Ubuntu: New Bug description: The static libraries are missing in libgtk-3-dev 3.10.8~6+qiana. Upstream (Ubuntu) also has this issue, but since this is a specialized qiana build, I felt I should also report this here. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1385619/+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 1384286] Re: add directory allowing scopes and apps to share data
Scopes installed from click packages are, as a matter of fact, installed
in ~/.local/share/unity-scopes/@{APP_PKGNAME}
No scope, no matter where it comes from, is ever installed in
/opt/click. If it is, it won't work because the registry won't look for
it there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1384286
Title:
add directory allowing scopes and apps to share data
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
Confirmed
Bug description:
Summary says it all, just need to decide on the directory. I propose using
this rule:
# Allow scopes to share data with the app shipped in the same click
owner @{HOME}/.local/share/@{APP_PKGNAME}/rw,
owner @{HOME}/.local/share/@{APP_PKGNAME}/** mrwkl,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286/+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 1389044] Re: Error while reading from descriptor: Broken pipe
** Package changed: linux (Ubuntu) = upstart (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1389044 Title: Error while reading from descriptor: Broken pipe Status in “upstart” package in Ubuntu: Confirmed Bug description: In my dmesg output I see this error in red: [9.665694] init: Error while reading from descriptor: Broken pipe No idea what it means and to what it is referring to. The attached extra debug information should tell you a bit more. Thanks for investigating! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael-heuberger 2171 F pulseaudio /dev/snd/controlC1: michael-heuberger 2171 F pulseaudio /dev/snd/controlC0: michael-heuberger 2171 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 4 15:29:19 2014 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1389044/+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 1385619] Re: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev
yeah, if you are using Mint then the issue is their and not an Ubuntu one -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1385619 Title: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev Status in The Linux Mint Distribution: New Status in “gtk+3.0” package in Ubuntu: New Bug description: The static libraries are missing in libgtk-3-dev 3.10.8~6+qiana. Upstream (Ubuntu) also has this issue, but since this is a specialized qiana build, I felt I should also report this here. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1385619/+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 1378437] Re: Facebook webapp does not work with the url dispatcher
** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/unity-webapps-qml /vivid-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-webapps-qml in Ubuntu. https://bugs.launchpad.net/bugs/1378437 Title: Facebook webapp does not work with the url dispatcher Status in Unity WebApps QML component: In Progress Status in The Webapps-core project: In Progress Status in Web Browser App: In Progress Status in “unity-webapps-qml” package in Ubuntu: New Status in “unity-webapps-qml” package in Ubuntu RTM: New Bug description: The facebook webapp does not work when is being opened as a result of the url dispatcher opening a non default url (e.g. to the user's account page instead of the default homepage), To manage notifications about this bug go to: https://bugs.launchpad.net/unity-webapps-qml/+bug/1378437/+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 1387261] Re: launcher badge missing due to dbus msgs getting lost
** Tags added: beta -- 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/1387261 Title: launcher badge missing due to dbus msgs getting lost Status in “unity8” package in Ubuntu: In Progress Bug description: when there are image updates available, the system settings app in the launcher should have a small badge to reflect there's something new for the user, however this is missing. there's been a bit of debug done and it seems the message the launcher needs to act on goes missing on it's way from the backend via dbus. from design wrt missing image update badge on system settings What you should see: Wherever the System Settings icon appears, it should have a badge with the number of updates available. https://wiki.ubuntu.com/SoftwareUpdates#Prompting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387261/+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 1378437] Re: Facebook webapp does not work with the url dispatcher
This bug was fixed in the package unity-webapps-qml - 0.1+15.04.20141103.1-0ubuntu1 --- unity-webapps-qml (0.1+15.04.20141103.1-0ubuntu1) vivid; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Alexandre Abreu ] * Add small guard before url navigation (LP: #1378437) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 03 Nov 2014 18:47:01 + ** Changed in: unity-webapps-qml (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-webapps-qml in Ubuntu. https://bugs.launchpad.net/bugs/1378437 Title: Facebook webapp does not work with the url dispatcher Status in Unity WebApps QML component: In Progress Status in The Webapps-core project: In Progress Status in Web Browser App: In Progress Status in “unity-webapps-qml” package in Ubuntu: Fix Released Status in “unity-webapps-qml” package in Ubuntu RTM: New Bug description: The facebook webapp does not work when is being opened as a result of the url dispatcher opening a non default url (e.g. to the user's account page instead of the default homepage), To manage notifications about this bug go to: https://bugs.launchpad.net/unity-webapps-qml/+bug/1378437/+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 1259510] Re: fontconfig segmentation fault during package installation
To solve this error when upgrading 14.04-14.10 I ran: $ dpkg -D40 -i ~/Downloads/fontconfig_2.11.0-0ubuntu4.1_amd64.deb Then I notice this file caused the error, so I seek the packge owning it: $ dpkg -S /usr/share/fonts/truetype/unfonts-core/UnBatangBold.ttf I then remove that package: $ sudo apt-get remove fonts-unfonts-core I know resume the pakcages install: $ sudo apt-get install -f which works ok now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1259510 Title: fontconfig segmentation fault during package installation Status in “fontconfig” package in Ubuntu: New Bug description: During update, while doing post-install processing, apt-get reports that the process died with a SIGSEGV, and /var/log/fontconfig.log has only one line: Segmentation fault (core dumped). I realize that this is not enough information, but I don't know what other information would be relevant (and/or how to obtain it), so I'd appreciate it if anyone could tell me what other information about my system or what other logs I need to add. A few days earlier, I had a problem where I couldn't log in, and it turned out to be a segfault in libfreetype.so. After I had copied several fonts from a Windows partition, fc-cache crashed and that seems to be what caused the segfaults in FreeType. I realized that the fonts I copied from the Windows partition had permissions 640, so they weren't readable when I ran fc-cache from my regular user account. After I chmod'ed them to 644 and ran fc-cache, the FreeType segfaults stopped and I was able to log back into X, but ever since then, whenever I try to update fontconfig, it segfaults in the post-install step and apt-get reports one package not fully installed (or something to that effect). I don't know if both problems are related. I just mentioned the fc- cache/libfreetype issue because it seemed odd to me that two font- related packages would start segfaulting within days of each other. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Dec 10 09:12:19 2013 InstallationDate: Installed on 2013-12-01 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131130) SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1259510/+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 1389165] [NEW] Some strings are not translatable
Public bug reported: There are strings in the shell that are still not translatable (Return to call), and there's risk of more, since we were not extracting calls specifying the domain explicitly. ** Affects: unity8 (Ubuntu) Importance: High Assignee: Albert Astals Cid (aacid) Status: In Progress ** Branch linked: lp:~aacid/unity8/dtrdomainpot -- 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/1389165 Title: Some strings are not translatable Status in “unity8” package in Ubuntu: In Progress Bug description: There are strings in the shell that are still not translatable (Return to call), and there's risk of more, since we were not extracting calls specifying the domain explicitly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389165/+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 1273261] Re: Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1273261 Title: Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file Status in “cryptsetup” package in Ubuntu: Confirmed Status in “initramfs-tools” package in Ubuntu: New Bug description: While booting cryptsetup outputs following error: /scripts/local- top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file, seems to be not related to this particular installation as saw the same output on other machines, also seems to be nothing major as everything boots fine, so just reporting to let you know it's there. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cryptsetup 2:1.4.3-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 27 15:58:16 2014 InstallationDate: Installed on 2014-01-18 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) crypttab: sda3_crypt UUID=68851a49-83a4-41eb-84c0-27d15280bbc1 none luks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261/+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 1389167] [NEW] HostbasedAuthentication produces spurious warnings
Public bug reported: Ubuntu 14.04.1 LTS openssh-client 1:6.6p1-2ubuntu2 We have HostbasedAuthentication set up in our environment so that users can ssh between equivalent hosts without a password. ssh_config contains (relevantly) HostbasedAuthentication yes PreferredAuthentications publickey,hostbased,password,keyboard-interactive EnableSSHKeysign yes sshd_config contains (relevantly) HostbasedAuthentication yes This works: ocelot:~$ ssh othermc othermc:~$ However, ssh-ing as an alternative user produces additional warning messages before the expected password prompt: ocelot:~$ ssh otheruser@othermc no matching hostkey found ssh_keysign: no reply key_sign failed otheruser@othermc's password: If instead of relying on EnableSSHKeysign in ssh_config I make the ssh binary setuid: chmod u+s /usr/bin/ssh ...the extra warnings go away and I get what I expect: ocelot:~$ ssh otheruser@othermc otheruser@othermc's password: This makes me suspect that there may be a problem with ssh-keysign. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1389167 Title: HostbasedAuthentication produces spurious warnings Status in “openssh” package in Ubuntu: New Bug description: Ubuntu 14.04.1 LTS openssh-client 1:6.6p1-2ubuntu2 We have HostbasedAuthentication set up in our environment so that users can ssh between equivalent hosts without a password. ssh_config contains (relevantly) HostbasedAuthentication yes PreferredAuthentications publickey,hostbased,password,keyboard-interactive EnableSSHKeysign yes sshd_config contains (relevantly) HostbasedAuthentication yes This works: ocelot:~$ ssh othermc othermc:~$ However, ssh-ing as an alternative user produces additional warning messages before the expected password prompt: ocelot:~$ ssh otheruser@othermc no matching hostkey found ssh_keysign: no reply key_sign failed otheruser@othermc's password: If instead of relying on EnableSSHKeysign in ssh_config I make the ssh binary setuid: chmod u+s /usr/bin/ssh ...the extra warnings go away and I get what I expect: ocelot:~$ ssh otheruser@othermc otheruser@othermc's password: This makes me suspect that there may be a problem with ssh-keysign. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1389167/+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 1198714] Re: [browser] Switching between tabs cumbersome
** Description changed: Current Behaviour: - When switching between tabs, I have to make two touches. Most other browsers only require one. - When switching between tabs, there is very limited space to display tab specific information. - Tab icons do not have a number indicating the number of tabs open. - We cannot switch between tabs using the left-to-right swipe motion. - We are forced to use the in-browser tab switching because we cannot have multiple instances of the browser app. - I can have a GMail web app, and Gmail open in a seperate tab, but I would have to switch between them differently. This can be fairly confusing because the windows aren't lableled when switching unless you go to the main Apps page. Expected Behaviour: - Use a switching behaviour similar to the way we switch between notifications to switch between tabs. I posted a video about it here: https://plus.google.com/113548024460495540073/posts/LKk7yHvFY68 - Alternatively, abandon the entire Tab functionality and only have new browser app instances. This will make the experience more aligned with the Web App experience. NOTE: I remember reading an article regarding windows switching tab switching. The article explained that the introduction of Tabs in applications was an attempt to take control of windows switching from the window manager. I don't have a reference, but I believe it was written with Ubuntu in mind. If knows about this article, it probably gives good use cases to abandone tabbing all together. + + UX Comment: + The new bottom edge functionality will address the issues above. + See bug https://bugs.launchpad.net/ubuntu-ux/+bug/1329943 ** Changed in: ubuntu-ux Status: Fix Committed = Won't Fix -- 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/1198714 Title: [browser] Switching between tabs cumbersome Status in Ubuntu UX bugs: Won't Fix Status in Web Browser App: New Status in “webbrowser-app” package in Ubuntu: Confirmed Bug description: Current Behaviour: - When switching between tabs, I have to make two touches. Most other browsers only require one. - When switching between tabs, there is very limited space to display tab specific information. - Tab icons do not have a number indicating the number of tabs open. - We cannot switch between tabs using the left-to-right swipe motion. - We are forced to use the in-browser tab switching because we cannot have multiple instances of the browser app. - I can have a GMail web app, and Gmail open in a seperate tab, but I would have to switch between them differently. This can be fairly confusing because the windows aren't lableled when switching unless you go to the main Apps page. Expected Behaviour: - Use a switching behaviour similar to the way we switch between notifications to switch between tabs. I posted a video about it here: https://plus.google.com/113548024460495540073/posts/LKk7yHvFY68 - Alternatively, abandon the entire Tab functionality and only have new browser app instances. This will make the experience more aligned with the Web App experience. NOTE: I remember reading an article regarding windows switching tab switching. The article explained that the introduction of Tabs in applications was an attempt to take control of windows switching from the window manager. I don't have a reference, but I believe it was written with Ubuntu in mind. If knows about this article, it probably gives good use cases to abandone tabbing all together. UX Comment: The new bottom edge functionality will address the issues above. See bug https://bugs.launchpad.net/ubuntu-ux/+bug/1329943 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1198714/+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 1124071] Re: [tabs] Cannot add Tabs programmatically
** Description changed: There seems to be no easy way to add a Tab to Tabs programmatically. I would be nice to be able add, remove and edit Tabs dynamically. So far I haven't found a way to do this. I have made an Android style ViewPager based on ListView. It is quite easy to update the pages with ListModel methods. + + UX Comments + Tabs are deprecated, use the new header instead, or headers sections ** Changed in: ubuntu-ux Status: Triaged = Won't Fix -- 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/1124071 Title: [tabs] Cannot add Tabs programmatically Status in RSS Feed Reader application for Ubuntu devices: Incomplete Status in Ubuntu UI Toolkit: Fix Released Status in Ubuntu UX bugs: Won't Fix Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Status in “ubuntu-ui-toolkit” source package in Trusty: Confirmed Bug description: There seems to be no easy way to add a Tab to Tabs programmatically. I would be nice to be able add, remove and edit Tabs dynamically. So far I haven't found a way to do this. I have made an Android style ViewPager based on ListView. It is quite easy to update the pages with ListModel methods. UX Comments Tabs are deprecated, use the new header instead, or headers sections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1124071/+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 1378437] Re: Facebook webapp does not work with the url dispatcher
** Tags removed: touch-2014-10-30 ** Tags added: touch-2014-11-06 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-webapps-qml in Ubuntu. https://bugs.launchpad.net/bugs/1378437 Title: Facebook webapp does not work with the url dispatcher Status in Unity WebApps QML component: In Progress Status in The Webapps-core project: In Progress Status in Web Browser App: In Progress Status in “unity-webapps-qml” package in Ubuntu: Fix Released Status in “unity-webapps-qml” package in Ubuntu RTM: New Bug description: The facebook webapp does not work when is being opened as a result of the url dispatcher opening a non default url (e.g. to the user's account page instead of the default homepage), To manage notifications about this bug go to: https://bugs.launchpad.net/unity-webapps-qml/+bug/1378437/+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 1379497] Re: [webapp-container] UA Override from an optional webapp-properies.json file is not set
** Tags removed: touch-2014-10-30
** Tags added: touch-2014-11-06
** Changed in: webbrowser-app
Status: In Progress = Fix Released
** Changed in: webbrowser-app (Ubuntu)
Status: New = Fix Released
--
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/1379497
Title:
[webapp-container] UA Override from an optional webapp-properies.json
file is not set
Status in Web Browser App:
Fix Released
Status in “webbrowser-app” package in Ubuntu:
Fix Released
Status in “webbrowser-app” package in Ubuntu RTM:
New
Bug description:
A Webapp has the option to either specify a command line option to
have a specific UA overriding the default or hgave a local webapp-
properties.json file that defines the UA override such as:
{
name: MyWebapp,
includes:[http://user-agent.me/*;],
domain:user-agent.me,
homepage:http://user-agent.me/;,
user-agent-override: Mozilla/5.0 custom-user-agent-string (unlike
AnyOtheBrowser)
}
This currently does work, or to be more precise works but the url is
set before during the init flow, and the UA string is being set after
the website was browsed to.
To manage notifications about this bug go to:
https://bugs.launchpad.net/webbrowser-app/+bug/1379497/+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 1358622] Re: webapp container redirection URL trimming breaks links to twitter in facebook app
** Tags removed: touch-2014-10-30 ** Tags added: touch-2014-11-06 -- 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/1358622 Title: webapp container redirection URL trimming breaks links to twitter in facebook app Status in Web Browser App: In Progress Status in “webbrowser-app” package in Ubuntu: New Bug description: Consider a facebook post that contains a link to http://t.co/OvsXJpPCtM; (twitter URL shortener). Facebook encodes this link as http://lm.facebook.com/l.php?u=http%3A%2F%2Ft.co%2FOvsXJpPCtMh=rAQH6jL54s=1;, which redirects to the original link. However calling Qt.openUrlExternally(…) on the encoded link won’t open it in the browser (or in the twitter webapp), it will trigger the URL dispatcher with the facebook webapp itself. So the actual link needs to be extracted from the encoded URL. The webapp container already has a mechanism to do that, in the form of a --popup-redirection-url-prefix command-line parameter, which basically trims the corresponding prefix off an encoded URL. For facebook, this prefix is http://lm.facebook.com/l.php?u=;. So the encoded URL is transformed into http%3A%2F%2Ft.co%2FOvsXJpPCtMh=rAQH6jL54s=1 and then decoded, which gives http://t.co/OvsXJpPCtMh=rAQH6jL54s=1;, which ends up on a 404, because of the additional parameters h=rAQH6jL54s=1 that were part of the encoded URL, not the original one. This prefix mechanism is too simple, we probably need a regexp mechanism to properly extract the target URL from the encoded form, without leaving trailing parameters. Note that in the current release of webapp-container as of today (0.23+14.10.20140818.2-0ubuntu1), there is a bug whereby the encoded URL is used, not the trimmed one. The following MR fixes this bug, but hits the 404 issue with twitter links in facebook posts: https://code.launchpad.net/~osomon/webbrowser-app/filter-session- storage-url-save/+merge/231204. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1358622/+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 1347764] Re: webapps user scripts overriding StateSaver saved url
** Tags removed: touch-2014-10-30 ** Tags added: touch-2014-11-06 -- 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/1347764 Title: webapps user scripts overriding StateSaver saved url Status in The Webapps-core project: Triaged Status in Web Browser App: Triaged Status in “webbrowser-app” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu RTM: New Bug description: placeholder bug for issue that has been discussed already: webapps and webbrowser are now using StateSaver to restore previous url if they are killed by oom killer. There is an issue with webapps that use user scripts (currently Facebook) where the user script runs after the save url is restored and overwrites it with it's own url. This will need to be updated to honor the value saved by StateSaver, if present. To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1347764/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
** Changed in: systemd-shim (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) ** Changed in: systemd-shim (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in “systemd-shim” package in Ubuntu: Fix Committed Status in “systemd-shim” package in Debian: Incomplete Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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 1381930] Re: [TOPBLOCKER] 7digital previews do not play in the scope
The url returned by the scope now seems wrong: http://previews.7digital.com/clip/40673459?oauth_nonce=99903452oauth_timestamp=1415099166country =scopes- api%3D0.6.7+14.10.20141014-0ubuntu1oauth_consumer_key=7d7e9ja2evm7oauth_signature_method =HMAC- SHA1oauth_version=1.0oauth_signature=5m0Dbus44WScuZ0WshMXhLxFLZw%3D Website says: Value of parameter country is not valid: scopes-api=0.6.7 14.10.20141014-0ubuntu1 ** Changed in: qtbase-opensource-src (Ubuntu) Status: Incomplete = Invalid ** Changed in: qtubuntu-media (Ubuntu) Status: Fix Committed = In Progress ** Changed in: qtubuntu-media (Ubuntu RTM) Status: Fix Committed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: [TOPBLOCKER] 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu: In Progress Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Invalid Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+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 1301015] Re: Networking does not restart
Yes, I, too, find this to be very frustrating! I need to be able to
*easily* restart networking remotely via SSH and this is impossible with
the new way of doing things. How can I help fix this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1301015
Title:
Networking does not restart
Status in “ifupdown” package in Ubuntu:
Confirmed
Bug description:
In Ubuntu Server 14.04 it appears it is not possible to restart
networking. This is fresh install from ISO.
wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
wirehive@ubuntu:~$ echo $?
1
wirehive@ubuntu:~$ sudo service networking restart
stop: Job failed while stopping
start: Job is already running: networking
wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
+ PATH=/sbin:/bin
+ RUN_DIR=/run/network
+ IFSTATE=/run/network/ifstate
+ STATEDIR=/run/network/state
+ '[' -x /sbin/ifup ']'
+ '[' -x /sbin/ifdown ']'
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
++ . /lib/lsb/init-functions.d/50-ubuntu-logging
+++ LOG_DAEMON_MSG=
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ CONFIGURE_INTERFACES=yes
+ EXCLUDE_INTERFACES=
+ VERBOSE=no
+ '[' -f /etc/default/networking ']'
+ verbose=
+ '[' no = yes ']'
+ case $1 in
+ init_is_upstart
+ '[' -x /sbin/initctl ']'
+ /bin/grep -q upstart
+ /sbin/initctl version
+ return 0
+ exit 1
wirehive@ubuntu:~$ sudo bash -x service networking restart
++ basename service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename service
+ USAGE='Usage: service option | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case ${1} in
+ '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
+ '[' 2 -eq 2 -a restart = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=networking
+ shift
+ '[' 1 -gt 0 ']'
+ case ${1} in
+ '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z networking ']'
+ '[' -z '' ']'
+ ACTION=restart
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/networking.conf ']'
+ which initctl
+ grep -q upstart
+ initctl version
+ case ${ACTION} in
+ stop networking
stop: Job failed while stopping
+ :
+ exec start networking
start: Job is already running: networking
wirehive@ubuntu:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
https://github.com/desrt/systemd-shim/commit/729b958d9d97 ** Changed in: systemd-shim (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in “systemd-shim” package in Ubuntu: Fix Committed Status in “systemd-shim” package in Debian: Incomplete Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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 1389192] [NEW] Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action
Public bug reported: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. What you see: Please setup an account in system settings What's wrong with this: A. Setup is a noun, so Please setup is ungrammatical. B. System Settings is a proper noun, so system settings is miscapitalized. C. A caption is a complete sentence (sometimes more than one), and this sentence is missing its period. D. There's no explanation of why you *should* set up an account. E. In system settings is a useless direction. The word Fitbit does not appear anywhere on the System Settings screen, leaving you lost. F. Sending people to System Settings is the wrong thing to do in the first place: they might already have a Fitbit account set up. What you should see: something like Track your fitness activities here using a Fitbit account. ( Use Fitbit… ) ( No Thanks ) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1389192 Title: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action Status in “unity8” package in Ubuntu: New Bug description: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. What you see: Please setup an account in system settings What's wrong with this: A. Setup is a noun, so Please setup is ungrammatical. B. System Settings is a proper noun, so system settings is miscapitalized. C. A caption is a complete sentence (sometimes more than one), and this sentence is missing its period. D. There's no explanation of why you *should* set up an account. E. In system settings is a useless direction. The word Fitbit does not appear anywhere on the System Settings screen, leaving you lost. F. Sending people to System Settings is the wrong thing to do in the first place: they might already have a Fitbit account set up. What you should see: something like Track your fitness activities here using a Fitbit account. ( Use Fitbit… ) ( No Thanks ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389192/+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 1388734] Re: Xorg freezes after starting gnome-do
** Summary changed: - Xorg freeze + Xorg freezes after starting gnome-do -- 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/1388734 Title: Xorg freezes after starting gnome-do Status in “xorg” package in Ubuntu: New Bug description: Happens every time I start gnome-do. gnome-do window will alocate some screen space but not show and only mirror some parts of the background. Mouse can be moved, even some mouse-over events work. But clicking and typing is not registered (not even ctrl-alt-f1). Only way to fix the problem is to ssh in from outside and kill gnome-do. Then everything works fine again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Starting userspace bootsplash utility[94G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Nov 3 08:44:34 2014 DistUpgraded: 2014-10-27 14:16:53,420 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0492] InstallationDate: Installed on 2013-09-16 (412 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to utopic on 2014-10-27 (6 days ago) dmi.bios.date: 05/07/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.05 dmi.board.asset.tag: CZC3112KV3 dmi.board.name: 3396 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3112KV3 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqElite8300CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP Compaq Elite 8300 CMT dmi.sys.vendor: Hewlett-Packard 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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Nov 3 08:34:04 2014 xserver.configfile: /etc/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388734/+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 1389195] [NEW] Fitbit section in Dashboard goes to an empty screen when tapped
Public bug reported: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. 2. Tap anywhere in the section, which is quite easy to do by accident. What happens: * You end up on a Dashboard screen that is completely empty. * If you didn't notice that a Back button has appeared next to Dashboard, you might reasonably conclude that the Dashboard has broken. What should happen: either * If you have no Fitbit account, the section should not go to a separate screen, or * if it does go to a separate screen, it should not be called Dashboard and should not be empty. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1389195 Title: Fitbit section in Dashboard goes to an empty screen when tapped Status in “unity8” package in Ubuntu: New Bug description: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. 2. Tap anywhere in the section, which is quite easy to do by accident. What happens: * You end up on a Dashboard screen that is completely empty. * If you didn't notice that a Back button has appeared next to Dashboard, you might reasonably conclude that the Dashboard has broken. What should happen: either * If you have no Fitbit account, the section should not go to a separate screen, or * if it does go to a separate screen, it should not be called Dashboard and should not be empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389195/+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 1384749] Re: [TOPBLOCKER] Detected X, Y coordinates for touch event on text field is off
Mir bug 1389189 about incomplete event data. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-mir in Ubuntu. https://bugs.launchpad.net/bugs/1384749 Title: [TOPBLOCKER] Detected X,Y coordinates for touch event on text field is off Status in Ubuntu UI Toolkit: In Progress Status in Ubuntu UX bugs: Fix Committed Status in Unity Mir: New Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Status in “unity-mir” package in Ubuntu: New Bug description: Tapping on a word in a text input seems to select the word below, rather than the one I intended to select The Y seems to be lower by approx. 1 GU Reproduce by - Go to messages and tap on message filed - Enter 4 rows of content - Tap on a word in the second row - The word below is often selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1384749/+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 1243233] Re: Holding Super key doesn't bring up shortcut overlay.
You're right! With an horizontal resolution of 1024, the overlay is not display. I took a screenshot of the overlay to see how it would look in 1024x768, and it doesn't fit horizontally, even with workspaces disabled. Also, the horizontal size probably depends on the used language (the texts may be longer/shorter in other languages). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1243233 Title: Holding Super key doesn't bring up shortcut overlay. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: After upgrading from 13.04 to 13.10, holding Super no longer brings up the help overlay. Holding Super worked before upgrading. Tapping the Super key still brings up the HUD, and holding it down still brings up the Launcher and after a second or so shows the numbers on the applications. In Compiz Config Manager, under Ubuntu Unity Plugin - Launcher, the Key to show the Dash, Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin - General, Enable Shortcut Hints Overlay is checked. This is also known to affect 14.04 (without compiz) when workspaces are enabled and screen resolution is 1024x768. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243233/+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 1389167] Re: HostbasedAuthentication produces spurious warnings
Digging a bit further, I think this arises because ssh-keysign punts off all its host key processing to openSSL, but openSSL does not support ED25519 keys. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1389167 Title: HostbasedAuthentication produces spurious warnings Status in “openssh” package in Ubuntu: New Bug description: Ubuntu 14.04.1 LTS openssh-client 1:6.6p1-2ubuntu2 We have HostbasedAuthentication set up in our environment so that users can ssh between equivalent hosts without a password. ssh_config contains (relevantly) HostbasedAuthentication yes PreferredAuthentications publickey,hostbased,password,keyboard-interactive EnableSSHKeysign yes sshd_config contains (relevantly) HostbasedAuthentication yes This works: ocelot:~$ ssh othermc othermc:~$ However, ssh-ing as an alternative user produces additional warning messages before the expected password prompt: ocelot:~$ ssh otheruser@othermc no matching hostkey found ssh_keysign: no reply key_sign failed otheruser@othermc's password: If instead of relying on EnableSSHKeysign in ssh_config I make the ssh binary setuid: chmod u+s /usr/bin/ssh ...the extra warnings go away and I get what I expect: ocelot:~$ ssh otheruser@othermc otheruser@othermc's password: This makes me suspect that there may be a problem with ssh-keysign. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1389167/+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 1389204] [NEW] No Calls Today and No Messages Today go to screens with empty buttons
Public bug reported: Ubuntu 14.10 r6 0. If you have made/sent/received any calls or messages today, wipe the phone. 1. Go to the Dashboard screen. 2. Tap No Calls Today or No Messages Today. 3. Tap the button. What happens: 2. You end up on a screen labelled Dashboard containing the text No Calls Today or No Messages Today and an empty button. 3. The screen goes black except for a close button in the corner. What should happen: either 2. Nothing happens, you don't end up on a separate screen; or 3. the screen does not contain a button that goes nowhere. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: video of the problem https://bugs.launchpad.net/bugs/1389204/+attachment/4252763/+files/No%20Calls%20Today.avi ** Summary changed: - No Calls Today and No Messages Today go to mysterious blackness generators when tapped + No Calls Today and No Messages Today go to screens with empty buttons -- 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/1389204 Title: No Calls Today and No Messages Today go to screens with empty buttons Status in “unity8” package in Ubuntu: New Bug description: Ubuntu 14.10 r6 0. If you have made/sent/received any calls or messages today, wipe the phone. 1. Go to the Dashboard screen. 2. Tap No Calls Today or No Messages Today. 3. Tap the button. What happens: 2. You end up on a screen labelled Dashboard containing the text No Calls Today or No Messages Today and an empty button. 3. The screen goes black except for a close button in the corner. What should happen: either 2. Nothing happens, you don't end up on a separate screen; or 3. the screen does not contain a button that goes nowhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389204/+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 1386323] Re: is friend app not available in 14.10?
Ths bug affects me too -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1386323 Title: is friend app not available in 14.10? Status in “friends-app” package in Ubuntu: New Bug description: is friend app not available in 14.10. I used to get notifications in the previous versions of ubuntu. Its not working in 14.10. I was using the friends app till ubuntu 14.04 as soon as I updated to ubuntu 14.10, the friends app is not working. I used to get notifications (notify osd) in the previous version. Neither the app is getting updated with the latest feeds from twitter and facebook nor I am getting any notifications. I tried uninstalling and reinstalling as well as remove the online accounts from the systems settings menu and added the accounts again. Neither way it doesnt seems to work. It was reallt a very good application. Please some one help me on this. Is the friends app still supported in the latest version of ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1386323/+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 1385803] Re: package lightdm 1.12.1-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1385803 Title: package lightdm 1.12.1-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in “lightdm” package in Ubuntu: Confirmed Bug description: encrypted home directory broken as well ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sun Oct 19 12:43:51 2014 DuplicateSignature: package:lightdm:1.12.1-0ubuntu1:subprocess installed post-removal script returned error exit status 1 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2014-10-18 (7 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) SourcePackage: lightdm Title: package lightdm 1.12.1-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.pam.d.lightdm: 2014-10-19T13:04:22.965443 mtime.conffile..etc.pam.d.lightdm.greeter: 2014-10-19T13:03:27.617443 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1385803/+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 1382133] Re: Issue with servers with SSLv3 disabled due to Poodle
Hi... is there a reason the fix hasn't been released for 14.04 LTS yet? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1382133 Title: Issue with servers with SSLv3 disabled due to Poodle Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution-data-server” source package in Precise: Fix Released Status in “evolution-data-server” source package in Trusty: Fix Committed Bug description: [ Description ] Cannot connect to servers with SSLv3 disabled, with a message Cannot communicate securely with peer: no common encryption algorithm(s). [ QA ] Try to connect to a server with SSLv3 disabled and see if you can retrieve mail (and that it errors before the update). [ Regression potential ] Might enable a different set of SSL/TLS versions, check with different servers. [ Original report ] Evolution developers asked me to relay that there is a fix to this issue available, please see https://mail.gnome.org/archives/evolution- list/2014-October/msg00113.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1382133/+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 53887] Re: [patch] Command completion should be enhanced
Upstream has now configuration parameters to make almost desired behavior. ** Changed in: bash (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/53887 Title: [patch] Command completion should be enhanced Status in “bash” package in Ubuntu: Invalid Bug description: When bash has more than one completion alternatives, it prints the list of possible completions. If user presses the TAB again, the list is showed again. There should be a completion mode which browses/suggests a item from the completion list instead of showing the list again. This would be like a mixture of the default completion mode and the menu-complete. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/53887/+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 1233185] Re: gdb-multiarch cannot read ARM cores: wrong size gregset struct in core file
I ran the test case on an armhf machine with gdb/gdb-multiarch 7.7.1-0ubuntu5~14.04.2 from trusty-proposed, and it works well now. I also copied the binary, libraries, and core dump to an amd64 machine and ran gdb-multiarch there, with the same result. So for this purpose, the trusty-proposed binary works fine now. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1233185 Title: gdb-multiarch cannot read ARM cores: wrong size gregset struct in core file Status in “gdb” package in Ubuntu: Fix Released Status in “gdb” source package in Trusty: Fix Committed Status in “gdb” package in Debian: Fix Released Bug description: We are getting complaints that the Launchpad apport retracers cannot create proper symbolic stack traces for crashes on ARM. It seems gdb- multiarch does not get along with our core dumps on ARM any more. Reproducing the full apport-retrace environment is a bit complicated, so I reduced this to a very simple test case: Log into an ARM machine, like the Nexus G4, or porter- armhf.canonical.com (shedir), using schroot -c saucy-armhf. 1. create a core dump of bash: $ cd /tmp/ $ bash -c 'ulimit -c unlimited; kill -SEGV $$' 2. Run it with gdb: $ gdb --batch --ex 'file /bin/bash' --ex 'core-file core' --ex 'bt' Core was generated by `bash -c ulimit -c unlimited; kill -SEGV $$'. Program terminated with signal 11, Segmentation fault. #0 0x7f2eae349257 in kill () at ../sysdeps/unix/syscall-template.S:8181 ../sysdeps/unix/syscall-template.S: Datei oder Verzeichnis nicht gefunden. #0 0x7f2eae349257 in kill () at ../sysdeps/unix/syscall-template.S:81 #1 0x004418a1 in kill_pid () [...] There are not a lot of symbols as usually one doesn't have bash- dbgsym etc. installed, but it's clearly able to produce a stack trace. 3. Run the same with gdb-multiarch: $ gdb-multiarch --batch --ex 'file /bin/bash' --ex 'core-file core' --ex 'bt' warning: wrong size gregset struct in core file Core was generated by `bash -c ulimit -c unlimited; kill -SEGV $$'. Program terminated with signal 11, Segmentation fault. warning: wrong size gregset struct in core file #0 unavailable in ?? () #0 unavailable in ?? () PC not available FTR, Apport uses gdb-multiarch on amd64, and --ex 'set architecture arm' --ex 'set gnutarget elf32-littlearm' to generate stack traces for ARM coredumps on x86 (using binaries/libaries/debug symbols for ARM that get unpacked into a temporary directory). The full invocation looks something like this: gdb-multiarch --ex 'set architecture arm' --ex 'set gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/s/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/s' --ex 'file /tmp/s/bin/bash' --ex 'core-file CoreDump' --ex 'bt full' --batch But as gdb-multiarch does not even work on a native ARM machine for a native ARM core dump of the very same machine/OS, I guess it's something more fundamental which got broken there. The same test case on amd64 works fine BTW, i. e. gdb-multiarch can process amd64 binaries on amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1233185/+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 1373908] Re: UOA integration always creates new evolution-data-server accounts on login
It seems to work for me ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1373908 Title: UOA integration always creates new evolution-data-server accounts on login Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution-data-server” source package in Trusty: Fix Committed Bug description: * Impact: e-d-s prompts for password at login when it shouldn't * Test case: - add a google account in the unity online accounts panel - log in - you shouldn't be prompted for a calendar password * Regression potential: make sure online calendars keep working as they should -- (This is probably the source of all those 'have to enter password again after login' bugs for UOA that are floating around) Bug symtoms: 1. Have to enter password at every login again for EDS 2. loads of accounts pile up in .config/evolution/sources (a new one on every login) What's going on: ubuntu_online_accounts_bus_acquired_cb() in eds/modules/ubuntu-online-accounts/module-ubuntu-online-accounts.c gets connected to the bus-aquired signal. Note also that evolution_source_registry_load_sources() from eds/services/evolution-source-registry/evolution-source-registry.c is connected to the same signal. Given when the plugins are loaded, UOA connects to the signal first, so UOA tries to match up EDS accounts to UOA accounts before the EDS accounts (sources) have been loaded. The patch is simply to use g_signal_connect_after in module-ubuntu- online-accounts.c, which fixes the problem for me. Note though that this change means a whole bunch of code in module- ubuntu-online-accounts.c that has never run will now be run... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evolution-data-server 3.12.6-0ubuntu2 [modified: usr/lib/evolution/evolution-source-registry] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 25 22:08:54 2014 InstallationDate: Installed on 2014-09-03 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1373908/+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 1374481] Re: Nearby and News scope do not load on reboot
This is ready and QA sign-off:d in a silo, but this bug has not been marked as topblocker nor is it in the additional bug wishlist. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1374481 Title: Nearby and News scope do not load on reboot Status in The Savilerow project: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: In Progress Status in “unity-scopes-shell” package in Ubuntu RTM: New Bug description: reporduce: 1- favourite nearby and/or news 2- reboot the phone 3 - unlock and swipe to nearby/news result: Scope is blank, not even departments are loaded in nearby expected result: scope load, to see what they look like, search for something and then cancel search. This triggers a refresh and the scopes then load ok. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1374481/+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 1386208] Re: Purple overflow panel in SuruGradient theme
Fix committed into lp:ubuntu-ui-toolkit/staging at revision None, scheduled for release in ubuntu-ui-toolkit, milestone Unknown ** Changed in: ubuntu-ui-toolkit Status: In Progress = Fix Committed -- 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/1386208 Title: Purple overflow panel in SuruGradient theme Status in File Manager application for Ubuntu devices: Fix Committed Status in Ubuntu UI Toolkit: Fix Committed Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: While testing the new header on trunk, I noticed that the actions on the header are purple. They should be the same colour as the rest of the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1386208/+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 1381930] Re: [TOPBLOCKER] 7digital previews do not play in the scope
** Branch linked: lp:~stolowski/unity-scopes-api/fix-user-agent-in- preview -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: [TOPBLOCKER] 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu: In Progress Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Invalid Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+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 1382097] Re: Issues with requests sent to the rest scopes server
*** This bug is a duplicate of bug 1381930 *** https://bugs.launchpad.net/bugs/1381930 ** This bug has been marked a duplicate of bug 1381930 [TOPBLOCKER] 7digital previews do not play in the scope -- 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/1382097 Title: Issues with requests sent to the rest scopes server Status in “unity-scopes-api” package in Ubuntu: In Progress Bug description: See for example the log line here: https://pastebin.canonical.com/118745/ I'm sure it's from a recent phone image because it has the software versions inside. This is what I see strange, though: - The country parameter is broken: ...country=scopes-api=0.6.6+... - I thought the scopes-api, plugin, release, etc, should be inside an user agent parameter, not all different separated parameters in the request... it's harder to use them if they're separated, and they will even change in the future (today we have a unity8 parameter, that at some point will be unity9, etc..) Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1382097/+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 1381930] Re: [TOPBLOCKER] 7digital previews do not play in the scope
** Also affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scopes-api (Ubuntu) Status: New = In Progress ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) = Pawel Stolowski (stolowski) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: [TOPBLOCKER] 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu: In Progress Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Invalid Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+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 1389215] [NEW] Brightness controls are not working in Unity / Xorg.
Public bug reported: Brightness controls are not working in Unity / Xorg. When pressing the keys fnhome and fnend on my Lenovo W510, I see the indicator on the screen showing the level of brightness changing, so key mapping is not the problem. However, the brightness is not changing. On the kernel level, I have the single following device: # cd /sys/class/backlight # ls -l total 0 lrwxrwxrwx 1 root root 0 Nov 3 17:16 acpi_video0 - ../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0 When playing with the fnhome and fnend, the value of /sys/class/backlight/brightness changes accordingly. The screen brightness does not change. Performing: # echo 10 brightness ...does not have any effect (regardless of the value provided, 10 being just an example). WORKAROUND There is an odd workaround. Simply go to the console using CTRLALTF1 and using the fnhome and fnend keys, brightness then changes. Return to Unity / Xorg with CTRLALTF7 and the selected brightness persists. NON WORKING WORKAROUND On the web, I read that adding: Option RegistryDwords EnableBrightnessControl=1' in xorg.conf might fix the problem. I do not have an xorg and when I let the proprietary Nvidia driver generate one and add this option, X does not start anymore. Ubuntu 14.04.1 LTS with latest updates as of this writing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 4 07:38:59 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-11-01 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 4318CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4318CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4318CTO dmi.product.version: ThinkPad W510 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.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Nov 4 01:40:35 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu
[Touch-packages] [Bug 1389220] [NEW] Moving windows cause jump so that title bar is under the compiz main title bar of the desktop below the current, i.e. window unmovable
Public bug reported: Moving windows (e.g `gnome-terminal` or `gnome-system-monitor`) with mouse dragging sometimes causes the window to jump to the desktop (I have 4) below the current (where the move action takes place) and its title bar then to be placed right under the man title bar of the compiz desktop (the one which switches to the title bar of the current active window). It is then unmovable. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.16.7-031607-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Tue Nov 4 13:56:26 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3904] MachineType: LENOVO 20221 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.7-031607-generic root=ZFS=rpool2/ROOT/ubuntu-utopic-1 boot=zfs bootfs=rpool2/ROOT/ubuntu-utopic-1 rpool=rpool2 ro quiet splash SourcePackage: unity 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+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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Nov 4 12:03:28 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5557 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1389220 Title: Moving windows cause jump so that title bar is under the compiz main title bar of the desktop below the current, i.e. window unmovable Status in “unity” package in Ubuntu: New Bug description: Moving windows (e.g `gnome-terminal` or `gnome-system-monitor`) with mouse dragging sometimes causes the window to jump to the desktop (I have 4) below the current (where the move action takes place) and its title bar then to be placed right under the man title bar of the compiz desktop (the one which switches to the title bar of the current active window). It is then unmovable. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.16.7-031607-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Tue Nov 4 13:56:26 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor
[Touch-packages] [Bug 1389223] [NEW] mtp-server not running on vivid 8
Public bug reported: STEPS: 1. fresh flash vivid image 8 on mako 2. Plug mako into pc 3. Log in to the phone 4. See screen shot for result EXPECTED: I expect to see a nautilus window pop up to say it is connected that is initial empty, Then I expect to login and be able to access the data/folder structure on the mako. ACTUAL: Turns out mtp-server is not running so I get the screenshot attached and nothing else. If I run phablet-shell and then run start mtp-server and then click on Nexus4 in Nautilus it opens as expected. phablet@ubuntu-phablet:~$ ps au | grep mtp phablet 3988 0.0 0.0 4844 672 pts/0S+ 12:54 0:00 grep --color=auto mtp ** Affects: mtp (Ubuntu) Importance: Critical Assignee: Mathieu Trudel-Lapierre (mathieu-tl) Status: New ** Tags: sanity ** Attachment added: no-mtp.png https://bugs.launchpad.net/bugs/1389223/+attachment/4252836/+files/no-mtp.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1389223 Title: mtp-server not running on vivid 8 Status in “mtp” package in Ubuntu: New Bug description: STEPS: 1. fresh flash vivid image 8 on mako 2. Plug mako into pc 3. Log in to the phone 4. See screen shot for result EXPECTED: I expect to see a nautilus window pop up to say it is connected that is initial empty, Then I expect to login and be able to access the data/folder structure on the mako. ACTUAL: Turns out mtp-server is not running so I get the screenshot attached and nothing else. If I run phablet-shell and then run start mtp-server and then click on Nexus4 in Nautilus it opens as expected. phablet@ubuntu-phablet:~$ ps au | grep mtp phablet 3988 0.0 0.0 4844 672 pts/0S+ 12:54 0:00 grep --color=auto mtp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1389223/+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 1373908] Re: UOA integration always creates new evolution-data-server accounts on login
This bug was fixed in the package evolution-data-server - 3.10.4-0ubuntu1.5 --- evolution-data-server (3.10.4-0ubuntu1.5) trusty; urgency=medium * debian/patches/0001-Fix-UOA-accounts-accumulating-on-startup.patch: - Fix UOA accounts accumulating on startup., thanks Michael Blennerhassett for debugging that issue and providing the fix for it (LP: #1373908) -- Iain Lane iain.l...@canonical.com Mon, 20 Oct 2014 20:43:25 +0100 ** Changed in: evolution-data-server (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1373908 Title: UOA integration always creates new evolution-data-server accounts on login Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution-data-server” source package in Trusty: Fix Released Bug description: * Impact: e-d-s prompts for password at login when it shouldn't * Test case: - add a google account in the unity online accounts panel - log in - you shouldn't be prompted for a calendar password * Regression potential: make sure online calendars keep working as they should -- (This is probably the source of all those 'have to enter password again after login' bugs for UOA that are floating around) Bug symtoms: 1. Have to enter password at every login again for EDS 2. loads of accounts pile up in .config/evolution/sources (a new one on every login) What's going on: ubuntu_online_accounts_bus_acquired_cb() in eds/modules/ubuntu-online-accounts/module-ubuntu-online-accounts.c gets connected to the bus-aquired signal. Note also that evolution_source_registry_load_sources() from eds/services/evolution-source-registry/evolution-source-registry.c is connected to the same signal. Given when the plugins are loaded, UOA connects to the signal first, so UOA tries to match up EDS accounts to UOA accounts before the EDS accounts (sources) have been loaded. The patch is simply to use g_signal_connect_after in module-ubuntu- online-accounts.c, which fixes the problem for me. Note though that this change means a whole bunch of code in module- ubuntu-online-accounts.c that has never run will now be run... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evolution-data-server 3.12.6-0ubuntu2 [modified: usr/lib/evolution/evolution-source-registry] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 25 22:08:54 2014 InstallationDate: Installed on 2014-09-03 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1373908/+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 1382133] Re: Issue with servers with SSLv3 disabled due to Poodle
This bug was fixed in the package evolution-data-server - 3.10.4-0ubuntu1.5 --- evolution-data-server (3.10.4-0ubuntu1.5) trusty; urgency=medium * debian/patches/0001-Fix-UOA-accounts-accumulating-on-startup.patch: - Fix UOA accounts accumulating on startup., thanks Michael Blennerhassett for debugging that issue and providing the fix for it (LP: #1373908) -- Iain Lane iain.l...@canonical.com Mon, 20 Oct 2014 20:43:25 +0100 ** Changed in: evolution-data-server (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1382133 Title: Issue with servers with SSLv3 disabled due to Poodle Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution-data-server” source package in Precise: Fix Released Status in “evolution-data-server” source package in Trusty: Fix Released Bug description: [ Description ] Cannot connect to servers with SSLv3 disabled, with a message Cannot communicate securely with peer: no common encryption algorithm(s). [ QA ] Try to connect to a server with SSLv3 disabled and see if you can retrieve mail (and that it errors before the update). [ Regression potential ] Might enable a different set of SSL/TLS versions, check with different servers. [ Original report ] Evolution developers asked me to relay that there is a fix to this issue available, please see https://mail.gnome.org/archives/evolution- list/2014-October/msg00113.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1382133/+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 1373908] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1373908 Title: UOA integration always creates new evolution-data-server accounts on login Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution-data-server” source package in Trusty: Fix Released Bug description: * Impact: e-d-s prompts for password at login when it shouldn't * Test case: - add a google account in the unity online accounts panel - log in - you shouldn't be prompted for a calendar password * Regression potential: make sure online calendars keep working as they should -- (This is probably the source of all those 'have to enter password again after login' bugs for UOA that are floating around) Bug symtoms: 1. Have to enter password at every login again for EDS 2. loads of accounts pile up in .config/evolution/sources (a new one on every login) What's going on: ubuntu_online_accounts_bus_acquired_cb() in eds/modules/ubuntu-online-accounts/module-ubuntu-online-accounts.c gets connected to the bus-aquired signal. Note also that evolution_source_registry_load_sources() from eds/services/evolution-source-registry/evolution-source-registry.c is connected to the same signal. Given when the plugins are loaded, UOA connects to the signal first, so UOA tries to match up EDS accounts to UOA accounts before the EDS accounts (sources) have been loaded. The patch is simply to use g_signal_connect_after in module-ubuntu- online-accounts.c, which fixes the problem for me. Note though that this change means a whole bunch of code in module- ubuntu-online-accounts.c that has never run will now be run... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evolution-data-server 3.12.6-0ubuntu2 [modified: usr/lib/evolution/evolution-source-registry] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 25 22:08:54 2014 InstallationDate: Installed on 2014-09-03 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1373908/+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
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Out of 90-somethign users this bug only seems to affect one user. (Of course, that user happens to be one of my bosses...) Because the problem is hard to reproduce I have a feeling that it'lll be difficult to track down and fix. Michael On 11/03/2014 05:18 PM, Bruce MacNaughton wrote: msp3k - I got the same thing but just ran unity --replace in a terminal window I had left open on the desktop. I didn't check to see if could open a terminal. But running unity --replace from the desktop (w/o dash, launcher, panel, menu bar, etc.) resulted in getting them all back. It was ugly - many errors but it worked. Everything seems fine afterwards. Any idea when I can specifically target the software for an update? The fix clearly hasn't hit me yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1383702] Re: [TOPBLOCKER] Welcome Wizard: Passphrase has no obvious way to continue
This bug was fixed in the package ubuntu-system-settings - 0.3+14.10.20141103~rtm-0ubuntu1 --- ubuntu-system-settings (0.3+14.10.20141103~rtm-0ubuntu1) 14.09; urgency=low [ Michael Terry ] * Add a Continue button when choosing a passphrase. And fix a few other design nits with choosing a password. [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 03 Nov 2014 19:58:15 + ** Changed in: ubuntu-system-settings (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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383702 Title: [TOPBLOCKER] Welcome Wizard: Passphrase has no obvious way to continue Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu RTM: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: STEPS: 1. Flash a fresh image 2. Select a language 3. Select passphrase 4. Add a passphrase EXPECTED: Every other page has a back and continue/skip buttons, I expect to see a continue button on the page ACTUAL: You have no obvious way to continue, there is no text saying to hit enter after the passphrase is completed nor is there a continue button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1383702/+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 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
I succeeded in rebasing the patch for 5.3.0, although with some level of uncertainty when doing that for example with QNetworkManagerEngine::deviceConnectionsChanged not existing in 5.3.0. It applies now and seems to build also successfully, although as of now the armhf build is still ongoing (at https://launchpad.net/~ci-train- ppa-service/+archive/ubuntu-rtm/landing-022). When armhf has finished, it'd be worth testing. lp:~kubuntu-packagers /kubuntu-packaging/qtbase-opensource-src_530_networkmanagerfixes is updated with the rebase. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+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 1374481] Re: [TOPBLOCKER] Nearby and News scope do not load on reboot
** Summary changed: - Nearby and News scope do not load on reboot + [TOPBLOCKER] Nearby and News scope do not load on reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1374481 Title: [TOPBLOCKER] Nearby and News scope do not load on reboot Status in The Savilerow project: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: In Progress Status in “unity-scopes-shell” package in Ubuntu RTM: New Bug description: reporduce: 1- favourite nearby and/or news 2- reboot the phone 3 - unlock and swipe to nearby/news result: Scope is blank, not even departments are loaded in nearby expected result: scope load, to see what they look like, search for something and then cancel search. This triggers a refresh and the scopes then load ok. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1374481/+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 1071722] Re: Mouse cursor duplicated in dual screen setup
I seem to have the same problem. I have a HP EliteBook 840 G1 with two external dell monitors (one horizontal and one vertical - rotated counter clockwise - although I don't think that has anything to do with it since I tried to set them all horizontal and the coursors were still doubled). The main cursor is correctly aligned and the shadow cursor is the arrow one rotated 90deg counter clockwise. The shadow cursor dissapears once the monitor are disconnected (they are connected through a docking station - the landscape one using VGA and the vertical one using HDMI). Also, the shadow cursor doesn't show on the middle (vertical, connected through HDMI) monitor. Ubuntu: 14.10 (utopic) installed 2 days ago with all updates installed :-) -- 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/1071722 Title: Mouse cursor duplicated in dual screen setup Status in “xorg” package in Ubuntu: Confirmed Bug description: I have attached a external monitor to my laptop. When I my the mouse from the primary display (my laptop screen) to the secondary display (external monitor), the mouse cursor image gets duplicated. On the primary screen it freezes its last location (so moving the mouse more quickly, makes sure that the mouse image is clearly visible) and on the secondary screen it keeps on performing as it should. When I move the mouse back to the primary screen, the duplicated mouse image disappears and everything works like normal again. When the duplication is 'active' the frozen mouse, still changes it's image (pointing finger, 'text thingy', resizing arrows, etc.) when my mouse on the secondary screen is hovering over elements that makes the image change. Since Ubuntu 12.10 I use the xserver-xorg-video-radeon package, as fglrx does not support my ATI video card (HD 3650) anymore. So I do not know whether the problem is also existing pre-12.10. This is not reproducible in the live environment of 13.10 and 14.04, but is in the installed ones. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-ati (not installed) - xserver-xorg-video-radeon (1:6.99.99~git20120913.8637f772-0ubuntu1) ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Oct 26 12:46:13 2012 InstallationDate: Installed on 2012-10-19 (6 days ago) InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-11-20 (44 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.12.4-031204-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1071722/+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 1071722] Re: Mouse cursor duplicated in dual screen setup
PS. I tried to run apport-collect, but it said You are not a reporter of this bug :-( -- 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/1071722 Title: Mouse cursor duplicated in dual screen setup Status in “xorg” package in Ubuntu: Confirmed Bug description: I have attached a external monitor to my laptop. When I my the mouse from the primary display (my laptop screen) to the secondary display (external monitor), the mouse cursor image gets duplicated. On the primary screen it freezes its last location (so moving the mouse more quickly, makes sure that the mouse image is clearly visible) and on the secondary screen it keeps on performing as it should. When I move the mouse back to the primary screen, the duplicated mouse image disappears and everything works like normal again. When the duplication is 'active' the frozen mouse, still changes it's image (pointing finger, 'text thingy', resizing arrows, etc.) when my mouse on the secondary screen is hovering over elements that makes the image change. Since Ubuntu 12.10 I use the xserver-xorg-video-radeon package, as fglrx does not support my ATI video card (HD 3650) anymore. So I do not know whether the problem is also existing pre-12.10. This is not reproducible in the live environment of 13.10 and 14.04, but is in the installed ones. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-ati (not installed) - xserver-xorg-video-radeon (1:6.99.99~git20120913.8637f772-0ubuntu1) ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Oct 26 12:46:13 2012 InstallationDate: Installed on 2012-10-19 (6 days ago) InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-11-20 (44 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 Tags: saucy Uname: Linux 3.12.4-031204-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1071722/+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 1389195] Re: Fitbit section in Dashboard goes to an empty screen when tapped
This is changing imminently, this was put in merely as a placeholder -- 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/1389195 Title: Fitbit section in Dashboard goes to an empty screen when tapped Status in “unity8” package in Ubuntu: Invalid Bug description: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. 2. Tap anywhere in the section, which is quite easy to do by accident. What happens: * You end up on a Dashboard screen that is completely empty. * If you didn't notice that a Back button has appeared next to Dashboard, you might reasonably conclude that the Dashboard has broken. What should happen: either * If you have no Fitbit account, the section should not go to a separate screen, or * if it does go to a separate screen, it should not be called Dashboard and should not be empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389195/+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 1389204] Re: No Calls Today and No Messages Today go to screens with empty buttons
Moving to hanloon ** Changed in: unity8 (Ubuntu) Status: New = Invalid -- 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/1389204 Title: No Calls Today and No Messages Today go to screens with empty buttons Status in “unity8” package in Ubuntu: Invalid Bug description: Ubuntu 14.10 r6 0. If you have made/sent/received any calls or messages today, wipe the phone. 1. Go to the Dashboard screen. 2. Tap No Calls Today or No Messages Today. 3. Tap the button. What happens: 2. You end up on a screen labelled Dashboard containing the text No Calls Today or No Messages Today and an empty button. 3. The screen goes black except for a close button in the corner. What should happen: either 2. Nothing happens, you don't end up on a separate screen; or 3. the screen does not contain a button that goes nowhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389204/+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 1389195] Re: Fitbit section in Dashboard goes to an empty screen when tapped
Also nothing to do with unity8, marking invalid ** Changed in: unity8 (Ubuntu) Status: New = Invalid -- 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/1389195 Title: Fitbit section in Dashboard goes to an empty screen when tapped Status in “unity8” package in Ubuntu: Invalid Bug description: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. 2. Tap anywhere in the section, which is quite easy to do by accident. What happens: * You end up on a Dashboard screen that is completely empty. * If you didn't notice that a Back button has appeared next to Dashboard, you might reasonably conclude that the Dashboard has broken. What should happen: either * If you have no Fitbit account, the section should not go to a separate screen, or * if it does go to a separate screen, it should not be called Dashboard and should not be empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389195/+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 1389192] Re: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action
This is changing imminently, this text was merely put in as a placeholder. -- 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/1389192 Title: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action Status in “unity8” package in Ubuntu: Invalid Bug description: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. What you see: Please setup an account in system settings What's wrong with this: A. Setup is a noun, so Please setup is ungrammatical. B. System Settings is a proper noun, so system settings is miscapitalized. C. A caption is a complete sentence (sometimes more than one), and this sentence is missing its period. D. There's no explanation of why you *should* set up an account. E. In system settings is a useless direction. The word Fitbit does not appear anywhere on the System Settings screen, leaving you lost. F. Sending people to System Settings is the wrong thing to do in the first place: they might already have a Fitbit account set up. What you should see: something like Track your fitness activities here using a Fitbit account. ( Use Fitbit… ) ( No Thanks ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389192/+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 1389192] Re: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action
Also nothing to do with unity8, marking invalid ** Changed in: unity8 (Ubuntu) Status: New = Invalid -- 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/1389192 Title: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action Status in “unity8” package in Ubuntu: Invalid Bug description: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. What you see: Please setup an account in system settings What's wrong with this: A. Setup is a noun, so Please setup is ungrammatical. B. System Settings is a proper noun, so system settings is miscapitalized. C. A caption is a complete sentence (sometimes more than one), and this sentence is missing its period. D. There's no explanation of why you *should* set up an account. E. In system settings is a useless direction. The word Fitbit does not appear anywhere on the System Settings screen, leaving you lost. F. Sending people to System Settings is the wrong thing to do in the first place: they might already have a Fitbit account set up. What you should see: something like Track your fitness activities here using a Fitbit account. ( Use Fitbit… ) ( No Thanks ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389192/+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 1311316] Re: After locking screen there is no input field to type password for unlock
This bug affects me. And it is very annoying. Yesterday, this bug acted different. When I went to login, the user name was root, which I was not logged in as. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1389220] Re: Moving windows cause jump so that title bar is under the compiz main title bar of the desktop below the current, i.e. window unmovable
** Description changed: Moving windows (e.g `gnome-terminal` or `gnome-system-monitor`) with mouse dragging sometimes causes the window to jump to the desktop (I have 4) below the current (where the move action takes place) and its title bar then to be placed right under the man title bar of the compiz desktop (the one which switches to the title bar of the current active window). It is then unmovable. + The jump occurs when the lower margin of the titlebar reaches ~2 cm over + the lower screen border. When I click on the desktop switcher applet I + can see that the window is display like its titlebar would still be on + the upper screen. + + The mouse is not movable below the lower screen border (I can still see + the tip of the cursor at the buttom). Changing the resolution doesn't + change the behavior. It occurs on both desktops which are on the screen + of my laptop as well as on screen which are attached via D-SUB. + ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.16.7-031607-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair .tmp.unity.support.test.0: - + ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Tue Nov 4 13:56:26 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:3904] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:3904] MachineType: LENOVO 20221 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.7-031607-generic root=ZFS=rpool2/ROOT/ubuntu-utopic-1 boot=zfs bootfs=rpool2/ROOT/ubuntu-utopic-1 rpool=rpool2 ro quiet splash SourcePackage: unity 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+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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Nov 4 12:03:28 2014 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id5557 - vendor CMN + product id5557 + vendor CMN xserver.version: 2:1.16.0-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1389220 Title: Moving windows cause jump so that title bar is under the compiz main title bar of the desktop below the current, i.e. window unmovable Status in “unity” package in Ubuntu: New Bug description: Moving windows (e.g `gnome-terminal` or `gnome-system-monitor`) with mouse dragging sometimes causes the window to jump to the desktop (I have 4) below the current (where the move action takes place) and its title bar then to be placed right under the man title bar of the compiz desktop (the one which switches to the title bar of the current active window). It is then unmovable. The jump occurs when the lower margin of the titlebar reaches ~2 cm over
[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
To replicate my rebasing environment see http://pastebin.ubuntu.com/8819119/. I originally did quilt push -f on the last patch and then manually fixed the codebase until I had gone through all the rejected parts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+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 1374481] Re: [TOPBLOCKER] Nearby and News scope do not load on reboot
This bug was fixed in the package unity-scopes-shell - 0.5.4+14.10.20141029.1~rtm-0ubuntu1 --- unity-scopes-shell (0.5.4+14.10.20141029.1~rtm-0ubuntu1) 14.09; urgency=low [ Pete Woods ] * Wait for location data at startup (with 1 second timeout) (LP: #1374481) -- Ubuntu daily release ps-jenk...@lists.canonical.com Wed, 29 Oct 2014 13:16:23 + ** Changed in: unity-scopes-shell (Ubuntu RTM) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1374481 Title: [TOPBLOCKER] Nearby and News scope do not load on reboot Status in The Savilerow project: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: In Progress Status in “unity-scopes-shell” package in Ubuntu RTM: Fix Released Bug description: reporduce: 1- favourite nearby and/or news 2- reboot the phone 3 - unlock and swipe to nearby/news result: Scope is blank, not even departments are loaded in nearby expected result: scope load, to see what they look like, search for something and then cancel search. This triggers a refresh and the scopes then load ok. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1374481/+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 1389201] [NEW] Error calling EVIOCSKEYCODE on device node: Invalid argument
You have been subscribed to a public bug: In dmesg I can see these two error lines [7.375599] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022d, key code 418): Invalid argument [7.375605] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022e, key code 419): Invalid argument res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error) No idea what these two mean and how we can fix this. Any clues? ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael-heuberger 2178 F pulseaudio /dev/snd/controlC2: michael-heuberger 2178 F pulseaudio /dev/snd/controlC0: michael-heuberger 2178 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 5 00:55:34 2014 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages utopic -- Error calling EVIOCSKEYCODE on device node: Invalid argument https://bugs.launchpad.net/bugs/1389201 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away
Jerry, If you still have that crash file, install unity debug symbols (see https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages) and do: apport-unpack /var/crash/_usr_bin_compiz.1000.crash /tmp/unity-crash Then: gdb /usr/bin/compiz /tmp/unity-crash/CoreDump At this point, do: bt full And post the output here -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1366351 Title: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings- daemon goes away Status in Compiz: Invalid Status in Unity: Fix Committed Status in “compiz” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: Compiz crashes when unity-settings-daemon goes away. Simple reproducer: killall -SEGV unity-settings-daemon. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 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: Sat Sep 6 10:48:43 2014 Disassembly: = 0x0: Cannot access memory at address 0x0 DistUpgraded: 2014-09-01 18:03:23,330 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:04a1] InstallationDate: Installed on 2014-03-24 (166 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: MSI MS-7640 ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LD_LIBRARY_PATH=set LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic root=UUID=2696ea28-d88b-431c-a1fa-1e0f297ee664 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to utopic on 2014-09-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.15 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 890FXA-GD70 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.15:bd10/31/2012:svnMSI:pnMS-7640:pvr1.0:rvnMSI:rn890FXA-GD70(MS-7640):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7640 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Sep 6 10:48:05 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so,
[Touch-packages] [Bug 1389232] Re: failed dashboard test case: unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
** Attachment added: Screenshot from 2014-11-04 08:42:43.png
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389232/+attachment/4252841/+files/Screenshot%20from%202014-11-04%2008%3A42%3A43.png
--
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/1389232
Title:
failed dashboard test case:
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
Status in “unity8” package in Ubuntu:
New
Bug description:
http://dashboard.ubuntu-
ci:8080/smokeng/utopic/touch_stable/krillin/141:20141104:20141028-3ca60be/661/unity8/232676/
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
test-log: {{{
07:08:45.747 WARNING testcase:115 - No tracing available - install the
python-autopilot-trace package!
07:08:45.759 WARNING testcase:162 - Process manager backend unavailable,
application snapshot support disabled.
07:08:45.793 INFO process_helpers:151 - Starting job unity8 with arguments
('QT_LOAD_TESTABILITY=1',).
07:08:46.254 INFO process_helpers:159 - unity8 start/running, process 14617
07:09:01.266 INFO process_helpers:95 - Greeter unlocked, continuing.
07:09:01.284 INFO process_helpers:207 - Stoping job unity8-dash.
07:09:01.502 INFO process_helpers:215 - unity8-dash stop/waiting
07:09:01.543 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:09:01.566 INFO process_helpers:151 - Starting job unity8-dash with
arguments ('BINARY=/usr/bin/unity8-dash', 'QT_LOAD_TESTABILITY=1',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks').
07:09:01.657 INFO process_helpers:159 - unity8-dash start/running, process
14839
07:09:28.834 ERROR proxies:410 - Introspect error on
:1.367:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the network
connection was broken.
07:09:28.837 DEBUG proxies:413 - Executing introspect queue due to error
07:09:40.166 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:42.668 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (392 items). This is likely to be slow. You may want
to consider optimising your query to return fewer items.
07:09:49.835 DEBUG _uinput:470 - Tapping at: 364,86
07:09:54.196 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:56.195 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (532 items). This is likely to be slow. You may want
to consider optimising your query to return fewer items.
07:10:06.466 INFO logging:45 - TextField: Write into the text field.
Arguments ('Test',). Keyword arguments: {}.
07:10:06.534 DEBUG _common:45 - Moving to object's globalRect coordinates.
07:10:06.535 DEBUG _uinput:470 - Tapping at: 309,86
07:10:06.730 INFO logging:45 - TextField: Clear the text field. Arguments ().
Keyword arguments: {}.
07:10:06.786 DEBUG _uinput:195 - Typing text 'Test'
07:10:06.787 DEBUG _uinput:57 - Pressing KEY_LEFTSHIFT (42).
07:10:06.888 DEBUG _uinput:57 - Pressing T (20).
07:10:06.992 DEBUG _uinput:88 - Releasing T (20).
07:10:07.095 DEBUG _uinput:88 - Releasing KEY_LEFTSHIFT (42).
07:10:07.198 DEBUG _uinput:57 - Pressing e (18).
07:10:07.301 DEBUG _uinput:88 - Releasing e (18).
07:10:07.404 DEBUG _uinput:57 - Pressing s (31).
07:10:07.506 DEBUG _uinput:88 - Releasing s (31).
07:10:07.608 DEBUG _uinput:57 - Pressing t (20).
07:10:07.711 DEBUG _uinput:88 - Releasing t (20).
07:10:23.778 INFO process_helpers:207 - Stoping job unity8-dash.
07:10:24.078 INFO process_helpers:215 - unity8-dash stop/waiting
07:10:24.082 INFO process_helpers:207 - Stoping job unity8.
07:10:25.375 INFO process_helpers:215 - unity8 stop/waiting
}}}
Traceback (most recent call last):
File /home/phablet/autopilot/unity8/shell/tests/test_emulators.py, line
54, in test_search
self.dash.enter_search_query('Test')
File /home/phablet/autopilot/unity8/shell/emulators/dash.py, line 156, in
enter_search_query
self.select_single(objectName=processingIndicator).visible.wait_for(False)
File /usr/lib/python3/dist-packages/autopilot/introspection/types.py,
line 178, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickRectangle.visible failed:
False != dbus.Boolean(True, variant_level=1)
To manage notifications about this bug go
[Touch-packages] [Bug 1389232] [NEW] failed dashboard test case: unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
Public bug reported:
http://dashboard.ubuntu-
ci:8080/smokeng/utopic/touch_stable/krillin/141:20141104:20141028-3ca60be/661/unity8/232676/
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
test-log: {{{
07:08:45.747 WARNING testcase:115 - No tracing available - install the
python-autopilot-trace package!
07:08:45.759 WARNING testcase:162 - Process manager backend unavailable,
application snapshot support disabled.
07:08:45.793 INFO process_helpers:151 - Starting job unity8 with arguments
('QT_LOAD_TESTABILITY=1',).
07:08:46.254 INFO process_helpers:159 - unity8 start/running, process 14617
07:09:01.266 INFO process_helpers:95 - Greeter unlocked, continuing.
07:09:01.284 INFO process_helpers:207 - Stoping job unity8-dash.
07:09:01.502 INFO process_helpers:215 - unity8-dash stop/waiting
07:09:01.543 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:09:01.566 INFO process_helpers:151 - Starting job unity8-dash with arguments
('BINARY=/usr/bin/unity8-dash', 'QT_LOAD_TESTABILITY=1',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks').
07:09:01.657 INFO process_helpers:159 - unity8-dash start/running, process 14839
07:09:28.834 ERROR proxies:410 - Introspect error on
:1.367:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the network
connection was broken.
07:09:28.837 DEBUG proxies:413 - Executing introspect queue due to error
07:09:40.166 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:42.668 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (392 items). This is likely to be slow. You may want to
consider optimising your query to return fewer items.
07:09:49.835 DEBUG _uinput:470 - Tapping at: 364,86
07:09:54.196 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:56.195 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (532 items). This is likely to be slow. You may want to
consider optimising your query to return fewer items.
07:10:06.466 INFO logging:45 - TextField: Write into the text field. Arguments
('Test',). Keyword arguments: {}.
07:10:06.534 DEBUG _common:45 - Moving to object's globalRect coordinates.
07:10:06.535 DEBUG _uinput:470 - Tapping at: 309,86
07:10:06.730 INFO logging:45 - TextField: Clear the text field. Arguments ().
Keyword arguments: {}.
07:10:06.786 DEBUG _uinput:195 - Typing text 'Test'
07:10:06.787 DEBUG _uinput:57 - Pressing KEY_LEFTSHIFT (42).
07:10:06.888 DEBUG _uinput:57 - Pressing T (20).
07:10:06.992 DEBUG _uinput:88 - Releasing T (20).
07:10:07.095 DEBUG _uinput:88 - Releasing KEY_LEFTSHIFT (42).
07:10:07.198 DEBUG _uinput:57 - Pressing e (18).
07:10:07.301 DEBUG _uinput:88 - Releasing e (18).
07:10:07.404 DEBUG _uinput:57 - Pressing s (31).
07:10:07.506 DEBUG _uinput:88 - Releasing s (31).
07:10:07.608 DEBUG _uinput:57 - Pressing t (20).
07:10:07.711 DEBUG _uinput:88 - Releasing t (20).
07:10:23.778 INFO process_helpers:207 - Stoping job unity8-dash.
07:10:24.078 INFO process_helpers:215 - unity8-dash stop/waiting
07:10:24.082 INFO process_helpers:207 - Stoping job unity8.
07:10:25.375 INFO process_helpers:215 - unity8 stop/waiting
}}}
Traceback (most recent call last):
File /home/phablet/autopilot/unity8/shell/tests/test_emulators.py, line 54,
in test_search
self.dash.enter_search_query('Test')
File /home/phablet/autopilot/unity8/shell/emulators/dash.py, line 156, in
enter_search_query
self.select_single(objectName=processingIndicator).visible.wait_for(False)
File /usr/lib/python3/dist-packages/autopilot/introspection/types.py, line
178, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickRectangle.visible failed:
False != dbus.Boolean(True, variant_level=1)
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Tags: qa-broken-test qa-daily-testing
--
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/1389232
Title:
failed dashboard test case:
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
Status in “unity8” package in Ubuntu:
New
Bug description:
http://dashboard.ubuntu-
ci:8080/smokeng/utopic/touch_stable/krillin/141:20141104:20141028-3ca60be/661/unity8/232676/
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
test-log: {{{
07:08:45.747
[Touch-packages] [Bug 1389201] Re: Error calling EVIOCSKEYCODE on device node: Invalid argument
This doesn't seem like a kernel issue. ** Package changed: linux (Ubuntu) = systemd (Ubuntu) -- 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/1389201 Title: Error calling EVIOCSKEYCODE on device node: Invalid argument Status in “systemd” package in Ubuntu: Confirmed Bug description: In dmesg I can see these two error lines [7.375599] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022d, key code 418): Invalid argument [7.375605] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022e, key code 419): Invalid argument res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error) No idea what these two mean and how we can fix this. Any clues? ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael-heuberger 2178 F pulseaudio /dev/snd/controlC2: michael-heuberger 2178 F pulseaudio /dev/snd/controlC0: michael-heuberger 2178 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 5 00:55:34 2014 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1389201/+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 1055166] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... fr
** Changed in: compiz Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1055166 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... from unity::UnityWindow::DrawWindowDecoration Status in Compiz: Fix Released Status in Mesa: Invalid Status in Unity: Invalid Status in Unity 6.0 series: Won't Fix Status in “compiz” package in Ubuntu: Fix Released Status in “mesa” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: See also bug 927168, which was resolved recently. Compiz crashed after installed something via Synaptic and just it installed that i want it crashed coz i want to see the black installition screen ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 6.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Sun Sep 23 21:36:37 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f031d57d73c:movntdq %xmm1,-0x10(%rdi) PC (0x7f031d57d73c) ok source %xmm1 ok destination -0x10(%rdi) (0x108d5b170) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, unsigned long, boost::functionbool (unsigned long) const, boost::functionvoid (unsigned long) const, boost::functionvoid () const, compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so TfpTexture::bindTexImage(unsigned long const) () from /usr/lib/compiz/libopengl.so Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: gnome-session[1561]: WARNING: Application 'compiz.desktop' killed by signal 11 gnome-session[1561]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[1561]: CRITICAL: We failed, but the fail whale is dead. Sorry To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1055166/+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 1389235] Re: failing dashboard test case: unity8.shell.tests.test_notifications.InteractiveNotificationBase.test_interactive(Native Device)
From the looks of the screenshot unity8 might have failed to load or
crashed
--
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/1389235
Title:
failing dashboard test case:
unity8.shell.tests.test_notifications.InteractiveNotificationBase.test_interactive(Native
Device)
Status in “unity8” package in Ubuntu:
New
Bug description:
http://dashboard.ubuntu-
ci:8080/smokeng/utopic/touch_stable/krillin/141:20141104:20141028-3ca60be/661/unity8/232697/
failing dashboard test case:
unity8.shell.tests.test_notifications.InteractiveNotificationBase.test_interactive(Native
Device)
test-log: {{{
07:19:20.641 WARNING testcase:115 - No tracing available - install the
python-autopilot-trace package!
07:19:20.650 WARNING testcase:162 - Process manager backend unavailable,
application snapshot support disabled.
07:19:20.660 WARNING utilities:263 - WARNING: in file
/home/phablet/autopilot/unity8/shell/tests/__init__.py, line 164 in setUp
This function is deprecated. Please use 'the Touch class to instantiate a
device object' instead.
07:19:20.827 INFO __init__:268 - Lib path is
'/usr/lib/arm-linux-gnueabihf/unity8', binary path is '/usr/bin/unity8'
07:19:20.828 INFO __init__:346 - Setting up LightDM mock type 'single'
07:19:20.905 INFO __init__:355 - New library path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single
07:19:20.945 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:19:20.966 INFO __init__:317 - Starting unity
07:19:21.036 INFO process_helpers:151 - Starting job unity8 with arguments
('BINARY=/usr/bin/unity8', 'ARGS=',
'LD_LIBRARY_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single',
'XDG_DATA_DIRS=/usr/share/unity8/mocks/data:/usr/share/ubuntu-touch:/usr/local/share:/usr/share',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks',
'QT_LOAD_TESTABILITY=1').
07:19:21.420 INFO process_helpers:159 - unity8 start/running, process 26926
07:19:26.293 ERROR proxies:410 - Introspect error on
:1.936:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout
by message bus)
07:19:26.294 DEBUG proxies:413 - Executing introspect queue due to error
07:19:26.404 ERROR proxies:410 - Introspect error on
:1.938:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout
by message bus)
07:19:26.405 DEBUG proxies:413 - Executing introspect queue due to error
07:19:27.914 INFO __init__:330 - Stopping unity
07:19:31.430 INFO __init__:246 - Resetting upstart env QT_LOAD_TESTABILITY to
None
}}}
Traceback (most recent call last):
File /home/phablet/autopilot/unity8/shell/tests/test_notifications.py,
line 127, in test_interactive
unity_proxy = self.launch_unity()
File /home/phablet/autopilot/unity8/shell/tests/__init__.py, line 299, in
launch_unity
self.unity_geometry_args,
File /home/phablet/autopilot/unity8/shell/tests/__init__.py, line 327, in
_launch_unity_with_upstart
return process_helpers.restart_unity_with_testability(*all_args)
File /home/phablet/autopilot/unity8/process_helpers.py, line 122, in
restart_unity_with_testability
return restart_unity(*args)
File /home/phablet/autopilot/unity8/process_helpers.py, line 139, in
restart_unity
return _get_unity_proxy_object(pid)
File /home/phablet/autopilot/unity8/process_helpers.py, line 248, in
_get_unity_proxy_object
emulator_base=emulators.UnityEmulatorBase,
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 171, in get_proxy_object_for_existing_process
process
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 324, in _find_matching_connections
in connections
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 325, in listcomp
if connection_matcher((bus, c))
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 292, in _filter_runner
for f in filter_list
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 292, in genexpr
for f in filter_list
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 775, in matches
eligible_pids = [pid] + _get_child_pids(pid)
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 677, in __call__
p.pid for p in psutil.Process(pid).get_children(recursive=True)
File /usr/lib/python3/dist-packages/psutil/__init__.py, line 296, in
__init__
self._init(pid
[Touch-packages] [Bug 1389235] [NEW] failing dashboard test case: unity8.shell.tests.test_notifications.InteractiveNotificationBase.test_interactive(Native Device)
Public bug reported:
http://dashboard.ubuntu-
ci:8080/smokeng/utopic/touch_stable/krillin/141:20141104:20141028-3ca60be/661/unity8/232697/
failing dashboard test case:
unity8.shell.tests.test_notifications.InteractiveNotificationBase.test_interactive(Native
Device)
test-log: {{{
07:19:20.641 WARNING testcase:115 - No tracing available - install the
python-autopilot-trace package!
07:19:20.650 WARNING testcase:162 - Process manager backend unavailable,
application snapshot support disabled.
07:19:20.660 WARNING utilities:263 - WARNING: in file
/home/phablet/autopilot/unity8/shell/tests/__init__.py, line 164 in setUp
This function is deprecated. Please use 'the Touch class to instantiate a
device object' instead.
07:19:20.827 INFO __init__:268 - Lib path is
'/usr/lib/arm-linux-gnueabihf/unity8', binary path is '/usr/bin/unity8'
07:19:20.828 INFO __init__:346 - Setting up LightDM mock type 'single'
07:19:20.905 INFO __init__:355 - New library path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single
07:19:20.945 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:19:20.966 INFO __init__:317 - Starting unity
07:19:21.036 INFO process_helpers:151 - Starting job unity8 with arguments
('BINARY=/usr/bin/unity8', 'ARGS=',
'LD_LIBRARY_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single',
'XDG_DATA_DIRS=/usr/share/unity8/mocks/data:/usr/share/ubuntu-touch:/usr/local/share:/usr/share',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks',
'QT_LOAD_TESTABILITY=1').
07:19:21.420 INFO process_helpers:159 - unity8 start/running, process 26926
07:19:26.293 ERROR proxies:410 - Introspect error on
:1.936:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by
message bus)
07:19:26.294 DEBUG proxies:413 - Executing introspect queue due to error
07:19:26.404 ERROR proxies:410 - Introspect error on
:1.938:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by
message bus)
07:19:26.405 DEBUG proxies:413 - Executing introspect queue due to error
07:19:27.914 INFO __init__:330 - Stopping unity
07:19:31.430 INFO __init__:246 - Resetting upstart env QT_LOAD_TESTABILITY to
None
}}}
Traceback (most recent call last):
File /home/phablet/autopilot/unity8/shell/tests/test_notifications.py, line
127, in test_interactive
unity_proxy = self.launch_unity()
File /home/phablet/autopilot/unity8/shell/tests/__init__.py, line 299, in
launch_unity
self.unity_geometry_args,
File /home/phablet/autopilot/unity8/shell/tests/__init__.py, line 327, in
_launch_unity_with_upstart
return process_helpers.restart_unity_with_testability(*all_args)
File /home/phablet/autopilot/unity8/process_helpers.py, line 122, in
restart_unity_with_testability
return restart_unity(*args)
File /home/phablet/autopilot/unity8/process_helpers.py, line 139, in
restart_unity
return _get_unity_proxy_object(pid)
File /home/phablet/autopilot/unity8/process_helpers.py, line 248, in
_get_unity_proxy_object
emulator_base=emulators.UnityEmulatorBase,
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 171, in get_proxy_object_for_existing_process
process
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 324, in _find_matching_connections
in connections
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 325, in listcomp
if connection_matcher((bus, c))
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 292, in _filter_runner
for f in filter_list
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 292, in genexpr
for f in filter_list
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 775, in matches
eligible_pids = [pid] + _get_child_pids(pid)
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 677, in __call__
p.pid for p in psutil.Process(pid).get_children(recursive=True)
File /usr/lib/python3/dist-packages/psutil/__init__.py, line 296, in
__init__
self._init(pid)
File /usr/lib/python3/dist-packages/psutil/__init__.py, line 331, in _init
raise NoSuchProcess(pid, None, msg)
psutil.NoSuchProcess: no process found with pid 26926
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Tags: qa-broken-test qa-daily-testing
** Attachment added: Screenshot from 2014-11-04 08:43:18.png
https://bugs.launchpad.net/bugs/1389235/+attachment/4252844/+files/Screenshot%20from%202014-11-04%2008%3A43%3A18.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
[Touch-packages] [Bug 1389239] [NEW] apparmor is uninstalled when deploying icehouse nova-compute on Precise
Public bug reported: When doing juju deploy nova-compute for icehouse with the latest charm on Ubuntu Precise, the apparmor package is uninstalled. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Affects: apparmor (Ubuntu Precise) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1389239 Title: apparmor is uninstalled when deploying icehouse nova-compute on Precise Status in “apparmor” package in Ubuntu: New Status in “libvirt” package in Ubuntu: New Status in “apparmor” source package in Precise: New Status in “libvirt” source package in Precise: New Bug description: When doing juju deploy nova-compute for icehouse with the latest charm on Ubuntu Precise, the apparmor package is uninstalled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1389239/+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 1389232] Re: failed dashboard test case: unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
This is because the dashboard scope does not finish searching within the
10s timeout, it's a known bug on the scope side. We could, in theory,
increase the timeout, but it would not really help.
** Changed in: unity8 (Ubuntu)
Status: New = Incomplete
--
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/1389232
Title:
failed dashboard test case:
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
Status in “unity8” package in Ubuntu:
Incomplete
Bug description:
http://dashboard.ubuntu-
ci:8080/smokeng/utopic/touch_stable/krillin/141:20141104:20141028-3ca60be/661/unity8/232676/
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
test-log: {{{
07:08:45.747 WARNING testcase:115 - No tracing available - install the
python-autopilot-trace package!
07:08:45.759 WARNING testcase:162 - Process manager backend unavailable,
application snapshot support disabled.
07:08:45.793 INFO process_helpers:151 - Starting job unity8 with arguments
('QT_LOAD_TESTABILITY=1',).
07:08:46.254 INFO process_helpers:159 - unity8 start/running, process 14617
07:09:01.266 INFO process_helpers:95 - Greeter unlocked, continuing.
07:09:01.284 INFO process_helpers:207 - Stoping job unity8-dash.
07:09:01.502 INFO process_helpers:215 - unity8-dash stop/waiting
07:09:01.543 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:09:01.566 INFO process_helpers:151 - Starting job unity8-dash with
arguments ('BINARY=/usr/bin/unity8-dash', 'QT_LOAD_TESTABILITY=1',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks').
07:09:01.657 INFO process_helpers:159 - unity8-dash start/running, process
14839
07:09:28.834 ERROR proxies:410 - Introspect error on
:1.367:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the network
connection was broken.
07:09:28.837 DEBUG proxies:413 - Executing introspect queue due to error
07:09:40.166 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:42.668 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (392 items). This is likely to be slow. You may want
to consider optimising your query to return fewer items.
07:09:49.835 DEBUG _uinput:470 - Tapping at: 364,86
07:09:54.196 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:56.195 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (532 items). This is likely to be slow. You may want
to consider optimising your query to return fewer items.
07:10:06.466 INFO logging:45 - TextField: Write into the text field.
Arguments ('Test',). Keyword arguments: {}.
07:10:06.534 DEBUG _common:45 - Moving to object's globalRect coordinates.
07:10:06.535 DEBUG _uinput:470 - Tapping at: 309,86
07:10:06.730 INFO logging:45 - TextField: Clear the text field. Arguments ().
Keyword arguments: {}.
07:10:06.786 DEBUG _uinput:195 - Typing text 'Test'
07:10:06.787 DEBUG _uinput:57 - Pressing KEY_LEFTSHIFT (42).
07:10:06.888 DEBUG _uinput:57 - Pressing T (20).
07:10:06.992 DEBUG _uinput:88 - Releasing T (20).
07:10:07.095 DEBUG _uinput:88 - Releasing KEY_LEFTSHIFT (42).
07:10:07.198 DEBUG _uinput:57 - Pressing e (18).
07:10:07.301 DEBUG _uinput:88 - Releasing e (18).
07:10:07.404 DEBUG _uinput:57 - Pressing s (31).
07:10:07.506 DEBUG _uinput:88 - Releasing s (31).
07:10:07.608 DEBUG _uinput:57 - Pressing t (20).
07:10:07.711 DEBUG _uinput:88 - Releasing t (20).
07:10:23.778 INFO process_helpers:207 - Stoping job unity8-dash.
07:10:24.078 INFO process_helpers:215 - unity8-dash stop/waiting
07:10:24.082 INFO process_helpers:207 - Stoping job unity8.
07:10:25.375 INFO process_helpers:215 - unity8 stop/waiting
}}}
Traceback (most recent call last):
File /home/phablet/autopilot/unity8/shell/tests/test_emulators.py, line
54, in test_search
self.dash.enter_search_query('Test')
File /home/phablet/autopilot/unity8/shell/emulators/dash.py, line 156, in
enter_search_query
self.select_single(objectName=processingIndicator).visible.wait_for(False)
File /usr/lib/python3/dist-packages/autopilot/introspection/types.py,
line 178, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickRectangle.visible failed:
False != dbus.Boolean(True
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Hello, I saw this bug seems to be fixed and released on September 17, anybody knows in which repository this fix has been released? Is this in trusty-proposed repository? How will we know if this fix has been released in the Trusty stable repository? Is this when Unity 7.2.4 will be released? Do you have any idea how long will it take? Have a good day and thanks for your help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1384800] Re: words with apostrophes are not suggested by prediction
** Also affects: presage (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: ubuntu-keyboard (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to presage in Ubuntu. https://bugs.launchpad.net/bugs/1384800 Title: words with apostrophes are not suggested by prediction Status in Ubuntu Keyboard: In Progress Status in “presage” package in Ubuntu: In Progress Status in “presage” package in Ubuntu RTM: New Status in “ubuntu-keyboard” package in Ubuntu RTM: New Bug description: The current word prediction does not suggest or correct words like we'll, it's they're etc. The expected behavior is if I typed its it should be autocorrected to it's and similar for other common words. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1384800/+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 1389239] Re: apparmor is uninstalled when deploying icehouse nova-compute on Precise
** Tags added: openstack uosci -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1389239 Title: apparmor is uninstalled when deploying icehouse nova-compute on Precise Status in “apparmor” package in Ubuntu: New Status in “libvirt” package in Ubuntu: New Status in “apparmor” source package in Precise: New Status in “libvirt” source package in Precise: New Bug description: When doing juju deploy nova-compute for icehouse with the latest charm on Ubuntu Precise, the apparmor package is uninstalled. Procedure to reproduce : $ juju switch local $ juju get-env | grep serie default-series: precise $ juju bootstrap $ bzr branch lp:charms/nova-compute $ juju deploy --repository=. local:nova-compute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1389239/+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 1389244] [NEW] lxc-info output different in terminal and file redirection
Public bug reported: - Versions information root@arachide:~# lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 root@arachide:~# apt-cache policy lxc lxc: Installed: 1.0.6-0ubuntu0.1 Candidate: 1.0.6-0ubuntu0.1 Version table: *** 1.0.6-0ubuntu0.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.3-0ubuntu3 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages --- lxc-info output is different when displayed directly in the terminal or redirected to a file Expected: same content when displayed in term or redirected to a file Actual result: contents different This behavior broke a custom script which was working like a charm on Ubuntu 13.10 with lxc version 1.0.0~alpha1 amd64. This is working correctly as well on Ubuntu 14.10 with the stock trusty version of lxc in the main repo (1.0.3) How to reproduce: root@arachide:~# lxc-info -n my_lxc Name: my_lxc State: STOPPED root@arachide:~# lxc-info -n vfc-sla test.txt root@arachide:~# cat test.txt Name: my_lxc Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED root@arachide:~# ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389244 Title: lxc-info output different in terminal and file redirection Status in “lxc” package in Ubuntu: New Bug description: - Versions information root@arachide:~# lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 root@arachide:~# apt-cache policy lxc lxc: Installed: 1.0.6-0ubuntu0.1 Candidate: 1.0.6-0ubuntu0.1 Version table: *** 1.0.6-0ubuntu0.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.3-0ubuntu3 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages --- lxc-info output is different when displayed directly in the terminal or redirected to a file Expected: same content when displayed in term or redirected to a file Actual result: contents different This behavior broke a custom script which was working like a charm on Ubuntu 13.10 with lxc version 1.0.0~alpha1 amd64. This is working correctly as well on Ubuntu 14.10 with the stock trusty version of lxc in the main repo (1.0.3) How to reproduce: root@arachide:~# lxc-info -n my_lxc Name: my_lxc State: STOPPED root@arachide:~# lxc-info -n vfc-sla test.txt root@arachide:~# cat test.txt Name: my_lxc Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED Name: my_lxc State: STOPPED root@arachide:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389244/+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 1389239] Re: apparmor is uninstalled when deploying icehouse nova-compute on Precise
Information from the Precise deployed node : # apt-cache policy libvirt-bin libvirt-bin: Installed: 1.2.2-0ubuntu13.1.6~cloud0 Candidate: 1.2.2-0ubuntu13.1.6~cloud0 Version table: *** 1.2.2-0ubuntu13.1.6~cloud0 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ precise-updates/icehouse/main amd64 Packages 100 /var/lib/dpkg/status 0.9.8-2ubuntu17.20 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 0.9.8-2ubuntu17 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages # apt-cache policy apparmor apparmor: Installed: (none) Candidate: 2.7.102-0ubuntu3.10 Version table: 2.7.102-0ubuntu3.10 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 2.7.102-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages # dpkg -l | grep apparmor rc apparmor 2.7.102-0ubuntu3.10 User-space parser utility for AppArmor ii libapparmor1 2.7.102-0ubuntu3.10 changehat AppArmor library From /var/log/juju/unit-nova-compute-0.log : 2014-11-04 14:00:09 INFO install Reading package lists... 2014-11-04 14:00:09 INFO juju-log Installing ['nova-compute', 'genisoimage', 'nova-compute-kvm'] with options: ['--option=Dpkg::Options::=--force-confold'] 2014-11-04 14:00:09 INFO install Reading package lists... 2014-11-04 14:00:09 INFO install Building dependency tree... 2014-11-04 14:00:09 INFO install Reading state information... 2014-11-04 14:00:10 INFO install The following extra packages will be installed: ... 2014-11-04 14:00:10 INFO install mailx 2014-11-04 14:00:10 INFO install The following packages will be REMOVED: 2014-11-04 14:00:10 INFO install apparmor 2014-11-04 14:00:10 INFO install The following NEW packages will be installed: ** Description changed: When doing juju deploy nova-compute for icehouse with the latest charm on Ubuntu Precise, the apparmor package is uninstalled. + + Procedure to reproduce : + $ juju switch local + $ juju get-env | grep serie + default-series: precise + $ juju bootstrap + $ bzr branch lp:charms/nova-compute + $ juju deploy --repository=. local:nova-compute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1389239 Title: apparmor is uninstalled when deploying icehouse nova-compute on Precise Status in “apparmor” package in Ubuntu: New Status in “libvirt” package in Ubuntu: New Status in “apparmor” source package in Precise: New Status in “libvirt” source package in Precise: New Bug description: When doing juju deploy nova-compute for icehouse with the latest charm on Ubuntu Precise, the apparmor package is uninstalled. Procedure to reproduce : $ juju switch local $ juju get-env | grep serie default-series: precise $ juju bootstrap $ bzr branch lp:charms/nova-compute $ juju deploy --repository=. local:nova-compute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1389239/+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 1389239] Re: apparmor is uninstalled when deploying icehouse nova-compute on Precise
Seems like 1.2.2-0ubuntu13.1.6~cloud0 needs to adjust its Depends. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1389239 Title: apparmor is uninstalled when deploying icehouse nova-compute on Precise Status in “apparmor” package in Ubuntu: New Status in “libvirt” package in Ubuntu: New Status in “apparmor” source package in Precise: New Status in “libvirt” source package in Precise: New Bug description: When doing juju deploy nova-compute for icehouse with the latest charm on Ubuntu Precise, the apparmor package is uninstalled. Procedure to reproduce : $ juju switch local $ juju get-env | grep serie default-series: precise $ juju bootstrap $ bzr branch lp:charms/nova-compute $ juju deploy --repository=. local:nova-compute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1389239/+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 1387163] Re: 'Show Desktop' on launcher crashes compiz for any Gtk-Headerbar app when using any third party Gtk(3.12) theme (Utopic/Vivid)
** Changed in: unity Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1387163 Title: 'Show Desktop' on launcher crashes compiz for any Gtk-Headerbar app when using any third party Gtk(3.12) theme (Utopic/Vivid) Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: This is happening for any gtk-3.12 theme which has proper support for gtk-headerbar. How to reproduce on Utopic: 1. sudo apt-get install Numix 2. sudo apt-get install gnome-tweak-tool 3. change Gtk theme to Numix 4. Open any app with Gtk-Headerbar ( NOT directly patched by Ubuntu) like gnome-tweak-tool, gnome-system-log 2. enable show-desktop on unity launcher 3. Click on show-desktop first time. it will show desktop. 4. Click on it again, it crashes compiz sometimes does not recover from it. Users have to fallback to TTY force restart lightdm. The problem also occurs for any headerbar app from Gnom3 ppa (for example gnome-contacts, baobab, gnome-maps). Attached crash file from /var/crash/compiz. Note: Compiz on other desktop shell/session works relatively well. For example in Gnome-Flashback-Compiz session it doesn't happen. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1387163/+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 1386872] Re: Incorrect termination Firefox when shutdown Ubuntu
** Changed in: unity Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1386872 Title: Incorrect termination Firefox when shutdown Ubuntu Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: 1. In Firefox go to Preference - General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message Firefox was not closed properly ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386872/+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 1386584] Re: SIGSEGV when notification contains |
** Changed in: unity Importance: Undecided = High ** Changed in: unity Status: New = Confirmed ** Changed in: unity Assignee: (unassigned) = Lars Uebernickel (larsu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1386584 Title: SIGSEGV when notification contains | Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When a notification on the messages menu contains the | character (in my case a nickname in xchat), the process unity-panel-service crashes with: ngl@BEATRIX:~/Scrivania/database$ /usr/lib/unity/unity-panel-service (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion 'str != NULL' failed (unity-panel-service:11336): Gtk-CRITICAL **: gtk_print_action_and_target: assertion 'strchr (action_name, '|') == NULL' failed Segmentation fault (core dumped) ngl@BEATRIX:~/Scrivania/database$ lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 ngl@BEATRIX:~/Scrivania/database$ apt-cache policy unity-services unity-services: Installed: 7.3.1+14.10.20141016-0ubuntu1 Candidate: 7.3.1+14.10.20141016-0ubuntu1 Version table: *** 7.3.1+14.10.20141016-0ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386584/+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 1370100] Re: Brigtness bar should get greyed out when auto-brightness is on
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1370100 Title: Brigtness bar should get greyed out when auto-brightness is on Status in “indicator-power” package in Ubuntu: Confirmed Bug description: Note: THIS bug is for the power menu that is dragged from the top, see attached image. 1. Drag down battery icon from the top 2. make sure auto-brghtness is enabled 3. try dragging the slider What happens: Nothing happens when you move the slider What should happen: If the slider is of no use during auto-brightness it should not be movable at all. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-power 12.10.6+14.10.20140912-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu2 Architecture: armhf Date: Tue Sep 16 19:53:00 2014 InstallationDate: Installed on 2014-09-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-020205) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-power.log: (process:3237): libnotify-WARNING **: Failed to connect to proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1370100/+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 1389250] [NEW] Location updates stop when screen is locked for a bit
Public bug reported: Hi, 1. start one or more location using apps; see that they get location updates as you move around 2. lock your screen, wait 30s 3. unlock screen, none of the apps get any location update anymore 4. kill and restart one of the location using apps, all apps now get location updates again Our location-service/platform-api/qt/etc. stack should resume location updates after locked screen / sleep. Cheers, ** Affects: location-service (Ubuntu) Importance: High Status: New ** Changed in: location-service (Ubuntu) Importance: Undecided = High -- 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/1389250 Title: Location updates stop when screen is locked for a bit Status in “location-service” package in Ubuntu: New Bug description: Hi, 1. start one or more location using apps; see that they get location updates as you move around 2. lock your screen, wait 30s 3. unlock screen, none of the apps get any location update anymore 4. kill and restart one of the location using apps, all apps now get location updates again Our location-service/platform-api/qt/etc. stack should resume location updates after locked screen / sleep. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389250/+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 1389232] Re: failed dashboard test case: unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
What needs to be done to make the dashboard green? do we need to retry
the search if it fails the first time or wait for some element to appear
before we start searching?
--
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/1389232
Title:
failed dashboard test case:
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
Status in “unity8” package in Ubuntu:
Confirmed
Bug description:
http://dashboard.ubuntu-
ci:8080/smokeng/utopic/touch_stable/krillin/141:20141104:20141028-3ca60be/661/unity8/232676/
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
test-log: {{{
07:08:45.747 WARNING testcase:115 - No tracing available - install the
python-autopilot-trace package!
07:08:45.759 WARNING testcase:162 - Process manager backend unavailable,
application snapshot support disabled.
07:08:45.793 INFO process_helpers:151 - Starting job unity8 with arguments
('QT_LOAD_TESTABILITY=1',).
07:08:46.254 INFO process_helpers:159 - unity8 start/running, process 14617
07:09:01.266 INFO process_helpers:95 - Greeter unlocked, continuing.
07:09:01.284 INFO process_helpers:207 - Stoping job unity8-dash.
07:09:01.502 INFO process_helpers:215 - unity8-dash stop/waiting
07:09:01.543 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:09:01.566 INFO process_helpers:151 - Starting job unity8-dash with
arguments ('BINARY=/usr/bin/unity8-dash', 'QT_LOAD_TESTABILITY=1',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks').
07:09:01.657 INFO process_helpers:159 - unity8-dash start/running, process
14839
07:09:28.834 ERROR proxies:410 - Introspect error on
:1.367:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the network
connection was broken.
07:09:28.837 DEBUG proxies:413 - Executing introspect queue due to error
07:09:40.166 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:42.668 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (392 items). This is likely to be slow. You may want
to consider optimising your query to return fewer items.
07:09:49.835 DEBUG _uinput:470 - Tapping at: 364,86
07:09:54.196 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:56.195 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (532 items). This is likely to be slow. You may want
to consider optimising your query to return fewer items.
07:10:06.466 INFO logging:45 - TextField: Write into the text field.
Arguments ('Test',). Keyword arguments: {}.
07:10:06.534 DEBUG _common:45 - Moving to object's globalRect coordinates.
07:10:06.535 DEBUG _uinput:470 - Tapping at: 309,86
07:10:06.730 INFO logging:45 - TextField: Clear the text field. Arguments ().
Keyword arguments: {}.
07:10:06.786 DEBUG _uinput:195 - Typing text 'Test'
07:10:06.787 DEBUG _uinput:57 - Pressing KEY_LEFTSHIFT (42).
07:10:06.888 DEBUG _uinput:57 - Pressing T (20).
07:10:06.992 DEBUG _uinput:88 - Releasing T (20).
07:10:07.095 DEBUG _uinput:88 - Releasing KEY_LEFTSHIFT (42).
07:10:07.198 DEBUG _uinput:57 - Pressing e (18).
07:10:07.301 DEBUG _uinput:88 - Releasing e (18).
07:10:07.404 DEBUG _uinput:57 - Pressing s (31).
07:10:07.506 DEBUG _uinput:88 - Releasing s (31).
07:10:07.608 DEBUG _uinput:57 - Pressing t (20).
07:10:07.711 DEBUG _uinput:88 - Releasing t (20).
07:10:23.778 INFO process_helpers:207 - Stoping job unity8-dash.
07:10:24.078 INFO process_helpers:215 - unity8-dash stop/waiting
07:10:24.082 INFO process_helpers:207 - Stoping job unity8.
07:10:25.375 INFO process_helpers:215 - unity8 stop/waiting
}}}
Traceback (most recent call last):
File /home/phablet/autopilot/unity8/shell/tests/test_emulators.py, line
54, in test_search
self.dash.enter_search_query('Test')
File /home/phablet/autopilot/unity8/shell/emulators/dash.py, line 156, in
enter_search_query
self.select_single(objectName=processingIndicator).visible.wait_for(False)
File /usr/lib/python3/dist-packages/autopilot/introspection/types.py,
line 178, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickRectangle.visible failed:
False != dbus.Boolean(True, variant_level=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net
[Touch-packages] [Bug 1351559] Re: Apps in spread are not anti-aliased
** Changed in: qtmir Assignee: Gerry Boland (gerboland) = Michael Zanetti (mzanetti) ** Changed in: qtmir Status: Confirmed = In Progress ** Branch linked: lp:~mzanetti/qtmir/sg-imagenode -- 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/1351559 Title: Apps in spread are not anti-aliased Status in Qt integration with the Mir display server: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: With qtcomp enabled, smoothing in the spread was disabled. This is unfortunately very visible on lower density devices, causing sharp edges on all diagonal lines. We need to investigate how to enable anti-aliasing with as little performance hit as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1351559/+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 1382772] Re: 1002:7942 [Samsung NP-R58DYLC/SEK] Corrupt panel and graphic artifacts
** Changed in: unity Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1382772 Title: 1002:7942 [Samsung NP-R58DYLC/SEK] Corrupt panel and graphic artifacts Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Panel and panel shadow textures are corrupt while other semi- transparent elements of UI look ok. It seems this problem affects only panel, panel shadow and bottom(!) border of ubuntu start menu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CasperVersion: 1.340 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: Sat Oct 18 09:45:52 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS600M [Radeon Xpress 1250] [1002:7942] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c034] LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. SR58P ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper quiet splash -- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 06YK dmi.board.name: SR58P dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr06YK:bd03/05/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnSR58P:pvr06YK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSR58P:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A: dmi.product.name: SR58P dmi.product.version: 06YK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Oct 18 11:47:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1382772/+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 1389235] Re: failing dashboard test case: unity8.shell.tests.test_notifications.InteractiveNotificationBase.test_interactive(Native Device)
Indeed, but nothing explains what actually happened :/ There's no unity8
crash, nothing I can see explains what's going on. The dbus exceptions
actually suggest something's gone wrong with the whole session. Maybe
unity8 crashed (there's a known crash related to notifications that's
going away soon), but did not leave much in terms of artifacts.
** Changed in: unity8 (Ubuntu)
Status: New = Incomplete
--
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/1389235
Title:
failing dashboard test case:
unity8.shell.tests.test_notifications.InteractiveNotificationBase.test_interactive(Native
Device)
Status in “unity8” package in Ubuntu:
Incomplete
Bug description:
http://dashboard.ubuntu-
ci:8080/smokeng/utopic/touch_stable/krillin/141:20141104:20141028-3ca60be/661/unity8/232697/
failing dashboard test case:
unity8.shell.tests.test_notifications.InteractiveNotificationBase.test_interactive(Native
Device)
test-log: {{{
07:19:20.641 WARNING testcase:115 - No tracing available - install the
python-autopilot-trace package!
07:19:20.650 WARNING testcase:162 - Process manager backend unavailable,
application snapshot support disabled.
07:19:20.660 WARNING utilities:263 - WARNING: in file
/home/phablet/autopilot/unity8/shell/tests/__init__.py, line 164 in setUp
This function is deprecated. Please use 'the Touch class to instantiate a
device object' instead.
07:19:20.827 INFO __init__:268 - Lib path is
'/usr/lib/arm-linux-gnueabihf/unity8', binary path is '/usr/bin/unity8'
07:19:20.828 INFO __init__:346 - Setting up LightDM mock type 'single'
07:19:20.905 INFO __init__:355 - New library path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single
07:19:20.945 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:19:20.966 INFO __init__:317 - Starting unity
07:19:21.036 INFO process_helpers:151 - Starting job unity8 with arguments
('BINARY=/usr/bin/unity8', 'ARGS=',
'LD_LIBRARY_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single',
'XDG_DATA_DIRS=/usr/share/unity8/mocks/data:/usr/share/ubuntu-touch:/usr/local/share:/usr/share',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks',
'QT_LOAD_TESTABILITY=1').
07:19:21.420 INFO process_helpers:159 - unity8 start/running, process 26926
07:19:26.293 ERROR proxies:410 - Introspect error on
:1.936:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout
by message bus)
07:19:26.294 DEBUG proxies:413 - Executing introspect queue due to error
07:19:26.404 ERROR proxies:410 - Introspect error on
:1.938:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout
by message bus)
07:19:26.405 DEBUG proxies:413 - Executing introspect queue due to error
07:19:27.914 INFO __init__:330 - Stopping unity
07:19:31.430 INFO __init__:246 - Resetting upstart env QT_LOAD_TESTABILITY to
None
}}}
Traceback (most recent call last):
File /home/phablet/autopilot/unity8/shell/tests/test_notifications.py,
line 127, in test_interactive
unity_proxy = self.launch_unity()
File /home/phablet/autopilot/unity8/shell/tests/__init__.py, line 299, in
launch_unity
self.unity_geometry_args,
File /home/phablet/autopilot/unity8/shell/tests/__init__.py, line 327, in
_launch_unity_with_upstart
return process_helpers.restart_unity_with_testability(*all_args)
File /home/phablet/autopilot/unity8/process_helpers.py, line 122, in
restart_unity_with_testability
return restart_unity(*args)
File /home/phablet/autopilot/unity8/process_helpers.py, line 139, in
restart_unity
return _get_unity_proxy_object(pid)
File /home/phablet/autopilot/unity8/process_helpers.py, line 248, in
_get_unity_proxy_object
emulator_base=emulators.UnityEmulatorBase,
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 171, in get_proxy_object_for_existing_process
process
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 324, in _find_matching_connections
in connections
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 325, in listcomp
if connection_matcher((bus, c))
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 292, in _filter_runner
for f in filter_list
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line 292, in genexpr
for f in filter_list
File /usr/lib/python3/dist-packages/autopilot/introspection/_search.py,
line
[Touch-packages] [Bug 1389232] Re: failed dashboard test case: unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
** Changed in: unity8 (Ubuntu)
Status: Incomplete = Confirmed
--
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/1389232
Title:
failed dashboard test case:
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
Status in “unity8” package in Ubuntu:
Confirmed
Bug description:
http://dashboard.ubuntu-
ci:8080/smokeng/utopic/touch_stable/krillin/141:20141104:20141028-3ca60be/661/unity8/232676/
unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_search
test-log: {{{
07:08:45.747 WARNING testcase:115 - No tracing available - install the
python-autopilot-trace package!
07:08:45.759 WARNING testcase:162 - Process manager backend unavailable,
application snapshot support disabled.
07:08:45.793 INFO process_helpers:151 - Starting job unity8 with arguments
('QT_LOAD_TESTABILITY=1',).
07:08:46.254 INFO process_helpers:159 - unity8 start/running, process 14617
07:09:01.266 INFO process_helpers:95 - Greeter unlocked, continuing.
07:09:01.284 INFO process_helpers:207 - Stoping job unity8-dash.
07:09:01.502 INFO process_helpers:215 - unity8-dash stop/waiting
07:09:01.543 INFO __init__:108 - New QML2 import path:
/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks
07:09:01.566 INFO process_helpers:151 - Starting job unity8-dash with
arguments ('BINARY=/usr/bin/unity8-dash', 'QT_LOAD_TESTABILITY=1',
'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks').
07:09:01.657 INFO process_helpers:159 - unity8-dash start/running, process
14839
07:09:28.834 ERROR proxies:410 - Introspect error on
:1.367:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the network
connection was broken.
07:09:28.837 DEBUG proxies:413 - Executing introspect queue due to error
07:09:40.166 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:42.668 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (392 items). This is likely to be slow. You may want
to consider optimising your query to return fewer items.
07:09:49.835 DEBUG _uinput:470 - Tapping at: 364,86
07:09:54.196 DEBUG dbus:352 - Selecting objects of type QQuickLoader with
attributes: {}
07:09:56.195 WARNING backends:229 - Your query
'Query(b'/unity8-dash/QQuickView/MainView/OrientationHelper/QQuickItem/QQuickItem/Dash/DashContent/QQuickItem/QQuickListView[id=6]//QQuickLoader')'
returned a lot of data (532 items). This is likely to be slow. You may want
to consider optimising your query to return fewer items.
07:10:06.466 INFO logging:45 - TextField: Write into the text field.
Arguments ('Test',). Keyword arguments: {}.
07:10:06.534 DEBUG _common:45 - Moving to object's globalRect coordinates.
07:10:06.535 DEBUG _uinput:470 - Tapping at: 309,86
07:10:06.730 INFO logging:45 - TextField: Clear the text field. Arguments ().
Keyword arguments: {}.
07:10:06.786 DEBUG _uinput:195 - Typing text 'Test'
07:10:06.787 DEBUG _uinput:57 - Pressing KEY_LEFTSHIFT (42).
07:10:06.888 DEBUG _uinput:57 - Pressing T (20).
07:10:06.992 DEBUG _uinput:88 - Releasing T (20).
07:10:07.095 DEBUG _uinput:88 - Releasing KEY_LEFTSHIFT (42).
07:10:07.198 DEBUG _uinput:57 - Pressing e (18).
07:10:07.301 DEBUG _uinput:88 - Releasing e (18).
07:10:07.404 DEBUG _uinput:57 - Pressing s (31).
07:10:07.506 DEBUG _uinput:88 - Releasing s (31).
07:10:07.608 DEBUG _uinput:57 - Pressing t (20).
07:10:07.711 DEBUG _uinput:88 - Releasing t (20).
07:10:23.778 INFO process_helpers:207 - Stoping job unity8-dash.
07:10:24.078 INFO process_helpers:215 - unity8-dash stop/waiting
07:10:24.082 INFO process_helpers:207 - Stoping job unity8.
07:10:25.375 INFO process_helpers:215 - unity8 stop/waiting
}}}
Traceback (most recent call last):
File /home/phablet/autopilot/unity8/shell/tests/test_emulators.py, line
54, in test_search
self.dash.enter_search_query('Test')
File /home/phablet/autopilot/unity8/shell/emulators/dash.py, line 156, in
enter_search_query
self.select_single(objectName=processingIndicator).visible.wait_for(False)
File /usr/lib/python3/dist-packages/autopilot/introspection/types.py,
line 178, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickRectangle.visible failed:
False != dbus.Boolean(True, variant_level=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389232/+subscriptions
--
Mailing list: https://launchpad.net/~touch
[Touch-packages] [Bug 1381930] Re: [TOPBLOCKER] 7digital previews do not play in the scope
** Branch linked: lp:~stolowski/unity-scopes-api/fix-user-agent-in- preview-rtm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: [TOPBLOCKER] 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu: In Progress Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Invalid Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+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 1389257] [NEW] Getting package versions via dpkg-query on startup is very expensive
Public bug reported:
The plugin executes dpkg-query on startup to get version numbers of 3
important packages (scopes-api, unity8, self). They are then passed to
Smart Scopes Server with every request. Using dpkg-query at this stage
seems to have big impact on startup time of the Dash (and phone).
Michael Vogt suggested a simple postinst/postrm script that is executed
for all 3 packages to put update their versions via a flat text file,
e.g.
::
debian/postinst
::
#!/bin/sh
set -e
if [ $1 = configure ]; then
dpkg-query -W -f'${Version}' $DPKG_MAINTSCRIPT_PACKAGE \
/var/lib/unity-scopes-shell/$DPKG_MAINTSCRIPT_PACKAGE
fi::
debian/postrm
::
#!/bin/sh
set -e
rm -f /var/lib/unity-scopes-shell/$DPKG_MAINTSCRIPT_PACKAGE
** Affects: unity-scopes-shell (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: unity-scopes-shell (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1389257
Title:
Getting package versions via dpkg-query on startup is very expensive
Status in “unity-scopes-shell” package in Ubuntu:
Confirmed
Bug description:
The plugin executes dpkg-query on startup to get version numbers of 3
important packages (scopes-api, unity8, self). They are then passed to
Smart Scopes Server with every request. Using dpkg-query at this stage
seems to have big impact on startup time of the Dash (and phone).
Michael Vogt suggested a simple postinst/postrm script that is
executed for all 3 packages to put update their versions via a flat
text file, e.g.
::
debian/postinst
::
#!/bin/sh
set -e
if [ $1 = configure ]; then
dpkg-query -W -f'${Version}' $DPKG_MAINTSCRIPT_PACKAGE \
/var/lib/unity-scopes-shell/$DPKG_MAINTSCRIPT_PACKAGE
fi::
debian/postrm
::
#!/bin/sh
set -e
rm -f /var/lib/unity-scopes-shell/$DPKG_MAINTSCRIPT_PACKAGE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1389257/+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
