[Touch-packages] [Bug 1303990] Re: Can't get udev debug logs
The debug output does appear in /var/log/syslog after sudo udevadm control --log-priority=debug at least in Ubuntu 14.04 LTS and 14.10, so this apparently got fixed. ** Changed in: systemd (Ubuntu) Status: New = Fix Released -- 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/1303990 Title: Can't get udev debug logs Status in “systemd” package in Ubuntu: Fix Released Bug description: I have tried running udevadm control --log-priority=debug and also tried modifying /etc/udev/udev.conf with log_level=debug but in both cases I do not see any udev entries in syslog. There is a /var/log/udev file that seems to be written at boot and not updated. How do I get debug output from udev? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: udev 204-0ubuntu19.2 ProcVersionSignature: Ubuntu 3.11.0-19.13-lowlatency 3.11.10.5 Uname: Linux 3.11.0-19-lowlatency x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CustomUdevRuleFiles: 90-omap-fastboot.rules Date: Mon Apr 7 12:40:24 2014 InstallationDate: Installed on 2013-06-21 (289 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. OptiPlex 9010 MarkForUpload: True ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-lowlatency root=UUID=cfe5038b-b116-455d-8e64-83e4551fbcde ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-12-24 (104 days ago) dmi.bios.date: 03/27/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 00F82W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/27/2013:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn00F82W:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.udev.udev.conf: # see udev(7) for details udev_log=debug mtime.conffile..etc.udev.udev.conf: 2014-04-04T17:32:04.851252 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1303990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 99461] Re: Window manager warning generated starting evince
** Changed in: gtk Status: Confirmed = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/99461 Title: Window manager warning generated starting evince Status in Evince document viewer: Invalid Status in GTK+ GUI Toolkit: Expired Status in “gtk+2.0” package in Ubuntu: Triaged Bug description: Binary package hint: evince Description of the problem: Starting evince makes metacity print a warning in ~/.xession-errors . Steps to reproduce: 1. Start a gnome-terminal . 2. In the gnome-terminal type tail -n 0 -f ~/.xsession-errors . 3. Start evince . Expected results: Nothing to be printed on the terminal. Actual results: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x343 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. How reproducible is the problem? The problem is reproducible every time. Version information: Ubuntu Feisty evince 0.8.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/99461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352165] [NEW] [NFORCE6M-A, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all
Public bug reported: Speakers are not recognized, I have reinstalled Pulse and Asla to no avail, worked fine 2 days ago suddenly no sound, installed new sound card, it is seen but the speakers are not and no sound from either on board audio or sound card - all hardware is OK ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ann1689 F pulseaudio /dev/snd/controlC0: ann1689 F pulseaudio /dev/snd/controlC1: ann1689 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 3 23:01:45 2014 InstallationDate: Installed on 2014-07-13 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Built-in Audio - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ann1689 F pulseaudio /dev/snd/controlC0: ann1689 F pulseaudio /dev/snd/controlC1: ann1689 F pulseaudio Symptom_Jack: Green Speaker, Rear Symptom_Type: No sound at all Title: [NFORCE6M-A, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: NFORCE6M-A dmi.board.vendor: ELITEGROUP COMPUTER SYSTEM CO.,LTD. dmi.board.version: 1.0 dmi.chassis.asset.tag: Unknow dmi.chassis.type: 3 dmi.chassis.vendor: nVIDIA dmi.chassis.version: NFORCE6M-A dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/11/2007:svnELITEGROUPCOMPUTERSYSTEMCO.,LTD.:pnNFORCE6M-A:pvr1.0:rvnELITEGROUPCOMPUTERSYSTEMCO.,LTD.:rnNFORCE6M-A:rvr1.0:cvnnVIDIA:ct3:cvrNFORCE6M-A: dmi.product.name: NFORCE6M-A dmi.product.version: 1.0 dmi.sys.vendor: ELITEGROUP COMPUTER SYSTEM CO.,LTD. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1352165 Title: [NFORCE6M-A, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: Speakers are not recognized, I have reinstalled Pulse and Asla to no avail, worked fine 2 days ago suddenly no sound, installed new sound card, it is seen but the speakers are not and no sound from either on board audio or sound card - all hardware is OK ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ann1689 F pulseaudio /dev/snd/controlC0: ann1689 F pulseaudio /dev/snd/controlC1: ann1689 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 3 23:01:45 2014 InstallationDate: Installed on 2014-07-13 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Built-in Audio - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ann1689 F pulseaudio /dev/snd/controlC0: ann1689 F pulseaudio /dev/snd/controlC1: ann1689 F pulseaudio Symptom_Jack: Green Speaker, Rear Symptom_Type: No sound at all Title: [NFORCE6M-A, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: NFORCE6M-A dmi.board.vendor: ELITEGROUP COMPUTER SYSTEM CO.,LTD. dmi.board.version: 1.0 dmi.chassis.asset.tag: Unknow dmi.chassis.type: 3 dmi.chassis.vendor: nVIDIA dmi.chassis.version: NFORCE6M-A dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/11/2007:svnELITEGROUPCOMPUTERSYSTEMCO.,LTD.:pnNFORCE6M-A:pvr1.0:rvnELITEGROUPCOMPUTERSYSTEMCO.,LTD.:rnNFORCE6M-A:rvr1.0:cvnnVIDIA:ct3:cvrNFORCE6M-A: dmi.product.name: NFORCE6M-A dmi.product.version: 1.0
[Touch-packages] [Bug 1349297] Re: Better fix for crash due to wrong objects being garbage collected
Simply removing parenttosubcreator_qqmlobjectcreator.patch and adding the new upstream patch instead does not seem to work: https://launchpadlibrarian.net/181479134/buildlog_ubuntu-utopic-amd64.qtdeclarative-opensource-src_5.3.0-3ubuntu8~utopic1~test1_FAILEDTOBUILD.txt.gz error: 'topLevelCreator' was not declared in this scope Would 5.3.0 need some additional patching? ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1349297 Title: Better fix for crash due to wrong objects being garbage collected Status in “qtdeclarative-opensource-src” package in Ubuntu: Incomplete Bug description: We need to stop using debian/patches/parenttosubcreator_qqmlobjectcreator.patch that has been rejected as a valid upstream patch and use https://codereview.qt- project.org/#/c/88064/ which also fixes the issue and is upstream (will be in the 5.3.2 release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1349297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351410] [NEW] screen does not rotate when entering wi-fi password
You have been subscribed to a public bug: For those with long WPA passwords, it would be *extremely* useful to allow the screen to rotate when entering the password to connect to an AP. FTR, Android allows this. ** Affects: unity8 (Ubuntu) Importance: Low Status: New -- screen does not rotate when entering wi-fi password https://bugs.launchpad.net/bugs/1351410 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 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 931389] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_segments()
I think that this should be a duped or linked to bug 1199571 against cairo as I think thats where this needs to be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/931389 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_segments() Status in “freetype” package in Ubuntu: Confirmed Bug description: Just opened Software Center while Compiz crashed unexpectetly and Software Center closed immediately. I'm using Precise alpha 2 with unity 5.2.0. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 Uname: Linux 3.2.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 13 13:18:51 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f1ac798b9e1:mov%rax,(%rdx) PC (0x7f1ac798b9e1) ok source %rax ok destination (%rdx) (0x7f1a7ead6010) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: Upgraded to precise on 2012-02-13 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/931389/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352012] Re: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
This error message indicates that you have a non-default filesystem on /mnt that's in a problematic state. The base-files package provides the /mnt directory on the filesystem, so dpkg assumes it should be able to unpack that directory if necessary. I think you will need to unmount /mnt on your system to upgrade base-files. Marking this bug as invalid, because I don't believe there's anything we can do in base-files to mitigate this. ** Changed in: base-files (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1352012 Title: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected Status in “base-files” package in Ubuntu: Invalid Bug description: Not sure what else happened. I just got a dialog box about this failing. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: base-files 7.2ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 Date: Sun Aug 3 16:22:49 2014 Dependencies: DpkgTerminalLog: Preparing to unpack .../base-files_7.2ubuntu5.1_i386.deb ... Unpacking base-files (7.2ubuntu5.1) over (7.2ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/base-files_7.2ubuntu5.1_i386.deb (--unpack): unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected DuplicateSignature: package:base-files:7.2ubuntu5:unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected ErrorMessage: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected InstallationDate: Installed on 2013-05-16 (444 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) SourcePackage: base-files Title: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected UpgradeStatus: Upgraded to trusty on 2014-05-03 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1352012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350425] Re: Ubuntu 14.04 ACR38 card reader. Says card is not found in java applet
** Summary changed: - Ubuntu 14.04 ACR38 card reader driver problem + Ubuntu 14.04 ACR38 card reader. Says card is not found in java applet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1350425 Title: Ubuntu 14.04 ACR38 card reader. Says card is not found in java applet Status in “pcsc-lite” package in Ubuntu: New Bug description: ACR38 card reader is not working. Assume that I have wrong driver installed. tm@Compaq-HP-6510b:~$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 tm@Compaq-HP-6510b:~$ java -version java version 1.8.0_11 Java(TM) SE Runtime Environment (build 1.8.0_11-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1350425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351410] Re: screen does not rotate when entering wi-fi password
Hi Seb - yes, that's exactly what I was meaning. ** Package changed: ubuntu-system-settings (Ubuntu) = unity8 (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/1351410 Title: screen does not rotate when entering wi-fi password Status in “unity8” package in Ubuntu: New Bug description: For those with long WPA passwords, it would be *extremely* useful to allow the screen to rotate when entering the password to connect to an AP. FTR, Android allows this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1351410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1258089] Re: Build python3 package
http://anonscm.debian.org/gitweb/?p=pkg- systemd/systemd.git;a=commitdiff;h=44bbbcf93da59db1e60d3049348e605122fffb7a ** Changed in: systemd (Ubuntu) Status: Triaged = Fix Committed -- 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/1258089 Title: Build python3 package Status in “systemd” package in Ubuntu: Fix Committed Status in “systemd” package in Fedora: Unknown Bug description: Drop python-systemd, we don't really need it. Build python3-systemd instead. For this, b-dep on python3:any. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323710] Re: After wake from suspend network-manager can't find wifi network
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
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/1323710
Title:
After wake from suspend network-manager can't find wifi network
Status in “network-manager” package in Ubuntu:
Confirmed
Bug description:
I'm not sure if this is a network-manager problem or a pm problem.
Since updating to trusty my laptop - Lenovo T510 - wakes from suspend
without wifi. Initially there the nm gui control showed no networks
and disonnected state. Ifconfig showed only the loopback. Wetting
wlan0 to up brought it back but nm wouldn't connect.
I created an unload_module entry and added:
SUSPEND_MODULES=$SUSPEND_MODULES iwlwifi
to:
/etc/pm/config.d/unload_modules
After that the nm gui showed networks and tried to connect to the correct one
but was unsuccessful.
I created /etc/pm/sleep.d/network-manager-resume
#!/bin/sh
case ${1} in
resume|thaw)
nmcli nm sleep false
;;
esac
but this hasn't helped.
I tried connecting directly using nmcli dev and got the error message:
Error: Connection activation failed: (53) The Wi-Fi network could not
be found.
Rebooting after waking restores networking.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue May 27 07:51:10 2014
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-11-19 (188 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.101
metric 9
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to trusty on 2014-05-01 (25 days ago)
nmcli-con:
NAME UUID TYPE
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
martin-5.0b4ef8c22-9ae1-4058-8bfc-c6442634467c
802-11-wireless 1401202160 Tue 27 May 2014 07:49:20 AM PDTyes
no /org/freedesktop/NetworkManager/Settings/2
Cisco03329a94faf57-01c2-44ef-a474-1acb3523c839
802-11-wireless 1385160323 Fri 22 Nov 2013 02:45:23 PM PSTyes
no /org/freedesktop/NetworkManager/Settings/1
martin-5.0 1 d662b0e5-a70d-4010-b3f8-846b6166a22a
802-11-wireless 0never yes
no /org/freedesktop/NetworkManager/Settings/0
Wired connection 105195919-bf9a-49c1-9991-64ce5d41c081
802-3-ethernet1401198260 Tue 27 May 2014 06:44:20 AM PDTyes
no /org/freedesktop/NetworkManager/Settings/3
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected
/org/freedesktop/NetworkManager/Devices/1
eth0 802-3-ethernetunavailable
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.8.8connected enabled enabled
enabledenabled disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1323710/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333261] Re: Left-edge long-swipe dash fade-in is not smooth
** Changed in: unity8 Status: Triaged = Won't Fix ** Changed in: unity8 (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1333261 Title: Left-edge long-swipe dash fade-in is not smooth Status in The Unity 8 shell: Won't Fix Status in “unity8” package in Ubuntu: Invalid Bug description: * launch an app * long-swipe from the left → see that the dash doesn't fade-in smoothly but jumps ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.89+14.10.20140619.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 23 15:36:06 2014 SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1333261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347053] Re: Clients are crashing with a fatal exception in MirSocketRpcChannel::send_message()
** Changed in: mir/0.6 Milestone: None = 0.6.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1347053 Title: Clients are crashing with a fatal exception in MirSocketRpcChannel::send_message() Status in Mir: In Progress Status in Mir 0.5 series: Won't Fix Status in Mir 0.6 series: Triaged Status in “mir” package in Ubuntu: Triaged Status in “unity-system-compositor” package in Ubuntu: Invalid Bug description: Starting unity8 when u-s-c is running results in them fighting over the hardware (not for the socket due to the default XDG_RUNTIME_DIR) and u-s-c crashing. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-system-compositor 0.0.4+14.10.20140718-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu2 Architecture: armhf Date: Tue Jul 22 16:26:40 2014 ExecutablePath: /usr/bin/unity-system-compositor-spinner GraphicsCard: InstallationDate: Installed on 2014-07-22 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140722-095505) LocalLibraries: /android/system/lib/liblog.so /android/system/lib/libhardware.so /android/system/lib/libstdc++.so /android/system/lib/libcutils.so /android/system/lib/libcorkscrew.so /android/system/lib/libsync.so /android/system/lib/libc.so /android/system/lib/hw/gralloc.msm8960.so /android/system/lib/libm.so /android/system/lib/libGLESv1_CM.so /android/system/lib/libmemalloc.so /android/system/lib/egl/libGLESv1_CM_adreno.so /android/system/lib/libz.so /android/system/lib/libgccdemangle.so /android/system/lib/libui.so /android/system/lib/libadreno_utils.so /android/system/lib/egl/libEGL_adreno.so /android/system/lib/libstlport.so /android/system/lib/egl/eglsubAndroid.so /android/system/lib/libutils.so /android/system/lib/libgsl.so /android/system/lib/libdsyscalls.so /android/system/lib/egl/libGLESv2_adreno.so /android/system/lib/libsc-a3xx.so /android/system/lib/libGLESv2.so /android/system/lib/libGLES_trace.so /android/system/lib/libEGL.so /android/system/lib/libqdutils.so ProcCmdline: /usr/bin/unity-system-compositor-spinner ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 Title: unity-system-compositor-spinner crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.54-1 version.lightdm: lightdm 1.11.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1347053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340510] Re: session screen seen upon quick power key strike
** Also affects: mir/0.6 Importance: Undecided Status: New ** Changed in: mir/0.6 Milestone: None = 0.6.1 ** Changed in: mir/0.6 Status: New = Triaged ** Changed in: mir/0.6 Importance: Undecided = Medium -- 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/1340510 Title: session screen seen upon quick power key strike Status in Mir: In Progress Status in Mir 0.4 series: Won't Fix Status in Mir 0.5 series: Won't Fix Status in Mir 0.6 series: Triaged Status in Unity System Compositor: New Status in The Unity 8 shell: New Status in “mir” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: Image #125 on N4 1) boot phone and unlock phone to display dash 2) strike power key to blank unblank screen quickly 3) the dash is seen instead of lockscreen for a brief moment logging against u-s-c as this was fixed, but power policy changes may have effected this To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1340510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1287736] Re: System Settings - Accounts and back shows black screen and 5s delay
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1287736 Title: System Settings - Accounts and back shows black screen and 5s delay Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Confirmed Status in “unity-mir” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: mako image #219 Open System Settings Tap Accounts Note a black flash between System Settings and Accounts Press 'Back' to go back from Accounts to System Settings Note a black flash - and sometimes a 5 second delay before getting back to System settings. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-system-settings 0.1+14.04.20140228-0ubuntu1 Uname: Linux 3.4.0-4-mako armv7l ApportVersion: 2.13.2-0ubuntu5 Architecture: armhf Date: Tue Mar 4 14:52:38 2014 InstallationDate: Installed on 2014-03-04 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140304) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1287736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1230091] Re: [enhancement] Trusted Session surface management (required for appstore app trust model), modal subwindows
** Changed in: mir Milestone: None = 0.7.0 -- 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/1230091 Title: [enhancement] Trusted Session surface management (required for appstore app trust model), modal subwindows Status in Content sharing/picking infrastructure and service: Triaged Status in Mir: Triaged Status in Unity Mir: Triaged Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Confirmed Status in “signon” package in Ubuntu: Confirmed Status in “unity-mir” package in Ubuntu: Confirmed Bug description: (I'm filing this as a bug in order to be able to point other people to it, and to track its progress; if there's a blueprint containing this task, please let me know) Some components (such as the Online Accounts trusted helper) need to be able to pop-up a window (typically, a dialog) on top of the running application. Such windows should be modal to the application, that is the user should not be able to interact with the application while the modal window is displayed on top of them. This also means that in the task switcher one shouldn't see two windows, but only the topmost modal window (and parts of the application window, in case the modal window on top is a non-fullscreen dialog). For developers, this API already exists in Qt: see https://qt-project.org/doc/qt-5.1/qtgui/qwindow.html#fromWinId It needs to be implemented in the QPA plugin, so feel free to add the relevant projects to the bug report. From jdstrand This is a hard requirement for application confinement because of our trust model-- permission to access sensitive data by AppStore apps is typically granted or denied at the time of access (caching the result for later use as appropriate), so users have a context for the access being requested. We do this instead of throwing up a permissions prompt at installation. However, for it to work, trusted helpers like online accounts and location require this functionality from unity-mir. A trust-store is also being implemented so other services like calendar and contacts can do the same. Because this feature is not implemented, the implementation for online accounts, location and the trust-store is blocked and appstore apps are therefore able to access these services without the user knowing. To manage notifications about this bug go to: https://bugs.launchpad.net/content-hub/+bug/1230091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348890] Re: [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN
There are no events at all in your log. So either Asus WMI hotkeys isn't the right device for the brightness keys, can you try AT Translated Set 2 keyboard? Or (more likely in this case), the kernel driver needs to be fixed to actually generate key events for the brightness keys; that's the case if you don't get any events on any of the input devices. Thanks! -- 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/1348890 Title: [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN Status in “systemd” package in Ubuntu: Incomplete Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1348890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343962] Re: Sound slider moves itself randomly when scrolling or moving sound pointer
Same here. This bug appeared after installing the Ubuntu SDK.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1343962
Title:
Sound slider moves itself randomly when scrolling or moving sound
pointer
Status in “indicator-sound” package in Ubuntu:
Confirmed
Bug description:
I've described this bug in details at askubuntu.com ::
http://askubuntu.com/questions/499268/strange-bug-with-sound-slider
In brief:
1) Problem caused by installation of Ubuntu-SDK
2) Removing Ubuntu-SDK didn't fix the problem
3) This problem occurs only with desktop sound slider (notification slider).
In Ubuntu sound settings, everything is fine.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute':
(true, '', [false]), 'phone-settings': (true, '', []), 'mic-volume': (true,
'', [0.1183929443359375]), 'scroll': (true, 'i', []),
'play-playlist.spotify.desktop': (true, 's', []), 'vlc.desktop': (true, '',
[{'running': false, 'state': 'Paused'}]), 'desktop-settings': (true, '',
[]), 'previous.vlc.desktop': (true, '', []), 'play-playlist.vlc.desktop':
(true, 's', []), 'spotify.desktop': (true, '', [{'running': false, 'state':
'Paused'}]), 'volume': (true, 'i', [0.51992553710937495]),
'play.spotify.desktop': (true, '', ['Paused']), 'previous.spotify.desktop':
(true, '', []), 'root': (true, '', [{'title': 'Dźwięk', 'accessible-desc':
'Głośność (51%)', 'icon': ('themed', ['audio-volume-medium-panel',
'audio-volume-medium', 'audio-volume', 'audio']), 'visible': true}]),
'next.spotify.desktop': (true, '', []), 'play.vlc.desktop': (true, '',
['Paused'])},)
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jul 18 12:28:16 2014
ExecutablePath:
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
InstallationDate: Installed on 2014-04-17 (91 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
ProcEnviron:
PATH=(custom, no user)
LANGUAGE=pl
XDG_RUNTIME_DIR=set
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1343962/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348300] Re: qmlplugindump crashed with SIGSEGV
Changing package to oxide-qt where the crash happens. ** Package changed: qtdeclarative-opensource-src (Ubuntu) = oxide-qt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1348300 Title: qmlplugindump crashed with SIGSEGV Status in “oxide-qt” package in Ubuntu: New Bug description: Launching Ubuntu SDK starts qmlplugindump but it crashes. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: qtdeclarative5-dev-tools 5.2.1-3ubuntu15.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Jul 24 19:47:53 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump InstallationDate: Installed on 2013-11-13 (253 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump -relocatable com.canonical.Oxide 1.0 /usr/lib/x86_64-linux-gnu/qt5/qml SegvAnalysis: Segfault happened at: 0x7f39e46760ba:mov(%rax),%rax PC (0x7f39e46760ba) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: qtdeclarative-opensource-src StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 Title: qmlplugindump crashed with SIGSEGV UpgradeStatus: Upgraded to trusty on 2014-04-08 (107 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1348300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351410] Re: screen does not rotate when entering wi-fi password
*** This bug is a duplicate of bug 1210199 *** https://bugs.launchpad.net/bugs/1210199 ** This bug has been marked a duplicate of bug 1210199 [Shell] support rotation -- 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/1351410 Title: screen does not rotate when entering wi-fi password Status in “unity8” package in Ubuntu: New Bug description: For those with long WPA passwords, it would be *extremely* useful to allow the screen to rotate when entering the password to connect to an AP. FTR, Android allows this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1351410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350425] Re: Ubuntu 14.04 ACR38 card reader. Says card is not found in java applet
You changed the bug title. Maybe the problem is with your application and not with the driver. Follow http://ludovicrousseau.blogspot.fr/2014/03/level-1-smart-card- support-on-gnulinux.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1350425 Title: Ubuntu 14.04 ACR38 card reader. Says card is not found in java applet Status in “pcsc-lite” package in Ubuntu: New Bug description: ACR38 card reader is not working. Assume that I have wrong driver installed. tm@Compaq-HP-6510b:~$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 tm@Compaq-HP-6510b:~$ java -version java version 1.8.0_11 Java(TM) SE Runtime Environment (build 1.8.0_11-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1350425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319778] Re: cannot resume from suspend Ubuntu 14.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pm-utils (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1319778 Title: cannot resume from suspend Ubuntu 14.04 Status in “pm-utils” package in Ubuntu: Confirmed Bug description: This is on a clean install of Ubuntu 14.04. The other bug report on this issue which comes close is an old one (Ubuntu 7.04 in filed in 2009). Hence a new bug No matter which method I use to suspend - shutting the lid or using the options in the session indicator, ubuntu 14.04 does not resume after suspend. This is also true no matter which desktop environment I am in - I have three: Unity, gnome-desktop and cairo-dock. Steps to reproduce: 1. Shut lid: suspend is initiated 2. press power button on notebook to resume, the bluetooth, wireless lights etc. are shining suggesting that the notebook is trying to resume 3. But no, it does not resume. 4. Power off completely and power on again Pinging to the notebook from another device when in the above state results in an unreachable error. Substitute Step 1 for suspending from main shutdown/session menu: result is the same It has been the same on my notebook since 11.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Thu May 15 16:29:34 2014 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1319778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349297] Re: Better fix for crash due to wrong objects being garbage collected
The same error happens also with 5.3.1 + the patch. Adding https://codereview.qt-project.org/#/c/88011/ to the mix seems to resolve the issue. Could it be confirmed that the set of those two patches would be wanted to go in? Is there regression potential when those patches alone are added on top of 5.3.0? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1349297 Title: Better fix for crash due to wrong objects being garbage collected Status in “qtdeclarative-opensource-src” package in Ubuntu: Incomplete Bug description: We need to stop using debian/patches/parenttosubcreator_qqmlobjectcreator.patch that has been rejected as a valid upstream patch and use https://codereview.qt- project.org/#/c/88064/ which also fixes the issue and is upstream (will be in the 5.3.2 release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1349297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339828] Re: Navigate using the scope headers does not work sometimes
*** This bug is a duplicate of bug 1349705 *** https://bugs.launchpad.net/bugs/1349705 ** This bug has been marked a duplicate of bug 1349705 [PATCH] Flickable gets confused when there's other flickables on top -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1339828 Title: Navigate using the scope headers does not work sometimes Status in The Unity 8 shell: Won't Fix Status in “qtdeclarative-opensource-src” package in Ubuntu: In Progress Bug description: Using the scopes header (titles) sometimes get broken and does no change the scopes. How to reproduce: = 1 - Go to apps scope 2 - Scroll until the bottom 3 - Scroll back to the top 4 - Click o the title to show all scopes names 5 - Click on Video title Expected result The video scope appears Current result === The Videos title move to left as normal but the apps scope still visible. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1339828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1293144] Re: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder
** Changed in: evolution (Ubuntu Trusty) Status: New = In Progress ** Changed in: evolution (Ubuntu Trusty) Assignee: (unassigned) = Iain Lane (laney) ** Also affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Changed in: evolution-data-server (Ubuntu) Status: New = Fix Released ** Changed in: evolution-data-server (Ubuntu Trusty) Status: New = In Progress ** Changed in: evolution-data-server (Ubuntu Trusty) Assignee: (unassigned) = Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1293144 Title: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder Status in The Evolution Mail Calendaring Tool: Fix Released Status in “evolution” package in Ubuntu: Fix Released Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution” source package in Trusty: In Progress Status in “evolution-data-server” source package in Trusty: In Progress Bug description: When I creates a new folder in Gmail the app closes. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: evolution 3.10.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Mar 16 12:21:08 2014 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2014-03-13 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313) ProcCmdline: evolution SegvAnalysis: Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi PC (0x7f88ad21b520) ok source 0x18(%r14) (0x0468) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1293144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1208019] Re: Eclipse menus don't show up in Trusty
This fix isn't working because it requires both the gtk patch and the unity-gtk-module patch simultaneously. -- 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/1208019 Title: Eclipse menus don't show up in Trusty Status in Eclipse: Unknown Status in GTK+ GUI Toolkit: Fix Released Status in Unity GTK+ module: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “unity-gtk-module” package in Ubuntu: Fix Released Status in “gtk+3.0” source package in Trusty: Fix Committed Status in “unity-gtk-module” source package in Trusty: In Progress Bug description: [Impact] Switching tabs between open source files with different file types in Eclipse causes the Source and Refactor menus to be empty in the global menu bar under Unity. This is a severe usability problem for many Eclipse users. The fix proposed has been available in a PPA and is well-tested. [Test Case] 1. Open a new project in Eclipse. 2. Open two files: one with a .java extension, another with a .txt extension. 3. Switch between the .java file and the .txt file and back again. 4. Open the Source or Refactor menu in the Unity global menu bar. Expected result: menus with menu items Actual result: empty menus for both [Regression Potential] The fix involves changes to both gtk and unity-gtk-module. The changes to gtk are minimal and only involve the reversal of a pair of signal emissions, in a part of the code (GtkMenuTracker) which is normally used by desktop environments, not typical user applications. Therefore regression potential for the gtk update is unlikely. The changes to unity-gtk-module involve emitting show and hide signals where they were none before has some regression potential for applications that are explicitly watching for when their menus are opening and closing. But this is rare for applications to do, and we likely would have already received bug reports for those that do. Being completely sure would require extensive testing across all gtk apps though. Both changes together have been available as a PPA, thoroughly tested for quite some time now. [Other Info] The changes to unity-gtk-module depend on the changes to gtk, so both must be tested in simultaneity. Suggested to upload both to trusty- proposed at the same time. Original bug report follows: === % === HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+subscriptions -- Mailing list: https://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 1348890] Re: [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN
I've tried all of them. Nothing. On Mon, Aug 4, 2014 at 11:24 AM, Martin Pitt martin.p...@ubuntu.com wrote: There are no events at all in your log. So either Asus WMI hotkeys isn't the right device for the brightness keys, can you try AT Translated Set 2 keyboard? Or (more likely in this case), the kernel driver needs to be fixed to actually generate key events for the brightness keys; that's the case if you don't get any events on any of the input devices. Thanks! -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1348890 Title: [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN Status in “systemd” package in Ubuntu: Incomplete Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1348890/+subscriptions -- Бекетов Данила -- 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/1348890 Title: [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN Status in “systemd” package in Ubuntu: Incomplete Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1348890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 721982] Re: Corrupt display for history search in vi-mode, 256-color prompt
** Changed in: bash (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/721982 Title: Corrupt display for history search in vi-mode, 256-color prompt Status in “bash” package in Ubuntu: Fix Released Status in “readline6” package in Ubuntu: Fix Released Status in “bash” package in Debian: Fix Released Status in “readline6” package in Debian: Fix Released Bug description: Binary package hint: bash This is on Ubuntu 10.10. It very likely still remains in Natty. I use bash with a prompt that is derived from the current backgrounded jobs (the script I use to do this is at http://micah.cowan.name/hg/promptjobs/ - you just source the file and it does everything). I've customized the colors used, to take advantage of 256-color support in gnome-terminal. An instance of the prompt that might be produced is: PS1=\[\033[m\017\033[38;5;103m\]micah- acer\[\033[1m\033[38;5;19m\](\[\033[m\017\033[38;5;83m\]\061\[\033[m\017\033[38;5;189m\]wtitle\[\033[1m\033[38;5;19m\])\[\033[m\017\033[m\017\033[38;5;103m\]$ \[\033[m\017\] (This prompt will only display correctly in xterm-compatible terminals; the term I use is gnome-terminal.) With a prompt like this, and in vi-mode (set -o vi in bash), attempting to initiate a search in the history, results in display glitches (specifically, the history line bash/readline jumps to is displayed far over to the right, and with a couple garbage characters before it). Steps to reproduce: 1. Be in vi-mode (set -o vi in bash): in particular, readline's non-incremental-reverse-search-history MUST be bound to the / key, as this has significant effects on how bash/readline choose to prompt for a history search string (even though, for me at least, the bind command doesn't seem to reflect this). If you're running these steps, it would be advisible for you to be sufficiently familiar with vi-style bindings to know how to enter commands. 2. Set PS1 as described above. 3. Invoke the non-incremental-reverse-search-history function by pressing ESC (to escape vi's insert-mode) and / (to prompt for reverse history). 4. At this point, the / you just typed may not be showing up properly: this is the first symptom that something's wrong. 5. Type in some string that should be present in your recent bash history (so that bash will jump to a different line), and hit enter. Result: The history line bash jumps to will be drawn in the wrong location (far right of the prompt), and with garbage characters; typing k or j (or the cursor keys) to move up or down in history continues to draw these lines in the wrong location. Expected Result: The jumped-to line ought to be drawn immediately to the right of the prompt, and without garbage characters before it. Cause of bug: This bug is from readline (it is present both in the readline6 source package (and probably older, such as readline5), and bash's own built-in readline code (which has few differences from the sources in readline6). The bug lies in the function rl_message in display.c, which is called by _rl_nsearch_init, which is called from noninc_search. rl_message is primarily intended for writing a message on the current line, which doesn't normally include invisible characters (escape sequences, like the one I'm using in my prompt to set advanced colors), but in this case is being (ab)used to include the prompt. It uses a buffer of only 128 characters, which in the case of the above prompt/PS1, is overrun. As long as the system library provides vsnprintf, this does not lead to a potential buffer overflow, but the results are truncated, and this is the source of the graphical display glitch, because (a) the prompt is truncated in the middle of a sequence of invisible characters, and (b) I think the readline code may have other bugs that cause character-counting not to work properly if the prompt itself is not completely present at the beginning of a buffer whose value is derived from the result of rl_message. Solution: rl_message ought to use a dynamically-allocated buffer instead, so it can adjust the size as needed. I'll attach a patch to provide this shortly. Workaround: The statically-allocated buffer is only used to store the final line in a multi-line prompt (including any invisible characters, and the special codes used by readline to mark the start and end of invisible-character sequences). Thus, if you add a newline in the prompt just before the \$ , the static buffer should have plenty of room. Similar methods might include not using 256 color support, or any other means to shorten the total size of the prompt string below 127. I'll attach a patch that implements the described solution momentarily. To manage notifications about this bug go to:
[Touch-packages] [Bug 1158088] [NEW] [needs-packaging] Mir
You have been subscribed to a public bug: Mir is a new display technology being developed by Canonical. It is an alternative to X.org and Wayland, designed specifically for the Unity window system. URL: http://unity.ubuntu.com/mir/ License: LGPL Notes: This package can be used either as a system compositor with X.org running on top of it, or natively with UnityNext. ** Affects: mir (Ubuntu) Importance: Wishlist Assignee: Canonical Desktop Team (canonical-desktop-team) Status: Fix Released -- [needs-packaging] Mir https://bugs.launchpad.net/bugs/1158088 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir 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 1349297] Re: Better fix for crash due to wrong objects being garbage collected
Ah https://codereview.qt-project.org/#/c/88011/ is a wanted one too, i may have forgotten to open a bug for it. On the regression potential, well i've looked at the rest of changes in qdeclarative and there are many to be able to confirm if these two standalone would or would not cause a regression. There is of course regression potential as with any patch. Having asked upstream they say that debian/patches/parenttosubcreator_qqmlobjectcreator is not totally horrible and would mostly work even if make things a bit slower and having the ocassional memory leak. If we want to live with it until we upgrade to 5.3.2, we just have to remember to remove it by then, i guess i'm ok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1349297 Title: Better fix for crash due to wrong objects being garbage collected Status in “qtdeclarative-opensource-src” package in Ubuntu: Incomplete Bug description: We need to stop using debian/patches/parenttosubcreator_qqmlobjectcreator.patch that has been rejected as a valid upstream patch and use https://codereview.qt- project.org/#/c/88064/ which also fixes the issue and is upstream (will be in the 5.3.2 release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1349297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1293144] Re: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder
** Description changed: + [ Description ] + + (from upstream bug report, might not happen for everyone) + + - Open evolution + - Go to mail view + - Try to create a new folder + + Check evo crashes before not after. + + I've also cherry-picked some related patches to make the created folder + be displayed correctly. Check it doesn't have an expander. + + [ Development fix ] + + Same patches (disconnect the signals) + + [ Regression potential ] + + Check that folders are created and displayed properly, including cases + that previously worked. + + [ Original description ] + When I creates a new folder in Gmail the app closes. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: evolution 3.10.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Mar 16 12:21:08 2014 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2014-03-13 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313) ProcCmdline: evolution SegvAnalysis: - Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi - PC (0x7f88ad21b520) ok - source 0x18(%r14) (0x0468) not located in a known VMA region (needed readable region)! - destination %rdi ok + Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi + PC (0x7f88ad21b520) ok + source 0x18(%r14) (0x0468) not located in a known VMA region (needed readable region)! + destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: - ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0 - g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0 + g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1293144 Title: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder Status in The Evolution Mail Calendaring Tool: Fix Released Status in “evolution” package in Ubuntu: Fix Released Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution” source package in Trusty: In Progress Status in “evolution-data-server” source package in Trusty: In Progress Bug description: [ Description ] (from upstream bug report, might not happen for everyone) - Open evolution - Go to mail view - Try to create a new folder Check evo crashes before not after. I've also cherry-picked some related patches to make the created folder be displayed correctly. Check it doesn't have an expander. [ Development fix ] Same patches (disconnect the signals) [ Regression potential ] Check that folders are created and displayed properly, including cases that previously worked. [ Original description ] When I creates a new folder in Gmail the app closes. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: evolution 3.10.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Mar 16 12:21:08 2014 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2014-03-13 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313) ProcCmdline: evolution SegvAnalysis: Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi PC (0x7f88ad21b520) ok source 0x18(%r14) (0x0468) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit ()
[Touch-packages] [Bug 1158088] Re: [needs-packaging] Mir
https://launchpad.net/distros/ubuntu/+source/mir ** Package changed: ubuntu = mir (Ubuntu) ** Changed in: mir (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1158088 Title: [needs-packaging] Mir Status in “mir” package in Ubuntu: Fix Released Bug description: Mir is a new display technology being developed by Canonical. It is an alternative to X.org and Wayland, designed specifically for the Unity window system. URL: http://unity.ubuntu.com/mir/ License: LGPL Notes: This package can be used either as a system compositor with X.org running on top of it, or natively with UnityNext. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1158088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 855123] Re: at-spi2-registryd crashed with signal 5 in g_type_create_instance()
** Changed in: at-spi2-core (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/855123 Title: at-spi2-registryd crashed with signal 5 in g_type_create_instance() Status in “at-spi2-core” package in Ubuntu: Triaged Bug description: opened software center and was informed of various crashes ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: at-spi2-core 2.1.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Tue Sep 20 22:44:32 2011 ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110901) ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session Signal: 5 SourcePackage: at-spi2-core StacktraceTop: ?? () ?? () ?? () g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: at-spi2-registryd crashed with signal 5 in g_type_create_instance() UpgradeStatus: Upgraded to oneiric on 2011-09-16 (4 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/855123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349297] Re: Better fix for crash due to wrong objects being garbage collected
Since we're not moving to 5.3.1+ in time for release, I'd be wary leaving a known-to-not-be-great patch around... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1349297 Title: Better fix for crash due to wrong objects being garbage collected Status in “qtdeclarative-opensource-src” package in Ubuntu: Incomplete Bug description: We need to stop using debian/patches/parenttosubcreator_qqmlobjectcreator.patch that has been rejected as a valid upstream patch and use https://codereview.qt- project.org/#/c/88064/ which also fixes the issue and is upstream (will be in the 5.3.2 release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1349297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349297] Re: Better fix for crash due to wrong objects being garbage collected
Then i guess the best is getting https://codereview.qt- project.org/#/c/88011/ + https://codereview.qt-project.org/#/c/88064/ somewhere in a PPA and give it a spin? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1349297 Title: Better fix for crash due to wrong objects being garbage collected Status in “qtdeclarative-opensource-src” package in Ubuntu: Incomplete Bug description: We need to stop using debian/patches/parenttosubcreator_qqmlobjectcreator.patch that has been rejected as a valid upstream patch and use https://codereview.qt- project.org/#/c/88064/ which also fixes the issue and is upstream (will be in the 5.3.2 release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1349297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 974480] Re: Notification area whitelist is obsolete
varlesh, I published our reasons for removing the notification area four years ago. http://design.canonical.com/2010/04/notification-area/ If the apps you list claim to work on Ubuntu but do not, please report bugs to the developers of those apps. -- 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/974480 Title: Notification area whitelist is obsolete Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Mark has asked us to consider retiring the notification area whitelist for 12.10. The application indicator system has been in place for two years now, which should be long enough for applications to adopt it. If the whitelist was retired, Java and Wine would be hard-coded as the only software still able to use the menu bar as if it was a notification area, because their developers don't necessarily know that Ubuntu even exists. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 736354] Re: gdbserver (arm, natty) - gdb (ia32, natty) fails
My comment #4 is not exactly, correct. (gdb) target remote 192.168.1.14:1234 Remote debugging using 192.168.1.14:1234 This is expected to work correctly becuase gdbserver should pass target arch information from server side to client side. I have seen this happens correctly when gdbserver is from Ubuntu from 12.04 to 13.10 and gdb-multiarch being Ubuntu 12.04. From 14.04 onwards, I see the same problem reproducing again. So, a regression in gdb. Re-opening bug. This is a bug for gdbserver (updated package). ** Changed in: gdb (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/736354 Title: gdbserver (arm,natty) - gdb (ia32,natty) fails Status in “gdb” package in Ubuntu: Confirmed Bug description: Binary package hint: gdb Attempting a remote debug session. On the arm machine: tgall@halimede:~$ gdbserver 192.168.1.15:1234 /bin/ls Process /bin/ls created; pid = 15437 Listening on port 1234 Remote debugging from host 192.168.1.15 readchar: Got EOF Remote side has terminated connection. GDBserver will reopen the connection. Listening on port 1234 On the intel machine using gdb-mutliarch gdb-multiarch /bin/ls GNU gdb (Ubuntu/Linaro 7.2-1ubuntu10) 7.2 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i686-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /bin/ls...(no debugging symbols found)...done. (gdb) target remote 192.168.1.14:1234 Remote debugging using 192.168.1.14:1234 warning: Architecture rejected target-supplied description Remote 'g' packet reply is too long: 2959b2be2058b2bee0070b403000 (gdb) Version info: ia32: gdb-multiarch 7.2-1ubuntu10 armel: gdbserver 7.2-1ubuntu10 Arm box root@halimede:~# lsb_release -rd Description: Ubuntu Natty (development branch) Release: 11.04 intel box tgall@proteus:~$ lsb_release -rd Description: Ubuntu Natty (development branch) Release: 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/736354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 947448] Re: Volume slider forgets output device on resume
Luke, that bug was assigned to our team, could you have a look and see
if that's something that's still accurate/should be look at or if it can
be closed?
** Changed in: alsa-driver (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Luke Yelavich
(themuso)
--
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/947448
Title:
Volume slider forgets output device on resume
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
I have a Thinkpad with internal speakers plus a MD-PORT AN1 USB HID
based audio card. If I set the USB port as the output then Rhythmbox
and the volume control work correctly and control the USB output.
If I suspend and resume, then Rhythmbox will continue to use the USB
device. The volume control however seems to revert to the internal
speakers.
Effect is music coming out but the volume control does nothing. Re-
setting the output via the Sound control panel fixes the problem.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: michaelh 2984 F pulseaudio
/dev/snd/pcmC1D0p: michaelh 2984 F...m pulseaudio
/dev/snd/controlC0: michaelh 2984 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf850 irq 48'
Mixer name : 'Conexant CX20561 (Hermosa)'
Components : 'HDA:14f15051,17aa20fd,0010'
Controls : 17
Simple ctrls : 12
Card1.Amixer.info:
Card hw:1 'AN1'/'XITEL MD-PORT AN1 at usb-:00:1d.0-2, full speed'
Mixer name : 'USB Mixer'
Components : 'USB09ef:0101'
Controls : 4
Simple ctrls : 3
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
7VHT16WW-1.06'
Mixer name : 'ThinkPad EC 7VHT16WW-1.06'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Mar 6 09:09:40 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64
(20120219)
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/bash
TERM=xterm
LANG=en_NZ.UTF-8
LANGUAGE=en_NZ:en
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel
Symptom_Jack: Speaker, Internal
Symptom_Type: Volume slider, or mixer problems
Title: [2732CTO, Conexant CX20561 (Hermosa), Speaker, Internal] volume slider
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7YET84WW (3.14 )
dmi.board.name: 2732CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr7YET84WW(3.14):bd12/16/2011:svnLENOVO:pn2732CTO:pvrThinkPadR500:rvnLENOVO:rn2732CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2732CTO
dmi.product.version: ThinkPad R500
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/947448/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 929403] Re: Wireless login is not pre-filled with its stored password
** Changed in: network-manager (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) = (unassigned) -- 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/929403 Title: Wireless login is not pre-filled with its stored password Status in “network-manager” package in Ubuntu: Incomplete Bug description: On the Precise beta, every time I log in, the wireless login prompt appears, asking me to log into our password-protected wifi network. This is similar to what you get when you lose wifi signal, *except* that now the password entry box is empty, not pre-filled with the stored password. This could be related to warnings I've been getting from e.g. apt-get about not having a keyring socket to connect to. I would reproduce the exact message, except I don't seem to be getting it now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/929403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352165] Re: [NFORCE6M-A, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_sigmatel.c?id=0a4278464eba4bf98c0d6304c62a1116553125d3 seen incorrect pin fixup port D should be line out instead of speaker when it support Jack detection send email to the author use hdajackretadk to fix the pin Node 0x0d [Pin Complex] wcaps 0x400181: Stereo Control: name=Speaker Jack, index=0, device=0 Pincap 0x173f: IN OUT HP Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 Pin Default 0x01114010: [Jack] Speaker at Ext Rear Conn = 1/8, Color = Green DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x40: OUT VREF_HIZ Unsolicited: tag=06, enabled=1 Connection: 1 0x02 s/class/sound/hwC0D0/driver_pin_configs: 0x0a 0x0221401f 0x0b 0x02a19020 0x0c 0x01a19020 0x0d 0x01114010 0x0e 0x408000f0 0x0f 0x01813022 0x10 0x074510a0 0x11 0x40c400f1 0x15 0x9037012e 0x1b 0x40e000f2 -- 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/1352165 Title: [NFORCE6M-A, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: Speakers are not recognized, I have reinstalled Pulse and Asla to no avail, worked fine 2 days ago suddenly no sound, installed new sound card, it is seen but the speakers are not and no sound from either on board audio or sound card - all hardware is OK ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ann1689 F pulseaudio /dev/snd/controlC0: ann1689 F pulseaudio /dev/snd/controlC1: ann1689 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 3 23:01:45 2014 InstallationDate: Installed on 2014-07-13 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Built-in Audio - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ann1689 F pulseaudio /dev/snd/controlC0: ann1689 F pulseaudio /dev/snd/controlC1: ann1689 F pulseaudio Symptom_Jack: Green Speaker, Rear Symptom_Type: No sound at all Title: [NFORCE6M-A, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: NFORCE6M-A dmi.board.vendor: ELITEGROUP COMPUTER SYSTEM CO.,LTD. dmi.board.version: 1.0 dmi.chassis.asset.tag: Unknow dmi.chassis.type: 3 dmi.chassis.vendor: nVIDIA dmi.chassis.version: NFORCE6M-A dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/11/2007:svnELITEGROUPCOMPUTERSYSTEMCO.,LTD.:pnNFORCE6M-A:pvr1.0:rvnELITEGROUPCOMPUTERSYSTEMCO.,LTD.:rnNFORCE6M-A:rvr1.0:cvnnVIDIA:ct3:cvrNFORCE6M-A: dmi.product.name: NFORCE6M-A dmi.product.version: 1.0 dmi.sys.vendor: ELITEGROUP COMPUTER SYSTEM CO.,LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1352165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333627] Re: update broke fonts in firefox
Thank you for your bug report. That's the only report we got about the issue so far it seems. It's weird that the fontconfig update would create that problem, can you try to downgrade back to the previous version and see if it resolves the issue for you? Could you also add before/after screenshots to the bug showing the issue? ** Changed in: fontconfig (Ubuntu) Importance: Undecided = Low ** Changed in: fontconfig (Ubuntu) Status: Confirmed = Incomplete -- 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/1333627 Title: update broke fonts in firefox Status in “fontconfig” package in Ubuntu: Incomplete Bug description: I have Ubuntu Studio 14.04. The updates window popped up and asked me to install updates. Which I did. This somehow broke my font configuration. So that I have blurry fonts in firefox. No other application is affected. I have modified nothing in /etc/fonts/conf.avail. If updates changes the contents of /etc/fonts/conf.d I do not see the purpose of having a conf.avail/conf.d - organization. The purpose must be to let users link or unlink files in conf.d to files in conf.avail. I don't expect updates to create links in /etc/fonts/conf.d that were previously created at installation time or upgrate time. So if I unlink something in /etc/fonts/conf.d I expect it to stay that way. Changes to the files themselves should go in /etc/fonts/conf.avail. Changes to which files are available by default in /etc/fonts/conf.d should be applied only when they are CHANGES. Not reinstall the default links with every update. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 ~$ apt-cache policy fontconfig fontconfig: Installed: 2.11.0-0ubuntu4.1 Candidate: 2.11.0-0ubuntu4.1 Version table: *** 2.11.0-0ubuntu4.1 0 500 http://no.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.11.0-0ubuntu4 0 500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1333627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
Some additional observations: I usually reproduce this bug on my desktop pc that doesnt have a touchpad/trackball (mouse only) by moving the cursor inside the launcher area while this command from comment #3 is executed: $ sudo evemu-play /dev/input/event# s.event (the comment: https://bugs.launchpad.net/oem-priority/+bug/1310518/comments/3) i.imgur.com/rtXckuE.jpg In the screenshot above I got the bug while I was switching workspaces and in this case alt+tab doesn't restore the mouse click. -- 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/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: New Status in OEM Priority Project trusty series: New Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press super on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1310518/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 985647] Re: Some Traditional Chinese words looks very strange during the installation process
unassiging the team from the desktop team, the bug hasn't move for years and we are not working on it ** Changed in: freetype (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/985647 Title: Some Traditional Chinese words looks very strange during the installation process Status in “freetype” package in Ubuntu: New Bug description: ISO version: precise-desktop-amd64.iso Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120418.2) Installation language: Traditional Chinese Description: Select Traditional Chinese as the installation language, some words looks very strange during the installation process. Please refer to the attached picture for more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/985647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 913708] Re: resume from suspend shows console login then desktop environment
unassiging the bug from the desktop team, the bug hasn't move for years and we are not working on it ** Changed in: pm-utils (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/913708 Title: resume from suspend shows console login then desktop environment Status in The Ubuntu Flicker-Free Boot Project: New Status in “pm-utils” package in Ubuntu: Triaged Bug description: If I perform the following steps I will be presented with a console login and then my desktop environment when resuming from suspend. 1) Switch to tty1 via Ctrl+Alt+F1 2) Switch back to X via Ctrl+Alt+F7 3) Suspend system 4) Resume system 5) Observe system displaying a console login (tty1) then a desktop environment during resume process ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pm-utils 1.4.1-8ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Uname: Linux 3.2.0-7-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CheckboxSubmission: 2e6ecd139611830c78226ad04ff4c093 CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f Date: Mon Jan 9 11:36:55 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: Upgraded to precise on 2012-01-04 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-flicker-free-boot/+bug/913708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317476] Re: read builtin does not timeout when using readline for input
This bug was fixed in the package bash - 4.3-8ubuntu1 --- bash (4.3-8ubuntu1) utopic; urgency=medium * Merge with Debian; remaining changes: bash (4.3-8) unstable; urgency=medium * Apply upstream patches 012 - 022, fixing the issues: - When a SIGCHLD trap runs a command containing a shell builtin while a script is running `wait' to wait for all running children to complete, the SIGCHLD trap will not be run once for each child that terminates. - Using reverse-i-search when horizontal scrolling is enabled does not redisplay the entire line containing the successful search results. - Under certain circumstances, $@ is expanded incorrectly in contexts where word splitting is not performed. - When completing directory names, the directory name is dequoted twice. This causes problems for directories with single and double quotes in their names. - An extended glob pattern containing a slash (`/') causes the globbing code to misinterpret it as a directory separator. - The code that creates local variables should not clear the `invisible' attribute when returning an existing local variable. Let the code that actually assigns a value clear it. - When assigning an array variable using the compound assignment syntax, but using `declare' with the rhs of the compound assignment quoted, the shell did not mark the variable as visible after successfully performing the assignment. - The -t timeout option to `read' does not work when the -e option is used. LP: #1317476. - When PS2 contains a command substitution, here-documents entered in an interactive shell can sometimes cause a segmentation fault. - When the readline `revert-all-at-newline' option is set, pressing newline when the current line is one retrieved from history results in a double free and a segmentation fault. Closes: #747341. - Using nested pipelines within loops with the `lastpipe' option set can result in a segmentation fault. * Fix typo in package description. Closes: #707810. -- Matthias Klose d...@ubuntu.com Mon, 04 Aug 2014 09:35:20 +0200 ** Changed in: bash (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1317476 Title: read builtin does not timeout when using readline for input Status in “bash” package in Ubuntu: Fix Released Bug description: As of 14.04 the read builtin seemingly ignores -t if -e is provided. In 13.10, $ time read -t2 -e -p ? ? real 0m2.000s user 0m0.000s sys 0m0.000s In 14.04, $ time read -t2 -e -p ? ? ^C real 0m5.254s user 0m0.000s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1317476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
Thanks. Reassigning to kernel then. ** Summary changed: - [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN + Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event ** Package changed: systemd (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event Status in “linux” package in Ubuntu: Confirmed Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351801] Re: lrt test found crash file _usr_bin_unity8.32011.crash
Not sure that this is the same thing. bug #1348702 was quite clear-cut. This one, I don't recognise much at all. A better stack trace would be useful. Any chance of getting that? -- 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/1351801 Title: lrt test found crash file _usr_bin_unity8.32011.crash Status in LRT crashes: New Status in “unity8” package in Ubuntu: New Bug description: Summary: Crash file _usr_bin_unity8.32011.crash was found Steps to reproduce: 1. Run lrt test in lp:lrt Expected result: No crashes happen Actual result: A crash happened System info: base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/utopic-proposed build_number: 165 version_detail: ubuntu=20140801,device=20140728.1,version=165 Device=mako To manage notifications about this bug go to: https://bugs.launchpad.net/lrt-crashes/+bug/1351801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1293144] Re: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder
** Branch linked: lp:~ubuntu-desktop/evolution-data-server/ubuntu-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1293144 Title: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder Status in The Evolution Mail Calendaring Tool: Fix Released Status in “evolution” package in Ubuntu: Fix Released Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “evolution” source package in Trusty: In Progress Status in “evolution-data-server” source package in Trusty: In Progress Bug description: [ Description ] (from upstream bug report, might not happen for everyone) - Open evolution - Go to mail view - Try to create a new folder Check evo crashes before not after. I've also cherry-picked some related patches to make the created folder be displayed correctly. Check it doesn't have an expander. [ Development fix ] Same patches (disconnect the signals) [ Regression potential ] Check that folders are created and displayed properly, including cases that previously worked. [ Original description ] When I creates a new folder in Gmail the app closes. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: evolution 3.10.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Mar 16 12:21:08 2014 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2014-03-13 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313) ProcCmdline: evolution SegvAnalysis: Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi PC (0x7f88ad21b520) ok source 0x18(%r14) (0x0468) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1293144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352142] Re: Doesn't load Japanese font on Ubuntu Touch
I'm wondering if this is related to the recent change to fix bug 1346766 -- 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/1352142 Title: Doesn't load Japanese font on Ubuntu Touch Status in “unity8” package in Ubuntu: New Bug description: Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese environment. How to reproduce: 1. Install Ubuntu Touch 2. Set environment to Japanese at first boot 3. Reboot system (option) 4. Check whether a glyph come from Japanese font Expected result: Use Japanese gothic font (Droid Sans Japanese), and no Mojibake. Actual result: Use AR PL Ukai CN (Chinese serif font), and some glyphs are missing. Please refer attached image. Other information from phablet-shell: $ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC' LANGUAGE=ja LC_TIME=ja_JP.UTF-8 LC_MONETARY=ja_JP.UTF-8 GDM_LANG=ja LC_ADDRESS=ja_JP.UTF-8 LANG=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_NUMERIC=ja_JP.UTF-8 LC_PAPER=ja_JP.UTF-8 = It seems that LANG env is vallid. For 音 (U+97F3), the glyph is visible in unity8, but use AR PL UKai CN. $ fc-match 'sans:charset=!!(Dl !!rW+' DroidSansJapanese.ttf: Droid Sans Regular $ fc-match 'sans:lang=ja:charset=!!(Dl !!rW+' DroidSansJapanese.ttf: Droid Sans Regular $ fc-match 'sans:lang=en:charset=!!(Dl !!rW+' ukai.ttc: AR PL UKai CN Book = Both of ukai and droid sans have U+97F3, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. For 楽 (U+697D), the glyph is invisible in unity8. $ fc-match 'sans:charset=!!%g9 /?6HG' DroidSansJapanese.ttf: Droid Sans Regular $ fc-match 'sans:lang=ja:charset=!!%g9 /?6HG' DroidSansJapanese.ttf: Droid Sans Regular $ fc-match 'sans:lang=en:charset=!!%g9 /?6HG' DroidSansJapanese.ttf: Droid Sans Regular = Because ukai doesn't have U+697D, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. $ sudo lsof -p `pidof unity8` | grep font unity8 2592 phablet memREG7,0 17151049 113683 /usr/share/fonts/truetype/arphic/ukai.ttc unity8 2592 phablet memREG7,0 415552 113610 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf unity8 2592 phablet memREG7,0 333616 113622 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf unity8 2592 phablet memREG7,0 353824 113613 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf = Why loads ukai.ttc instead of DroidSansJapanese.ttf? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1352142/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302090] Re: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged
reatasking subwoofer as line out is a trick which force the driver share volume control with speaker the drawback is missing volume control of the subwoofer but you have volume controls for your headset and headphone -- 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/1302090 Title: Dell Alienware 14, Speaker sound output is mono until a headphone jack is plugged Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Here's the required release and package information: Description:Ubuntu Trusty Tahr (development branch) Release:14.04 Package: linux-image-extra-3.13.0-19-generic Version: 3.13.0-19.40 When playing audio through speakers on my Alienware 14 2014, the sound output is in mono until I plug a headphone in any of the two available headphone jacks (obviously, the auto-mute option must be disabled). When I do so, the sound starts to play in stereo. I would love the sound output to be stereo by default and not be forced to plug anything to achieve that. Attached is the alsa-info.sh output for my machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349297] Re: Better fix for crash due to wrong objects being garbage collected
Uploaded 1h ago, armhf binaries should be published soon (30min): https://launchpad.net/~canonical-qt5-edgers/+archive/ubuntu/qt5-beta1 / ppa:canonical-qt5-edgers/qt5-beta1 It includes also Saviq's other changes that are going in as the 'ubuntu8' via a landing silo, so these two new patches would be ubuntu9 then. Note that you can't have that Saviq's landing PPA enabled at the same time as it has higher version number. I'll myself give it a better spin later when the ubuntu8 is first published and I can get a proper landing silo for ubuntu9 (+ fix changelog). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1349297 Title: Better fix for crash due to wrong objects being garbage collected Status in “qtdeclarative-opensource-src” package in Ubuntu: Incomplete Bug description: We need to stop using debian/patches/parenttosubcreator_qqmlobjectcreator.patch that has been rejected as a valid upstream patch and use https://codereview.qt- project.org/#/c/88064/ which also fixes the issue and is upstream (will be in the 5.3.2 release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1349297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351698] Re: rhythmbox crashed with SIGSEGV in gst_pad_query()
*** This bug is a duplicate of bug 1302634 *** https://bugs.launchpad.net/bugs/1302634 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1302634, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1351698/+attachment/4168327/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1351698/+attachment/4168329/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1351698/+attachment/4168330/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1351698/+attachment/4168331/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1351698/+attachment/4168332/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1351698/+attachment/4168333/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1351698/+attachment/4168334/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1302634 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1351698 Title: rhythmbox crashed with SIGSEGV in gst_pad_query() Status in “gstreamer1.0” package in Ubuntu: New Bug description: Crashed while trying to play songs from an MTP device. TESTCASE: 1. In rhythmbox copy a song from the local library to the media device 2. Select the song on the device and press play ACTUAL RESULT This crash ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: libgstreamer1.0-0 1.4.0-1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 2 22:40:25 2014 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2013-09-03 (332 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902) ProcCmdline: rhythmbox ProcEnviron: PATH=(custom, user) LANGUAGE=fr_FR XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7efee4964b69:mov0x30(%r12),%rdi PC (0x7efee4964b69) ok source 0x30(%r12) (0x0030) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/rhythmbox/plugins/mtpdevice/libmtpdevice.so ?? () from /usr/lib/rhythmbox/plugins/mtpdevice/libmtpdevice.so ?? () from /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0 gst_pad_query () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'system-image-cli' Title: rhythmbox crashed with SIGSEGV in gst_pad_query() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1351698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352239] [NEW] Windows aren't rendered/updated when using Unity
Public bug reported: This is possible related to Bug #1352231 When using Unity windows aren't rendered or updated. In LXDE everything works fine. Steps to reproduce: 1. Log into Unity 2. Open a Window What should happen: The window is shown I can interact with it. What actually happens: Only the Mouse-Cursor changes. I can only see anything happened after running unity --replace. For every Update(Window movement, ...) I have to repeat unity --replace in order to see the changes. When did this regression happen: Last known working configuration was 28 July 2014. The problem started with the update to linux kernel 3.13.0-20-generic, where temporarily fixed by booting 3.13.0-19-generic but it seems like every kernel is affected since now this workaround doesn't help either. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Aug 4 10:56:48 2014 EcryptfsInUse: Yes SourcePackage: unity SystemImageInfo: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression third-party-packages utopic ** Attachment added: Xorg.0.log1 https://bugs.launchpad.net/bugs/1352239/+attachment/4169325/+files/Xorg.0.log1 -- 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/1352239 Title: Windows aren't rendered/updated when using Unity Status in “unity” package in Ubuntu: New Bug description: This is possible related to Bug #1352231 When using Unity windows aren't rendered or updated. In LXDE everything works fine. Steps to reproduce: 1. Log into Unity 2. Open a Window What should happen: The window is shown I can interact with it. What actually happens: Only the Mouse-Cursor changes. I can only see anything happened after running unity --replace. For every Update(Window movement, ...) I have to repeat unity --replace in order to see the changes. When did this regression happen: Last known working configuration was 28 July 2014. The problem started with the update to linux kernel 3.13.0-20-generic, where temporarily fixed by booting 3.13.0-19-generic but it seems like every kernel is affected since now this workaround doesn't help either. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Aug 4 10:56:48 2014 EcryptfsInUse: Yes SourcePackage: unity SystemImageInfo: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1352239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350874] Re: /usr/include/ubuntu/application/ui/input/event_deprecated.h:79:24: error: redefinition of ‘struct PointerCoordinate’
20140801 doesn't fix this. Please would somebody look and verify their fix by trying to rebuild gst-plugins-bad1.0 against it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1350874 Title: /usr/include/ubuntu/application/ui/input/event_deprecated.h:79:24: error: redefinition of ‘struct PointerCoordinate’ Status in “platform-api” package in Ubuntu: Confirmed Bug description: You can reproduce this by building gst-plugins-bad1.0 in current Utopic. Any builds which include event.h directly or indirectly are going to fail. In file included from /usr/include/ubuntu/application/ui/input/event.h:211:0, from /usr/include/ubuntu/application/ui/window_properties.h:25, from /usr/include/ubuntu/application/ui/window.h:27, from gstamc.h:35, from gstamchybris.c:27: /usr/include/ubuntu/application/ui/input/event_deprecated.h:79:24: error: redefinition of ‘struct PointerCoordinate’ struct PointerCoordinate ^ In file included from /usr/include/ubuntu/application/ui/window_properties.h:25:0, from /usr/include/ubuntu/application/ui/window.h:27, from gstamc.h:35, from gstamchybris.c:27: /usr/include/ubuntu/application/ui/input/event.h:168:12: note: originally defined here struct PointerCoordinate ^ Makefile:869: recipe for target 'libgstandroidmedia_la-gstamchybris.lo' failed structs have file scope; you can't have two with the same name. platform-api 2.2.0+14.10.20140730-0ubuntu1 but this was introduced in 2.2.0+14.10.20140728-0ubuntu1 (https://launchpadlibrarian.net/180999524/platform- api_2.1.0%2B14.10.20140721-0ubuntu1_2.2.0%2B14.10.20140728-0ubuntu1.diff.gz). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/platform-api/+bug/1350874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351951] Re: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tracker (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1351951 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() Status in Meta-tracker: New Status in “tracker” package in Ubuntu: Confirmed Bug description: Bug in version 1.0.2, duplicaded of Bug #1342923(?) ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: tracker 1.0.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Aug 3 12:43:09 2014 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2014-04-27 (98 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x7f23da50ee13 _IO_vfprintf_internal+7443: repnz scas %es:(%rdi),%al PC (0x7f23da50ee13) ok source %es:(%rdi) (0xc0449a50) not located in a known VMA region (needed readable region)! destination %al ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: tracker StacktraceTop: _IO_vfprintf_internal (s=s@entry=0x7f23d619b640, format=optimized out, format@entry=0x7f23db83dae0 Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s'), ap=ap@entry=0x7f23d619b7e8) at vfprintf.c:1642 __GI___vasprintf_chk (result_ptr=0x7f23d619b798, flags=1, format=0x7f23db83dae0 Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s'), args=0x7f23d619b7e8) at vasprintf_chk.c:66 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_new_valist () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/1351951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352239] Re: Windows aren't rendered/updated when using Unity
** Attachment added: dmesg.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1352239/+attachment/4169333/+files/dmesg.txt -- 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/1352239 Title: Windows aren't rendered/updated when using Unity Status in “unity” package in Ubuntu: New Bug description: This is possible related to Bug #1352231 When using Unity windows aren't rendered or updated. In LXDE everything works fine. Steps to reproduce: 1. Log into Unity 2. Open a Window What should happen: The window is shown I can interact with it. What actually happens: Only the Mouse-Cursor changes. I can only see anything happened after running unity --replace. For every Update(Window movement, ...) I have to repeat unity --replace in order to see the changes. When did this regression happen: Last known working configuration was 28 July 2014. The problem started with the update to linux kernel 3.13.0-20-generic, where temporarily fixed by booting 3.13.0-19-generic but it seems like every kernel is affected since now this workaround doesn't help either. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Aug 4 10:56:48 2014 EcryptfsInUse: Yes SourcePackage: unity SystemImageInfo: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1352239/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Summary changed: - replace the text Empty! with something more useful + [Indicators] replace the text Empty! with something more useful ** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Status: New = Triaged -- 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 Ubuntu UX bugs: Triaged Status in “indicator-messages” package in Ubuntu: New 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/ubuntu-ux/+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 1350803] Re: [Spread] Threashold in spread for closing apps should be increased
** Changed in: ubuntu-ux Status: New = Triaged -- 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/1350803 Title: [Spread] Threashold in spread for closing apps should be increased Status in Ubuntu UX bugs: Triaged Status in The Unity 8 shell: Incomplete Status in “unity8” package in Ubuntu: New Bug description: Currently, the close threshold is too small (you can close app with a fast swipe even for short distance movement), should be increased To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1327091] Re: Ubuntu floating home button
** Changed in: ubuntu-ux Status: Triaged = Opinion -- 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/1327091 Title: Ubuntu floating home button Status in Ubuntu UX bugs: Opinion Status in “unity8” package in Ubuntu: Incomplete Bug description: Since we do not have the hardware keys, I am thinking whether we can have a floating circle (top most) kind of thing like what iPhone has. The feature is called apple floating home button. Tap it, and it pops up a menu to navigate, and a user can drag it to anywhere of the screen if it blocks you. I personally think it is a useful feature to the end users, and it is a convenience. We can use it to navigate to the scope, application, or other pages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1327091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Unable to mount Blank CD-R disc. Location is already mounted. Status in “glib2.0” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.
I just made a fresh install of 14.04.1 64bit and I can confirm that the bug is present. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Unable to mount Blank CD-R disc. Location is already mounted. Status in “glib2.0” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350017] Re: [clock-app] There is no vibration when an alarm goes off
** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1350017 Title: [clock-app] There is no vibration when an alarm goes off Status in Clock application for Ubuntu devices: In Progress Status in Ubuntu UX bugs: Triaged Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: It'd be probably nice to also have vibration beside the sound alert when an alarm triggers. - Design Solution -- Giorgio Venturi updated the design spec for the clock app at [1]. The vibration will be enabled by default for all alarms. The user however will be provided a global setting to disable that if required. [1] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1229950] Re: [messaging-app]draft messages aren't saved
** Changed in: ubuntu-ux Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1229950 Title: [messaging-app]draft messages aren't saved Status in Messaging App: Confirmed Status in Ubuntu UX bugs: Triaged Status in “messaging-app” package in Ubuntu: Confirmed Bug description: Drafting an sms message and then pressing back to go back to the main messaging screen causes we to lose my unsent message 1. open messaging and select a contact 2. draft a new message to them 3. open toolbar and select back to go back to primary screen 4. Tap the contact again Expected Results draft version of message is retained in the text box actual result blank text box, without the draft message To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1229950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 974480] Re: Notification area whitelist is obsolete
@mpt, you can explain all you want, but it doesn't change the fact that this has broken a valuable part of Ubuntu. Does not the chorus of complaints mean something to you? We know that we want the developers to make their changes, but some developers simply just don't care (I know, because I have tried asking). Will it really break Ubuntu to put the whitelist back in? -- 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/974480 Title: Notification area whitelist is obsolete Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Mark has asked us to consider retiring the notification area whitelist for 12.10. The application indicator system has been in place for two years now, which should be long enough for applications to adopt it. If the whitelist was retired, Java and Wine would be hard-coded as the only software still able to use the menu bar as if it was a notification area, because their developers don't necessarily know that Ubuntu even exists. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352253] [NEW] hotkey to toggle microphone mute (ALT + F4) shows a speaker, not a microphone
Public bug reported:
This is incorrect for 2 reasons:
1) The overlay should show a microphone icon since that is what is being
toggled.
2) It's currently using the same icon as the speaker / sound output mute hotkey
(ALT + F1).
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute':
(true, '', [false]), 'phone-settings': (true, '', []), 'mic-volume': (true,
'', [0.510009765625]), 'scroll': (true, 'i', []), 'vlc.desktop': (true, '',
[{'running': false, 'state': 'Paused'}]), 'previous.vlc.desktop': (true,
'', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '',
[{'running': false, 'state': 'Paused'}]), 'previous.rhythmbox.desktop':
(true, '', []), 'volume': (true, 'i', [0.350067138671875]),
'play-playlist.vlc.desktop': (true, 's', []), 'root': (true, '', [{'title':
'Son', 'accessible-desc': 'Volume (35%)', 'icon': ('themed',
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume',
'audio']), 'visible': true}]), 'play.rhythmbox.desktop': (true, '',
['Paused']), 'play-playlist.rhythmbox.desktop': (true, 's', []),
'next.rhythmbox.desktop': (true, '', []), 'play.vlc.desktop': (true, '',
['Paused'])},)
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug 4 10:39:43 2014
InstallationDate: Installed on 2014-04-11 (114 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to utopic on 2014-05-08 (87 days ago)
** Affects: indicator-sound (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug utopic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1352253
Title:
hotkey to toggle microphone mute (ALT + F4) shows a speaker, not a
microphone
Status in “indicator-sound” package in Ubuntu:
New
Bug description:
This is incorrect for 2 reasons:
1) The overlay should show a microphone icon since that is what is being
toggled.
2) It's currently using the same icon as the speaker / sound output mute
hotkey (ALT + F1).
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute':
(true, '', [false]), 'phone-settings': (true, '', []), 'mic-volume': (true,
'', [0.510009765625]), 'scroll': (true, 'i', []), 'vlc.desktop': (true, '',
[{'running': false, 'state': 'Paused'}]), 'previous.vlc.desktop': (true,
'', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '',
[{'running': false, 'state': 'Paused'}]), 'previous.rhythmbox.desktop':
(true, '', []), 'volume': (true, 'i', [0.350067138671875]),
'play-playlist.vlc.desktop': (true, 's', []), 'root': (true, '', [{'title':
'Son', 'accessible-desc': 'Volume (35%)', 'icon': ('themed',
['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume',
'audio']), 'visible': true}]), 'play.rhythmbox.desktop': (true, '',
['Paused']), 'play-playlist.rhythmbox.desktop': (true, 's', []),
'next.rhythmbox.desktop': (true, '', []), 'play.vlc.desktop': (true, '',
['Paused'])},)
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug 4 10:39:43 2014
InstallationDate: Installed on 2014-04-11 (114 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to utopic on 2014-05-08 (87 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1352253/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1058602] Re: [regression] Samba shares showing up in Launcher - No way to remove permanently
Fresh install of 14.04.1 64bit, when I insert or remove DVD from DVD Writer, samba shares (cifs) reappear. If I unlock DVD icon from launcher, it also removes ALL samba share icons. Similarly, if I again remove ANY samba share icon, they ALL disaapear, together with DVD icon. Safely removing USB flash/HD does has the same behaviour in about 50% of cases. -- 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/1058602 Title: [regression] Samba shares showing up in Launcher - No way to remove permanently Status in Unity: New Status in “unity” package in Ubuntu: Fix Released Bug description: On Ubuntu 12.10 beta 2, freshly upgraded from 12.04, I'm now getting my Samba shares (mounted using cifs, so with an entry in fstab) showing up in the Launcher, with network folders icons, which was not the case before. I'm not sure if it's a feature or a bug, but for sure, there should be a way to disable this, globally (i.e. option to not show network shares in Launcher) or for each icon (i.e. with remove from Launcher in the menu). For internal hard disk, which is also showing up in the Launcher since 12.10, there is a Remove from Launcher option in the menu, which is great. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1058602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1287736] Re: System Settings - Accounts and back shows black screen and 5s delay
I can't reproduce the long delay either. The inability to restart OA is the same issue as Bug #1269841 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1287736 Title: System Settings - Accounts and back shows black screen and 5s delay Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Incomplete Status in “unity-mir” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu: Incomplete Bug description: mako image #219 Open System Settings Tap Accounts Note a black flash between System Settings and Accounts Press 'Back' to go back from Accounts to System Settings Note a black flash - and sometimes a 5 second delay before getting back to System settings. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-system-settings 0.1+14.04.20140228-0ubuntu1 Uname: Linux 3.4.0-4-mako armv7l ApportVersion: 2.13.2-0ubuntu5 Architecture: armhf Date: Tue Mar 4 14:52:38 2014 InstallationDate: Installed on 2014-03-04 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140304) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1287736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1287736] Re: System Settings - Accounts and back shows black screen and 5s delay
As for the long black screen on return, i'll mark it incomplete for now, since I don't know of a way to reproduce the issue anymore. ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu) Status: Confirmed = Incomplete ** Changed in: unity8 (Ubuntu) Status: Confirmed = Incomplete ** Changed in: unity-mir (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1287736 Title: System Settings - Accounts and back shows black screen and 5s delay Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Incomplete Status in “unity-mir” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu: Incomplete Bug description: mako image #219 Open System Settings Tap Accounts Note a black flash between System Settings and Accounts Press 'Back' to go back from Accounts to System Settings Note a black flash - and sometimes a 5 second delay before getting back to System settings. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-system-settings 0.1+14.04.20140228-0ubuntu1 Uname: Linux 3.4.0-4-mako armv7l ApportVersion: 2.13.2-0ubuntu5 Architecture: armhf Date: Tue Mar 4 14:52:38 2014 InstallationDate: Installed on 2014-03-04 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140304) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1287736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1287736] Re: System Settings - Accounts and back shows black screen and 5s delay
If possible can you try to upload the crash dump via ubuntu-bug to get it retraced? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1287736 Title: System Settings - Accounts and back shows black screen and 5s delay Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Incomplete Status in “unity-mir” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu: Incomplete Bug description: mako image #219 Open System Settings Tap Accounts Note a black flash between System Settings and Accounts Press 'Back' to go back from Accounts to System Settings Note a black flash - and sometimes a 5 second delay before getting back to System settings. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-system-settings 0.1+14.04.20140228-0ubuntu1 Uname: Linux 3.4.0-4-mako armv7l ApportVersion: 2.13.2-0ubuntu5 Architecture: armhf Date: Tue Mar 4 14:52:38 2014 InstallationDate: Installed on 2014-03-04 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140304) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1287736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 947448] Re: Volume slider forgets output device on resume
38027.160124] PM: Entering mem sleep
[38027.160213] Suspending console(s) (use no_console_suspend to debug)
[38027.161142] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[38027.228349] [fglrx] IRQ 50 Disabled
[38027.228459] [fglrx] Preparing suspend fglrx in kernel.
[38027.228466] kworker/u:9: page allocation failure: order:10, mode:0x4020
[38027.228469] Pid: 2002, comm: kworker/u:9 Tainted: P C O
3.2.0-17-generic #27-Ubuntu
[38027.228471] Call Trace:
[38027.228478] [8111c536] warn_alloc_failed+0xf6/0x150
[38027.228481] [8111f84f] ? get_page_from_freelist+0x1cf/0x540
[38027.228483] [8112039b] __alloc_pages_nodemask+0x64b/0x820
[38027.228487] [81157043] alloc_pages_current+0xa3/0x110
[38027.228490] [8111b55e] __get_free_pages+0xe/0x40
[38027.228493] [8116189f] kmalloc_order_trace+0x3f/0xd0
[38027.228495] [81162420] __kmalloc+0x180/0x190
[38027.228497] [8111b55e] ? __get_free_pages+0xe/0x40
[38027.228552] [a030dade] KCL_MEM_SmallBufferAllocAtomic+0x1e/0x20
[fglrx]
[38027.228578] [a0320fa3] firegl_save_fb+0x233/0x360 [fglrx]
[38027.228609] [a0330d34] ?
mc_heap_get_reserved_blocks_info+0x174/0x2a0 [fglrx]
[38027.228611] [8116167b] ? kfree+0x3b/0x140
[38027.228637] [a03200c4] ? firegl_pm_save_framebuffer+0x204/0x300
[fglrx]
[38027.228665] [a0322d9d] ? firegl_cail_powerdown+0x8d/0x200 [fglrx]
[38027.228683] [a030ae07] ? fglrx_pci_suspend+0x87/0x150 [fglrx]
[38027.228688] [813315e6] ? pci_legacy_suspend+0x46/0xe0
[38027.228690] [8133271d] ? pci_pm_suspend+0xdd/0x130
[38027.228694] [813f8740] ? device_pm_wait_for_dev+0x30/0x30
[38027.228697] [813f8be5] ? pm_op+0x175/0x1c0
[38027.228699] [813f8e9a] ? __device_suspend+0x1fa/0x230
[38027.228702] [81092120] ? async_schedule+0x20/0x20
[38027.228704] [813f997f] ? async_suspend+0x1f/0xa0
[38027.228706] [8109219f] ? async_run_entry_fn+0x7f/0x180
[38027.228709] [81084d8a] ? process_one_work+0x11a/0x480
[38027.228712] [81085b34] ? worker_thread+0x164/0x370
[38027.228714] [810859d0] ? manage_workers.isra.29+0x130/0x130
[38027.228717] [8108a38c] ? kthread+0x8c/0xa0
[38027.228720] [81663374] ? kernel_thread_helper+0x4/0x10
[38027.228722] [8108a300] ? flush_kthread_worker+0xa0/0xa0
[38027.228725] [81663370] ? gs_change+0x13/0x13
--
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/947448
Title:
Volume slider forgets output device on resume
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
I have a Thinkpad with internal speakers plus a MD-PORT AN1 USB HID
based audio card. If I set the USB port as the output then Rhythmbox
and the volume control work correctly and control the USB output.
If I suspend and resume, then Rhythmbox will continue to use the USB
device. The volume control however seems to revert to the internal
speakers.
Effect is music coming out but the volume control does nothing. Re-
setting the output via the Sound control panel fixes the problem.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: michaelh 2984 F pulseaudio
/dev/snd/pcmC1D0p: michaelh 2984 F...m pulseaudio
/dev/snd/controlC0: michaelh 2984 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf850 irq 48'
Mixer name : 'Conexant CX20561 (Hermosa)'
Components : 'HDA:14f15051,17aa20fd,0010'
Controls : 17
Simple ctrls : 12
Card1.Amixer.info:
Card hw:1 'AN1'/'XITEL MD-PORT AN1 at usb-:00:1d.0-2, full speed'
Mixer name : 'USB Mixer'
Components : 'USB09ef:0101'
Controls : 4
Simple ctrls : 3
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
7VHT16WW-1.06'
Mixer name : 'ThinkPad EC 7VHT16WW-1.06'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Mar 6 09:09:40 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64
(20120219)
PackageArchitecture:
[Touch-packages] [Bug 1268848] Re: Unity in 13.10 unstable with Radeon 7950
I finally installed 14.04.1 64bit a few days ago, and so far, so good... -- 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/1268848 Title: Unity in 13.10 unstable with Radeon 7950 Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: About a month ago I installed a fresh Ubuntu 13.10 64bit on a i5 machine, 8GB RAM, with Radeon 7950 graphic card. Before this, I was running 12.04 64bit without any graphic driver related problems. I tried both Catalyst versions from official repository, latest 13.12 drivers from AMD site and open source drivers (radeon), and I can't tell which one was more unstable. After a few hours of use, I could not play any videos with any of the drivers (tried mplayer and VLC, both crashed with various errors), OpenGL isn't working anymore (even glxgears was crashing) and I had various artifacts on screen (like parts of window rendered on the wrong place on screen). Putting machine to sleep and waking it up later produced even more errors. I also tried to turn off various things in CCSM, without any positive results. Steam client had terrible flickering almost all the time, it was practically unusable; also about 8 of 10 times it was crashing on startup. After about two weeks of trying to make it usable, I gave up and installed MATE desktop. Not a single graphic error since then. Steam works flawlessly, 3D games also, Wine games, playing videos, everything. I kind of like how Unity works, I was using it for the last two years as my main desktop (on the same machine), but this behaviour is unexpected and utterly undesireable. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 14 07:26:14 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: fglrx, 13.251, 3.11.0-14-generic, x86_64: installed fglrx, 13.251, 3.11.0-15-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-14-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-15-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0424] InstallationDate: Installed on 2013-12-06 (38 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) JockeyStatus: kmod:fglrx - ATI Fire GL (Proprietary, Enabled, In use) kmod:fglrx_updates - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=UUID=eab5c9d7-0979-4fae-9ed5-a26a530694de ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: Z68 Extreme4 Gen3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd07/08/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Extreme4Gen3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Jan 10 14:53:12 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2~saucy1
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
I'll poke, but I can't get even the bad output on my current Utopic system - laney@iota LANG=zh_TW.UTF-8 fc-match -s sans-serif | head -5 DejaVuSans.ttf: DejaVu Sans Book DejaVuSans-Bold.ttf: DejaVu Sans Bold DejaVuSans-Oblique.ttf: DejaVu Sans Oblique DejaVuSans-BoldOblique.ttf: DejaVu Sans Bold Oblique Verdana.ttf: Verdana Normal I do have the locale installed. How do you guys get this? appending :lang=zh-cn does get me droid first. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: New Status in “language-selector” package in Ubuntu: New Bug description: There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: Droid Sans Fallback Regular uming.ttc: AR PL UMing CN Light uming.ttc: AR PL UMing HK Light ukai.ttc: AR PL UKai CN Book DejaVuSans.ttf: DejaVu Sans Book Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Also affects: friendly-recovery (Ubuntu) Importance: Undecided Status: New -- 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/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Committed Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: In Progress Status in “upstart” package in Ubuntu: Triaged Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (= 1.11-0ubuntu3). dbus depends on upstart (= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Changed in: friendly-recovery (Ubuntu) Status: New = Fix Committed ** Changed in: friendly-recovery (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Committed Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: In Progress Status in “upstart” package in Ubuntu: Triaged Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (= 1.11-0ubuntu3). dbus depends on upstart (= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Branch linked: lp:~ubuntu-core-dev/friendly-recovery/ubuntu -- 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/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Committed Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: In Progress Status in “upstart” package in Ubuntu: Triaged Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (= 1.11-0ubuntu3). dbus depends on upstart (= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340154] Re: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode
Thanks Marius, I've done what I can - I hope you can help to secure this backport request with the appropriate support teams. Please do let me know if there is anything else I can do to help make this happen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1340154 Title: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode Status in “modem-manager-gui” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: Incomplete Bug description: To-date, cannot utilise Modem Manager GUI in 12.04 LTS, as it is understood that there is a 'bug' in Modem Manager version 0.5.2 that installed in Ubuntu 12.04 by default. On modem initialization it sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode. I understand the GUI works well and has been introduced into Saucy Salamander and later versions, but Modem Manager versions 0.6 or later has not yet been made available for 12.04 LTS users which enables its SMS functions etc to work. It is hoped that an updated version of Modem Manager that addresses this and other bug fixes can be introduced into 12.04 LTS very soon for users like myself who have been looking out patiently for a couple of years for this functionality. Thanks in advance for the anticipated support... cheers! See also bug report upstream in modem manager GUI: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?15.item.3.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1340154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340154] Re: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode
Also, should the 'Status' be changed now? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1340154 Title: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode Status in “modem-manager-gui” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: Incomplete Bug description: To-date, cannot utilise Modem Manager GUI in 12.04 LTS, as it is understood that there is a 'bug' in Modem Manager version 0.5.2 that installed in Ubuntu 12.04 by default. On modem initialization it sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode. I understand the GUI works well and has been introduced into Saucy Salamander and later versions, but Modem Manager versions 0.6 or later has not yet been made available for 12.04 LTS users which enables its SMS functions etc to work. It is hoped that an updated version of Modem Manager that addresses this and other bug fixes can be introduced into 12.04 LTS very soon for users like myself who have been looking out patiently for a couple of years for this functionality. Thanks in advance for the anticipated support... cheers! See also bug report upstream in modem manager GUI: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?15.item.3.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1340154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Branch linked: lp:ubuntu/utopic-proposed/friendly-recovery -- 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/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Committed Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: In Progress Status in “upstart” package in Ubuntu: Triaged Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (= 1.11-0ubuntu3). dbus depends on upstart (= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1228711] Re: [Dialler] Audible/haptic feedback while dialing
Linked implementation proposals for having audible feedback (DTMF tones) during dialling. ** Branch linked: lp:~piiramar/telephony-service/dial-tones ** Branch linked: lp:~piiramar/dialer-app/dial-tones -- 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/1228711 Title: [Dialler] Audible/haptic feedback while dialing Status in Dialer app for Ubuntu Touch: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: Confirmed Bug description: Touchscreen-driven devices lack the physical feedback of pressing a real button. Many other touch OSs make up for this by providing audible or haptic feedback while dialing a number. Ubuntu's dialer currently does neither. An audible tone should be played when a number is pressed, optionally haptic feedback could also be provided. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1228711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334495] Re: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts
** Branch linked: lp:~gunnarhj/ubuntu/utopic/fonts-android/droid-sans- fallback-fix ** Branch linked: lp:~gunnarhj/ubuntu/utopic/fonts-android/droid-sans- fallback-fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts Status in “fonts-android” package in Ubuntu: In Progress Status in “language-selector” package in Ubuntu: In Progress Status in “fonts-android” source package in Trusty: Triaged Status in “language-selector” source package in Trusty: Triaged Bug description: Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a italic font, others in a normal font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the normal characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of locale looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= fc-match: »DejaVuSans.ttf: DejaVu Sans Book« This is my first bug filed at launchpad. I filed it for language-selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1334495/+subscriptions -- Mailing list: https://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 1340154] Re: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode
Thanks for your help and suggestions, Graham. I hope someone is able to progress this further as mine did not work with a PAE kernel. (Yes, I noted the Lubuntu-fake-PAE option...) On 02/08/14 22:06, Graham Inggs wrote: I also have a system which I thought could not be upgraded beyond 12.04 because of a lack of PAE support, but then I recently found that many Pentium M CPUs can work with a PAE kernel, but do not advertise PAE support. To check whether this is the case for your system, simply install a PAE kernel: sudo apt-get install linux-generic-pae linux-headers-generic-pae See: https://help.ubuntu.com/community/EnablingPAE If you find your system really does not work with a PAE kernel, all is not lost, see: https://help.ubuntu.com/community/Lubuntu-fake-PAE I'm marking this bug as affecting modemmanager instead of modem-manager- gui. ** Changed in: modem-manager-gui (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1340154 Title: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode Status in “modem-manager-gui” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: Incomplete Bug description: To-date, cannot utilise Modem Manager GUI in 12.04 LTS, as it is understood that there is a 'bug' in Modem Manager version 0.5.2 that installed in Ubuntu 12.04 by default. On modem initialization it sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode. I understand the GUI works well and has been introduced into Saucy Salamander and later versions, but Modem Manager versions 0.6 or later has not yet been made available for 12.04 LTS users which enables its SMS functions etc to work. It is hoped that an updated version of Modem Manager that addresses this and other bug fixes can be introduced into 12.04 LTS very soon for users like myself who have been looking out patiently for a couple of years for this functionality. Thanks in advance for the anticipated support... cheers! See also bug report upstream in modem manager GUI: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?15.item.3.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1340154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1220013] Re: python-apt can SIGSEGV when encountering Packages stanzas with no Description field (was: update-apt-xapian-index crashed with SIGSEGV in File())
** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1220013 Title: python-apt can SIGSEGV when encountering Packages stanzas with no Description field (was: update-apt-xapian-index crashed with SIGSEGV in File()) Status in “apt” package in Ubuntu: Confirmed Status in “apt-xapian-index” package in Ubuntu: Confirmed Status in “python-apt” package in Ubuntu: Confirmed Bug description: Errors Bucket: http://errors.ubuntu.com/bug/1220013 There are 600+ reports of this on errors.ubuntu.com. Something wrong ProblemType: CrashDistroRelease: Ubuntu 13.10 Package: apt-xapian-index 0.45ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Tue Sep 3 01:23:23 2013 ExecutablePath: /usr/sbin/update-apt-xapian-index InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --quiet ProcEnviron: TERM=linux PATH=(custom, no user) SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0xb6c9e020:imul $0x3c,(%eax),%ebp PC (0xb6c9e020) ok source $0x3c ok destination (%eax) (0xd7ac1000) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11SourcePackage: apt-xapian-index StacktraceTop: ?? () from /usr/lib/python2.7/dist-packages/apt_pkg.so ?? () PyObject_GetAttr () PyEval_EvalFrameEx () ?? () Title: update-apt-xapian-index crashed with SIGSEGV in PyObject_GetAttr() UpgradeStatus: Upgraded to saucy on 2013-08-16 (17 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1220013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351914] Re: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()
*** This bug is a duplicate of bug 1351951 *** https://bugs.launchpad.net/bugs/1351951 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1351951, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1351914/+attachment/4168675/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1351914/+attachment/4168677/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1351914/+attachment/4168679/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1351914/+attachment/4168680/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1351914/+attachment/4168681/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1351914/+attachment/4168682/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1351914/+attachment/4168683/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1351951 tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1351914 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() Status in “tracker” package in Ubuntu: New Bug description: Upgraded from 14.04 to 14.10. After a boot failure, I used to purge gnome-shell and install it again it with the * option. After rebooting the system, auto-login was disabled and the error occurred after login. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: tracker 1.0.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 3 15:14:30 2014 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2014-04-18 (107 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x7fd5f4618e13 _IO_vfprintf_internal+7443: repnz scas %es:(%rdi),%al PC (0x7fd5f4618e13) ok source %es:(%rdi) (0xdc1e8ee0) not located in a known VMA region (needed readable region)! destination %al ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: tracker StacktraceTop: _IO_vfprintf_internal (s=s@entry=0x7fd5e3ffe640, format=optimized out, format@entry=0x7fd5f5947ae0 Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s'), ap=ap@entry=0x7fd5e3ffe7e8) at vfprintf.c:1642 __GI___vasprintf_chk (result_ptr=0x7fd5e3ffe798, flags=1, format=0x7fd5f5947ae0 Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s'), args=0x7fd5e3ffe7e8) at vasprintf_chk.c:66 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_new_valist () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() UpgradeStatus: Upgraded to utopic on 2014-08-03 (0 days ago) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1351914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
** Branch linked: lp:~gunnarhj/ubuntu/utopic/language-selector/droid- sans-fallback-fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: In Progress Status in “language-selector” package in Ubuntu: In Progress Status in “fonts-android” source package in Trusty: Triaged Status in “language-selector” source package in Trusty: Triaged Bug description: There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: Droid Sans Fallback Regular uming.ttc: AR PL UMing CN Light uming.ttc: AR PL UMing HK Light ukai.ttc: AR PL UKai CN Book DejaVuSans.ttf: DejaVu Sans Book Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334495] Re: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts
** Branch linked: lp:~gunnarhj/ubuntu/utopic/language-selector/droid- sans-fallback-fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts Status in “fonts-android” package in Ubuntu: In Progress Status in “language-selector” package in Ubuntu: In Progress Status in “fonts-android” source package in Trusty: Triaged Status in “language-selector” source package in Trusty: Triaged Bug description: Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a italic font, others in a normal font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the normal characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of locale looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= fc-match: »DejaVuSans.ttf: DejaVu Sans Book« This is my first bug filed at launchpad. I filed it for language-selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1334495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352289] [NEW] qt5-default makes the qdbus command fail
Public bug reported: The qt5-default package installs this symlink: lrwxrwxrwx 1 root root 50 mai 12 11:44 /usr/lib/x86_64-linux- gnu/qtchooser/default.conf - ../../../share/qtchooser/qt5-x86_64-linux- gnu.conf and when the qdbus-qt5 package is not installed, the qdbus command fails: $ qdbus qdbus: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qdbus': No such file or directory which is the cause of many problems in KDE. One way to fix this would be to have qt5-default depend on qdbus-qt5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qt5-default 5.2.1+dfsg-1ubuntu14.2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: KDE Date: Mon Aug 4 13:09:42 2014 EcryptfsInUse: Yes SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1352289 Title: qt5-default makes the qdbus command fail Status in “qtbase-opensource-src” package in Ubuntu: New Bug description: The qt5-default package installs this symlink: lrwxrwxrwx 1 root root 50 mai 12 11:44 /usr/lib/x86_64-linux- gnu/qtchooser/default.conf - ../../../share/qtchooser/qt5-x86_64 -linux-gnu.conf and when the qdbus-qt5 package is not installed, the qdbus command fails: $ qdbus qdbus: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qdbus': No such file or directory which is the cause of many problems in KDE. One way to fix this would be to have qt5-default depend on qdbus-qt5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qt5-default 5.2.1+dfsg-1ubuntu14.2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: KDE Date: Mon Aug 4 13:09:42 2014 EcryptfsInUse: Yes SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1352289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
This bug was fixed in the package friendly-recovery - 0.2.26 --- friendly-recovery (0.2.26) utopic; urgency=medium * Drop /usr/share/recovery-mode symlink and transition, this happened in oneiric already. * Move from cdbs to dh to simplify/modernize build system. * Update to copyright format 1.0. * Bump Standards-Version to 3.9.5. * lib/recovery-mode/options/dpkg: Fix ubuntu-release-upgrader mode again: Update to Python 3, and fix --datadir. * When running under systemd, call its remount-fs service for remounting r/w instead of mountall. * Add systemd unit, hooking into local-fs-pre.target. This is based on emergency.target, but watches out for recovery on the kernel command line, similar to upstart. (LP: #1351316) Add alternative systemd-sysv dependency (LP: #1351306) -- Martin Pitt martin.p...@ubuntu.com Mon, 04 Aug 2014 12:42:25 +0200 ** Changed in: friendly-recovery (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 sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: In Progress Status in “upstart” package in Ubuntu: Triaged Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (= 1.11-0ubuntu3). dbus depends on upstart (= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://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 1340154] Re: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode
Hi Marius - I'm not sure how to report this bug upstream, can you please help me out if it is still necessary? Cheers. On 04/08/14 03:05, Marius B. Kotsbak wrote: Please find or report this bug upstream first: https://bugzilla.gnome.org/browse.cgi?product=NetworkManager Or see bug #1076981 and bug #1351935 to backport a newer modem manager to 12.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1340154 Title: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode Status in “modem-manager-gui” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: Incomplete Bug description: To-date, cannot utilise Modem Manager GUI in 12.04 LTS, as it is understood that there is a 'bug' in Modem Manager version 0.5.2 that installed in Ubuntu 12.04 by default. On modem initialization it sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode. I understand the GUI works well and has been introduced into Saucy Salamander and later versions, but Modem Manager versions 0.6 or later has not yet been made available for 12.04 LTS users which enables its SMS functions etc to work. It is hoped that an updated version of Modem Manager that addresses this and other bug fixes can be introduced into 12.04 LTS very soon for users like myself who have been looking out patiently for a couple of years for this functionality. Thanks in advance for the anticipated support... cheers! See also bug report upstream in modem manager GUI: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?15.item.3.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1340154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
Ubuntu 14.04.1 + latest updates Still reproducible: after changing layout to russian shortcuts are not working. ** Summary changed: - Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 + Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1 -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “openjdk-7” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-shell” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347863] Re: syslog levels are off
** Changed in: openssh (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1347863 Title: syslog levels are off Status in “openssh” package in Ubuntu: New Bug description: On several kinds of log messages, the syslog error level is off. This is quite annoying when using the systemd journal, since journalctl formats messages according to their syslog level. See man syslog(3) for description of the syslog levels. Jul 12 19:55:25 host sshd[6507]: fatal: Write failed: Connection reset by peer [preauth] This one is currently LOG_CRIT, should probably be LOG_WARNING, since it is most likely caused by network problems on the remote side. Jul 15 12:38:54 host sshd[21025]: error: Received disconnect from remote-ip: 3: com.jcraft.jsch.JSchException: Auth fail [preauth] This one is currently LOG_ERR, should probably be LOG_NOTICE, since it is caused by specified behaviour of the remote side in the preauth phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1347863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349297] Re: Better fix for crash due to wrong objects being garbage collected
** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: Incomplete = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1349297 Title: Better fix for crash due to wrong objects being garbage collected Status in “qtdeclarative-opensource-src” package in Ubuntu: In Progress Bug description: We need to stop using debian/patches/parenttosubcreator_qqmlobjectcreator.patch that has been rejected as a valid upstream patch and use https://codereview.qt- project.org/#/c/88064/ which also fixes the issue and is upstream (will be in the 5.3.2 release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1349297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
On 2014-08-04 12:24, Iain Lane wrote: laney@iota LANG=zh_TW.UTF-8 fc-match -s sans-serif | head -5 DejaVuSans.ttf: DejaVu Sans Book DejaVuSans-Bold.ttf: DejaVu Sans Bold DejaVuSans-Oblique.ttf: DejaVu Sans Oblique DejaVuSans-BoldOblique.ttf: DejaVu Sans Bold Oblique Verdana.ttf: Verdana Normal Hmm.. That would indicate that zh_TW.UTF-8 is not generated on your system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: In Progress Status in “language-selector” package in Ubuntu: In Progress Status in “fonts-android” source package in Trusty: Triaged Status in “language-selector” source package in Trusty: Triaged Bug description: There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: Droid Sans Fallback Regular uming.ttc: AR PL UMing CN Light uming.ttc: AR PL UMing HK Light ukai.ttc: AR PL UKai CN Book DejaVuSans.ttf: DejaVu Sans Book Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351306] Re: Cannot uninstall upstart and install systemd-sysv
** Branch linked: lp:~xnox/ubuntu/utopic/upstart/core-split -- 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/1351306 Title: Cannot uninstall upstart and install systemd-sysv Status in “avahi” package in Ubuntu: Fix Released Status in “dbus” package in Ubuntu: Fix Released Status in “friendly-recovery” package in Ubuntu: Fix Released Status in “plymouth” package in Ubuntu: Fix Released Status in “sysvinit” package in Ubuntu: In Progress Status in “upstart” package in Ubuntu: Triaged Bug description: upstart is currently quite deeply wired into our dependencies. Even in a minimally bootstrapped chroot needs it, although this doesn't do any booting at all: # dpkg -P upstart dpkg: dependency problems prevent removal of upstart: initscripts depends on upstart. plymouth depends on upstart (= 1.11-0ubuntu3). On a desktop the list is quite a bit longer: ubuntu-minimal depends on upstart. avahi-daemon depends on upstart (= 0.6.7-4). friendly-recovery depends on upstart. (See bug 1351316, needs sysv/systemd script first) initscripts depends on upstart. ureadahead depends on upstart (= 0.6.0). (No need to fix -- can just drop that along with upstart for systemd images, systemd has readahead built in) plymouth depends on upstart (= 1.11-0ubuntu3). dbus depends on upstart (= 0.6.3-6). unity-services depends on upstart. init depends on upstart. (Not important right now, switch to alternative deps once systemd is ready) Most of the latter probably don't need to; versioned depends might be converted into equivalent versioned breaks, for others an alternative dependency might be considered. The main exception is that we are using session upstart on the desktop (unity-services etc.), for this we probably need to split out an upstart-sysv (for /sbin/init, reboot, halt, etc., similar to systemd-sysv) or an upstart-core (similar to sysvinit-core vs. sysvinit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1351306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352289] Re: qt5-default makes the qdbus command fail
*** This bug is a duplicate of bug 1295835 *** https://bugs.launchpad.net/bugs/1295835 ** This bug has been marked a duplicate of bug 1295835 qtchooser should have a fallback mechanism (for version AND architecture) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1352289 Title: qt5-default makes the qdbus command fail Status in “qtbase-opensource-src” package in Ubuntu: New Bug description: The qt5-default package installs this symlink: lrwxrwxrwx 1 root root 50 mai 12 11:44 /usr/lib/x86_64-linux- gnu/qtchooser/default.conf - ../../../share/qtchooser/qt5-x86_64 -linux-gnu.conf and when the qdbus-qt5 package is not installed, the qdbus command fails: $ qdbus qdbus: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qdbus': No such file or directory which is the cause of many problems in KDE. One way to fix this would be to have qt5-default depend on qdbus-qt5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qt5-default 5.2.1+dfsg-1ubuntu14.2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: KDE Date: Mon Aug 4 13:09:42 2014 EcryptfsInUse: Yes SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1352289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 71878] Re: gimp crashed to _gtk_file_system_model_get_path
** Changed in: gtk Status: New = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/71878 Title: gimp crashed to _gtk_file_system_model_get_path Status in GTK+ GUI Toolkit: Expired Status in “gtk+2.0” package in Ubuntu: Triaged Bug description: I was editing away nicely, learning keyboard shortcuts. Finished what I was doing and went to 'save as'. While I opened another app in the background (gramps) to get the right filename it just suddently said crash. (actually it was sudden - not drawn out like I've written :-) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/71878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
Aha, just saw that the locale is installed. Well, then take it as an example of the current unreliable behaviour. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: In Progress Status in “language-selector” package in Ubuntu: In Progress Status in “fonts-android” source package in Trusty: Triaged Status in “language-selector” source package in Trusty: Triaged Bug description: There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: Droid Sans Fallback Regular uming.ttc: AR PL UMing CN Light uming.ttc: AR PL UMing HK Light ukai.ttc: AR PL UKai CN Book DejaVuSans.ttf: DejaVu Sans Book Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1231729] Re: QQmlExpression: Attempted to evaluate an expression in an invalid context sometimes logged after deleting account - freezes system-settings.
** Changed in: ubuntu-system-settings-online-accounts Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1231729 Title: QQmlExpression: Attempted to evaluate an expression in an invalid context sometimes logged after deleting account - freezes system- settings. Status in Online Accounts setup for Ubuntu Touch: Fix Released Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Fix Released Bug description: I have experienced the system-settings app getting frozen after deleting accounts on and off for a while. I ignored it initially because I assumed it was due to incomplete state caused by my in-development provider plugin. However, that plugin is now finished, and I'm still seeing the freezes and now I've confirmed that it occurs with other plugins. I haven't been able to fully isolate this bug, but these steps reproduce it with some reliability (~75%): this happens as often on the desktop as on the device. 1. Successfully create two accounts using the same provider (tested with ubuntuone and twitter). (I'm not sure it has to be the same provider) 2. delete both. sometimes, the UI will freeze after deleting the first, sometimes after deleting the second. In every case where it does freeze, this error is logged just before it freezes: QQmlExpression: Attempted to evaluate an expression in an invalid context As comments, I'll post a few traces from running system-settings from the console on the desktop, with U1_DEBUG=1 loaded, which redirects QDebug() to stderr. (in case you're wondering where the output comes from). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1231729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296133] Re: Suspend and hibernate missing from KMenu and Power Management in System settings
Here is some debugging I did on my system with DBus (as found in various bug reports, wiki, forums, ...): $ qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanSuspend yes $ qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend true does suspend my system, but does not lock the screen. $ qdbus org.freedesktop.PowerManagement /org/freedesktop/PowerManagement org.freedesktop.PowerManagement.CanSuspend false $ qdbus org.freedesktop.PowerManagement /org/freedesktop/PowerManagement org.freedesktop.PowerManagement.Suspend does lock the screen but does not suspend. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1296133 Title: Suspend and hibernate missing from KMenu and Power Management in System settings Status in “upower” package in Ubuntu: Confirmed Bug description: I have used install scripts to install Kubuntu 14.04 on three completely different systems. Although the packages installed are basically the same, one of the system has no Suspend/hibernate options in the KMenu nor in the Power management in the KDE System settings. Since this is a laptop, this also means that the battery life is greatly reduced, because it cannot go to standby when lid is closed or when it's idle. Interestingly, If I logout, there is a Standby button on the lighdm login screen. If I click it, the laptop goes to standby and wakes up without problems. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Sat Mar 22 21:18:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-14 (8 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Alpha amd64 (20140130) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1296133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333627] Re: update broke fonts in firefox
This is after the update of many packages. It should not look like this. ** Attachment added: Bug after installing updates https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1333627/+attachment/4169446/+files/1%20fonts%20got%20messed%20up%20cut.png -- 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/1333627 Title: update broke fonts in firefox Status in “fontconfig” package in Ubuntu: Incomplete Bug description: I have Ubuntu Studio 14.04. The updates window popped up and asked me to install updates. Which I did. This somehow broke my font configuration. So that I have blurry fonts in firefox. No other application is affected. I have modified nothing in /etc/fonts/conf.avail. If updates changes the contents of /etc/fonts/conf.d I do not see the purpose of having a conf.avail/conf.d - organization. The purpose must be to let users link or unlink files in conf.d to files in conf.avail. I don't expect updates to create links in /etc/fonts/conf.d that were previously created at installation time or upgrate time. So if I unlink something in /etc/fonts/conf.d I expect it to stay that way. Changes to the files themselves should go in /etc/fonts/conf.avail. Changes to which files are available by default in /etc/fonts/conf.d should be applied only when they are CHANGES. Not reinstall the default links with every update. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 ~$ apt-cache policy fontconfig fontconfig: Installed: 2.11.0-0ubuntu4.1 Candidate: 2.11.0-0ubuntu4.1 Version table: *** 2.11.0-0ubuntu4.1 0 500 http://no.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.11.0-0ubuntu4 0 500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1333627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333627] Re: update broke fonts in firefox
I already resolved this issue by deleting the links, as described above. I downgraded to 2.11.0-0ubuntu4, and nothing wrong happened. Then I upgraded, and still nothing wrong happened. So there must have been another package update that caused this. I don't know what other package would mess around in /etc/fonts/conf.d. I will attach the pictures of before and after. ** Attachment added: This is how it is supposed to look https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1333627/+attachment/4169444/+files/1%20fonts%20before%20problem%2C%20and%20after%20fix%20cut.png -- 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/1333627 Title: update broke fonts in firefox Status in “fontconfig” package in Ubuntu: Incomplete Bug description: I have Ubuntu Studio 14.04. The updates window popped up and asked me to install updates. Which I did. This somehow broke my font configuration. So that I have blurry fonts in firefox. No other application is affected. I have modified nothing in /etc/fonts/conf.avail. If updates changes the contents of /etc/fonts/conf.d I do not see the purpose of having a conf.avail/conf.d - organization. The purpose must be to let users link or unlink files in conf.d to files in conf.avail. I don't expect updates to create links in /etc/fonts/conf.d that were previously created at installation time or upgrate time. So if I unlink something in /etc/fonts/conf.d I expect it to stay that way. Changes to the files themselves should go in /etc/fonts/conf.avail. Changes to which files are available by default in /etc/fonts/conf.d should be applied only when they are CHANGES. Not reinstall the default links with every update. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 ~$ apt-cache policy fontconfig fontconfig: Installed: 2.11.0-0ubuntu4.1 Candidate: 2.11.0-0ubuntu4.1 Version table: *** 2.11.0-0ubuntu4.1 0 500 http://no.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.11.0-0ubuntu4 0 500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1333627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
