[Touch-packages] [Bug 1388734] [NEW] Xorg freeze
Public bug reported: 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze ubuntu utopic -- 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 freeze 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'
[Touch-packages] [Bug 1378660] Re: Use a Trusted Prompt to handle (re-)authentication and (re-)authorization
** Changed in: ubuntu-system-settings-online-accounts Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1378660 Title: Use a Trusted Prompt to handle (re-)authentication and (re-)authorization Status in Online Accounts setup for Ubuntu Touch: Fix Released Status in “signon” package in Ubuntu: Fix Released Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Fix Released Bug description: Whenever the OAuth flow needs to be started on behalf of an application, we emit a notification which, if clicked, will initiate the OAuth flos in a separate window. However, if the client application has its own visible window, the authentication window could (and should, according to design) be happening as a prompt session on top of the application. In order to do so, we need signond to pass the PID of the client application, and online-accounts-ui to create a prompt session for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1378660/+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 1386653] Re: [TOPBLOCKER] Scopes fail to launch when the network stack is not up
Ideally yes, but does anyone know really what fixed it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1386653 Title: [TOPBLOCKER] Scopes fail to launch when the network stack is not up Status in “unity-scope-click” package in Ubuntu: Invalid Status in “unity-scope-scopes” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Bug description: I've seen this randomly from time to time on every other boot, but it happens reliably when flight mode is enabled Steps to reproduce: - Enable flight mode - Reboot Expected result: - Scopes launch and fail network requests Actual: - Black scope screen Notes: - Launcher items work and launch fine - Indicators work fine In the logs I see something like: unity8: Pre-populating scope unity-scope-nearby Pre-populating scope com.canonical.scopes.photos_photos file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:77:1: QM L Label: Binding loop detected for property height file:///usr/share/unity8/Dash/CardTool.qml:179:38: Unable to assign [undefined] to bool invalidateScopeResults: no such scope ' musicaggregator ' invalidateScopeResults: no such scope ' mediascanner-music ' invalidateScopeResults: no such scope ' videoaggregator ' invalidateScopeResults: no such scope ' mediascanner-video ' scope-registry: ... RegistryObject::ScopeProcess::on_process_death(): Process for scope: clickscope exited ... current build number: 129 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-26 15:25:59 version version: 129 version ubuntu: 20141026 version device: 20141015-32e0f27 version custom: 1413941794 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1386653/+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 1364292] Re: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset
Why has this expired? It's still a bug, and it's still outstanding. ** Changed in: xorg (Ubuntu) Status: Expired = Opinion -- 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/1364292 Title: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset Status in “xorg” package in Ubuntu: Opinion Bug description: I have just installed Ubuntu 14.04 64-bit on my Toshiba Portege R600-10Q laptop (a model from 2009). I am now trying to display the desktop on a BenQ Senseye3 22 monitor, via the vga output, but it's not working - the monitor says No Signal Detected!. What I've done: I have gone into Screen Display, where I can see the monitor is detected by the laptop. The monitor has a 1920 x 1080 native resolution, which I have tried to use, but I have also set it to lower resolutions, e.g. 1024 x 576. I have tried to use the monitor in dual screen, mirrored and single screen mode - none work. I have tried pressing Fn + F5 to get single screen output - the laptop screen goes blank, but still no output on the monitor. I have tried several monitors (of the same type, and also of a different make), so I don't think it's that. If I plug the vga cable in after boot up, then the monitor receives no signal. WORKAROUND: If, and only if, the monitor was plugged in to the PC's VGA output during boot up, then the display outputs to the monitor correctly. The laptop has the Intel® GS45 Express chipset for graphics acceleration. I installed mesa-utils and ran glxinfo in a terminal. Amongst the output was: OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset Also, in the About This Computer window I see: Graphics: Mobile Intel® GM45 Express Chipset I wonder if the problem is that my chipset is GS45 not GM45. The output of sudo lshw -C video is: *-display:0 description: VGA compatible controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:44 memory:ff40-ff7f memory:e000-efff ioport:cff8(size=8) *-display:1 UNCLAIMED description: Display controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 version: 07 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:ffc0-ffcf ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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: Tue Sep 2 10:00:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:000c] Subsystem: Toshiba America Info Systems Device [1179:000c] InstallationDate: Installed on 2014-08-28 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA PORTEGE R600 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=fe977943-4013-472e-b627-f7184c9e190f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd11/27/2008:svnTOSHIBA:pnPORTEGER600:pvrPPR61E-00Q00CEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE R600 dmi.product.version: PPR61E-00Q00CEN dmi.sys.vendor: TOSHIBA 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
[Touch-packages] [Bug 1386653] Re: [TOPBLOCKER] Scopes fail to launch when the network stack is not up
Doesn't look like it :-) There could be a million reasons. In the absence of any other information, I don't think we have a choice but to wait and see whether it comes back. I could stare at our code for years without seeing the bug (assuming there is one). I guess the most important point here is that we need to beef up our integration testing (in unity-scopes-api and elsewhere). We are working on that at the moment… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1386653 Title: [TOPBLOCKER] Scopes fail to launch when the network stack is not up Status in “unity-scope-click” package in Ubuntu: Invalid Status in “unity-scope-scopes” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Bug description: I've seen this randomly from time to time on every other boot, but it happens reliably when flight mode is enabled Steps to reproduce: - Enable flight mode - Reboot Expected result: - Scopes launch and fail network requests Actual: - Black scope screen Notes: - Launcher items work and launch fine - Indicators work fine In the logs I see something like: unity8: Pre-populating scope unity-scope-nearby Pre-populating scope com.canonical.scopes.photos_photos file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:77:1: QM L Label: Binding loop detected for property height file:///usr/share/unity8/Dash/CardTool.qml:179:38: Unable to assign [undefined] to bool invalidateScopeResults: no such scope ' musicaggregator ' invalidateScopeResults: no such scope ' mediascanner-music ' invalidateScopeResults: no such scope ' videoaggregator ' invalidateScopeResults: no such scope ' mediascanner-video ' scope-registry: ... RegistryObject::ScopeProcess::on_process_death(): Process for scope: clickscope exited ... current build number: 129 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-26 15:25:59 version version: 129 version ubuntu: 20141026 version device: 20141015-32e0f27 version custom: 1413941794 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1386653/+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 1388436] Re: ga-z97-d3h motherboard, no sound using line out
** Description changed: Problems with the sound (chipset z97). I've got the sound in Windows - so it is a software bug. Freshly installed default system. First time this was Kubuntu 14.04 then it was upgraded to 14.10 for a fresh kernel. No effect to the problem. Found the similar problems here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421, but none of the workarounds helped me. Upgrading to the 3.17 kernel dind't help. - meklon@meklon-desktop:~$ lsb_release -rd - Description:Ubuntu 14.10 - Release:14.10 + UPD: It is the same bug as described in + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357723 Please + merge them or close this one. Fully confirmed. + + + meklon@meklon-desktop:~$ lsb_release -rd + Description:Ubuntu 14.10 + Release:14.10 meklon@meklon-desktop:~$ uname -a Linux meklon-desktop 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Expecting: sound output from the rear panel. What happened: no sound at all. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC1D3p: meklon 3589 F...m pulseaudio - /dev/snd/controlC1: meklon 3589 F pulseaudio - /dev/snd/controlC0: meklon 3589 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC1D3p: meklon 3589 F...m pulseaudio + /dev/snd/controlC1: meklon 3589 F pulseaudio + /dev/snd/controlC0: meklon 3589 F pulseaudio CurrentDesktop: KDE Date: Sat Nov 1 22:45:33 2014 InstallationDate: Installed on 2014-10-31 (1 days ago) InstallationMedia: Kubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cayman/Antilles HDMI Audio [Radeon HD 6900 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [Z97-D3H, ATI R6xx HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: Upgraded to utopic on 2014-11-01 (0 days ago) dmi.bios.date: 04/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1388436 Title: ga-z97-d3h motherboard, no sound using line out Status in “alsa-driver” package in Ubuntu: New Bug description: Problems with the sound (chipset z97). I've got the sound in Windows - so it is a software bug. Freshly installed default system. First time this was Kubuntu 14.04 then it was upgraded to 14.10 for a fresh kernel. No effect to the problem. Found the similar problems here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421, but none of the workarounds helped me. Upgrading to the 3.17 kernel dind't help. UPD: It is the same bug as described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357723 Please merge them or close this one. Fully confirmed. meklon@meklon-desktop:~$ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 meklon@meklon-desktop:~$ uname -a Linux meklon-desktop 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Expecting: sound output from the rear panel. What happened: no sound at all. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D3p: meklon
[Touch-packages] [Bug 1388094] Re: Slider component can have problems when binding value
The live Slider value change is expected to get the value updated on each move. I do not really see what could we improve in the component there. Could you provide a small sample code that reproduces the binding loop you worked around? -- 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/1388094 Title: Slider component can have problems when binding value Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: In ubuntu-system-settings and the indicators, we deal with values that come from system services. When binding to the value in the Slider component, this can cause unpredictable behavior because we get property notifications back that change the value while the slider is being moved. This has been worked around in ubuntu-settings-component by creating a SliderMenu which used in the indicators and system- settings for things using the MenuModel provided by the indicator services. The SliderMenu is based on the Slider for the SDK, but adds some logic for handling this value binding loop. It would be best to improve the Slider to handle this sort of problem and reduce the amount of custom components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1388094/+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 1388744] [NEW] Letter G has gone
Public bug reported: Ubuntu doesn't display g's any more, in popups, in Eclipse, anywhere. Chrome does display g's. 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 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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: Mon Nov 3 09:36:16 2014 DistUpgraded: 2014-06-13 15:13:21,940 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2014-01-04 (302 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-06-13 (142 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. 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.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: Mon Nov 3 09:22:01 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10331 vendor HWP xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Attachment added: Screenshot from 2014-11-03 09:37:11.png https://bugs.launchpad.net/bugs/1388744/+attachment/4251857/+files/Screenshot%20from%202014-11-03%2009%3A37%3A11.png -- 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/1388744 Title: Letter G has gone Status in “xorg” package in Ubuntu: New Bug description: Ubuntu doesn't display g's any more, in popups, in Eclipse, anywhere. Chrome does display g's. 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 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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: Mon Nov 3 09:36:16 2014 DistUpgraded: 2014-06-13 15:13:21,940 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2014-01-04 (302 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-06-13 (142 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias:
[Touch-packages] [Bug 1388744] Re: Letter G has gone
** Attachment added: Screenshot from 2014-11-03 09:37:22.png https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388744/+attachment/4251883/+files/Screenshot%20from%202014-11-03%2009%3A37%3A22.png -- 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/1388744 Title: Letter G has gone Status in “xorg” package in Ubuntu: New Bug description: Ubuntu doesn't display g's any more, in popups, in Eclipse, anywhere. Chrome does display g's. 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 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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: Mon Nov 3 09:36:16 2014 DistUpgraded: 2014-06-13 15:13:21,940 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2014-01-04 (302 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-06-13 (142 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. 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.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: Mon Nov 3 09:22:01 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10331 vendor HWP xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388744/+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 1388254] Re: Sync openexr 1.6.1-8 (main) from Debian unstable (main)
This bug was fixed in the package openexr - 1.6.1-8 Sponsored for Artur Rona (ari-tczew) --- openexr (1.6.1-8) unstable; urgency=medium * QA upload. * Orphan package, set maintainer to QA. * Add 20_autoreconf.diff by Andreas Barth to let autoreconf run successfully and use dh-autoreconf. Closes: #759719 * Point Vcs-* to anonscm.debian.org. -- Andreas Metzler ametz...@debian.org Sun, 31 Aug 2014 07:56:20 +0200 ** Changed in: openexr (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1388254 Title: Sync openexr 1.6.1-8 (main) from Debian unstable (main) Status in “openexr” package in Ubuntu: Fix Released Bug description: Please sync openexr 1.6.1-8 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Build using dh-autoreconf. * Update for recent autoconf/autoheader. * Build using dh-autoreconf. * Update for recent autoconf/autoheader. * Build using dh-autoreconf. * Update for recent autoconf/autoheader. dh-autoreconf is already supported in Debian. Changelog entries since current vivid version 1.6.1-7ubuntu1: openexr (1.6.1-8) unstable; urgency=medium * QA upload. * Orphan package, set maintainer to QA. * Add 20_autoreconf.diff by Andreas Barth to let autoreconf run successfully and use dh-autoreconf. Closes: #759719 * Point Vcs-* to anonscm.debian.org. -- Andreas Metzler ametz...@debian.org Sun, 31 Aug 2014 07:56:20 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1388254/+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 1388744] Re: Letter G has gone
** Attachment added: Screenshot from 2014-11-03 09:37:37.png https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388744/+attachment/4251884/+files/Screenshot%20from%202014-11-03%2009%3A37%3A37.png -- 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/1388744 Title: Letter G has gone Status in “xorg” package in Ubuntu: New Bug description: Ubuntu doesn't display g's any more, in popups, in Eclipse, anywhere. Chrome does display g's. 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 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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: Mon Nov 3 09:36:16 2014 DistUpgraded: 2014-06-13 15:13:21,940 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2014-01-04 (302 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-06-13 (142 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. 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.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: Mon Nov 3 09:22:01 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10331 vendor HWP xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388744/+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 1388744] Re: Letter G has gone
** Attachment added: Screenshot from 2014-11-03 09:39:37.png https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388744/+attachment/4251885/+files/Screenshot%20from%202014-11-03%2009%3A39%3A37.png -- 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/1388744 Title: Letter G has gone Status in “xorg” package in Ubuntu: New Bug description: Ubuntu doesn't display g's any more, in popups, in Eclipse, anywhere. Chrome does display g's. 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 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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: Mon Nov 3 09:36:16 2014 DistUpgraded: 2014-06-13 15:13:21,940 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2014-01-04 (302 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-06-13 (142 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. 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.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: Mon Nov 3 09:22:01 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10331 vendor HWP xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388744/+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 1361734] Re: Holding down 1 at start of number enters then erases it
*** This bug is a duplicate of bug 1338970 *** https://bugs.launchpad.net/bugs/1338970 ** This bug has been marked a duplicate of bug 1338970 No voicemail number defined == No feedback when attempting to dial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1361734 Title: Holding down 1 at start of number enters then erases it Status in “dialer-app” package in Ubuntu: Expired Bug description: Ubuntu 14.10 r203 1. Navigate to the keypad screen of the phone app. 2. Clear any number present. 3. Hold down any key except 0 or 1, then release it. 4. Delete the number entered. 5. Hold down 1, then release it. What happens: 3. The number is entered. 5. The 1 is entered, then disappears. What should happen: 5. The 1 is entered, and remains. It's understandable that holding down 0 doesn't enter 0, because it enters + instead. But there doesn't seem to be any reason for a 1 to be entered then erased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1361734/+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 1356699] Re: Replace InvalidateResults dbus-send with list updated pub/sub mechanism
*** This bug is a duplicate of bug 1361221 *** https://bugs.launchpad.net/bugs/1361221 ** Branch unlinked: lp:unity-scopes-api/staging ** Branch unlinked: lp:~marcustomlinson/unity-scopes-api/lp-1356699 ** Branch unlinked: lp:~marcustomlinson/unity-scopes-shell/lp-1356699 -- 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/1356699 Title: Replace InvalidateResults dbus-send with list updated pub/sub mechanism Status in “unity-scopes-api” package in Ubuntu: In Progress Status in “unity-scopes-shell” package in Ubuntu: In Progress Status in “unity-scopes-shell” package in Ubuntu RTM: In Progress Bug description: The dbus InvalidateResults message was intended to be a temporary solution until we implemented a proper list updated pub/sub mechanism. Now that we have one, we should replace the dbus-send call in SSRegistryObject with publisher_-send_message() as done in RegistryObject. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1356699/+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 1384502] Re: fstab entry for nfs /home fails to mount on boot
Same here with an 14.10 AMD64 installation on a KVM machine. The workaround with mount -a in rc.local doesn't help much for daemons that need the mounted NFS share at startup. They're failing when the mount isn't present at boot time. I've stopped further deployment of Utopic until this bug has been fixed. It is really a showstopper and needs a fix very soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1384502 Title: fstab entry for nfs /home fails to mount on boot Status in “mountall” package in Ubuntu: Triaged Bug description: i'm uncertain exactly when this issue started as we use cfengine (verifies all expected mounts in place, manually mounts those that are not). from a note i have i believe it goes back as far as lucid. the symptom is that an /etc/fstab entry for an nfs-mounted /home is not mounted during the system boot. once the system is network- accessible, manually running `mount -tnfs -av` as root (or using cfengine or any number of other solutions) is sufficient. per lp#836533 i added --verbose to /etc/init/mountall.conf and will attach the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the smoking gun appears to be: mount.nfs: Failed to resolve server nfs-home: Temporary failure in name resolution ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mountall 2.53 ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8 Uname: Linux 3.13.0-38.65-generic x86_64 .run.mount.utab: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 22 16:35:47 2014 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw bootdegraded=true SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+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 1387282] Re: bluetooth rfkill status not synced between upstart and systemd
This bug was fixed in the package rfkill - 0.5-1ubuntu2
---
rfkill (0.5-1ubuntu2) vivid; urgency=medium
* Ensure that rfkill devices have ID_PATH attribute:
- debian/control: Add dependency for systemd = 215-5ubuntu2.
- debian/rfkill.postinst: udev-trigger rfkill devices to ensure systemd
215-5ubuntu2's adjusted 99-systemd.rules are applied on upgrade.
- This upgrade fix needs to be kept until after Ubuntu 16.04 LTS.
* debian/rfkill-{store,restore}.upstart: Use /lib/systemd/systemd-rfkill, to
keep rfkill state between boots synchronized between upstart and systemd.
(LP: #1387282)
-- Martin Pitt martin.p...@ubuntu.com Mon, 03 Nov 2014 07:47:56 +0100
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1387282
Title:
bluetooth rfkill status not synced between upstart and systemd
Status in “rfkill” package in Ubuntu:
Fix Released
Status in “systemd” package in Ubuntu:
Fix Released
Bug description:
I cannot use bluetooth devices while using systemd as the default init
system.
While going to gnome-control-center to check for bluetooth devices,
all the bluetooth functionality is deactivated.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: systemd 208-8ubuntu8
Uname: Linux 3.17.1-031701-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Oct 29 17:43:44 2014
InstallationDate: Installed on 2014-10-22 (7 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64
(20140923)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1387282/+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 1387282] Re: bluetooth rfkill status not synced between upstart and systemd
This bug was fixed in the package systemd - 215-5ubuntu2 --- systemd (215-5ubuntu2) vivid; urgency=medium * Merge fixes from Debian: - Adjust timedated and hostnamed autopkgtests to current upstream version. - Replace our Debian hwdb.bin location patch with what got committed upstream. Run hwdb update with the new --usr option to keep current behaviour. - debian/README.Debian: Document how to debug boot or shutdown problems with the debug shell. (Closes: #766039) - Skip-99-systemd.rules-when-not-running-systemd-as-in.patch: Call path_id under all init systems, to get consistent ID_PATH attributes. This is required so that tools like systemd-rfkill can be used with SysVinit or upstart scripts, too. (LP: #1387282) -- Martin Pitt martin.p...@ubuntu.com Mon, 03 Nov 2014 07:15:38 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: rfkill (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1387282 Title: bluetooth rfkill status not synced between upstart and systemd Status in “rfkill” package in Ubuntu: Fix Released Status in “systemd” package in Ubuntu: Fix Released Bug description: I cannot use bluetooth devices while using systemd as the default init system. While going to gnome-control-center to check for bluetooth devices, all the bluetooth functionality is deactivated. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-8ubuntu8 Uname: Linux 3.17.1-031701-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 29 17:43:44 2014 InstallationDate: Installed on 2014-10-22 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140923) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1387282/+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 1372860] Re: Contacts app sends you to Online Accounts and strands you there
The fix is purely in the contact par, so taking OA off the list ** No longer affects: ubuntu-system-settings-online-accounts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1372860 Title: Contacts app sends you to Online Accounts and strands you there Status in Ubuntu UX bugs: In Progress Status in “address-book-app” package in Ubuntu: Triaged Status in “address-book-app” package in Ubuntu RTM: Fix Released Bug description: First time in contacts when asked to add an account to sync. You are taken into settings and add an account which returns to main settings screen. This should take you into the new account to tick the contacts sync check box! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings-online-accounts 0.4+14.10.20140908~rtm-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Tue Sep 23 11:54:02 2014 InstallationDate: Installed on 2014-09-16 (7 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-030205) SourcePackage: ubuntu-system-settings-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1372860/+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 1376044] Re: [TOPBLOCKER] [scopes] Ubuntu button on launcher is hardcoded to click scope
** Changed in: ubuntu-ux Status: New = 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/1376044 Title: [TOPBLOCKER] [scopes] Ubuntu button on launcher is hardcoded to click scope Status in Ubuntu UX bugs: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: The Ubuntu button should bring the user to their first favorite scope, rather than always the click scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 (not installed) ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 19:11:58 2014 InstallationDate: Installed on 2013-04-26 (522 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1376044/+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 1388359] Re: User metrics can no longer be changed by double tap
** Changed in: unity8 (Ubuntu) Status: Confirmed = Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Daniel d'Andrada (dandrader) -- 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/1388359 Title: User metrics can no longer be changed by double tap Status in “unity8” package in Ubuntu: Triaged Bug description: Krillin #139 proposed On the welcome screen I only see No text messages sent today. In previous images double tapping the welcome screen would cycle through music played, phone calls made/received etc. I don't seem to be able to get it to move on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388359/+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 1387752] Re: [Dash] [Apps Scope] Ubuntu Store icon should be entire width of screen
** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1387752 Title: [Dash] [Apps Scope] Ubuntu Store icon should be entire width of screen Status in Ubuntu UX bugs: New Status in “unity-scope-click” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: Replace tall/narrow 'Ubuntu Store' icon with version that is the same width as rows of application icon above it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1387752/+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 1387031] Re: software-properties is *not* an offical package from Ubuntu -- can't create bug report
Tested today again and now it works! Can not say, what have changed and/or what created the misbehavior... ** Attachment added: output of sudo apt-cache policy software-properties-common https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1387031/+attachment/4251924/+files/software-properties-common.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1387031 Title: software-properties is *not* an offical package from Ubuntu -- can't create bug report Status in “software-properties” package in Ubuntu: Incomplete Bug description: Steps to reproduce this: Open up a Terminal, then type: sudo ubuntu-bug software-properties-common After a few seconds a window opens up and it says: Das Problem kann nicht gemeldet werden: Dies ist kein offizielles Ubuntu-Paket. Bitte entfernen Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang. Translation: (The problem can not reported: This is not a offical Ubuntu package. Please remove all packages from 3rd Party and retry the process.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1387031/+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 1387134] Re: when enabled nvidia graphics card, desktop freezes
There's more stuff going on in my dmesg. Not sure if it helps, but anyway: [ 9827.568968] [ cut here ] [ 9827.569058] WARNING: CPU: 2 PID: 1952 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() [ 9827.569062] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) dm_crypt rtsx_usb_ms memstick ax88179_178a usbnet mii btusb asus_nb_wmi uvcvideo videobuf2_vmalloc videobuf2_memops asus_wmi videobuf2_core sparse_keymap v4l2_common videodev media snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_hda_controller kvm snd_hda_codec crct10dif_pclmul snd_usb_audio crc32_pclmul snd_usbmidi_lib snd_hwdep ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi arc4 aesni_intel aes_x86_64 lrw gf128mul glue_helper iwldvm ablk_helper mac80211 cryptd rfcomm bnep bluetooth 6lowpan_iphc iwlwifi snd_seq joydev serio_raw snd_seq_device snd_timer lpc_ich cfg80211 snd soundcore [ 9827.569140] mei_me mei shpchp int3403_thermal binfmt_misc mac_hid parport_pc ppdev lp parport nls_iso8859_1 hid_generic usbhid hid ses enclosure rtsx_usb_sdmmc rtsx_usb uas usb_storage nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper psmouse drm ahci libahci wmi video [ 9827.569182] CPU: 2 PID: 1952 Comm: Xorg Tainted: G OE 3.16.0-24-generic #32-Ubuntu [ 9827.569186] Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.212 09/17/2012 [ 9827.569190] 0009 88029cbbfbf8 8177fcbc [ 9827.569197] 88029cbbfc30 8106fd8d 88029fe1b000 [ 9827.569203] 880035d88210 88029be27000 88029be27000 88029cbbfc40 [ 9827.569209] Call Trace: [ 9827.569226] [8177fcbc] dump_stack+0x45/0x56 [ 9827.569236] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [ 9827.569244] [8106fe6a] warn_slowpath_null+0x1a/0x20 [ 9827.569291] [c01efffc] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] [ 9827.569303] [810b9590] ? prepare_to_wait_event+0x100/0x100 [ 9827.569346] [c01f2ac3] intel_crtc_disable_planes+0x33/0x1c0 [i915] [ 9827.569386] [c01f3090] ironlake_crtc_disable+0x50/0x980 [i915] [ 9827.569430] [c00caf53] ? drm_modeset_lock+0x33/0xf0 [drm] [ 9827.569438] [81785ab2] ? mutex_lock+0x12/0x30 [ 9827.569479] [c01f4457] intel_crtc_update_dpms+0x67/0xa0 [i915] [ 9827.569522] [c01f8ac9] intel_connector_dpms+0x59/0x70 [i915] [ 9827.569559] [c00c1e19] drm_mode_obj_set_property_ioctl+0x399/0x3a0 [drm] [ 9827.569593] [c00c1e50] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] [ 9827.569618] [c00b0a4f] drm_ioctl+0x1df/0x680 [drm] [ 9827.569632] [811f4bc8] do_vfs_ioctl+0x2c8/0x4a0 [ 9827.569639] [811e31a1] ? __sb_end_write+0x31/0x60 [ 9827.569649] [811e0d12] ? vfs_write+0x1b2/0x1f0 [ 9827.569655] [811f4e21] SyS_ioctl+0x81/0xa0 [ 9827.569663] [81787ced] system_call_fastpath+0x1a/0x1f [ 9827.569667] ---[ end trace a41706fd70b872ee ]--- [ 9828.321052] [drm:intel_dp_start_link_train] *ERROR* too many voltage retries, give up [ 9833.866218] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 9833.866460] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 9833.867286] nouveau E[PBUS][:01:00.0] MMIO write of 0x801f FAULT at 0x6013d4 [ !ENGINE ] -- 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/1387134 Title: when enabled nvidia graphics card, desktop freezes Status in “xorg” package in Ubuntu: Confirmed Bug description: Screen freezes occasionally while simply browsing the web, can be recovered by ctrl+alt+f1 and ctrl+alt+f7 This has been the case in 14.04, and it's still the case in 14.10 (64 bit) Asus UX32V 331.89-0ubuntu5 *** 331.89-0ubuntu5 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages 100 /var/lib/dpkg/status 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] Ez egy könyvtár: '/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) .tmp.unity.support.test.0:
[Touch-packages] [Bug 1383410] Re: gcc PR 58854 - 4.8.1 and 4.8.2 are known to miscompile the ARM kernel
@Paolo: Do you know when this fix was applied and rolled out on Ubuntu Trusty? I'm asking because I can't find it mentioned in the changelogs and I want to find out, if some of the stuff I compiled might be affected. If I knew when the fix was rolled out, I could narrow that down. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1383410 Title: gcc PR 58854 - 4.8.1 and 4.8.2 are known to miscompile the ARM kernel Status in “gcc-4.8” package in Ubuntu: Invalid Bug description: From https://lkml.org/lkml/2014/10/10/272: gcc versions 4.8.[012] and 4.9.0 generates code that prematurely adjusts the stack pointer such that still-to-be-referenced locals are below the stack pointer, which allows them to be overwritten by interrupts. rmk already has a patch in his for-next branch that blacklist this compiler: http://ftp.arm.linux.org.uk/cgit/linux-arm.git/commit/?h=for- nextid=7fc150543c73de71859631c8a6b17e3067fe7617 and Trusty's toolchain is affected: [flag@stinkpad linux-2.6]$ make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h make[1]: `include/generated/mach-types.h' is up to date. CC kernel/bounds.s GEN include/generated/bounds.h CC arch/arm/kernel/asm-offsets.s arch/arm/kernel/asm-offsets.c:53:2: error: #error Your compiler is too buggy; it is known to miscompile kernels #error Your compiler is too buggy; it is known to miscompile kernels ^ arch/arm/kernel/asm-offsets.c:54:2: error: #error and result in filesystem corruption and oopses. #error and result in filesystem corruption and oopses. ^ make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 [flag@stinkpad linux-2.6]$ [flag@stinkpad linux-2.6]$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.2-19ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) [flag@stinkpad linux-2.6]$ [flag@stinkpad linux-2.6]$ dpkg -l | grep linux-gnueabihf- ii gcc-4.6-arm-linux-gnueabihf-base 4.6.3-8ubuntu1cross1.67 all GCC, the GNU Compiler Collection (base package) ii gcc-4.8-arm-linux-gnueabihf-base 4.8.2-16ubuntu4cross0.11amd64GCC, the GNU Compiler Collection (base package) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1383410/+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 1332947] Re: HDPI: unity randomly turns on large text in universal access
I now have 3 clients (all up to date, 32 and 64 bit installations) for whom it's happening on 14.04: 1) 24 inch 1920x1080 Samsung screen connected via HDMI (desktop) 2) 10 inch 1280x800 screen (netbook) 3) 15.6 inch 1920x1080 screen (laptop I mentioned previously) Yet on my own 15.6 1920x1080 screen (another laptop) this never happened. I think it's safe to assume that this has little to nothing to do with high DPI judging by examples above. Now what we need is a way to permanently deactivate this annoying setting so it never comes back unless we want it to. -- 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/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress Bug description: I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every couple of reboots, the 'large text' option in Universal Access gets switched on upon login. It happens in roughly 1 out of 5 reboots for 1 or more users on the computer. It appears to happen to people with small HighDPI screens. In my case, it's 13 inch at 2560x1600. Another example is 13 inch at 1080p - http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0 unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status intel iris pro graphics (lspci -vvv): 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device 011a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 66 Region 0: Memory at b000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at a000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1332947/+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 1387959] Re: [TOPBLOCKER] unity8 crash in image krillin rtm 139
I was only able to reproduce the thread pounding on the phone, neither X11, Mir desktop session or the emulator have shown this same behaviour. On the device, however, this is happening right from the start. The incomplete backtrace also suggests this is triggered from the android side, IIUC. -- 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/1387959 Title: [TOPBLOCKER] unity8 crash in image krillin rtm 139 Status in “unity8” package in Ubuntu: Confirmed Bug description: Earlier today, a few QA folks tested image krillin rtm 138 plus silo 13, and found that it fixed the unity8 crash from bug 1382595. Silo 13 plus silo 10 landed in image 139. Now, in image 139, unity8 is crashy again. Olli mentioned getting two crashes within a few minutes, and I got a unity8 crash while trying to accept an incoming call. I'm not sure if it's the same crash as before, or if it's a new one. Attached is the crash dump I got just after hitting 'accept' for an incoming call. I tried to pre-process it in apport-cli, but it failed with Sorry, the program unity8 closed unexpectedly // Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+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 1385709] Re: network-manager service doesn't start at boot time
@amichair Your workaround worked for me. Thank you, Daniel bit.ly/danielsilion -- 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/1385709 Title: network-manager service doesn't start at boot time Status in “network-manager” package in Ubuntu: Confirmed Bug description: I just completed the upgrade from Kubuntu 14.04 to 14.10. Haven't had any network trouble before the upgrade. After the upgrade, the network-manager service does not start when the computer boots up - the Kubuntu splash screen says 'waiting for network configuration', then 'waiting another 60 seconds for network configuration' (or something like that), then finally boots up without a network connection. Also the Network Management tray icon tooltip says that the network-manager service is not running. However if I then manually open the terminal and run 'sudo service network-manager start', then it starts ok and the network connects within a few seconds and everything works ok until the next reboot. I'm on a desktop PC with a wired LAN connection and no wifi adapter. network-manager version is 0.9.8.8-0ubuntu28. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1385709/+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 1383297] Re: Edge tutorial's redesign: new gestures
** Changed in: ubuntu-ux Status: Fix Committed = In Progress -- 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/1383297 Title: Edge tutorial's redesign: new gestures Status in Ubuntu UX bugs: In Progress Status in “unity8” package in Ubuntu: Triaged Bug description: The first-boot edge tutorial should cover a wider range of gestures than it currently does. Things like right edge swipe, bottom edge swipe, and long vs short swipes. Visual designs (not entirely finished yet): https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383297/+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 1388788] [NEW] Remove the message to restart device when resetting the launcher
Public bug reported: krillin #140 With the fix for bug 1376707 it is not longer needed to restart the device to reset the launcher and the message saying so should be removed. ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Attachment added: reset_launcher_needs_restart.png https://bugs.launchpad.net/bugs/1388788/+attachment/4251973/+files/reset_launcher_needs_restart.png ** Package changed: unity8 (Ubuntu) = ubuntu-system-settings (Ubuntu) -- 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/1388788 Title: Remove the message to restart device when resetting the launcher Status in “ubuntu-system-settings” package in Ubuntu: New Bug description: krillin #140 With the fix for bug 1376707 it is not longer needed to restart the device to reset the launcher and the message saying so should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1388788/+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 1388359] Re: User metrics can no longer be changed by double tap
** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- 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/1388359 Title: User metrics can no longer be changed by double tap Status in “unity8” package in Ubuntu: In Progress Bug description: Krillin #139 proposed On the welcome screen I only see No text messages sent today. In previous images double tapping the welcome screen would cycle through music played, phone calls made/received etc. I don't seem to be able to get it to move on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388359/+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 1387835] Re: When a dump is not collected, due to lack of memory, the reason should be in the log
** Branch linked: lp:apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1387835 Title: When a dump is not collected, due to lack of memory, the reason should be in the log Status in “apport” package in Ubuntu: Fix Committed Bug description: Using utopic, when there is not enough available memory on the system the gdb dump is not collected. It would useful to have the reason stated in the log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1387835/+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 1387835] Re: When a dump is not collected, due to lack of memory, the reason should be in the log
Fixed in trunk: http://bazaar.launchpad.net/~apport- hackers/apport/trunk/revision/2871 ** Changed in: apport (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1387835 Title: When a dump is not collected, due to lack of memory, the reason should be in the log Status in “apport” package in Ubuntu: Fix Committed Bug description: Using utopic, when there is not enough available memory on the system the gdb dump is not collected. It would useful to have the reason stated in the log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1387835/+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 1238410] Re: Inconsistent cursor visibility with cursor plugin enabled
Since my duplicate doesn't seem to add Ubuntu vivid to the affected packages and the problem seems to have returned there: How do I mark the bug as affects ubuntu vivid here? Or is doing so the Right Thing To Do? -- 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/1238410 Title: Inconsistent cursor visibility with cursor plugin enabled Status in GNOME Desktop Common Files: Fix Released Status in Gnome Settings Daemon: New Status in Unity: New Status in X.Org X server: In Progress Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Confirmed Status in “unity” source package in Saucy: Invalid Status in “xorg-server” source package in Saucy: Fix Released Bug description: On fresh boots the greeter desktop may have the cursor visible or may not until mouse is moved. On a log out/in the cursor is almost always invisible until mouse is moved. (unless made visible in greeter screen, then visible on Desktop This is all well good, maybe some intentional aesthetics/design (https://bugzilla.gnome.org/show_bug.cgi?id=687791) , however sometimes the cursor never becomes visible. In that case hitting some keys or context menu can cause it to show, though most times a log out is needed. (with the removal of ctrl+alt+delete log out this means most users will need to either blindly find the session indicator or hit power button. When the g-s-d cursor plugin is disabled then the cursor is always visible, it the plugin has no use in an ubuntu session then maybe it should be default disabled There is also the possibility, particularly on ssd drives, of a login with no session indicator. This occasionally combines with no visible cursor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 11 00:38:16 2013 InstallationDate: Installed on 2013-10-03 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131002) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1238410/+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 1238410] Re: Inconsistent cursor visibility with cursor plugin enabled
Only to make things easier for everybody affected by the bug: If I am right gsettings set org.gnome.settings-daemon.plugins.cursor active false fixes the problem. -- 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/1238410 Title: Inconsistent cursor visibility with cursor plugin enabled Status in GNOME Desktop Common Files: Fix Released Status in Gnome Settings Daemon: New Status in Unity: New Status in X.Org X server: In Progress Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Confirmed Status in “unity” source package in Saucy: Invalid Status in “xorg-server” source package in Saucy: Fix Released Bug description: On fresh boots the greeter desktop may have the cursor visible or may not until mouse is moved. On a log out/in the cursor is almost always invisible until mouse is moved. (unless made visible in greeter screen, then visible on Desktop This is all well good, maybe some intentional aesthetics/design (https://bugzilla.gnome.org/show_bug.cgi?id=687791) , however sometimes the cursor never becomes visible. In that case hitting some keys or context menu can cause it to show, though most times a log out is needed. (with the removal of ctrl+alt+delete log out this means most users will need to either blindly find the session indicator or hit power button. When the g-s-d cursor plugin is disabled then the cursor is always visible, it the plugin has no use in an ubuntu session then maybe it should be default disabled There is also the possibility, particularly on ssd drives, of a login with no session indicator. This occasionally combines with no visible cursor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 11 00:38:16 2013 InstallationDate: Installed on 2013-10-03 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131002) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1238410/+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 1236290] Re: [gesture recognition] Implement improved edge gesture detection to reduce false positives and pass non-edge gestures through to the focused app
** Changed in: unity8 (Ubuntu RTM) Status: In Progress = Fix Released ** Changed in: ubuntu-ux Status: Fix Committed = 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/1236290 Title: [gesture recognition] Implement improved edge gesture detection to reduce false positives and pass non-edge gestures through to the focused app Status in Ubuntu UX bugs: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: (from section 3.1 Edge drag gestures in the Unity Gesture UI Guidelines doc https://docs.google.com/a/canonical.com/document/d /1WJF8YdphrorvHiB5FFVxsitL5Pz-tpZ5-kmtzoD3tFc/edit ) These are Unity level gestures that allow the user to reveal and interact with shell elements like the Launcher. To reduce the number of false positives, edge drag gestures are only triggered when a user drags their finger over the edge of the screen and the drag does not have following charastics: - If the initial velocity is zero or close to zero an edge gesture is not triggered. The gesture is passed through to the app. This is because the intended gesture is probably a tap or a hold - If the initial velocity is high an edge gesture is not triggered. The gesture is passed through to the app. This is because the intended gesture is probably a flick - If the initial direction is not close to perpendicular to the edge an edge gesture is not triggered. This is because the intended gesture may be a vertical drag. - If at the gesture’s initiation the user has more than one finger touching the screen an edge gesture is not triggered. This is because the intended gesture may be a pinch, spread or rotate. --- Desired resolution: - Implement the heuristics defined above for detecting edge gestures to reduce the incidence of false positives. - The exact values for these heuristics should be easily modifiable so that we can experiment with different values to find the optimal values. - Gestures performed on the edge of the screen when are no longer detected as edge gestures due to the above heuristics should be passed through to the currently focused app. Note: The solution must fix the problem described in bug 1350881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1236290/+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 1385630] Re: systemd 215 hangs during boot
Yes, it's certainly a race condition of some sort. Unfortunately quite impossible to debug remotely as there are no available logs/kernel traces :-( SysRQ missing is also a bit unhelpful there (yes, it's usually Alt+PrintScr); does that work if boot works normally? If it just doesn't work with that hang, then the kernel is so thoroughly locked up that not even SysRQ helps. Maybe try with a different keyboard? And why systemd 208 was always successful, but 215 not? Well, that's exactly the $10,000 question that this report is about :-) It has slightly different udev rules and does different things at bootup, but there's been a lot of changes between those versions. Do you get the hang if you boot without quiet and also without splash? That's text-mode only and might be a bit faster again. -- 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/1385630 Title: systemd 215 hangs during boot Status in “systemd” package in Ubuntu: Incomplete Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+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 1355653] Re: Can't find /usr/lib/systemd/system/serial-getty@hvc0.service file
No response to comment #2 in 6 weeks, and no explanation where the
hvc0 thing comes from, so I close this. If you have more information,
I'm happy to reopen. Thanks!
** Changed in: systemd (Ubuntu)
Status: Incomplete = Invalid
--
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/1355653
Title:
Can't find /usr/lib/systemd/system/serial-getty@hvc0.service file
Status in “systemd” package in Ubuntu:
Invalid
Bug description:
== Comment: #6 - Onkar N. Mahajan onmah...@in.ibm.com - 2014-08-12 02:49:19
==
We are trying to run automated tests on Ubuntu guest.
OS: GNU/Linux
OS Version: Ubuntu Utopic Unicorn (development branch) \n
\l
Kernel Version: 3.13.0-24-generic
HTX Version: htxubuntu-296
Host Name: wyp02
Machine Serial No: Not Found
Machine Type/Model: IBM pSeries (emulated by qemu)
System FW Level: Not Found
While an internal test script tries to auto login for running the tests on the
guest, we are getting the following error :
Setting up HTX autostart
/usr/lpp/htx/etc/scripts/bootme: line 59:
/usr/lib/systemd/system/serial-getty@hvc0.service: No such file or directory
Unable to find this file for auto-login
so we added the below lines to /etc/init/hvc0.conf :
'exec /sbin/getty --autologin root -8 38400 tty1'
Now, the reboot is stuck, with below boot logs :
# virsh console ubuntu --force
Connected to domain ubuntu
Escape character is ^]
wait-for-state stop/waiting
* Stopping rsync daemon rsync [ OK
]
* Asking all remaining processes to terminate...[ OK
]
* All processes ended within 1 seconds... [ OK
]
* Deactivating swap... [ OK
]
* Will now restart
[ 3579.261038] reboot: Restarting system
SLOF **
QEMU Starting
Build Date = May 16 2014 15:10:20
FW Version = mockbuild@ release 20140514
Press s to enter Open Firmware.
Populating /vdevice methods
Populating /vdevice/l-lan@1000
Populating /vdevice/v-scsi@3000
SCSI: Looking for devices
8001 CD-ROM : QEMU QEMU CD-ROM 1.6.
8000 DISK : QEMU QEMU HARDDISK1.6.
8100 DISK : QEMU QEMU HARDDISK1.6.
8200 DISK : QEMU QEMU HARDDISK1.6.
8300 DISK : QEMU QEMU HARDDISK1.6.
8400 DISK : QEMU QEMU HARDDISK1.6.
8500 DISK : QEMU QEMU HARDDISK1.6.
8600 DISK : QEMU QEMU HARDDISK1.6.
8700 DISK : QEMU QEMU HARDDISK1.6.
Populating /vdevice/vty@3000
Populating /vdevice/nvram@7100
Populating /pci@8002000
Adapters on 08002000
00 0800 (D) : 106b 003fserial bus [ usb-ohci ]
Scanning USB
OHCI: initializing
Using default console: /vdevice/vty@3000
Welcome to Open Firmware
Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php
Trying to load: from: disk ... Successfully loaded
* finddevice /memory grub workaround *
error: no suitable video mode found.
error: failure writing sector 0x50790a0 to `ieee1275/disk'.
* finddevice /memory grub workaround *
* finddevice /memory grub workaround *
Press any key to continue...
OF stdout device is: /vdevice/vty@3000
Preparing to boot Linux version 3.13.0-24-generic (buildd@denneed02) (gcc
version 4.8.2 (Ubuntu 4.8.2-19u buntu1) ) #47-Ubuntu SMP Fri May
2 23:29:18 UTC 2014 (Ubuntu 3.13.0-24.47-generic 3.13.9)
Detected machine type: 0101
Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
command line: BOOT_IMAGE=/boot/vmlinux-3.13.0-24-generic
root=UUID=581f7086-a132-458d-80b9-4b1df0888db5 r o splash quiet
vt.handoff=7
memory layout at init:
memory_limit : (16 MB aligned)
alloc_bottom : 0490
alloc_top: 3000
alloc_top_hi : 000f4240
rmo_top : 3000
ram_top : 000f4240
instantiating rtas at 0x2fff... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings
[Touch-packages] [Bug 1388139] Re: package udev 204-5ubuntu20.7 failed to install/upgrade: postinst segfault
I think I may be 'missing' /bin/udevadm ? Indeed, not sure why. Even if udev failed to configure it should still be unpacked. What's the output of dpkg -s udev | grep Status:? Your log now shows: /usr/share/initramfs-tools/hooks/udev: 2: set: Illegal option -t Can you please show what line 2 is? The sed should have changed it to set -x, if it's something else can you please manually edit it to that? -- 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/1388139 Title: package udev 204-5ubuntu20.7 failed to install/upgrade: postinst segfault Status in “systemd” package in Ubuntu: Incomplete Bug description: Happened during normal system update. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.7 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 Date: Fri Oct 31 16:21:06 2014 DpkgTerminalLog: Preparing to unpack .../udev_204-5ubuntu20.8_i386.deb ... Segmentation fault (core dumped) dpkg: error processing archive /var/cache/apt/archives/udev_204-5ubuntu20.8_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 139 DuplicateSignature: package:udev:204-5ubuntu20.7:subprocess new pre-installation script returned error exit status 139 ErrorMessage: subprocess new pre-installation script returned error exit status 139 InstallationDate: Installed on 2012-05-02 (911 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=477c8345-1b95-4f17-89d0-878af1bd6232 ro quiet splash SourcePackage: systemd Title: package udev 204-5ubuntu20.7 failed to install/upgrade: subprocess new pre-installation script returned error exit status 139 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: Upgraded to trusty on 2014-04-25 (188 days ago) dmi.bios.date: 03/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x 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:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785-M:rvrRevX.0x: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/1388139/+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 1386361] Re: network-manager-openvpn leaks while connecting
** Description changed: Network-manager-openvpn leaks while connecting. Maybe that is intended behavior when activating a VPN-connection manually but it also leaks when Automatically connect to VPN when using this connection is checked. + + By leaking I mean that there are packages leaving/entering the machine + without passing through the VPN. Verfied the following way: 1. Set up a VPN that connects via UDP (verify it). 2. Configure a Wifi network that blocks UDP, check Automatically connect to VPN... and preselect your special VPN. 3. Connect to that newly configured Wifi network. 4. Browse the internet. Another way: 1. Type traceroute ubuntu.com into a terminal but don't press enter. 2. Start the Wifi network that uses the Automatically connect... VPN... feature. 3. Go back to the terminal press enter. 4. After the VPN has connected repeat the command. 5. Compare the first hop of the traceroute results. I consider this a security bug since it endangers users relying on a working/leak-free VPN. ** Description changed: Network-manager-openvpn leaks while connecting. Maybe that is intended - behavior when activating a VPN-connection manually but it also leaks + behavior when activating a VPN-connection manually but it also *leaks when Automatically connect to VPN when using this connection is - checked. + checked*. By leaking I mean that there are packages leaving/entering the machine without passing through the VPN. Verfied the following way: 1. Set up a VPN that connects via UDP (verify it). 2. Configure a Wifi network that blocks UDP, check Automatically connect to VPN... and preselect your special VPN. 3. Connect to that newly configured Wifi network. 4. Browse the internet. Another way: 1. Type traceroute ubuntu.com into a terminal but don't press enter. 2. Start the Wifi network that uses the Automatically connect... VPN... feature. 3. Go back to the terminal press enter. 4. After the VPN has connected repeat the command. 5. Compare the first hop of the traceroute results. I consider this a security bug since it endangers users relying on a working/leak-free VPN. ** Description changed: Network-manager-openvpn leaks while connecting. Maybe that is intended - behavior when activating a VPN-connection manually but it also *leaks + behavior when activating a VPN-connection manually but it also **leaks when Automatically connect to VPN when using this connection is - checked*. + checked**. By leaking I mean that there are packages leaving/entering the machine without passing through the VPN. Verfied the following way: 1. Set up a VPN that connects via UDP (verify it). 2. Configure a Wifi network that blocks UDP, check Automatically connect to VPN... and preselect your special VPN. 3. Connect to that newly configured Wifi network. 4. Browse the internet. Another way: 1. Type traceroute ubuntu.com into a terminal but don't press enter. 2. Start the Wifi network that uses the Automatically connect... VPN... feature. 3. Go back to the terminal press enter. 4. After the VPN has connected repeat the command. 5. Compare the first hop of the traceroute results. I consider this a security bug since it endangers users relying on a working/leak-free VPN. -- 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/1386361 Title: network-manager-openvpn leaks while connecting Status in “network-manager” package in Ubuntu: New Status in “network-manager-openvpn” package in Ubuntu: New Bug description: Network-manager-openvpn leaks while connecting. Maybe that is intended behavior when activating a VPN-connection manually but it also **leaks when Automatically connect to VPN when using this connection is checked**. By leaking I mean that there are packages leaving/entering the machine without passing through the VPN. Verfied the following way: 1. Set up a VPN that connects via UDP (verify it). 2. Configure a Wifi network that blocks UDP, check Automatically connect to VPN... and preselect your special VPN. 3. Connect to that newly configured Wifi network. 4. Browse the internet. Another way: 1. Type traceroute ubuntu.com into a terminal but don't press enter. 2. Start the Wifi network that uses the Automatically connect... VPN... feature. 3. Go back to the terminal press enter. 4. After the VPN has connected repeat the command. 5. Compare the first hop of the traceroute results. I consider this a security bug since it endangers users relying on a working/leak-free VPN. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1386361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1284352] Re: snd_hda_codec: module verification failed: signature and/or required key missing - tainting kernel
Hello David, You got point on this. In fact it was the remnants of a realtrek drivers compilation. I did delete the snd.ko and did reinstall the whole sound base, then i have installed the daily dkms. Everythink back now. Thank you so much for your usefuk remark. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1284352 Title: snd_hda_codec: module verification failed: signature and/or required key missing - tainting kernel Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Well, another ubuntu update, another round of fighting to get sound working. Dual boot to Windows 8 to make sure sound works, so hardware is fine. While in Linux terminal: brian@vaio:~$ brian@vaio:~$ lsmod | grep snd snd_hda_codec 137465 0 snd_hwdep 13602 1 snd_hda_codec snd_pcm 102033 1 snd_hda_codec snd_page_alloc 18710 1 snd_pcm snd_seq_midi 13324 0 snd_seq_midi_event 14899 1 snd_seq_midi snd_rawmidi30095 1 snd_seq_midi snd_seq61560 2 snd_seq_midi_event,snd_seq_midi snd_seq_device 14497 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 29433 2 snd_pcm,snd_seq snd69141 8 snd_hwdep,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_seq_device,snd_seq_midi soundcore 12680 1 snd brian@vaio:~$ cat /proc/asound/cards --- no soundcards --- brian@vaio:~$ sudo alsa force-reload Unloading ALSA sound driver modules: snd-hda-codec snd-hwdep snd-pcm snd-page-alloc snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq snd-seq-device snd-timer. Loading ALSA sound driver modules: snd-hda-codec snd-hwdep snd-pcm snd-page-alloc snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq snd-seq-device snd-timer. brian@vaio:~$ cat /proc/asound/cards --- no soundcards --- brian@vaio:~$ ubuntu-bug -s audio ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [ 21.837687] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Mon Feb 24 14:13:08 2014 InstallationDate: Installed on 2013-10-20 (127 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1140Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEC390X:pvrC607HR4N:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCEC390X dmi.product.version: C607HR4N dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1284352/+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 1386380] Re: network-manager-openvpn leaks w/ IPv6
** Description changed: To verify: 1. Connect to a Wifi network that assigns IPv6 addresses. 2. Open http://whatsmyipv6.org/ note down the address. 3. Connect to a VPN. 4. Open http://whatsmyipv6.org/ and compare with the result from step 2. - Temporary fix: - Set the Method dropdown under IPv6 Settings in your Wifi connection to Ignore. + Temporary fix (at least in some cases): + $ sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 I consider this a security bug since it endangers users relying on a working/leak-free VPN. ** Description changed: + By leaking I mean that there are packages leaving/entering the machine + without passing through the VPN. + To verify: 1. Connect to a Wifi network that assigns IPv6 addresses. 2. Open http://whatsmyipv6.org/ note down the address. 3. Connect to a VPN. 4. Open http://whatsmyipv6.org/ and compare with the result from step 2. - Temporary fix (at least in some cases): - $ sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 + Temporary fix (at least in my case): + sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 I consider this a security bug since it endangers users relying on a working/leak-free VPN. -- 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/1386380 Title: network-manager-openvpn leaks w/ IPv6 Status in “network-manager” package in Ubuntu: New Status in “network-manager-openvpn” package in Ubuntu: New Bug description: By leaking I mean that there are packages leaving/entering the machine without passing through the VPN. To verify: 1. Connect to a Wifi network that assigns IPv6 addresses. 2. Open http://whatsmyipv6.org/ note down the address. 3. Connect to a VPN. 4. Open http://whatsmyipv6.org/ and compare with the result from step 2. Temporary fix (at least in my case): sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 I consider this a security bug since it endangers users relying on a working/leak-free VPN. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1386380/+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 1374040] Re: Searches in Ubuntu App Store aren't localized
** Tags removed: touch-2014-10-30 ** Tags added: touch-2014-11-13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1374040 Title: Searches in Ubuntu App Store aren't localized Status in Click Package metadata search service: In Progress Status in “unity-scope-click” package in Ubuntu: Invalid Bug description: Core-app Calendar is now available in the Ubuntu App Store. Until recently, it was available in RTM image, as its name appeared localized (e.g. Calendario in Spanish). However, in order to install it, the app only appears in the Store in English. Test case. - Switch the phone to Spanish. - Reboot. - Go to Ubuntu App Store. - Search for Calendario. Expected result. - Calendar shows, with its translated name (.desktop file). Actual result. - No result. So, searches and results must support .desktop localization. To manage notifications about this bug go to: https://bugs.launchpad.net/click-package-index/+bug/1374040/+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 1388359] Re: User metrics can no longer be changed by double tap
http://paste.ubuntu.com/8802213/ is what gets printed into ~/.cache/upstart/unity8.log if i double-tap on the usermetrics UI in the greeter -- 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/1388359 Title: User metrics can no longer be changed by double tap Status in “unity8” package in Ubuntu: In Progress Bug description: Krillin #139 proposed On the welcome screen I only see No text messages sent today. In previous images double tapping the welcome screen would cycle through music played, phone calls made/received etc. I don't seem to be able to get it to move on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388359/+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 1385124] Re: upstart : after a random uptime service failed to start - unable to granpt: No such file or directory
** Tags added: upstart ** Tags added: grantp -- 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/1385124 Title: upstart : after a random uptime service failed to start - unable to granpt: No such file or directory Status in “upstart” package in Ubuntu: New Bug description: Kernel : latest 3.14.20 + grsec Description: Ubuntu 14.04.1 LTS Release: 14.04 Upstart version : Upstart : 1.12.1-0ubuntu4.2 Problem reported on more than 10 servers with the same configuration I use upstart to start and stop my service. After a random time (for minutes to days), some services begin failed to start, some other continue starting but always put a new line in dmesg Example for rsyslogd service which never success to start when the problem begin : service rsyslog restart stop: Unknown instance: start: Job failed to start dmesg [...] init: Failed to spawn rsyslog pre-start process: unable to granpt: No such file or directory init: Failed to spawn startpar-bridge (rsyslog--stopped) main process: unable to granpt: No such file or directory init: Failed to spawn rsyslog pre-start process: unable to granpt: No such file or directory init: Failed to spawn startpar-bridge (rsyslog--stopped) main process: unable to granpt: No such file or directory init: Failed to spawn rsyslog pre-start process: unable to granpt: No such file or directory init: Failed to spawn startpar-bridge (rsyslog--stopped) main process: unable to granpt: No such file or directory And for ssh, which success : service ssh restart ssh stop/waiting ssh start/running, process 32052 dmesg [...] tinit: Failed to spawn startpar-bridge (ssh--stopped) main process: unable to granpt: No such file or directory init: Failed to spawn startpar-bridge (ssh--started) main process: unable to granpt: No such file or directory The only solution I found is to reboot servers, until next time the problem appeared. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1385124/+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 1388825] [NEW] expand_ppa_line function removed from ppa
Public bug reported: The following change removes the expand_ppa_line function, without any mention elsewhere. http://bazaar.launchpad.net/~ubuntu-core-dev/software- properties/main/revision/904#softwareproperties/ppa.py I don't know if this is intended, if so: shouldn't this change have been done in a non BC breaking way, by first deprecating the function? DistroRelease: Ubuntu 14.10 Package: python-software-properties 0.94 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1388825 Title: expand_ppa_line function removed from ppa Status in “software-properties” package in Ubuntu: New Bug description: The following change removes the expand_ppa_line function, without any mention elsewhere. http://bazaar.launchpad.net/~ubuntu-core-dev/software- properties/main/revision/904#softwareproperties/ppa.py I don't know if this is intended, if so: shouldn't this change have been done in a non BC breaking way, by first deprecating the function? DistroRelease: Ubuntu 14.10 Package: python-software-properties 0.94 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1388825/+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 1388827] [NEW] crash when cancelling SIM pin entry
Public bug reported: Boot the phone with two SIM cards loaded, requiring SIM PIN. When the phone boots up and asks you for the first SIM PIN, click the cancel button. There's 50% chance it'll take down the whole session while trying to bring up the SIM pin entry dialog for the second PIN. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: - Boot the phone with SIM card(s) loaded, requiring SIM PIN. When the - phone boots up and asks you for the SIM PIN, click the cancel button. - There's 50% chance it'll take down the whole session. + Boot the phone with two SIM cards loaded, requiring SIM PIN. When the + phone boots up and asks you for the first SIM PIN, click the cancel + button. There's 50% chance it'll take down the whole session while + trying to bring up the SIM pin entry dialog for the second PIN. -- 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/1388827 Title: crash when cancelling SIM pin entry Status in “unity8” package in Ubuntu: New Bug description: Boot the phone with two SIM cards loaded, requiring SIM PIN. When the phone boots up and asks you for the first SIM PIN, click the cancel button. There's 50% chance it'll take down the whole session while trying to bring up the SIM pin entry dialog for the second PIN. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388827/+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 1388827] Re: crash when cancelling SIM pin entry
*** This bug is a duplicate of bug 1386803 *** https://bugs.launchpad.net/bugs/1386803 ** This bug has been marked a duplicate of bug 1386803 [TOPBLOCKER] unity8 crashing a lot since image #126 -- 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/1388827 Title: crash when cancelling SIM pin entry Status in “unity8” package in Ubuntu: New Bug description: Boot the phone with two SIM cards loaded, requiring SIM PIN. When the phone boots up and asks you for the first SIM PIN, click the cancel button. There's 50% chance it'll take down the whole session while trying to bring up the SIM pin entry dialog for the second PIN. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388827/+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 1388827] Re: crash when cancelling SIM pin entry
*** This bug is a duplicate of bug 1386803 *** https://bugs.launchpad.net/bugs/1386803 seems to happen in media-hub: #0 0x0018 in ?? () #1 0xa7713caa in std::functionvoid (core::ubuntu::media::Player::PlaybackStatus)::function(std::functionvoid (core::ubuntu::media::Player::PlaybackStatus) const) (this=0xa5c18acc, __x=...) at /usr/include/c++/4.9/functional:2412 #2 0xa7713f88 in SlotWrapper (this=0xa5c18acc) at /usr/include/core/signal.h:45 #3 core::Signalcore::ubuntu::media::Player::PlaybackStatus::operator() (this=optimized out, args#0=core::ubuntu::media::Player::stopped) at /usr/include/core/signal.h:135 #4 0xa7716832 in core::dbus::Signalmpris::Player::Signals::PlaybackStatusChanged, core::ubuntu::media::Player::PlaybackStatus::operator() (this=0x1a55740, msg=std::shared_ptr (count 1, weak 1) 0x9e2fb5e8) at /usr/include/core/dbus/impl/signal.h:343 #5 0xb1034546 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 #6 0xb102ad54 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 #7 0xb1029572 in core::dbus::Bus::handle_message(std::shared_ptrcore::dbus::Message const) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 #8 0xb102960e in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 #9 0xb383932e in dbus_connection_dispatch () from /lib/arm-linux-gnueabihf/libdbus-1.so.3 #10 0xb10419c8 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 #11 0xb103f4d8 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 #12 0xb103f7b6 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 #13 0xb1028958 in core::dbus::Bus::run() () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4 #14 0xb62aa5a4 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 #15 0xb5fcff98 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0 #16 0xb619d22c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6 -- 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/1388827 Title: crash when cancelling SIM pin entry Status in “unity8” package in Ubuntu: New Bug description: Boot the phone with two SIM cards loaded, requiring SIM PIN. When the phone boots up and asks you for the first SIM PIN, click the cancel button. There's 50% chance it'll take down the whole session while trying to bring up the SIM pin entry dialog for the second PIN. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388827/+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 1388052] Re: OptionSelector in dialog has inconsistent borders
Thanks Matthew, that's not really a border, it's a Divider, which listitem elements have set by default. There is a showDivider property that can be set to false. The fact that the line doesn't reach the border should be fixed in https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/thindivider- margins/+merge/239320 (which didn't land yet) There might also be an issue there in setting, that it uses the list version of the optionselector, which is why it has a divider. The code could use the non list variant or toggle showDivider to false Should we reassign to settings to address the previous point, or do you still think the OptionSelector in the toolkit is wrong? Your issue might be rather with the fact that listitem show a divider by default (it's also what leads to have an extra line next to section divider in some places)... -- 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/1388052 Title: OptionSelector in dialog has inconsistent borders Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: Ubuntu 14.10 r135 1. Go to System Settings Wi-Fi. 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose Connect to hidden network. 4. Look at the Security menu. What you see: The menu has a border along most of its bottom, but not all, and not the other three sides. What you should see: The menu has a consistent border. To be consistent with text fields, probably its corners should be rounded as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1388052/+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 1387944] Re: Transition to bluez5
*** This bug is a duplicate of bug 1162781 *** https://bugs.launchpad.net/bugs/1162781 ** This bug has been marked a duplicate of bug 1162781 bluez package out of date, 5.3 is available -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1387944 Title: Transition to bluez5 Status in “bluez” package in Ubuntu: New Status in “bluez” package in Debian: Fix Released Bug description: Please package bluez 5 for ubuntu vivid. It changes much of the API and is required by projects such as gnome-bluetooth, bluedevil, and blueman. Bluez 4 has been deprecated for some time, so fixes will only be received in version 5 anyway. The only components that need major work are ubuntu-only packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1387944/+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+15.04.20141031.2-0ubuntu1 --- ubuntu-system-settings (0.3+15.04.20141031.2-0ubuntu1) vivid; urgency=low [ Sebastien Bacher ] * Tweaks to try to make the section headers and titles closer to the design. Use a custom component, with tweaked margins and disabled tap effects, for that. [ Iain Lane ] * Move formatSize into a new Utilities class in the qml context and call this from the updates panel to consistently display sizes (LP: #1385286) * Update to work with UPower = 0.99 as well as current versions (LP: #1330037) [ Albert Astals ] * i18n++ (LP: #1386730) [ William Hua ] * Re-translate the UI when reboot is cancelled after language change. (LP: #1377984) [ jonas-drange ] * [cellular] split Cellular Data and Connection type into two separate pieces in the UI for both single and multi SIM (LP: #1361226) * [wifi] use actiongroup to hide connect to other networks (LP: #1377076) [ Michael Terry ] * When the power button is held down, show the shutdown dialog like we do in the unity8 shell. (LP: #1381731) * Add a Continue button when choosing a passphrase. And fix a few other design nits with choosing a password. [ Michael Zanetti ] * Drop reboot notification label on launcher reset. (LP: #1376707) [ Mathieu Trudel-Lapierre ] * [bluetooth] Show bluetooth address instead of name while it's not detected; to be updated once available. (LP: #1382767) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 31 Oct 2014 14:53:52 + ** Changed in: ubuntu-system-settings (Ubuntu) Status: In Progress = Fix Released ** No longer affects: ubuntu-system-settings -- 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: In Progress 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 1387806] Re: Connect to Hidden Network dialog has wonky padding
The x1/x2 difference is a toolkit issue for sure (the toolkit demo gallery has the same margins difference), it looks like the y1/y2 is as well but there might be some settings tweak as well then so keeping a component in low priority, to check again how are things looking once the uitk is fixed ** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided = Low ** Also affects: ubuntu-ui-toolkit Importance: Undecided Status: New ** Summary changed: - Connect to Hidden Network dialog has wonky padding + toolkit dialogs have wonky padding ** Changed in: ubuntu-system-settings (Ubuntu) Status: New = Confirmed -- 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/1387806 Title: toolkit dialogs have wonky padding Status in Ubuntu UI Toolkit: New Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: Ubuntu 14.10 r135 1. Go to System Settings Wi-Fi. 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose Connect to hidden network. What you see: A dialog where the left padding (x1) is less than the right padding (x2), and the top padding (y1) is less than the bottom padding (y2). What you should see: A dialog where the left and right padding are equal (x1 = x2), and the top and bottom padding are equal (y1 = y2). I don't know whether this is a System Settings bug, a toolkit bug, or a combination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1387806/+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
I have this problem but can access the desktop using SSH. Is there a process I can kill/restart to fix this condition? -- 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 1385418] Re: update for 15.04 frameworks
This was fixed with 1.3.0 in vivid. ** Changed in: apparmor-easyprof-ubuntu (Ubuntu) Status: Triaged = Fix Released -- 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/1385418 Title: update for 15.04 frameworks Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Bug description: Policy updates for 15.04 frameworks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1385418/+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 1387806] Re: toolkit dialogs have wonky padding
note that the title has the same issue, it's not correctly horizontally centered -- 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/1387806 Title: toolkit dialogs have wonky padding Status in Ubuntu UI Toolkit: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 r135 1. Go to System Settings Wi-Fi. 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose Connect to hidden network. What you see: A dialog where the left padding (x1) is less than the right padding (x2), and the top padding (y1) is less than the bottom padding (y2). What you should see: A dialog where the left and right padding are equal (x1 = x2), and the top and bottom padding are equal (y1 = y2). I don't know whether this is a System Settings bug, a toolkit bug, or a combination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1387806/+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 961977] Re: Launcher shows arrows for applications on all workspaces
Correction: I have upgraded up until 14.10 and am sure things still worked as I was used to . Reinstalling broke things. -- 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/961977 Title: Launcher shows arrows for applications on all workspaces Status in Unity: Fix Released Status in Unity Distro Priority: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Failed checkbox-unity testcase launcher/arrows-notin-currentws (on step 5). When an application is opened on more than one workspace and there is an application window on the current workspace, the arrows on the launcher show the count for all applications on all workspaces. By design it should be only the windows on the current workspace. How to reproduce: 1. Start nautilus on workspace 1 2. Switch to workspace 2 3. Start a new nautilus window on workspace 2 Expected result: Launcher shows one arrow to the left of the nautilus icon. Actual result: Launcher shows two arrows to the left of the nautilus icon. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/961977/+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 1328513] Re: Preview header title truncated
** Changed in: ubuntu-ux Status: Fix Committed = 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/1328513 Title: Preview header title truncated Status in The Savilerow project: Fix Released Status in Ubuntu UX bugs: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: When developing a news scope. The title in the grid card fits the news headline, but in the preview (the same text) the title gets truncated. This looks very strange and makes reading news hard tbh. Shouldnt we have a common behaviour (see attached files) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1328513/+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 1350952] Re: [Indicators] replace the text Empty! with something more useful
** Changed in: ubuntu-ux Assignee: James Mulholland (jamesjosephmulholland) = Paty Davila (dizzypaty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1350952 Title: [Indicators] replace the text Empty! with something more useful Status in Transfer Indicator: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “indicator-messages” package in Ubuntu: Invalid Status in “indicator-transfer” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Bug description: when clearing the menu on this indicator (and others), the text Empty! is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-transfer/+bug/1350952/+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 1388569] Re: popup dialog content shifted to the left in image 140
*** This bug is a duplicate of bug 1387806 *** https://bugs.launchpad.net/bugs/1387806 There's a good chance this is related to my bug fixing on scrollable dialogs. I haven't noticed it before unfortunately… it looks as if there's a consistent margin there affecting the centering. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed ** This bug has been marked a duplicate of bug 1387806 toolkit dialogs have wonky padding -- 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/1388569 Title: popup dialog content shifted to the left in image 140 Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: on krilling image 140 all content of popup dialogs is shifted to the left instead of being properly centerd (i think this has started far before 140 though, but can not nail it to one specific image) this is easily reproducable by bringing up the shutdown/reboot dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1388569/+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 1387806] Re: toolkit dialogs have wonky padding
** Changed in: ubuntu-ui-toolkit Status: New = Confirmed -- 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/1387806 Title: toolkit dialogs have wonky padding Status in Ubuntu UI Toolkit: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 r135 1. Go to System Settings Wi-Fi. 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose Connect to hidden network. What you see: A dialog where the left padding (x1) is less than the right padding (x2), and the top padding (y1) is less than the bottom padding (y2). What you should see: A dialog where the left and right padding are equal (x1 = x2), and the top and bottom padding are equal (y1 = y2). I don't know whether this is a System Settings bug, a toolkit bug, or a combination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1387806/+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 1387806] Re: toolkit dialogs have wonky padding
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- 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/1387806 Title: toolkit dialogs have wonky padding Status in Ubuntu UI Toolkit: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 r135 1. Go to System Settings Wi-Fi. 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose Connect to hidden network. What you see: A dialog where the left padding (x1) is less than the right padding (x2), and the top padding (y1) is less than the bottom padding (y2). What you should see: A dialog where the left and right padding are equal (x1 = x2), and the top and bottom padding are equal (y1 = y2). I don't know whether this is a System Settings bug, a toolkit bug, or a combination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1387806/+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 961977] Re: Launcher shows arrows for applications on all workspaces
I want to propose reverting this change. I consider the current behavior to be a bug. Switching is far more useful across workspaces and hardly useful inside the current one. I have been upgrading Ubuntu since 12.04 up until 14.04 and am quite sure the behavior did not break then. Recently I reinstalled 14.10 and now I can not get the correct behavior back. So I assume it is a setting that is just not offered anymore. PLEASE revert or at least make this configurable. -- 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/961977 Title: Launcher shows arrows for applications on all workspaces Status in Unity: Fix Released Status in Unity Distro Priority: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Failed checkbox-unity testcase launcher/arrows-notin-currentws (on step 5). When an application is opened on more than one workspace and there is an application window on the current workspace, the arrows on the launcher show the count for all applications on all workspaces. By design it should be only the windows on the current workspace. How to reproduce: 1. Start nautilus on workspace 1 2. Switch to workspace 2 3. Start a new nautilus window on workspace 2 Expected result: Launcher shows one arrow to the left of the nautilus icon. Actual result: Launcher shows two arrows to the left of the nautilus icon. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/961977/+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 1387758] Re: gstreamer1.0-tools package not available for rtm branch
That package is available no? https://launchpad.net/ubuntu/+source/gstreamer1.0/1.4.0-1/+build/6199586 has a build for it and debs What did you try to do exactly? ** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided = Low ** Changed in: gstreamer1.0 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1387758 Title: gstreamer1.0-tools package not available for rtm branch Status in “gstreamer1.0” package in Ubuntu: Incomplete Bug description: Need to have the gstreamer1.0-tools available so that tools like gst- discoverer-1.0 and gst-launch-1.0 are available for use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1387758/+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 1320534] Re: missing /run/shm backwards compat symlink
** Branch linked: lp:ubuntu/vivid-proposed/sysvinit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1320534 Title: missing /run/shm backwards compat symlink Status in “mountall” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: Fix Committed Status in “systemd” package in Debian: New Bug description: systemd does not honor ubuntu default mountpoints as listed in /lib/init/fstab specifically just /run/shm is missing, which breaks existing ubuntu chroots which have installed initscripts package which made /dev/shm a symlink to /run/shm. initscripts.postinst should probably stop doing that, as that breaks ubuntu chroots on systems that don't have /run/shm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1320534/+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 1387758] Re: gstreamer1.0-tools package not available for rtm branch
https://launchpad.net/ubuntu-rtm/+source/gstreamer1.0/1.4.0-1 as well -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1387758 Title: gstreamer1.0-tools package not available for rtm branch Status in “gstreamer1.0” package in Ubuntu: Incomplete Bug description: Need to have the gstreamer1.0-tools available so that tools like gst- discoverer-1.0 and gst-launch-1.0 are available for use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1387758/+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
I would like to know the answer to that as well. Back in the good 'ol days the screen lock was a separate process, and pkill -9 gnome-screensaver would bring back the desktop. But now...? There is a process called /usr/lib/unity/unity-panel-service --lockscreen-mode, but if I kill -9 on it, it just comes back with a new PID. Michael On 11/03/2014 08:38 AM, Bruce MacNaughton wrote: I have this problem but can access the desktop using SSH. Is there a process I can kill/restart to fix this condition? -- 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
Re: [Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
When I do that, I get the desktop back, but no dash, launcher, or panel. On 11/03/2014 08:54 AM, Erik wrote: unity --replace On Mon, Nov 3, 2014 at 5:38 AM, Bruce MacNaughton bmacnaugh...@msn.com wrote: I have this problem but can access the desktop using SSH. Is there a process I can kill/restart to fix this condition? -- You received this bug notification because you are subscribed to the bug report. 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 -- 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 1387806] Re: toolkit dialogs have wonky padding
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/lessItemSpacing -- 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/1387806 Title: toolkit dialogs have wonky padding Status in Ubuntu UI Toolkit: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 r135 1. Go to System Settings Wi-Fi. 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose Connect to hidden network. What you see: A dialog where the left padding (x1) is less than the right padding (x2), and the top padding (y1) is less than the bottom padding (y2). What you should see: A dialog where the left and right padding are equal (x1 = x2), and the top and bottom padding are equal (y1 = y2). I don't know whether this is a System Settings bug, a toolkit bug, or a combination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1387806/+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 1387806] Re: toolkit dialogs have wonky padding
** Changed in: ubuntu-ui-toolkit Assignee: (unassigned) = Christian Dywan (kalikiana) ** Changed in: ubuntu-ui-toolkit Status: Confirmed = In Progress -- 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/1387806 Title: toolkit dialogs have wonky padding Status in Ubuntu UI Toolkit: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 r135 1. Go to System Settings Wi-Fi. 2. If Wi-Fi is off, turn it on. 3. Scroll to the bottom of the list and choose Connect to hidden network. What you see: A dialog where the left padding (x1) is less than the right padding (x2), and the top padding (y1) is less than the bottom padding (y2). What you should see: A dialog where the left and right padding are equal (x1 = x2), and the top and bottom padding are equal (y1 = y2). I don't know whether this is a System Settings bug, a toolkit bug, or a combination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1387806/+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 1386653] Re: [TOPBLOCKER] Scopes fail to launch when the network stack is not up
the only thing that's gone in recently was the dbus update to clean up dead client obj's -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1386653 Title: [TOPBLOCKER] Scopes fail to launch when the network stack is not up Status in “unity-scope-click” package in Ubuntu: Invalid Status in “unity-scope-scopes” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Bug description: I've seen this randomly from time to time on every other boot, but it happens reliably when flight mode is enabled Steps to reproduce: - Enable flight mode - Reboot Expected result: - Scopes launch and fail network requests Actual: - Black scope screen Notes: - Launcher items work and launch fine - Indicators work fine In the logs I see something like: unity8: Pre-populating scope unity-scope-nearby Pre-populating scope com.canonical.scopes.photos_photos file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:77:1: QM L Label: Binding loop detected for property height file:///usr/share/unity8/Dash/CardTool.qml:179:38: Unable to assign [undefined] to bool invalidateScopeResults: no such scope ' musicaggregator ' invalidateScopeResults: no such scope ' mediascanner-music ' invalidateScopeResults: no such scope ' videoaggregator ' invalidateScopeResults: no such scope ' mediascanner-video ' scope-registry: ... RegistryObject::ScopeProcess::on_process_death(): Process for scope: clickscope exited ... current build number: 129 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-26 15:25:59 version version: 129 version ubuntu: 20141026 version device: 20141015-32e0f27 version custom: 1413941794 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1386653/+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 1387758] Re: gstreamer1.0-tools package not available for rtm branch
I tried doing an apt-cache search for gstreamer1.0-tools and it did not show up as an installable candidate. I tried this on a device itself using the rtm branch. Can you confirm that you in fact see this when doing apt-cache search? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1387758 Title: gstreamer1.0-tools package not available for rtm branch Status in “gstreamer1.0” package in Ubuntu: Incomplete Bug description: Need to have the gstreamer1.0-tools available so that tools like gst- discoverer-1.0 and gst-launch-1.0 are available for use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1387758/+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 1387959] Re: [TOPBLOCKER] unity8 crash in image krillin rtm 139
** Tags added: rouch-2014-11-06 ** Tags removed: rouch-2014-11-06 ** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1387959 Title: [TOPBLOCKER] unity8 crash in image krillin rtm 139 Status in “unity8” package in Ubuntu: Confirmed Bug description: Earlier today, a few QA folks tested image krillin rtm 138 plus silo 13, and found that it fixed the unity8 crash from bug 1382595. Silo 13 plus silo 10 landed in image 139. Now, in image 139, unity8 is crashy again. Olli mentioned getting two crashes within a few minutes, and I got a unity8 crash while trying to accept an incoming call. I'm not sure if it's the same crash as before, or if it's a new one. Attached is the crash dump I got just after hitting 'accept' for an incoming call. I tried to pre-process it in apport-cli, but it failed with Sorry, the program unity8 closed unexpectedly // Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+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 |
Confirmed, way to trigger it easily - connect to IRC using xchat-gnome with messaging menu integration enabled - connect with another client and a nickname including a | - talk to the first client - segfault Lars, could you have a look to this one? ** Changed in: unity (Ubuntu) Importance: Undecided = High ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity (Ubuntu) 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” 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/ubuntu/+source/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 1298330] Re: GtkFileChooserDialog hangs in org.gtk.vfs.Mount QueryInfo
** Changed in: gtk Status: New = Incomplete -- 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/1298330 Title: GtkFileChooserDialog hangs in org.gtk.vfs.Mount QueryInfo Status in GTK+ GUI Toolkit: Incomplete Status in “gtk+3.0” package in Ubuntu: Triaged Bug description: I'm getting this quite often in Trusty (file-roller, evolution...): when an app tries to open a file-chooser dialog, it hangs while calling g_dbus_proxy_call_sync on org.gtk.vfs.Mount.QueryInfo in gtk_places_sidebar_init See attached bt (full at the bottom). To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1298330/+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 1379657] Re: Run click hook run-user in the ubuntu-core image
** Branch linked: lp:ubuntu/vivid-proposed/click -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1379657 Title: Run click hook run-user in the ubuntu-core image Status in “click” package in Ubuntu: Fix Committed Bug description: The ubuntu-touch image uses the click-user-hoks.conf upstart session hook to run click hook run-user so that the hooks for the user are updated. The core images have /usr/lib/systemd/user/click-user-hooks.service that does the same but apparently its not always working (according to kickinz1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1379657/+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 1386534] Re: kernel dependent deterministic view crash on X startup
There is a typo at the last item of the list above, so the correct list is: 3.13.0-36-generic NO problem 3.13.0-37-generic problem in question 3.16.0-23-generic problem in question 3.16.0-24-generic problem in question -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2
[Touch-packages] [Bug 1383486] Re: menu to select zoom doesn't drop down
The popovers work for me in vivid, seems the patches are good -- 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/1383486 Title: menu to select zoom doesn't drop down Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “gtk+3.0” source package in Utopic: Confirmed Bug description: To reproduce open a pdf file in evince from pcmanfm or another file manager. Then move the mouse to the upper right corner of the window along the top bar. Then try to click on the arrow pointing down to drop down the menu. The mouse pointer will click but no menu will drop down. I can still edit the zoom by clickin in this bar but I cannoy select fit page or fit width like I used to be able to in 14.04. I am using lxde as my desktop environment with openbox as my window manager. evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Description: Ubuntu 14.10 Release: 14.10 I expected a menu to be able to choose zoom instead I can only change zoom by typing in the box. Work around is to manually set a zoom by typing it in. This could lead to some accessibility problems for people with low vision if they need to zoom in on a pdf and don't know the workaround. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu7 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Oct 20 14:08:31 2014 InstallationDate: Installed on 2014-09-30 (19 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1383486/+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
This is still not solved in ubuntu touch rtm r5 on my nexus 4. Is there any work going on? Thanks in advance. -- 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: New Status in “webbrowser-app” package in Ubuntu: Confirmed 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 1372948] Re: Keyboard doesn't auto-capitalize 'I'
** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-1372948 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1372948 Title: Keyboard doesn't auto-capitalize 'I' Status in Ubuntu Keyboard: Confirmed Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: In English 'I' is not auto-capitalized. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-keyboard 0.99.trunk.phablet2+14.10.20140910~rtm-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Tue Sep 23 15:44:57 2014 InstallationDate: Installed on 2014-09-16 (7 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-030205) SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1372948/+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
Assigning to Michi only so he can comment on the proposed path. Please
assign back to me if you agree.
** Description changed:
- Summary says it all, just need to decide on the directory.
+ 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}/** mrwklix,
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
Assignee: (unassigned) = Michi Henning (michihenning)
** Description changed:
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}/** mrwklix,
+ # 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,
--
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 1380848] Re: Apps and services use large amount of CPU after unity8 resets
I wonder if we should make it so the whole session is restarted (or even the phone rebooted) if unity8 respawned... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1380848 Title: Apps and services use large amount of CPU after unity8 resets Status in Media Hub: Triaged Status in “dbus-cpp” package in Ubuntu: New Bug description: I noticed that media-hub-service can get into a state where it uses a large amount of CPU. Steps to reproduce 1) Start music-app 2) Play music 3) Pause music 4) Close the music-app 5) $ pkill unity8 (to emulate unity crashing a resetting) Notice that media-hub-service is now using a large amount of CPU, note this [0] is the media-hub.log at the time. The device has to be reset to get the CPU usage back to normal. 0 - http://pastebin.ubuntu.com/8553411/ To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1380848/+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: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
I agree it may look fixed with silo 16 (and it likely helps), yet I can't reproduce the issue on image 140; without the updated package installed: phablet@ubuntu-phablet:~$ apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu29 Candidate: 0.9.8.8-0ubuntu30 Version table: 0.9.8.8-0ubuntu30 0 500 http://ppa.launchpad.net/ci-train-ppa-service/landing-016/ubuntu-rtm/ 14.09/main armhf Packages *** 0.9.8.8-0ubuntu29 0 500 http://derived.archive.canonical.com/ubuntu-rtm/ 14.09/main armhf Packages 100 /var/lib/dpkg/status qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status always returns proper status on my device. -- 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: 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: Confirmed 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 670364] Re: compiz / g_main_loop integration test application
** Changed in: unity (Ubuntu) Status: Triaged = Won't Fix ** Changed in: unity Status: Triaged = Won't Fix ** Changed in: compiz Status: Triaged = Won't Fix -- 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/670364 Title: compiz / g_main_loop integration test application Status in Compiz: Won't Fix Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: The new integration of g_main_loop into compiz may impact the rest of its core, or plugins. This task captures the need to develop a test application to exercise that integration and help identify potential regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/670364/+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 1201180] Re: powerbtn.sh conflicts with logind
** Branch linked: lp:ubuntu/vivid-proposed/acpid -- 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/1201180 Title: powerbtn.sh conflicts with logind Status in “acpid” package in Ubuntu: Fix Released Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+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
** Tags added: rtm14
--
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 1388005] Re: ppa-purge
** Changed in: xorg (Ubuntu) Status: Incomplete = Invalid -- 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/1388005 Title: ppa-purge Status in “xorg” package in Ubuntu: Invalid Bug description: je bonjour je ne parviens pas à intaller ppa-purge ou de le mettre en ligne de commande terminal donc je ne sais pas mettre à jour. Merci pour votre aide Sur le forum je n'ai pas encore eu de solution Cordialement JPDW 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 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 31 10:22:33 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a8c] InstallationDate: Installed on 2014-05-10 (174 days ago) InstallationMedia: Cubuntu 14.04 - Release amd64 LightdmGreeterLog: ** (lightdm-gtk-greeter:1656): WARNING **: Failed to load user background: Impossible d'ouvrir le fichier « /home/jpdwhp/.cinnamon/backgrounds/Champagne3.JPG » : Permission non accordée LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1661): WARNING **: Failed to load user background: Impossible d'ouvrir le fichier « /home/jpdwhp/.cinnamon/backgrounds/Champagne3.JPG » : Permission non accordée g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: Compaq-Presario WC690AA-UUG CQ5310BE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=2e8ed171-6550-4a46-a4b4-3db56a7eed2d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.09 dmi.board.name: ETON dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.09:bd11/27/2009:svnCompaq-Presario:pnWC690AA-UUGCQ5310BE:pvr:rvnFOXCONN:rnETON:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: WC690AA-UUG CQ5310BE dmi.sys.vendor: Compaq-Presario 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.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 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: Fri Oct 31 08:25:00 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 49177 vendor PHL xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388005/+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: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
I'm on 140 (clean flash) and it's not the case here (regarding comment #21). y1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status/connectivit online disabled wi-fi (only connection) y1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status/connectivit online enabled flight mode y1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status/connectivit online phablet@ubuntu-phablet:~$ nmcli nm RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running disconnectedenabled disabled enabled disabled y1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status/connectivit offline -- 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: 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: Confirmed 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 1386109] Re: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
scratch that, re-applying the update I can again reproduce the bug. indicator-network helps but is not the full solution. -- 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: 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: Confirmed 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 1386109] Re: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
indicator-network armhf 0.5.1+14.10.20141030~rtm-0ubuntu1 fixes the issue; the new upload with rebuild against the new dbus-cpp seems to fix the problem sufficiently: the qdbus command now tracks the right global state properly. -- 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: 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: Confirmed 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 1388647] [NEW] DRI_PRIME=1 has no effect in Ubuntu 14.10
You have been subscribed to a public bug: On an Optimus laptop with both GPUs enabled, having run this command so that the Nvidia GPU can be used to offload 3D work from the Intel GPU: ``` xrandr --setprovideroffloadsink nouveau Intel ``` Then running this command: ``` DRI_PRIME=1 glxinfo | grep OpenGL vendor string ``` provides the incorrect output: ``` OpenGL vendor string: Intel Open Source Technology Center ``` when it should actually show that the Nouveau driver is in use for the program. This worked previously in Ubuntu 14.04. Apart from only having a 3.16 kernel (instead of 3.17) Ubuntu 14.10 actually supports recent enough versions of the requisite packages necesarry to get DRI 3 offloading support, so perhaps this is part of the problem. Or, more likely, I notice a Nouveau failure after startup, and then again after running xrandr commands, for example: ``` [ 170.912483] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 217.550205] thinkpad_acpi: EC reports that Thermal Table has changed [ 223.857442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.858395] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.860200] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] [ 224.654622] thinkpad_acpi: EC reports that Thermal Table has changed [ 825.172094] thinkpad_acpi: EC reports that Thermal Table has changed [ 831.132156] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.133030] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.134832] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] ``` Perhaps this is just a regression in either the Nouveau or Intel drivers for my hardware. I'm using a Lenovo T430. I can confirm that I'm able to start the laptop without errors when I only enable the Intel GPU or NVidia GPU separately, and only see this error when both GPUs are enabled simultaneously. Extra Info: 1: Description: Ubuntu 14.10 Release:14.10 2: N/A 3: The text 'nouveau' should have appeared in the output of the command. 4: The text 'Intel' appeared in the output of the command. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- DRI_PRIME=1 has no effect in Ubuntu 14.10 https://bugs.launchpad.net/bugs/1388647 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1381041] Re: [TOPBLOCKER] Network indicator is sometimes blank
** Branch linked: lp:ubuntu/vivid-proposed/indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1381041 Title: [TOPBLOCKER] Network indicator is sometimes blank Status in “indicator-network” package in Ubuntu: In Progress Status in “indicator-network” source package in Utopic: New Status in “indicator-network” source package in Vivid: In Progress Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: This is on krillin r103, but it has been happening for a while. See attached photo. I am not certain what triggers it. but I think it may happen when wifi APs become in and out of range while walking around town (as if the list does not refresh reliably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1381041/+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 1388647] Re: DRI_PRIME=1 has no effect in Ubuntu 14.10
** Package changed: ubuntu = xorg (Ubuntu) -- 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/1388647 Title: DRI_PRIME=1 has no effect in Ubuntu 14.10 Status in “xorg” package in Ubuntu: New Bug description: On an Optimus laptop with both GPUs enabled, having run this command so that the Nvidia GPU can be used to offload 3D work from the Intel GPU: ``` xrandr --setprovideroffloadsink nouveau Intel ``` Then running this command: ``` DRI_PRIME=1 glxinfo | grep OpenGL vendor string ``` provides the incorrect output: ``` OpenGL vendor string: Intel Open Source Technology Center ``` when it should actually show that the Nouveau driver is in use for the program. This worked previously in Ubuntu 14.04. Apart from only having a 3.16 kernel (instead of 3.17) Ubuntu 14.10 actually supports recent enough versions of the requisite packages necesarry to get DRI 3 offloading support, so perhaps this is part of the problem. Or, more likely, I notice a Nouveau failure after startup, and then again after running xrandr commands, for example: ``` [ 170.912483] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 217.550205] thinkpad_acpi: EC reports that Thermal Table has changed [ 223.857442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.858395] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.860200] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] [ 224.654622] thinkpad_acpi: EC reports that Thermal Table has changed [ 825.172094] thinkpad_acpi: EC reports that Thermal Table has changed [ 831.132156] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.133030] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.134832] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] ``` Perhaps this is just a regression in either the Nouveau or Intel drivers for my hardware. I'm using a Lenovo T430. I can confirm that I'm able to start the laptop without errors when I only enable the Intel GPU or NVidia GPU separately, and only see this error when both GPUs are enabled simultaneously. Extra Info: 1: Description: Ubuntu 14.10 Release: 14.10 2: N/A 3: The text 'nouveau' should have appeared in the output of the command. 4: The text 'Intel' appeared in the output of the command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388647/+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 1388359] Re: User metrics can no longer be changed by double tap
** Branch linked: lp:~dandrader/unity8/doubleTapUserMetrics-lp1388359 -- 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/1388359 Title: User metrics can no longer be changed by double tap Status in “unity8” package in Ubuntu: In Progress Bug description: Krillin #139 proposed On the welcome screen I only see No text messages sent today. In previous images double tapping the welcome screen would cycle through music played, phone calls made/received etc. I don't seem to be able to get it to move on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1388359/+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 1388876] [NEW] Pinch to zoom not supported when taking video
Public bug reported: Steps to reproduce: 1. Open the camera application 2. Press the Video button to switch to video mode 3. Place two fingers on the screen and move them apart to attempt to zoom Expected result: The picture zooms in and a slider appears indicating the zoom level Actual result: The slider appears but the picture does not zoom in and there is no marker on the slider to indicate the zoom level ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1388876 Title: Pinch to zoom not supported when taking video Status in “camera-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the camera application 2. Press the Video button to switch to video mode 3. Place two fingers on the screen and move them apart to attempt to zoom Expected result: The picture zooms in and a slider appears indicating the zoom level Actual result: The slider appears but the picture does not zoom in and there is no marker on the slider to indicate the zoom level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1388876/+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 1388875] [NEW] [gtk-mir-backend] Clicking seems to confuse GTK (or the shell)
Public bug reported: Using utopic or current vivid, clicking on buttons/menubar in gtk application under unity8-mir leads to not working softwares. Not sure if that's the GTK backend or Mir to blame Small example attached, the program has a button and a label, click on the button should display clicked!. Under unity8 the button seems to stop reacting after the first click and sometime the program closes (compile with gcc button.c -o button`pkgconfig --cflags --libs gtk+-3.0`, to run it you need to have a .desktop running the binary and including the X-Ubuntu-Touch=true key) ** Affects: gtk+3.0 (Ubuntu) Importance: High Status: New ** Tags: gtk-mir ** Attachment added: small program example https://bugs.launchpad.net/bugs/1388875/+attachment/4252073/+files/button.c ** Tags added: gtk-mir -- 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/1388875 Title: [gtk-mir-backend] Clicking seems to confuse GTK (or the shell) Status in “gtk+3.0” package in Ubuntu: New Bug description: Using utopic or current vivid, clicking on buttons/menubar in gtk application under unity8-mir leads to not working softwares. Not sure if that's the GTK backend or Mir to blame Small example attached, the program has a button and a label, click on the button should display clicked!. Under unity8 the button seems to stop reacting after the first click and sometime the program closes (compile with gcc button.c -o button`pkgconfig --cflags --libs gtk+-3.0`, to run it you need to have a .desktop running the binary and including the X-Ubuntu-Touch=true key) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1388875/+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: com.ubuntu.connectivity1.NetworkingStatus.Status is always online
Confirming, network-manager 0.9.8.0-0ubuntu30 fixes the issue; I'm marking it as tested on image 140. ** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium ** Changed in: network-manager (Ubuntu) Status: Confirmed = In Progress ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- 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: 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 1164083] Re: libreoffice spams stdout with Fontconfig warning: ignoring C.UTF-8: not a valid language tag
I confirm this on a up-to-date ubuntu 14.04 amd64 server installation. My X server is running on a different machine. Running gnome-terminal gives: Fontconfig warning: ignoring C.UTF-8: not a valid language tag Maybe I could change locale settings to workaround this, but it is bug and there seems to be a fix available. $ locale LANG=C.UTF-8 LANGUAGE= LC_CTYPE=C.UTF-8 LC_NUMERIC=pt_PT.UTF-8 LC_TIME=pt_PT.UTF-8 LC_COLLATE=C.UTF-8 LC_MONETARY=pt_PT.UTF-8 LC_MESSAGES=C.UTF-8 LC_PAPER=pt_PT.UTF-8 LC_NAME=pt_PT.UTF-8 LC_ADDRESS=pt_PT.UTF-8 LC_TELEPHONE=pt_PT.UTF-8 LC_MEASUREMENT=pt_PT.UTF-8 LC_IDENTIFICATION=pt_PT.UTF-8 LC_ALL= ** Changed in: fontconfig (Ubuntu) Status: New = Confirmed -- 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/1164083 Title: libreoffice spams stdout with Fontconfig warning: ignoring C.UTF-8: not a valid language tag Status in “fontconfig” package in Ubuntu: Confirmed Bug description: when libreoffice is started from the shell command line, it spams the terminal window with a stream of messages Fontconfig warning: ignoring C.UTF-8: not a valid language tag This message should be reported at most once per libreoffice invocation. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fontconfig 2.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Wed Apr 3 14:22:46 2013 InstallationDate: Installed on 2011-11-01 (519 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: fontconfig UpgradeStatus: Upgraded to quantal on 2013-03-21 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1164083/+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 1346734] Re: Unprivileged LXC containers don't work under systemd
Asked upstream about this: http://lists.freedesktop.org/archives /systemd-devel/2014-November/024856.html ** Changed in: systemd (Ubuntu) Importance: Undecided = Medium -- 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/1346734 Title: Unprivileged LXC containers don't work under systemd Status in “systemd” package in Ubuntu: Triaged Bug description: With systemd 208, unprivileged containers stop working when running under systemd (working fine under upstart with cgmanager). Quoting Stephane Graber: In this setup, things don't work nearly as well. On login I'm only placed into the name=systemd cgroup and not in any of the others, which means that unprivileged LXC isn't usable. Martin suggested setting JoinControllers in /etc/systemd/system.conf but upon closer inspection, this isn't at all what we want. This setting is used to tell systemd what controllers to co-mount, by default this is set to cpu,cpuset (which caused the earlier cgmanager breakage). Even though this option isn't helpful for what we want (i.e. setting the list of cgroup controllers the first PID of a user session should be added to), we should nonetheless set it to an empty string which should instruct systemd not to co-mount any controller, therefore giving us a more reliable behavior (identical to what we have in the upstart world and unlikely to confuse lxc and other stuff doing direct cgroup access). Additionally, we need to find an equivalent to our good old Controllers logind.conf option, or re-introduce it or just patch logind so that it will always join all the controllers (similar to what the shim does). == Actions == * Update systemd.conf to set JoinControllers to an empty value. * Make it so new user sessions are joined to all the available controllers by doing one of the following: - Find the magic undocumented config variable - Re-introduce the Controllers option in logind.conf - Patch logind to have it always join all available controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1346734/+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 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
This bug was fixed in the package indicator-network - 0.5.1+15.04.20141103-0ubuntu1 --- indicator-network (0.5.1+15.04.20141103-0ubuntu1) vivid; urgency=low [ CI bot ] * Resync trunk [ Jussi Pakkanen ] * Use std::quick_exit. (LP: #1381041) [ Marcus Tomlinson ] * Fix GMainLoopDispatch dispatching ordering when. called inside GMainLoop already Fix GMainLoopDispatch locking. Force all signals from external (dbus-cpp) threads through. GMainLoopDispatch (LP: #1374419) [ Antti Kaijanmäki ] * Increase the default timeouts to match industry standards. (LP: #1381041) * Fix GMainLoopDispatch dispatching ordering when. called inside GMainLoop already Fix GMainLoopDispatch locking. Force all signals from external (dbus-cpp) threads through. GMainLoopDispatch (LP: #1374419) indicator-network (0.5.1+14.10.20141015-0ubuntu1) 14.09; urgency=low [ Antti Kaijanmäki ] * deadlock if calling unlock() inside ready signal for a modem that does not require unlocking. (LP: #1333121) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 03 Nov 2014 11:48:11 + ** Changed in: indicator-network (Ubuntu Vivid) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-network” source package in Utopic: New Status in “indicator-network” source package in Vivid: Fix Released Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: This and other corruptions in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, Instant Staff should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+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 1379657] Re: Run click hook run-user in the ubuntu-core image
This bug was fixed in the package click - 0.4.34.2 --- click (0.4.34.2) vivid; urgency=medium [ Michael Vogt ] * Demote ubuntu-app-launch-tools from a click recommends to a suggests, since they are not needed on server installs. * Use dh-systemd to enable click system and user hook integration (LP: #1379657). * add ubuntu-sdk-15.04 based on ubuntu-sdk-libs/ubuntu-sdk-libs-dev * click/tests/preload.h: - replace deprecated Attributes: with annotations on the identifier * click/tests/Makefile.am: - add --libtool to g-ir-scanner so that it uses the generated libtool instead of the system libtool which is now part of the libtool-bin package in vivid [ Colin Watson ] * Make click info always try opening the input file as a package and only try to interpret it as a file in an installed package if that fails, rather than guessing by the input file extension. * Allow click chroot install and click chroot upgrade to operate on sessions. [ David Planella ] * Adds internationalization tools and CMake macros required by the new Qt Creator app and scope templates that provide internationalization code. [ Pete Woods ] * Include Canonical's cmake-extras project in the schroot. -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 03 Nov 2014 12:49:25 + ** Changed in: click (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1379657 Title: Run click hook run-user in the ubuntu-core image Status in “click” package in Ubuntu: Fix Released Bug description: The ubuntu-touch image uses the click-user-hoks.conf upstart session hook to run click hook run-user so that the hooks for the user are updated. The core images have /usr/lib/systemd/user/click-user-hooks.service that does the same but apparently its not always working (according to kickinz1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1379657/+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
