[Touch-packages] [Bug 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly
Reducing the the time to 30s if it doesn’t kill properly would be a good idea. I have reported a bug with the developer of linconnect as well. https://github.com/hauckwill/linconnect-server/issues -- 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/1457400 Title: reduce 90s session kill timeout if the session does not shutdown cleanly Status in systemd package in Ubuntu: Confirmed Bug description: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1010909] Re: permission denied: /usr/bin/{mktexpk, mktextfm}
I have reproduced the failures on generating fonts with evince on a dvi
file and apparmor 2.8.95~2430-0ubuntu5.1 and can confirm that apparmor
2.8.95~2430-0ubuntu5.2 addresses the issue. Marking verification-done.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1010909
Title:
permission denied: /usr/bin/{mktexpk,mktextfm}
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
[impact]
This bug prevents viewing dvi files with evince while confined by
apparmor.
[steps to reproduce]
1) install evince, ensure evince apparmor policy is enabled
2) view a dvi with evince
3) with the fix applied, evince should be able to display the dvi
document and should not generate apparmor rejections in syslog
[regression potential]
The change in the patch for this bug is a loosening of the apparmor
policy for the sanitized helpers of evince. The risk of an introduced
regression is small.
[original description]
1) lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
2) apt-cache policy evince apparmor texlive
evince:
Installed: 3.14.1-0ubuntu1
Candidate: 3.14.1-0ubuntu1
Version table:
*** 3.14.1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
apparmor:
Installed: 2.8.98-0ubuntu4
Candidate: 2.8.98-0ubuntu4
Version table:
*** 2.8.98-0ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
texlive:
Installed: 2014.20141024-1ubuntu1
Candidate: 2014.20141024-1ubuntu1
Version table:
*** 2014.20141024-1ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
3) What is expected to happen is when one attempts to open
https://bugs.launchpad.net/ubuntu/+source/texlive-
bin/+bug/1010909/+attachment/4282336/+files/example.dvi it does so
successfully.
4) What happens instead is it hangs indefinitely, as per output of running
evince via a terminal
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1010909/+attachment/4282345/+files/error.txt
. This would appear to be due to apparmor as per:
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1010909/+attachment/4282344/+files/kern.log
However, attempting to disable the offending profile fails:
sudo aa-complain /usr/bin/evince//sanitized_helper
/usr/bin/evince//sanitized_helper does not exist, please double-check the
path.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: texlive-binaries 2009-11ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Sat Jun 9 17:05:03 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/zsh
SourcePackage: texlive-bin
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1010909/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453703] Re: Gnome Shell
Hi Christopher, it doesn't look like I have that option. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1453703 Title: Gnome Shell Status in xorg package in Ubuntu: Incomplete Bug description: Windows in Gnome shell turn invisible. e.g. when opening Terminator and maximizing it, it turns invisible. It shows up when going to Activities. I have to use a shortcut to restore it to see it again. When maximizing SublimeText, there's tearing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: GNOME Date: Mon May 11 09:53:28 2015 DistUpgraded: 2014-06-17 09:13:14,256 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.11.0-18-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox, 4.3.10, 3.13.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2002] InstallationDate: Installed on 2014-02-18 (446 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-06-17 (328 days ago) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67BL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10189-211 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1222.1415:bd12/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-211:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon May 11 08:19:04 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 8 inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 9 inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22653 vendor GSM xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1453703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 193325] Re: "unknown media type" during update
Also I'm pretty sure the bug lies in the package shared-mime-info. It certainly isn't limited to Nautilus alone since I use Kubuntu and the bug shows up there: Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/193325 Title: "unknown media type" during update Status in Nautilus: Confirmed Status in shared MIME database: Fix Released Status in shared-mime-info package in Ubuntu: Fix Released Bug description: Messages below seen during the latest round of updates. The messages from several packages seem to be mixed around, so I'm not sure which one triggered them. I suspect nautilus. Setting up shared-mime-info (0.23-3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ucf (3.004-0ubuntu3) ... Setting up seahorse (2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ubuntu-gdm-themes (0.24) ... Setting up linux-restricted-modules-common (2.6.24.9-8.25) ... Setting up nautilus-data (1:2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up compiz-core (1:0.7.0-0ubuntu3) ... To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/193325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 193325] Re: "unknown media type" during update
Why is this bug still unfixed? It's appeared in every version of Ubuntu I've used since at least 8.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/193325 Title: "unknown media type" during update Status in Nautilus: Confirmed Status in shared MIME database: Fix Released Status in shared-mime-info package in Ubuntu: Fix Released Bug description: Messages below seen during the latest round of updates. The messages from several packages seem to be mixed around, so I'm not sure which one triggered them. I suspect nautilus. Setting up shared-mime-info (0.23-3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ucf (3.004-0ubuntu3) ... Setting up seahorse (2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up ubuntu-gdm-themes (0.24) ... Setting up linux-restricted-modules-common (2.6.24.9-8.25) ... Setting up nautilus-data (1:2.21.91-0ubuntu3) ... Unknown media type in type 'x-content/video-vcd' Unknown media type in type 'x-content/video-svcd' Unknown media type in type 'x-content/video-dvd' Unknown media type in type 'x-content/image-dcf' Unknown media type in type 'x-content/audio-cdda' Unknown media type in type 'x-content/blank-cd' Unknown media type in type 'x-content/blank-dvd' Unknown media type in type 'x-content/blank-bd' Unknown media type in type 'x-content/blank-hddvd' Unknown media type in type 'x-content/audio-dvd' Unknown media type in type 'x-content/video-bluray' Unknown media type in type 'x-content/video-hddvd' Unknown media type in type 'x-content/image-picturecd' Unknown media type in type 'x-content/audio-player' Unknown media type in type 'x-content/software' Setting up compiz-core (1:0.7.0-0ubuntu3) ... To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/193325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457400] Re: linconnect_server.py hangs on shut down
This probably got introduced with the fix for bug 1448259. So, this general behaviour is "correct" in the sense that processes should not be killed immediately after SIGTERMing them. But 90s is a bit much for session shutdowns, this could be reduced to something like 30 s. This is still a long session shutdown, but you really wan this if e. g. LibreOffice asks you about unsaved documents and the like. I don't know what the timeout under upstart was, but apparently it was a lot smaller. ** Summary changed: - linconnect_server.py hangs on shut down + reduce 90s session kill timeout if the session does not shutdown cleanly ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1457400 Title: reduce 90s session kill timeout if the session does not shutdown cleanly Status in systemd package in Ubuntu: Confirmed Bug description: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457754] [NEW] "E: Method http has died unexpectedly" when run under lxc on wily apt 1.0.9.9ubuntu1
Public bug reported: lxc-create -t download -n wily-gui -- -d ubuntu -r wily -a amd64 + some config according to https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in- containers/ + enabling network. --- root@wily-gui:/home/ubuntu# apt update E: Method http has died unexpectedly! E: Sub-process http received a segmentation fault. --- Downgrading apt to https://launchpad.net/ubuntu/+source/apt/1.0.9.7ubuntu4 in the LXC rootfs seems to fix the issue. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Description changed: + lxc-create -t download -n wily-gui -- -d ubuntu -r wily -a amd64 + some + config according to https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in- + containers/ + enabling network. + --- root@wily-gui:/home/ubuntu# apt update E: Method http has died unexpectedly! E: Sub-process http received a segmentation fault. --- Downgrading apt to https://launchpad.net/ubuntu/+source/apt/1.0.9.7ubuntu4 in the LXC rootfs seems to fix the issue. -- 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/1457754 Title: "E: Method http has died unexpectedly" when run under lxc on wily apt 1.0.9.9ubuntu1 Status in apt package in Ubuntu: New Bug description: lxc-create -t download -n wily-gui -- -d ubuntu -r wily -a amd64 + some config according to https://www.stgraber.org/2014/02/09/lxc-1-0 -gui-in-containers/ + enabling network. --- root@wily-gui:/home/ubuntu# apt update E: Method http has died unexpectedly! E: Sub-process http received a segmentation fault. --- Downgrading apt to https://launchpad.net/ubuntu/+source/apt/1.0.9.7ubuntu4 in the LXC rootfs seems to fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1457754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed
I've checked the test with staging, and I get warnings for 0.1, 1.0, 1.1
and 1.2 imports. So seems staging has some fix which makes the warning
to be printed everywhere but 1.3.
About the logs, staging (and I think overlay PPA will get it soon) has
more info on where the problem relies. I am getting the following log:
"test.qml:5:5: QML Button: Theme.createStyleComponent() is deprecated.
Use ThemeSettings instead."
Theme is a context property. Context properties and Singletons are
impossible to know from which QML file are invoked. So we cannot really
display any meaningful information on where the component is used. We
cannot know whether the functionality is called from a toolkit component
or from an application or custom component based on toolkit. As seen
above, the staging which is also planned to be released, has more
information on Theme.createStyleComponent(), but that is the only one
can give valuable information. Theme.palette or Theme.name will not know
the caller context, and will not be able to specify from what document
it is addressed.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1457528
Title:
Theme.createStyleComponent deprecation useless warnings are displayed
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
Take that example
"import QtQuick 2.0
import Ubuntu.Components 0.1
Item {
Button {
text: "click"
}
}"
run it on wily, you get those warnings
"QML Button: Theme.createStyleComponent() is deprecated. Use
ThemeSettings instead."
the warning is not helpful, it warns about a standard component issue
(so something in the responsability of the uitk team, not the code
writer), lists the issue on something you are not using (what is
"Theme.createStyleComponent()" that's not used in the code example?),
it's just confusing...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457528/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457400] Re: linconnect_server.py hangs on shut down
I ran the command . johny@johny-laptop:~$ pkill -fe linconnect_server.py python2 killed (pid 2469) But its not actually getting killed. If I go to system monitor and see, the process is still there. If I kill the process by right clicking it System monitor and pressing kill. The process gets killed. And when I try to shut-down after that its back to normal. If you could see this, I installed it like this. http://www.webupd8.org/2014/01/get-android-notifications-on-your.html There was no exception and it works nicely. I have been using it for very long, its not something that I installed recently. Its been working fine for long. But this problem only started recently only. -- 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/1457400 Title: linconnect_server.py hangs on shut down Status in systemd package in Ubuntu: Incomplete Bug description: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434986] Re: Not working network connection after boot
I`ve tested Wily and the problem persist, my motherboard is http://www.gigabyte.com/products/product-page.aspx?pid=5189#sp lspci: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Please help me, this problem maybe affect a lot of people, is very annoying :´O( I’m just a poor latinoamerican boy. -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457400] Re: linconnect_server.py hangs on shut down
What happens at shutdown is that all processes are sent SIGTERM, so that they have a chance to intercept, save their state/clean up, etc. After a timeout (default 90s) SIGKILL is sent. So it seems linconnect_server.py does not actually shut down on SIGTERM? I tried to download and install it, but the install.sh crashed in pip with Exception: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in main status = self.run(options, args) File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 304, in run requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, bundle=self.bundle) File "/usr/lib/python2.7/dist-packages/pip/req.py", line 1178, in prepare_files url = finder.find_requirement(req_to_install, upgrade=self.upgrade) File "/usr/lib/python2.7/dist-packages/pip/index.py", line 292, in find_requirement elif is_prerelease(version) and not (self.allow_all_prereleases or req.prereleases): File "/usr/lib/python2.7/dist-packages/pip/util.py", line 739, in is_prerelease return any([any([y in set(["a", "b", "c", "rc", "dev"]) for y in x]) for x in parsed]) TypeError: 'int' object is not iterable Can you try "pkill -fe linconnect_server.py" in a running session and see if linconnect_server continues to run after that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1457400 Title: linconnect_server.py hangs on shut down Status in systemd package in Ubuntu: Incomplete Bug description: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319829] Re: aa-genprof will crash when select scan on Ubuntu 14.04 server
I have reproduced the traceback when profiling empathy with apparmor 2.8.95~2430-0ubuntu5.1 from trusty-updates, and can confirm that apparmor 2.8.95~2430-0ubuntu5.2 from trusty-proposed fixes the problem. Marking verification-done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1319829 Title: aa-genprof will crash when select scan on Ubuntu 14.04 server Status in AppArmor Linux application security framework: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Trusty: Confirmed Bug description: [impact] This bug makes it difficult for trusty users to use the apparmor policy utilities. [steps to reproduce] See below [regression potential] This issue is being addressed by updating the python utilities to the version in apparmor 2.9.2 as tracked in bug 1449769. This represents are large change which would normally be risky; however, these changes are isolated to the python utils (so no changes to the policy parser/loader or enforcement), there are a large number of bugs that exist in the trusty version that make using the tools difficult, so it would be difficult to regress further, and the updated version includes many new unit tests to try to prevent from regressions from occurring. [additional info] The python utils testsuite is run as part of the test-apparmor.py test script in lp:qa-regression-testing. The test-apparmor.py also has additional basic usage tests to ensure that basic functionality is maintained. These tests are run as part of the process fro each kernel update. [original description] Operating system : Ubuntu 14.04 LTS x86_64 server Command used : sudo aa-genprof suricata I will be asked to scan or finish, I selected "scan". Then it crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1319829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1294797] Re: aa-genprof traceback with apparmor 2.8.95
I have reproduced the traceback when profiling empathy with apparmor
2.8.95~2430-0ubuntu5.1 from trusty-updates, and can confirm that
apparmor 2.8.95~2430-0ubuntu5.2 from trusty-proposed fixes the problem.
Marking verification-done.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1294797
Title:
aa-genprof traceback with apparmor 2.8.95
Status in AppArmor Linux application security framework:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
Confirmed
Bug description:
[impact]
This bug makes it difficult for trusty users to use the apparmor
policy utilities.
[steps to reproduce]
See below
[regression potential]
This issue is being addressed by updating the python utilities to the
version in apparmor 2.9.2 as tracked in bug 1449769. This represents
are large change which would normally be risky; however, these changes
are isolated to the python utils (so no changes to the policy
parser/loader or enforcement), there are a large number of bugs that
exist in the trusty version that make using the tools difficult, so it
would be difficult to regress further, and the updated version
includes many new unit tests to try to prevent from regressions from
occurring.
[additional info]
The python utils testsuite is run as part of the test-apparmor.py test
script in lp:qa-regression-testing. The test-apparmor.py also has
additional basic usage tests to ensure that basic functionality is
maintained. These tests are run as part of the process fro each kernel
update.
[original description]
In a terminal, I run:
$ sudo aa-genprof /usr/bin/empathy
...
[(S)can system log for AppArmor events] / (F)inish
At this point, I start empathy, then stop it.
Now I go back to the terminal:
Reading log entries from /var/log/syslog.
Updating AppArmor profiles in /etc/apparmor.d.
Traceback (most recent call last):
File "/usr/sbin/aa-genprof", line 150, in
lp_ret = apparmor.do_logprof_pass(logmark, passno)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2240, in
do_logprof_pass
read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2558, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2584, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2689, in
parse_profile_data
filelist[file]['profiles'][profile][hat] = True
TypeError: 'bool' object does not support item assignment
If I run it again, I get a different traceback:
Traceback (most recent call last):
File "/usr/sbin/aa-genprof", line 150, in
lp_ret = apparmor.do_logprof_pass(logmark, passno)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2240, in
do_logprof_pass
read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2558, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2584, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3031, in
parse_profile_data
raise AppArmorException(_('Syntax Error: Unknown line found in file: %s
line: %s') % (file, lineno + 1))
apparmor.common.AppArmorException: 'Syntax Error: Unknown line found in file:
/etc/apparmor.d/zz-unconfined line: 3'
/etc/apparmor.d/zz-unconfined contains:
# v2 compatible wildly permissive profile
profile "zz_unconfined" {
capability,
network,
/** rwlkm,
/** pix,
# TODO: when dbus hits:
dbus,
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1294797/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319829] Re: aa-genprof will crash when select scan on Ubuntu 14.04 server
Bah, my apologies, posted to the wrong bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1319829 Title: aa-genprof will crash when select scan on Ubuntu 14.04 server Status in AppArmor Linux application security framework: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Trusty: Confirmed Bug description: [impact] This bug makes it difficult for trusty users to use the apparmor policy utilities. [steps to reproduce] See below [regression potential] This issue is being addressed by updating the python utilities to the version in apparmor 2.9.2 as tracked in bug 1449769. This represents are large change which would normally be risky; however, these changes are isolated to the python utils (so no changes to the policy parser/loader or enforcement), there are a large number of bugs that exist in the trusty version that make using the tools difficult, so it would be difficult to regress further, and the updated version includes many new unit tests to try to prevent from regressions from occurring. [additional info] The python utils testsuite is run as part of the test-apparmor.py test script in lp:qa-regression-testing. The test-apparmor.py also has additional basic usage tests to ensure that basic functionality is maintained. These tests are run as part of the process fro each kernel update. [original description] Operating system : Ubuntu 14.04 LTS x86_64 server Command used : sudo aa-genprof suricata I will be asked to scan or finish, I selected "scan". Then it crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1319829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457400] Re: linconnect_server.py hangs on shut down
** Summary changed: - Ubuntu taking long to shutdown + linconnect_server.py hangs on shut down -- 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/1457400 Title: linconnect_server.py hangs on shut down Status in systemd package in Ubuntu: Incomplete Bug description: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399129] Re: A system icon of iBus is not displayed in Kubuntu Plasma 5
As for this problem, solution was carried out on the iBus side: https://code.google.com/p/ibus/issues/detail?id=1749 but the problem that a system icon is not displayed is continued while iBus is installed when I installed Kubuntu 15.04 in Japanese. Therefore I report this comment and maintain current status. The live boot of Kubuntu 15.04 displays a status icon of iBus. Therefore a problem unlike Kubuntu 14.10 Plasma 5 may occur. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1399129 Title: A system icon of iBus is not displayed in Kubuntu Plasma 5 Status in IBus: Unknown Status in ibus package in Ubuntu: Triaged Bug description: In Kubuntu 14.10 Plasma 5, a system icon of iBus is not displayed. I installed Kubuntu 14.10 Plasma 5 in Japanese (日本語). Because iBus-Anthy is installed then, I change it to Anthy in Super+Space and can perform Japanese input again. but systray does not have an icon, and a big problem occurs in operability. This problem is one of the side effects of systray of Plasma 5 having changed the specifications: https://community.kde.org/Plasma/5.0_Errata http://blog.martin-graesslin.com/blog/2014/03/system-tray-in-plasma-next/ As for this problem, bug report is performed in iBus: https://code.google.com/p/ibus/issues/detail?id=1749 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1399129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399129] Re: A system icon of iBus is not displayed in Kubuntu Plasma 5
** Attachment added: "kubuntu1504japanese.png" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1399129/+attachment/4402184/+files/kubuntu1504japanese.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1399129 Title: A system icon of iBus is not displayed in Kubuntu Plasma 5 Status in IBus: Unknown Status in ibus package in Ubuntu: Triaged Bug description: In Kubuntu 14.10 Plasma 5, a system icon of iBus is not displayed. I installed Kubuntu 14.10 Plasma 5 in Japanese (日本語). Because iBus-Anthy is installed then, I change it to Anthy in Super+Space and can perform Japanese input again. but systray does not have an icon, and a big problem occurs in operability. This problem is one of the side effects of systray of Plasma 5 having changed the specifications: https://community.kde.org/Plasma/5.0_Errata http://blog.martin-graesslin.com/blog/2014/03/system-tray-in-plasma-next/ As for this problem, bug report is performed in iBus: https://code.google.com/p/ibus/issues/detail?id=1749 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1399129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448636] Re: Suspend/resume failure misspells "occurred"
This bug was fixed in the package apport - 2.17.3-0ubuntu1 --- apport (2.17.3-0ubuntu1) wily; urgency=medium * New upstream release: - SECURITY UPDATE: When /proc/sys/fs/suid_dumpable is enabled, crashing a program that is suid root or not readable for the user would create root-owned core files in the current directory of that program. Creating specially crafted core files in /etc/logrotate.d or similar could then lead to arbitrary code execution with root privileges. Now core files do not get written for these kinds of programs, in accordance with the intention of core(5). Thanks to Sander Bos for discovering this issue! (CVE-2015-1324, LP: #1452239) - SECURITY UPDATE: When writing a core dump file for a crashed packaged program, don't close and reopen the .crash report file but just rewind and re-read it. This prevents the user from modifying the .crash report file while "apport" is running to inject data and creating crafted core dump files. In conjunction with the above vulnerability of writing core dump files to arbitrary directories this could be exploited to gain root privileges. Thanks to Philip Pettersson for discovering this issue! (CVE-2015-1325, LP: #1453900) - apportcheckresume: Fix "occured" typo, thanks Matthew Paul Thomas. (LP: #1448636) - signal_crashes test: Fix test_crash_setuid_* to look at whether suid_dumpable was enabled. - test/run: Run UI tests under dbus-launch, newer GTK versions require this now. -- Martin Pitt Wed, 20 May 2015 16:58:35 +0200 ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-1324 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-1325 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1448636 Title: Suspend/resume failure misspells "occurred" Status in apport package in Ubuntu: Fix Released Bug description: apport 2.14.1-0ubuntu3.8, Ubuntu 14.04 1. Trigger a KernelOops (for example, by following the steps for bug 1298792 if it isn't fixed yet). 2. Choose "Show Details". 3. Expand the "Annotation" section. What you see: "This occured..." What you should see: "This occurred..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1448636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452239] Re: root escalation with fs.suid_dumpable=2
This bug was fixed in the package apport - 2.17.3-0ubuntu1 --- apport (2.17.3-0ubuntu1) wily; urgency=medium * New upstream release: - SECURITY UPDATE: When /proc/sys/fs/suid_dumpable is enabled, crashing a program that is suid root or not readable for the user would create root-owned core files in the current directory of that program. Creating specially crafted core files in /etc/logrotate.d or similar could then lead to arbitrary code execution with root privileges. Now core files do not get written for these kinds of programs, in accordance with the intention of core(5). Thanks to Sander Bos for discovering this issue! (CVE-2015-1324, LP: #1452239) - SECURITY UPDATE: When writing a core dump file for a crashed packaged program, don't close and reopen the .crash report file but just rewind and re-read it. This prevents the user from modifying the .crash report file while "apport" is running to inject data and creating crafted core dump files. In conjunction with the above vulnerability of writing core dump files to arbitrary directories this could be exploited to gain root privileges. Thanks to Philip Pettersson for discovering this issue! (CVE-2015-1325, LP: #1453900) - apportcheckresume: Fix "occured" typo, thanks Matthew Paul Thomas. (LP: #1448636) - signal_crashes test: Fix test_crash_setuid_* to look at whether suid_dumpable was enabled. - test/run: Run UI tests under dbus-launch, newer GTK versions require this now. -- Martin Pitt Wed, 20 May 2015 16:58:35 +0200 ** Changed in: apport (Ubuntu Wily) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1452239 Title: root escalation with fs.suid_dumpable=2 Status in Apport crash detection/reporting: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Precise: Fix Released Status in apport source package in Trusty: Fix Released Status in apport source package in Utopic: Fix Released Status in apport source package in Vivid: Fix Released Status in apport source package in Wily: Fix Released Bug description: Sander Bos discovered that Apport enabled a user to perform a root escalation since it now configures fs.suid_dumpable=2. Here's a brief description of the issue: 1- A regular user can trigger a coredump with /proc/$PID/stat as root:root simply by doing chmod u-r 2- The root-owned coredump will them be written in the CWD, which in the PoC is /etc/logrotate.d 3- logrotate will gladly skip parts of the coredump it doesn't understand and will successfully run the parts it does I've set a CRD of 2015-05-21 (original proposal: 2015-05-12) for the publication of this issue. I have assigned CVE-2015-1324 to this issue. We can either: 1- Disable fs.suid_dumpable=2 2- Stop creating core dump files when they are to be created as root 3- Create root-owned core dump files in a well-known location To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1452239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457730] [NEW] Upstart packaging conflicts with man Xsession
Public bug reported:
Ubuntu 14.04, upstart 1.12.1-0ubuntu4.2.
man Xsession:
"Xsession may optionally be passed a single argument indicating the type of X
session to be started."
"default produces the same behavior as if no session type argument had been
given at all."
In /etc/X11/Xsession.d/20x11-common_process-args and in
/etc/X11/Xsession.d/50x11-common_determine-startup, Xsession processes its
command line, the user settings, and the Debian alternatives system and sets
STARTUP which after that is the correct program to run.
I.e. the program to run is decided at the "50" number.
As an example of correct behaviour, gnome-session-common in
/etc/X11/Xsession.d/55gnome-session_gnomerc processes $STARTUP in
55gnome-session_gnomerc.
Unfortunately /etc/X11/Xsession.d/00upstart doesn't care for $STARTUP
only works if "$1" points to an Exec= line of an xsession.desktop file.
This does work with e.g. lightdm, but it breaks in a lot of other cases,
notably in LTSP where LDM passes "" as the default case when the user
didn't select anything at all from the session selection combo box.
This used to work in 12.04 and it's now broken in 14.04. I haven't
checked non LTS releases.
The fix consists of two parts:
1) To rename /etc/X11/Xsession.d/00upstart to /etc/X11/Xsession.d/55upstart, so
that $STARTUP is set. This doesn't cause any issues with the variables that
00upstart sets inside it, they're only accessed after the "50" number which is
where $STARTUP is determined.
2) Inside 55upstart, to change
BASESESSION=${1% *}
to
BASESESSION=${STARTUP%% *}
That's all, but if you do want more common code with 55gnome-session_gnomerc,
you can copy the code from there, it does the same thing even if it calls it
BASESTARTUP instead of BASESESSION.
Thanks,
Alkis
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1457730
Title:
Upstart packaging conflicts with man Xsession
Status in upstart package in Ubuntu:
New
Bug description:
Ubuntu 14.04, upstart 1.12.1-0ubuntu4.2.
man Xsession:
"Xsession may optionally be passed a single argument indicating the type of
X session to be started."
"default produces the same behavior as if no session type argument had been
given at all."
In /etc/X11/Xsession.d/20x11-common_process-args and in
/etc/X11/Xsession.d/50x11-common_determine-startup, Xsession processes its
command line, the user settings, and the Debian alternatives system and sets
STARTUP which after that is the correct program to run.
I.e. the program to run is decided at the "50" number.
As an example of correct behaviour, gnome-session-common in
/etc/X11/Xsession.d/55gnome-session_gnomerc processes $STARTUP in
55gnome-session_gnomerc.
Unfortunately /etc/X11/Xsession.d/00upstart doesn't care for $STARTUP
only works if "$1" points to an Exec= line of an xsession.desktop
file. This does work with e.g. lightdm, but it breaks in a lot of
other cases, notably in LTSP where LDM passes "" as the default case
when the user didn't select anything at all from the session selection
combo box.
This used to work in 12.04 and it's now broken in 14.04. I haven't
checked non LTS releases.
The fix consists of two parts:
1) To rename /etc/X11/Xsession.d/00upstart to /etc/X11/Xsession.d/55upstart,
so that $STARTUP is set. This doesn't cause any issues with the variables that
00upstart sets inside it, they're only accessed after the "50" number which is
where $STARTUP is determined.
2) Inside 55upstart, to change
BASESESSION=${1% *}
to
BASESESSION=${STARTUP%% *}
That's all, but if you do want more common code with 55gnome-session_gnomerc,
you can copy the code from there, it does the same thing even if it calls it
BASESTARTUP instead of BASESESSION.
Thanks,
Alkis
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1457730/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1027410] Re: Crash when opening a WMV file
[Expired for libav (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libav (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1027410 Title: Crash when opening a WMV file Status in libav package in Ubuntu: Expired Status in vlc package in Ubuntu: Invalid Bug description: There is a WMV file I am trying to play but VLC crashes when I open it : VLC media player 2.0.1 Twoflower (revision 2.0.1-0-gf432547) [0x9cbd908] main libvlc: Lancement de vlc avec l'interface par défaut. Utilisez « cvlc » pour démarrer VLC sans interface. [vc1 @ 0xb5304200] Bits overconsumption: 102040 > 102032 [vc1 @ 0xb5304200] concealing 837 DC, 837 AC, 837 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 22776 > 22768 [vc1 @ 0xb5304200] concealing 980 DC, 980 AC, 980 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 74392 > 74384 [vc1 @ 0xb5304200] concealing 366 DC, 366 AC, 366 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 39104 > 39096 at 38x19 [vc1 @ 0xb5304200] concealing 369 DC, 369 AC, 369 MV errors [0xb5100618] main input error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 300 ms) [0xb5100618] main input error: ES_OUT_RESET_PCR called [wmav2 @ 0xb5322a20] prev_block_len_bits 6 out of range [wmav2 @ 0xb5322a20] next_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] block_len_bits 6 out of range [vc1 @ 0xb5304200] Bits overconsumption: 94824 > 94816 [vc1 @ 0xb5304200] concealing 1004 DC, 1004 AC, 1004 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 69064 > 69056 [vc1 @ 0xb5304200] concealing 630 DC, 630 AC, 630 MV errors [wmav2 @ 0xb5322a20] prev_block_len_bits 6 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] frame_len overflow [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] overflow in spectral RLE, ignoring [wmav2 @ 0xb5322a20] next_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] next_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 5 out of range [wmav2 @ 0xb5322a20] next_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] block_len_bits 5 out of range [wmav2 @ 0xb5322a20] block_len_bits 6 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 6 out of range [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range [wmav2 @ 0xb5322a20] block_len_bits 4 out of range [wmav2 @ 0xb5322a20] next_block_len_bits 4 out of range [vc1 @ 0xb5304200] Bits overconsumption: 80344 > 80336 [vc1 @ 0xb5304200] concealing 411 DC, 411 AC, 411 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 61368 > 61360 [vc1 @ 0xb5304200] concealing 753 DC, 753 AC, 753 MV errors [vc1 @ 0xb5304200] Bits overconsumption: 53624 > 53616 at 0x22 [vc1 @ 0xb5304200] concealing 229 DC, 229 AC, 229 MV errors Erreur de segmentation (core dumped) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: vlc 2.0.1-4 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 Date: Sat Jul 21 16:00:32 2012 ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to precise on 2012-04-27 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1027410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433382] Re: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Static, crackling sounds using module-loopback
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1433382 Title: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Static, crackling sounds using module-loopback Status in alsa-driver package in Ubuntu: Expired Bug description: I recently hooked up a SB X-Fi Surrount 5.1 Pro external sound card to my computer. It has a Line-In port which I wanted to use for playing audio from another computer. I enabled the loopback module like so: pactl load-module module-loopback And although I could then hear sound from Line-In, it was distorted by static, crackling sounds. I took the advice I found here: https://wiki.ubuntu.com/Audio/PositionReporting Making this change to /etc/pulse/default.pa: load-module module-udev-detect tsched=0 After rebooting and again loading the loopback module, the playback was static-free. As instructed by the above webpage, I'm filing this bug to track the issue and suggested solution. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66 Uname: Linux 3.2.0-77-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfa62 irq 95' Mixer name : 'Realtek ALC898' Components : 'HDA:10ec0899,104384d8,0013' Controls : 47 Simple ctrls : 23 Card1.Amixer.info: Card hw:1 'Pro'/'Creative Technology Ltd SB X-Fi Surround 5.1 Pro at usb-:00:1d.0-1.3, high ' Mixer name : 'USB Mixer' Components : 'USB041e:3237' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 36' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Tue Mar 17 21:02:47 2015 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro successful Symptom_Card: GF114 HDMI Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - SB X-Fi Surround 5.1 Pro, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd04/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1433382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445572] Re: [Right edge] Apps closing shouldn't be possible during the edge gesture
Sorry, but I don't understand what do you mean "the whole spread animation breaks" exactly, Do you mean the size or position of the spread item changed suddenly when vertically swipe starting the horizontal swipe? Or the spread just disappeared suddenly? -- 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/1445572 Title: [Right edge] Apps closing shouldn't be possible during the edge gesture Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: Steps to repro: - Open few apps - start right edge gesture - during the gesture (while moving towards left and still holding finger down) interact with the spread items with another finger. For example try to swipe up or down to close. Result: - sometimes you can swipe an app to close it. sometimes the whole spread animation breaks. Expected result: - The spread items can't be interacted with during the edge gesture. The items should be interactive only after user has finished the gesture by releasing the finger. --- Desired design: Expected result To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1445572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background
I'm encountering this regularly as well on Ubuntu 14.04.02 with Rhythmbox 3.0.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/978604 Title: Banshee/Rhythmbox regularly stop playing audio when left on in the background Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio source package in Precise: Confirmed Bug description: If Banshee or Rhythmbox is left playing in the background they will randomly stop playing in the latest builds of Ubuntu 12.04. Starting a new piece of music usually fixes the problem. If left to its own devices, the music will start playing again at some random time, at some random position. This problem exists on both my desktop machine (custom built Intel machine) and my laptop (Macbook 5,1). It has been happening for several months now. I became frustrated enough to load up pulseaudio in debugging mode. The log shows that when the music player just finishes playing one piece, and tries to start the next piece, you see something like this: --- ( 335.399| 34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to corking ( 335.400| 0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 bytes. ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes. ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: before: 3705 ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: after: 3705 ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes. ( 335.400| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 335.400| 0.000) D: [alsa-sink] sink.c: latency = 1643 ( 335.400| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes on render memblockq. ( 335.400| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes on implementor. ( 335.400| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 335.400| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds. ( 335.402| 0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0: 34% 1: 34% ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 dB 1: -28.11 dB ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0: 34% 1: 34% ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: in dB: 0: -28.00 dB 1: -28.00 dB ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 0: 100% 1: 100% (accurate-enough=yes) ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: in dB: 0: -0.11 dB 1: -0.11 dB ( 335.402| 0.000) D: [alsa-sink] sink.c: Volume not changing ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 bytes. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes. ( 335.402| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: before: 3825 ( 335.402| 0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to vacuum. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: after: 3825 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes. ( 335.402| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 335.402| 0.000) D: [alsa-sink] sink.c: latency = 1402 ( 335.402| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 335.402| 0.000) I: [pulseaudio] sink-input.c: Freeing input 3 "'zero-project - 05 - Forest of the unicorns' by 'zero-project'" ( 335.402| 0.000) D: [pulseaudio] module-stream-restore.c: Not restoring device for stream sink-input-by-media-role:music, because already set to 'alsa_output.pci-_00_1b.0.analog-stereo'. ( 335.403| 0.000) D: [pulseaudio] module-intended-roles.c: Not setting device for stream Playback Stream, because already set. ( 335.403| 0.000) I: [pulseaudio] module-stream-restore.c: Restoring volume for sink input sink-input-by-media-role:music. ( 335.403| 0.000) I: [pulseaudio] module-stream-restore.c: Restoring mute state for sink input sink-input-by-media-role:music. ( 335.403| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes busy. ( 335.403| 0.000) I: [pulseaudio] resampler.c: Forcing resampler 'copy', because of fixed, identical sample rates. ( 335.403| 0.000) I: [pulseaudio] resampler.c: Using resampler 'copy' ( 335.403| 0.000) I: [pulseaudio] resampler.c: Using float32le as working format. ( 335.403| 0.000) D: [pulseaudio] memblockq.c: memblockq requested: maxlength=33554432, tlength=0, base=4, prebuf=0, m
[Touch-packages] [Bug 1457564] Re: Boot hangs before graphic login
Removing "quiet" and "splash" results in the kubuntu logo and the "starting version 219" message not showing up, boot messages instead but just a black screen in the end. I could not make much of the syslog, see attached. There are no errors in Xorg.0.log, BTW. I ran the "systemctl start sddm" from tty2, logged in as my user. Just retried from a rescue shell: "Error getting authority: Error initializing authority: [...] (g-io-error-quark, 1)". /etc/X11/default- display-manager has "/usr/bin/sddm". ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457564/+attachment/4402139/+files/syslog -- 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/1457564 Title: Boot hangs before graphic login Status in systemd package in Ubuntu: Incomplete Bug description: Please note: there are obviously several different causes for this error. Other reports on launchpad and elsewhere identified sddm, systemd, nvidia drivers and grub config. Since none of the solutions mentioned there helped in my case, I am deliberately leaving the information on the source package open. I have upgraded to Kubuntu Vivid 15.04 shortly after the final release and used that without issues until two days ago when I ran updates (apt log attached). Ran »sudo systemctl enable sddm.service -f«, then reboot: no change. Changed the GRUB_CMDLINE_LINUX_DEFAULT option in /etc/default/grub to include »nomodeset«: no change. Other variations of this line did not help, either. I do not have nvidia or nouveau driver packages installed. I am aware that 219 is the current systemd version, so I tried the upstart option in grub. Hangs, too (though with different error message). »systemctl start sddm« asks for password, the returns »authentication complete« (in all-caps); nothing else happens. Re-installing linux-generic or kubuntu-desktop had no effect. What can I do to at least identify the cause of this issue? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."
I also get 'File descriptor 50 (/dev/pts/6) leaked on vgs invocation. Parent PID 14069: /usr/sbin/grub-probe ' whenever apt-get updates grub's configuration file... which is several times when you're removing multiple old kernels... I would've thought this would be fixed by now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/591823 Title: "File descriptor \d+ (\S+) leaked on lvs invocation." Status in aptitude: Confirmed Status in lvm2 - Logical Volume Manager: Fix Released Status in lvm2 package in Ubuntu: Opinion Bug description: If you see messages like these: File descriptor 40 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 41 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 42 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 43 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh You can set LVM_SUPPRESS_FD_WARNINGS to suppress these warnings. Reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581339 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432986 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466138 This is a slightly controversial bug and it's not yet fixed either way (aka fix not to leak file descriptors or stop warning by default) To manage notifications about this bug go to: https://bugs.launchpad.net/aptitude/+bug/591823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457698] Re: Aggregator can't subsearch the same child twice to get different depts
Discussed this with Chris. Problem is real. Basically, the Nearby Scope fires more than one query at a particular child, but with different department, or potentially different query string and/or filter settings. Doing this is quite legit. The loop detection is too stringent right now because it axes off any query that loops around, regardless of whether the query details are the same or not. We need to change the loop detection to take all of the query state into account. That way, queries that differ in some detail will still be forwarded to children, but queries that loop around unchanged and therefore indicate a real accidental loop are still axed. ** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Critical ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) => Michi Henning (michihenning) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1457698 Title: Aggregator can't subsearch the same child twice to get different depts Status in unity-scopes-api package in Ubuntu: New Bug description: As of the latest vivid images, NearBy can no longer subsearch children several times, which is used for example to search the coffee dept, as well as the bars dept for the I'm Thirsty section of nearby. The query string is blank in both instances, with only the dept of the child scope changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1457698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457698] [NEW] Aggregator can't subsearch the same child twice to get different depts
Public bug reported: As of the latest vivid images, NearBy can no longer subsearch children several times, which is used for example to search the coffee dept, as well as the bars dept for the I'm Thirsty section of nearby. The query string is blank in both instances, with only the dept of the child scope changing ** Affects: unity-scopes-api (Ubuntu) Importance: Critical Assignee: Michi Henning (michihenning) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1457698 Title: Aggregator can't subsearch the same child twice to get different depts Status in unity-scopes-api package in Ubuntu: New Bug description: As of the latest vivid images, NearBy can no longer subsearch children several times, which is used for example to search the coffee dept, as well as the bars dept for the I'm Thirsty section of nearby. The query string is blank in both instances, with only the dept of the child scope changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1457698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 886478] Re: New Alt + tab switcher doesn't follow system font
Hello Lê, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/886478 Title: New Alt + tab switcher doesn't follow system font Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Users who switch the system font and then use Alt+Tab will see a jarring effect when the Ubuntu font is displayed. This can also lead to not fully supported language issues. [ Test Case ] 1. Switch the system font to something else besides Ubuntu. 2. Use Alt+Tab. 3. Observe any fonts displayed in Alt+Tab follow the system font. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff -- Original Description: In my laptop, I have to change from default ubuntu font to droid font because the default one doesn't fully support vietnamese. Let it sit there will make the overall system feel awkward. And now, while the whole system is in droid, only the switcher is still using the ubuntu font. Plz make the switcher follow the system font or at least, make a way to configure its appearance. -- Desired solution: - Alt+tab switcher should use the system font - This change should result in ZERO change to the appearance of the font in Alt+Tab on a fresh installation of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/886478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313597] Re: Shortcut overlay cannot be closed by clicking the close button in 14.04
Hello Po-Hsu, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1313597 Title: Shortcut overlay cannot be closed by clicking the close button in 14.04 Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Due to an input handling race, the first time users log into Unity on their system, the shortcut overlay may not close when clicking the "X" in the corner. This leads to a poor user experience. [ Test Case ] 1. Remove ~/.config/unity/first_run.stamp. 2. Log into Unity. 3. Shortcut hints overlay should be shown. 4. Click on "X" in the corner. [ Regression Potential ] This is a workaround for a race, so some users may never see the race to begin with. That said, no regression should be observed as in worse case, the shortcut hints still cannot be closed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff --- Original Description: In 14.04, the shortcut overlay would pop-out automatically on first boot. Although there is a close button on the top-left corner, it cannot be closed by clicking it. (it could be dismissed by the super key, or open a new window) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 926979] Re: compiz crashed with SIGSEGV in nux::Property::operator=(bool const&) from unity::dash::DashView::AnalyseLensURI(std::string const&) from unity::dash::DashView::
Hello Joel, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/926979 Title: compiz crashed with SIGSEGV in nux::Property::operator=(bool const&) from unity::dash::DashView::AnalyseLensURI(std::string const&) from unity::dash::DashView::OnActivateRequest(_GVariant*) Status in Unity: Fix Committed Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: Won't Fix Status in Unity 7.0 series: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Certain cases when clicking on Dash items may cause a crash. [ Test Case ] It's not entirely clear how the crash is triggered, but no crash should be observed when clicking on Dash entries. [ Regression Potential ] The change is small and no regressions should be observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Clicked dash, Internet applications. Opened a new bug as the others appear to suggest a fix is released for those bugs. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.0.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4 Uname: Linux 3.2.0-3-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Sun Feb 5 14:51:39 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7eff5ff51d10 <_ZN3nux8PropertyIbEaSERKb+32>: mov 0x18(%rdi),%rdi PC (0x7eff5ff51d10) ok source "0x18(%rdi)" (0x03f0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: nux::Property::operator=(bool const&) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::AnalyseLensURI(std::string const&) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::OnActivateRequest(_GVariant*) () from /usr/lib/compiz/libunityshell.so unity::UBusManager::OnCallback(_GVariant*, void*) () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in nux::Property::operator=() UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo usrp video To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/926979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1246891] Re: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher
Hello Marco, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1246891 Title: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Users the use Launcher keynav mode may end up with a Launcher that is not displayed correctly, leaving a poor user experience. [ Test Case ] 1. Make sure there are enough icons in the Launcher to cause the Launcher to fold. 2. Press Alt+F1 3. Press right-key 4. Press left-key 5. Observe the Launcher is not folder while still in keynav mode. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: 1) Press Alt+F1 2) Press right-key 3) Press left-key Expected result: 3) The launcher goes back to keynav mode and unfolds completely. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1246891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 932486] Re: showing quicklist from launcher keynav mode focuses last application
Hello Thomi, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/932486 Title: showing quicklist from launcher keynav mode focuses last application Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Poor user experience due to the app window not being focused as expected. [ Test Case ] 0. Have at least one application window open 1. Enter launcher keynav mode with Alt+F1 2. Select a launcher icon with the Up or Down keys. 3. Show the quicklist by pressing Right. 4. Collapse the quicklist by pressing Left. 5. Observe that the app window never has focus during the above steps. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff Original Description: To reproduce: 0) Have at least one application window open 1) Enter launcher keynav mode with Alt+F1 * Note that when entering keynav mode, the application loses focus. THe triangle to the right of it's launcher icon is no longer drawn, and the window title is not displayed in the panel. 2) Select a launcher icon with the Up or Down keys. 3) Show the quicklist by pressing Right. * Note that the application becomes active again - it's window title is drawn to the panel, and the triangle to the right of the launcher icon is drawn again. 4) Collapse the quicklist by pressing Left. * The app loses focus again. This seems like inconsistent behavior to me... either the app should never lose focus when we enter keynav mode, or should not be activated when we show a quicklist. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/932486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308265] Re: First password letter not registered in lockscreen if screen off
Hello Michał, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1308265 Title: First password letter not registered in lockscreen if screen off Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Not having the first character registered when trying to unlock the lockscreen can most definitely lead to frustration and thus, poor user experience. [ Test Case ] 1. Lock the screen and let the monitor blank as well. 2. Try unlocking the screen by typing your password. 3. Observe lockscreen unlocks. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: With the new lockscreen, if my screen is off, I just start typing, every time my password is too short. It looks like the first key only triggers the screen on and does not go to the input field. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140414.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 23:59:08 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1029114] Re: With autohide and the HUD enabled the launcher can appear at incorrect times
Hello Andrew, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1029114 Title: With autohide and the HUD enabled the launcher can appear at incorrect times Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] When the Launcher is suddenly revealed when it's not intended to can cause confusion and a poor user experience. [ Test Case ] 1. Turn on launcher auto hide 2. Display the HUD (tap Alt) 3. Move the mouse to the left side of the screen (as if you are showing the launcher) 4. Note the launcher is not displayed 5. Now hide the HUD (either tap Alt or select the X in the top left corner) 6. Observe the Launcher is not revealed. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Hi What Happened: 1) Turn on launcher auto hide 2) Display the HUD (tap Alt) 3) Move the mouse to the left side of the screen (as if you are showing the launcher) 4) Note the launcher is not displayed 5) Now hide the HUD (either tap Alt or select the X in the top left corner) 6) Note that the launcher is now displayed, after the HUD closes. What I expected to happen: - I expected that the launcher is not displayed at step 6. I expected for the launcher to not be displayed at step 6 because the user could have the HUD displayed for a long period of time then decide that they don't need the HUD. The launcher is then suddenly revealed to them as they moved their cursor to the left side of the screen a few minutes a ago. This could then confuse the user to why the launcher has appeared when all they did was close the HUD. Hope this can be fixed soon. Andy ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12.0-0ubuntu3~webapps7 [origin: LP-PPA-webapps-preview] ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,compiztoolbox,snap,resize,move,grid,imgpng,mousepoll,place,unitymtgrabhandles,wall,gnomecompat,session,regex,resizeinfo,animation,expo,fade,scale,ezoom,workarounds,unityshell] CrashDB: unity Date: Wed Jul 25 21:19:17 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.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/unity/+bug/1029114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436095] Re: AP test failure: unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
Hello Stephen, or anyone else affected,
Accepted unity into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: unity (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
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/1436095
Title:
AP test failure:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
Status in Unity:
Fix Committed
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Status in unity source package in Trusty:
Fix Committed
Bug description:
[ Impact ]
Failed Autopilot tests are not good.
[ Test Case ]
1. Run 'autopilot run
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click'
2. Run 'autopilot run
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click'
3. Observe that the tests don't fail.
[ Regression Potential ]
None observed.
Debdiff of the SRU is found here:
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff
-
Original Description:
The following two AP tests consistently ERROR during regular Unity
testing.
==
ERROR:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
--
Empty attachments:
/var/log/syslog
unity-log: {{{WARN 2015-03-24 13:43:02 nux.inputmethod.ibus
InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
128, in test_scaled_window_closes_on_middle_click
self.assertWindowIsScaledEquals(target_xid, False)
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
68, in assertWindowIsScaledEquals
self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 421, in
assertThat
mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 471, in
_matchHelper
mismatch = matcher.match(matchee)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py",
line 113, in match
wait_fun(self.matcher, self.timeout)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py",
line 129, in _callable_wait_for
new_value = refresh_fn()
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
67, in
refresh_fn = lambda: xid in [w.xid for w in
self.unity.screen.scaled_windows]
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 520, in __getattr__
self.refresh_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 474, in refresh_state
_, new_state = self.get_new_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 564, in get_new_state
raise StateNotFoundError(self.__class__.__name__, id=self.id)
StateNotFoundError: Object not found with name 'Window' and properties {'id':
148832}.
==
ERROR:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click
--
Empty attachments:
/var/log/syslog
unity-log: {{{WARN 2015-03-24 14:00:34 nux.inputmethod.ibus
InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
148, in test_scaled_window_closes_on_close_button_click
s
[Touch-packages] [Bug 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
Hello Francesco, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.5+14.04.20150521.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] Users of the on-screen keyboard cannot properly use the Dash and the on-screen keyboard at the same time. [ Test Case ] 1. Install and start the on-screen keyboard Onboard. 2. Open the Dash. 3. Ensure you can interact with Onboard as you would expect. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes
Try running "apport-collect 1457101" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1457101 Title: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes Status in Ubuntu One Infrastructure: New Status in powerd package in Ubuntu: Confirmed Bug description: After two last updates (I remember second one was also a kernel update) my Ubuntu has started sudden crashing, either desktop view freezes, sometimes sound which was played goes to fast circuit. Sometimes it crashes to full terminal screen, reporting kernel panic mode. I'm sorry I dont know how to find these crash reports from my Ubuntu, hope you can advice me. After crash, only thing possible is to reset my laptop manually. Ubuntu has also started to inform internal failure with powerd, and asks to report them to developers. I think I have send that report three times now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319829] Re: aa-genprof will crash when select scan on Ubuntu 14.04 server
I have reproduced the traceback with apparmor 2.8.95~2430-0ubuntu5.1 from trusty-updates, and can confirm that apparmor 2.8.95~2430-0ubuntu5.2 from trusty-proposed fixes the problem. Marking verification-done. ** Tags added: aa-tools verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1319829 Title: aa-genprof will crash when select scan on Ubuntu 14.04 server Status in AppArmor Linux application security framework: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Trusty: Confirmed Bug description: [impact] This bug makes it difficult for trusty users to use the apparmor policy utilities. [steps to reproduce] See below [regression potential] This issue is being addressed by updating the python utilities to the version in apparmor 2.9.2 as tracked in bug 1449769. This represents are large change which would normally be risky; however, these changes are isolated to the python utils (so no changes to the policy parser/loader or enforcement), there are a large number of bugs that exist in the trusty version that make using the tools difficult, so it would be difficult to regress further, and the updated version includes many new unit tests to try to prevent from regressions from occurring. [additional info] The python utils testsuite is run as part of the test-apparmor.py test script in lp:qa-regression-testing. The test-apparmor.py also has additional basic usage tests to ensure that basic functionality is maintained. These tests are run as part of the process fro each kernel update. [original description] Operating system : Ubuntu 14.04 LTS x86_64 server Command used : sudo aa-genprof suricata I will be asked to scan or finish, I selected "scan". Then it crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1319829/+subscriptions -- Mailing list: https://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 1454444] Re: Storage view does not count correctly space used by app
That makes sense and I have no preference where it should be implemented. If there is better home for this bug, we should move it there. I assigned this bug to Settings app since there it's visible, so it was good starting point :) If we create new bug please add it here, so we can track it for krillin. On Tue, May 19, 2015 at 9:14 AM, Sebastien Bacher wrote: > @Ondrej, well, my point is that libclick could provide a function that > does that, it would be a better place because other codebase might have > to get the same information and a common function in the framework used > would make more sense that local implementation in every software > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/145 > > Title: > Storage view does not count correctly space used by app > > Status in the base for Ubuntu mobile products: > New > Status in click package in Ubuntu: > New > Status in ubuntu-system-settings package in Ubuntu: > Incomplete > > Bug description: > When going to Settings->About phone -> Storage > Storage used per app count does not include space used by app in > ~/.local// > This makes is hard to determine which app is actually eating all the > storage. > It also makes whole list kinda pointless, since we can have easily app > easting 1G or more and never see it in the lis. > Apps like podcast, browser, twitter can easily eat hundreds of MB > without being spotted in the list. > > Expected result: > space occupied by all is calculated from the size of application itself, > plus data used by application under ~/.local// > > tested on RTM krillin (stable/bq-aquaris.en/krillin) v22 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/canonical-devices-system-image/+bug/145/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/145 Title: Storage view does not count correctly space used by app Status in the base for Ubuntu mobile products: New Status in click package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: When going to Settings->About phone -> Storage Storage used per app count does not include space used by app in ~/.local// This makes is hard to determine which app is actually eating all the storage. It also makes whole list kinda pointless, since we can have easily app easting 1G or more and never see it in the lis. Apps like podcast, browser, twitter can easily eat hundreds of MB without being spotted in the list. Expected result: space occupied by all is calculated from the size of application itself, plus data used by application under ~/.local// tested on RTM krillin (stable/bq-aquaris.en/krillin) v22 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443178] Re: Accounts Service always relies on language fallback if never set by the user
This bug was fixed in the package accountsservice - 0.6.35-0ubuntu7.2
---
accountsservice (0.6.35-0ubuntu7.2) trusty-proposed; urgency=medium
* debian/patches/0010-set-language.patch:
Use static variables inside user_get_fallback_value() to prevent
execution of expensive code at each invocation (LP: #1443178).
-- Gunnar Hjalmarsson Tue, 12 May 2015 18:30:00
+0200
** Changed in: accountsservice (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
Fix Released
Status in accountsservice source package in Trusty:
Fix Released
Status in accountsservice source package in Vivid:
Fix Released
Bug description:
trusty and vivid SRU requests
=
[Impact]
Until a user has set the language or regional formats explicitly,
accountsservice makes the system default values available. The code
for 'calculating' the system defaults is expensive, and it's triggered
frequently. The case in the original description of this bug report is
one example of bad performance for this reason. Another example is a
system with many users (see e.g. bug #1350393).
This upload adds a couple of static variables inside the function in
question, to avoid that the expensive code is executed at each
invocation. Under certain conditions this improves the performance
significantly.
[Test Case]
Hmm.. There is no easy use case to reproduce the bug. The original
description below gives a hint.
[Regression Potential]
On a multi-user system, if the system defaults in /etc/default/locale
are changed, accountsservice will keep providing the old system
default values until the system is rebooted. (Previously it took
effect instantly.) I think the advantages with the proposed change
outweigh this subtle change in behavior (which hardly anyone will
notice anyway).
Can't think of anything besides that.
[Original description]
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else
g_value_set_string (value, user_get_fallback_value
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_string (value, user->formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, "FormatsLocale"));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while
for accountsservice to reply back to indicator-sound when the sync
happens, possibly causing sync aborts (as indicator-sound only waits 1
second before triggering ano
[Touch-packages] [Bug 1456579] Re: ubuntu-bug segfaults, Kubuntu 15.04 (100% reproducible - multiple machines)
** Changed in: apport (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1456579 Title: ubuntu-bug segfaults, Kubuntu 15.04 (100% reproducible - multiple machines) Status in apport package in Ubuntu: Confirmed Bug description: On multiple machines ubuntu-bug segfaults if I choose the following options 'other problem' -> 'other display-related problem' It immediately 100% of the time segfaults i.e [325594.232720] apport-kde[14031]: segfault at 38 ip 7f38386f10c3 sp 7ffdf8a0ae80 error 4 in libQt5Core.so.5.4.1[7f383866b000+533000] However if I choose 'other problem' -> 'I don't know' it does create bug report. Another user in IRC confirmed it was happening to them also. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 19 12:06:40 2015 InstallationDate: Installed on 2015-04-28 (21 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1456579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443178] Re: Accounts Service always relies on language fallback if never set by the user
This bug was fixed in the package accountsservice - 0.6.37-1ubuntu10.1
---
accountsservice (0.6.37-1ubuntu10.1) vivid-proposed; urgency=medium
* debian/patches/0010-set-language.patch:
Use static variables inside user_get_fallback_value() to prevent
execution of expensive code at each invocation (LP: #1443178).
-- Gunnar Hjalmarsson Tue, 12 May 2015 17:44:00
+0200
** Changed in: accountsservice (Ubuntu Vivid)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
Fix Released
Status in accountsservice source package in Trusty:
Fix Committed
Status in accountsservice source package in Vivid:
Fix Released
Bug description:
trusty and vivid SRU requests
=
[Impact]
Until a user has set the language or regional formats explicitly,
accountsservice makes the system default values available. The code
for 'calculating' the system defaults is expensive, and it's triggered
frequently. The case in the original description of this bug report is
one example of bad performance for this reason. Another example is a
system with many users (see e.g. bug #1350393).
This upload adds a couple of static variables inside the function in
question, to avoid that the expensive code is executed at each
invocation. Under certain conditions this improves the performance
significantly.
[Test Case]
Hmm.. There is no easy use case to reproduce the bug. The original
description below gives a hint.
[Regression Potential]
On a multi-user system, if the system defaults in /etc/default/locale
are changed, accountsservice will keep providing the old system
default values until the system is rebooted. (Previously it took
effect instantly.) I think the advantages with the proposed change
outweigh this subtle change in behavior (which hardly anyone will
notice anyway).
Can't think of anything besides that.
[Original description]
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else
g_value_set_string (value, user_get_fallback_value
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_string (value, user->formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, "FormatsLocale"));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while
for accountsservice to reply back to indicator-sound when the sync
happens, possibly causing sync aborts (as indicator-sound only waits 1
second before triggering an
[Touch-packages] [Bug 1362188] Re: Introducing favorites made it impossible to only load one scope in scope-tool
This works fine nowadays ** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => Fix Released ** Changed in: unity8 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1362188 Title: Introducing favorites made it impossible to only load one scope in scope-tool Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: With the introduction of favorites in the most recent scope plugin, it's currently impossible to run the scope tool with just one scope: ⟫ unity-scope-tool /usr/lib/x86_64-linux-gnu/unity-scopes/clickstore/com.canonical.scopes.clickstore.ini /usr/lib/x86_64-linux-gnu/unity-scopes/scopes/scopes.ini scoperegistry: unity::ResourceException: cannot open scope installation directory "/custom/lib/x86_64-linux-gnu/unity-scopes": No such file or directory scoperegistry: could not open OEM installation directory, ignoring OEM scopes warning: ignoring unknown key PageHeader.background in group Appearance in file /usr/lib/x86_64-linux-gnu/unity-scopes/scopes/scopes.ini scoperegistry: no remote registry configured, only local scopes will be available ScopesWatcher::add_install_dir(): install dir watch: unity::ResourceException: DirWatcher::add_watch(): failed to add watch for path: "/custom/lib/x86_64-linux-gnu/unity-scopes". inotify_add_watch() failed. (fd = 14, path = /custom/lib/x86_64-linux-gnu/unity-scopes) file:///usr/share/unity8/ScopeTool.qml:139:23: Unable to assign null to QString No such scope: "clickscope" No such scope: "videoaggregator" No such scope: "mediascanner-music" ⟫ unity-scope-tool /usr/lib/x86_64-linux-gnu/unity-scopes/clickstore/com.canonical.scopes.clickstore.ini scoperegistry: unity::ResourceException: cannot open scope installation directory "/custom/lib/x86_64-linux-gnu/unity-scopes": No such file or directory scoperegistry: could not open OEM installation directory, ignoring OEM scopes scoperegistry: no remote registry configured, only local scopes will be available ScopesWatcher::add_install_dir(): install dir watch: unity::ResourceException: DirWatcher::add_watch(): failed to add watch for path: "/custom/lib/x86_64-linux-gnu/unity-scopes". inotify_add_watch() failed. (fd = 14, path = /custom/lib/x86_64-linux-gnu/unity-scopes) file:///usr/share/unity8/ScopeTool.qml:139:23: Unable to assign null to QString Unable to add overview scope, can't find with ID: "scopes" No such scope: "clickscope" No such scope: "videoaggregator" No such scope: "mediascanner-music" The scopes scope should be added to the registry regardless of options passed on the console, and the scopes passed on the console should be used as the favorite set instead of the gsetting. If no options passed, we displayed all available scopes before... not sure if that's possible now? ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-plugin-scopes 0.5.4+14.10.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 27 15:42:54 2014 SourcePackage: unity-scopes-shell SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: '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-scopes-shell/+bug/1362188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443178] Update Released
The verification of the Stable Release Update for accountsservice has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
Fix Released
Status in accountsservice source package in Trusty:
Fix Committed
Status in accountsservice source package in Vivid:
Fix Released
Bug description:
trusty and vivid SRU requests
=
[Impact]
Until a user has set the language or regional formats explicitly,
accountsservice makes the system default values available. The code
for 'calculating' the system defaults is expensive, and it's triggered
frequently. The case in the original description of this bug report is
one example of bad performance for this reason. Another example is a
system with many users (see e.g. bug #1350393).
This upload adds a couple of static variables inside the function in
question, to avoid that the expensive code is executed at each
invocation. Under certain conditions this improves the performance
significantly.
[Test Case]
Hmm.. There is no easy use case to reproduce the bug. The original
description below gives a hint.
[Regression Potential]
On a multi-user system, if the system defaults in /etc/default/locale
are changed, accountsservice will keep providing the old system
default values until the system is rebooted. (Previously it took
effect instantly.) I think the advantages with the proposed change
outweigh this subtle change in behavior (which hardly anyone will
notice anyway).
Can't think of anything besides that.
[Original description]
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else
g_value_set_string (value, user_get_fallback_value
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_string (value, user->formats_locale);
else
g_value_set_string (value, user_get_fallback_value
(user, "FormatsLocale"));
break;
user_set_property never gets called unless the user changes the system
language from system-settings or wizard.
Once you change the language, it will set a valid language at
/var/lib/AccountsService/users/, causing this behavior to stop.
Another bad side effect of this issue is that it takes quite a while
for accountsservice to reply back to indicator-sound when the sync
happens, possibly causing sync aborts (as indicator-sound only waits 1
second before triggering another sync).
[Touch-packages] [Bug 1439220] Re: No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring
** Changed in: ubuntu-gnome-default-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1439220 Title: No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu- settings.gschema.override'; ignoring override for this key. Status in ubuntu-gnome-default-settings package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: Get that error now when installing a package (synaptic install dialog box) Unpacking nautilus (1:3.14.2-0ubuntu8) over (1:3.14.2-0ubuntu6) ... Processing triggers for libglib2.0-0:i386 (2.44.0-1) ... No such key 'external-editor' in schema 'org.gnome.eog.ui' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. note: i have installed the 3.16 version of gsettings-desktop-schemas (gnome3-staging ppa), so maybe it is related to. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libglib2.0-0 2.44.0-1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Wed Apr 1 16:06:11 2015 SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1439220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355363] Re: Can't open scope preview in search
You can't search on the bottom swipe anymore ** Changed in: unity8 (Ubuntu) Status: Triaged => 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/1355363 Title: Can't open scope preview in search Status in unity8 package in Ubuntu: Invalid Bug description: With overview, steps to reproduce: - bottom swipe to dash overview - search for "video" - long-press on any scope in "Recommendations" category Expected: - preview opens Current: - nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1355363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450642] Update Released
The verification of the Stable Release Update for libseccomp has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls Status in Snappy Ubuntu: Fix Committed Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Vivid: Fix Released Status in libseccomp source package in Wily: Fix Released Bug description: [Impact] Several syscalls were discovered to be missing when using the launcher on snappy. These should be added so we may properly support seccomp filtering. [Test Case] seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log. Eg: Regression Test Summary tests run: 6494 tests skipped: 52 tests passed: 6494 tests failed: 0 tests errored: 0 Furthermore, on a snappy system, perform: $ sudo snappy install hello-world $ hello-world.env It should show the environment. On an arm system with 2.1.1-1 from the archive, this will fail due to a seccomp denial: audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 compat=0 ip=0xb6fb0bd6 code=0x0 (note, snappy images have a ppa fix for this, see notes below). To test the segfault fix, do: $ scmp_sys_resolver 1024 Segmentation fault It should return: $ scmp_sys_resolver 1024 UNKNOWN For the new 3.19 syscalls: $ scmp_sys_resolver getrandom -1 it should return something like (actual number depends on arch, this is on armhf): $ scmp_sys_resolver getrandom 384 autopkgtests for libseccomp have been added as part of this update to verify that the library recognizes all the syscalls from 3.19 and the private syscalls. These tests can be run like so (assuming you are in the unpacked source and the binaries are in ../binary): $ export REL=vivid $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED" Alternatively, if you don't have autopkgtest setup, you can do: $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter ... PASS $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-scmp_sys_resolver ... PASS Lastly, seccomp is used by lxc. lxc can be tested by using the test case as outlined in step 4 of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only. [Regression Potential] If the above tests, regression potential is considered low. Unknown syscalls will continue to be handled as before. Description of changes: add finit_module: https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15 sync the syscall table entries - 3.16 https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75 https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4 https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718 https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a sync the syscall table entries - 3.17 https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9 sync the syscall table entries - 3.19 https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3 This should also be applied (fix a segfault for invalid syscall numbers): https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3 In addition, add-missing-arm-private-syscalls.patch is add to add 5 private ARM syscalls. These are absolutely required on snappy. This portion of the patch has been well tested and is included by default in stable snappy images via the snappy image PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1450642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://la
[Touch-packages] [Bug 1445134] Re: Network manager never scanning for new access points
** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- 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/1445134 Title: Network manager never scanning for new access points Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Bug description: While trying to reproduce another bug related with the last seen value from the access points, I noticed that network manager is never really scanning for new access points on my desktop, not even when not connected. $ sudo nmcli g logging level debug domains wifi_scan Then powered an access point, but was never really able to see it. From syslog, noticed that there is never really a scan, which explains why the ap never goes away and why it is not able to find it in the first place. If I force a scan via cmdline it works as expected (and I noticed a scan also happens when changing connections). Was also able to reproduce this issue on mako, with the following image: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 173 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-16 14:58:58 version version: 173 version ubuntu: 20150416 version device: 20150210 version custom: 20150416 In the mako case, I booted with a known connection in place, it connected successfully but it never really scans for other access points. Scan works fine after disconnecting though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 14:21:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-29 (534 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev lxcbr0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410190] Re: /usr/bin/ubuntu-location-serviced:*** Error in `/usr/bin/ubuntu-location-serviced': malloc(): memory corruption (fast): ADDR ***
** Changed in: location-service (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1410190 Title: /usr/bin/ubuntu-location-serviced:*** Error in `/usr/bin/ubuntu- location-serviced': malloc(): memory corruption (fast): ADDR *** Status in location-service package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding location-service. This problem was most recently seen with version 2.1+15.04.20150106~rtm-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/284a0959d15e8ca7d2d39ec2dbb85d403132b356 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1410190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450642] Re: seccomp missing many new syscalls
This bug was fixed in the package libseccomp - 2.1.1-1ubuntu1~vivid2 --- libseccomp (2.1.1-1ubuntu1~vivid2) vivid-proposed; urgency=medium * add-finit-module.patch: add finit_module syscalls to x86 and x86-64 syscall tables * update syscalls for modern kernels (skipping MIPS) - update syscalls for 3.16: + update-x86-syscall-table.patch + update-x86_64-syscall-table.patch + update-arm-syscall-table.patch + update-x32-syscall-table.patch + sync-syscall-table-entries.patch + sync-syscall-table-entries-fixtypo.patch - update syscalls for 3.17: + sync-syscall-table-entries-3.17.patch - update syscalls for 3.19: + sync-syscall-table-entries-3.19.patch - LP: #1450642 * fix-segfault-with-unknown.patch: fix segfault when find unknown syscall * debian/patches/add-missing-arm-private-syscalls.path: add missing private ARM syscalls * add autopkgtests for scmp_sys_resolver and filter testing and SYS_getrandom() testing -- Jamie Strandboge Fri, 08 May 2015 17:10:14 -0400 ** Changed in: libseccomp (Ubuntu Vivid) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls Status in Snappy Ubuntu: Fix Committed Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Vivid: Fix Released Status in libseccomp source package in Wily: Fix Released Bug description: [Impact] Several syscalls were discovered to be missing when using the launcher on snappy. These should be added so we may properly support seccomp filtering. [Test Case] seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log. Eg: Regression Test Summary tests run: 6494 tests skipped: 52 tests passed: 6494 tests failed: 0 tests errored: 0 Furthermore, on a snappy system, perform: $ sudo snappy install hello-world $ hello-world.env It should show the environment. On an arm system with 2.1.1-1 from the archive, this will fail due to a seccomp denial: audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 compat=0 ip=0xb6fb0bd6 code=0x0 (note, snappy images have a ppa fix for this, see notes below). To test the segfault fix, do: $ scmp_sys_resolver 1024 Segmentation fault It should return: $ scmp_sys_resolver 1024 UNKNOWN For the new 3.19 syscalls: $ scmp_sys_resolver getrandom -1 it should return something like (actual number depends on arch, this is on armhf): $ scmp_sys_resolver getrandom 384 autopkgtests for libseccomp have been added as part of this update to verify that the library recognizes all the syscalls from 3.19 and the private syscalls. These tests can be run like so (assuming you are in the unpacked source and the binaries are in ../binary): $ export REL=vivid $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED" Alternatively, if you don't have autopkgtest setup, you can do: $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter ... PASS $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-scmp_sys_resolver ... PASS Lastly, seccomp is used by lxc. lxc can be tested by using the test case as outlined in step 4 of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only. [Regression Potential] If the above tests, regression potential is considered low. Unknown syscalls will continue to be handled as before. Description of changes: add finit_module: https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15 sync the syscall table entries - 3.16 https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75 https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4 https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718 https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a sync the syscall table entries - 3.17 https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9 sync the syscall table entries - 3.19 https://github.com/seccomp/libseccomp/commit/7b80fb2fb683ca
[Touch-packages] [Bug 1455097] Re: pm-suspend.log and pm-powersave.log not updated since upgrade to vivid
** Changed in: pm-utils (Ubuntu) Importance: Undecided => Medium -- 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/1455097 Title: pm-suspend.log and pm-powersave.log not updated since upgrade to vivid Status in pm-utils package in Ubuntu: Confirmed Bug description: I added a new script in /etc/pm/sleep.d/ that worked fine before the upgrade to vivid. I was wondering why it doesn't work and I find out that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last logs from pm-suspend were on Apr 28, when I upgraded from utopic to vivid. The laptop suspends and wakes fine, it just seems that no pm scripts are run after suspend/powersave. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 15:36:26 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-12 (792 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 PackageArchitecture: all 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/1455097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448259] Re: Systemd does not send SIGTERM first on shutdown
** Changed in: systemd (Debian) Status: Fix Committed => 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/1448259 Title: Systemd does not send SIGTERM first on shutdown Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Released Status in systemd package in Debian: Fix Released Status in systemd package in Fedora: Unknown Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old "BSD shutdown" functionality. This report is for Ubuntu 15.04. SRU TEST CASE: - Open a terminal, enter some commands, then run "reboot". - After a reboot, chances are very high that your bash history does not contain your most recently typed commands - With the updated package, the bash history should be intact. REGRESSION POTENTIAL: - The original commit was applied because of an inherent race condition with cgroup's release_agent -- in rare corner cases an nspawn container (probably also LXC) can miss them. In that case it's possible that you instead get a 90s timeout on the unit that is shutting down. But this does not mean data loss, just a rare shutdown hang from containers (for the record, I never actually saw that hanging with LXC), so I think it's a good trade-off. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368688] Re: Inconsistence between /etc/init and /etc/init.d files
This just bit us, also. We migrated from Solaris to Ubuntu 14.04 for
our dhcp server. Please fix!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1368688
Title:
Inconsistence between /etc/init and /etc/init.d files
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
After upgrade Ubuntu server from 12.04 LTS to 14.04 LTS (with
do-release-upgrade) I found a strange behavior in /var/log/messages from
isc-dhcp-server. It had doubled DHCPREQUESTS/OFFERS/ACKs... It was like:
~~
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
~~
Futher investigation show that there was actually two dhcpd processes:
~~
dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcp-server/dhcpd.pid
/usr/sbin/dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid
~~
The first one was executed from "/etc/init/isc-dhcp-server.conf" and second
from "/etc/init.d/isc-dhcp-server".
Looking inside "init/isc-dhcp-server.conf" I found:
~~
respawn
script
. /etc/default/isc-dhcp-server
..
exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES
~~
As you can see path to PID file is hardcoded.
But in "init.d/isc-dhcp-server" startup script:
~~
# try to read pid file name from config file, with fallback to
/var/run/dhcpd.pid
if [ -z "$DHCPD_PID" ]; then
DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*"(.*)"[
\t]*;.*$/\1/p' < "$DHCPD_CONF" 2>/dev/null | head -n 1)
fi
DHCPD_PID="${DHCPD_PID:-/var/run/dhcpd.pid}"
..
case "$1" in
start)
test_config
log_daemon_msg "Starting $DESC" "$NAME"
start-stop-daemon --start --quiet --pidfile "$DHCPD_PID" \
--exec /usr/sbin/dhcpd -- \
-q $OPTIONS -cf "$DHCPD_CONF" -pf "$DHCPD_PID"
$INTERFACES
~~
So obivous is to either change init script to NOT use hardcoded path to PID
file and use $DHCP_PID (from /etc/default/isc-dhcp-server, which is sourced
inside this script), or at least change it to "default" one: /var/run/dhcpd.pid
OR
change init.d script to fallback to "/run/dhcp-server/dhcpd.pid"
instead of "/var/run/dhcpd.pid"
P.S. /var/run is a link to /run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1368688/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322265] Re: No success/failure feedback when doing ratings/reviews
Would appreciate input from deisgn here in what we need to do. ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1322265 Title: No success/failure feedback when doing ratings/reviews Status in Ubuntu UX bugs: New Status in unity-scope-click package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: When entering text into review field the status of the "send" button does not change meaning it does not indicate it would be enabled. However, tabbing the button is possible. When doing so, review text disappears as expected but there is no feedback whether it was successfully send to server or not. In fact, it seems it wasn't as the review doesn't show up when relaunching the preview. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1322265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268097] Re: [System settings] Can't set user-supplied ring tone
Iam also on the bq aquaris and I tried downloading an mp3 ringtone with uDropCabin hoping it offers me to open the file with an application that can set it as ringtone. Usually when playing music on Android, i* etc devices you have always an option to set current music as a ringtone. I even tried via contacts to choose a ringtone but it seems there is even no chance to set a separate ringtone for different people. Essential features missing here in my opinion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1268097 Title: [System settings] Can't set user-supplied ring tone Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Triaged Status in content-hub package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: AFAICS I can't set a custom ring tone without using a writable image. (http://askubuntu.com/questions/372759/ringtones-in-ubuntu-touch) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1268097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1284704] Re: Tabbar in Dash: tapping empty part causes weird tab switch
There's no tabbar in the header anymore ** Changed in: unity8 (Ubuntu) Status: Triaged => 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/1284704 Title: Tabbar in Dash: tapping empty part causes weird tab switch Status in unity8 package in Ubuntu: Invalid Bug description: Need tablet or desktop to test this. I have 4 lenses installed: Home, Music, Applications, Videos. In the header, tap the "Home" to show the list of all tab names - this list should not overflow to reproduce the bug. Now tap about 2 cm to the right of the ">" arrow, where there is nothing to tap on. For me, when I do that, I get a haptic feedback, and the "Home" text animates around weirdly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1284704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1276334] Re: Indicators are killed when unity8 stops under unity7 desktop
Does this still happen? I can't reproduce it anymore ** Changed in: unity8 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1276334 Title: Indicators are killed when unity8 stops under unity7 desktop Status in unity8 package in Ubuntu: Incomplete Bug description: When running unity8 from the desktop and quitting it again, all indicators will be killed. I have to manually start them for them to show up in unity7 again. Not a huge problem, but would be nice if this could be fixed. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1276334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1258588] Re: unity8.upstart uses bashism
It works fine in dash, bash and zsh
Do you know of any shell that doesn't support this syntax?
Which shell does upstart decide to use?
** Changed in: unity8 (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1258588
Title:
unity8.upstart uses bashism
Status in unity8 package in Ubuntu:
Incomplete
Bug description:
unity8 upstart job appears to be using bashism [1]
https://wiki.ubuntu.com/DashAsBinSh#A.24.7B7D
Please review and fix appropriately.
Offending line:
30: exec ${BINARY:-unity8} $ARGS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1258588/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable
>From IRC: 16:20 < nessita> jsalisbury, just wanted to sync about the bisect we're doing for LP: #1201528, since I'm now in 3.8.13.1 and audio died with the underrun error. So I re-read all the comments and noticed that in commnet #39 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201528/comments/39) I reproduced the issue with kernel 3.8.0-27-generic 16:21 < nessita> I'm now installing latest 3.7 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ which is 3.7.10 and see if audio breaks, will report in the bug So, in summary: Kernel 3.8.13.1 -> AUDIO BREAKS Kernel 3.7.10 -> audio does not break Will try other versions of 3.8. -- 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/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-driver source package in Vivid: Confirmed Status in linux source package in Vivid: Confirmed Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita 13188 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b InstallationDate: Installed on 2014-05-11 (366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Tags: vivid vivid vivid vivid Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: B
[Touch-packages] [Bug 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes
I think you have seen my screenshot already. I'm trying to send the files tomorrow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1457101 Title: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes Status in Ubuntu One Infrastructure: New Status in powerd package in Ubuntu: Confirmed Bug description: After two last updates (I remember second one was also a kernel update) my Ubuntu has started sudden crashing, either desktop view freezes, sometimes sound which was played goes to fast circuit. Sometimes it crashes to full terminal screen, reporting kernel panic mode. I'm sorry I dont know how to find these crash reports from my Ubuntu, hope you can advice me. After crash, only thing possible is to reset my laptop manually. Ubuntu has also started to inform internal failure with powerd, and asks to report them to developers. I think I have send that report three times now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes
I'm sorry, trying to send attachment through this pages gives error :ERR_ACCESS_DENIED after post comment. I tried to write to some text to comment field and description. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1457101 Title: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes Status in Ubuntu One Infrastructure: New Status in powerd package in Ubuntu: Confirmed Bug description: After two last updates (I remember second one was also a kernel update) my Ubuntu has started sudden crashing, either desktop view freezes, sometimes sound which was played goes to fast circuit. Sometimes it crashes to full terminal screen, reporting kernel panic mode. I'm sorry I dont know how to find these crash reports from my Ubuntu, hope you can advice me. After crash, only thing possible is to reset my laptop manually. Ubuntu has also started to inform internal failure with powerd, and asks to report them to developers. I think I have send that report three times now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452239] Re: root escalation with fs.suid_dumpable=2
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1452239 Title: root escalation with fs.suid_dumpable=2 Status in Apport crash detection/reporting: Fix Released Status in apport package in Ubuntu: Fix Committed Status in apport source package in Precise: Fix Released Status in apport source package in Trusty: Fix Released Status in apport source package in Utopic: Fix Released Status in apport source package in Vivid: Fix Released Status in apport source package in Wily: Fix Committed Bug description: Sander Bos discovered that Apport enabled a user to perform a root escalation since it now configures fs.suid_dumpable=2. Here's a brief description of the issue: 1- A regular user can trigger a coredump with /proc/$PID/stat as root:root simply by doing chmod u-r 2- The root-owned coredump will them be written in the CWD, which in the PoC is /etc/logrotate.d 3- logrotate will gladly skip parts of the coredump it doesn't understand and will successfully run the parts it does I've set a CRD of 2015-05-21 (original proposal: 2015-05-12) for the publication of this issue. I have assigned CVE-2015-1324 to this issue. We can either: 1- Disable fs.suid_dumpable=2 2- Stop creating core dump files when they are to be created as root 3- Create root-owned core dump files in a well-known location To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1452239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398945] Re: Alarms are not set on manta devices
*** This bug is a duplicate of bug 1456281 *** https://bugs.launchpad.net/bugs/1456281 ** This bug has been marked a duplicate of bug 1456281 Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1398945 Title: Alarms are not set on manta devices Status in qtorganizer5-eds package in Ubuntu: New Bug description: STEPS: 1. Open the clock app 2. Allow location service 3. Swipe up from the bottom of the screen 4. tap on the plus 5. set an alarm for a few minutes time EXPECTED: I expect to see the alarm notification move to the datetime-indicator and the alarm to go off ACTUAL: No icon appears in the indicator and no alarms go off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtorganizer5-eds/+bug/1398945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456281] Re: Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu Vivid) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1456281 Title: Alarms not going off in ubuntu-touch/rc-proposed/bq-aquaris.en Status in the base for Ubuntu mobile products: In Progress Status in indicator-datetime package in Ubuntu: In Progress Status in indicator-datetime source package in Vivid: Confirmed Bug description: This ticket is to track a missing alarm issue that seems to have started showing up between May 15 and 18th. in #unity-api, mzanetti reports that alarms on a ubuntu-touch/rc- proposed/bq-aquaris.en are not showing up at the right time; rather, they're skewed by timezone. He's in UTC+2 and set a 6:30 alarm that didn't go off until 8:30. Alesage in Orlando is also reporting missing alarms when he tests on arale. When I test on a fresh flash of ubuntu-touch/rc-proposed/bq-aquaris.en (r9) I'm seeing the same behavior rerported by mzanetti. What's really odd though is when I apt-get source that version of indicator-datetime and run it myself, things work correctly. Alarms also working correctly on mako 15.10 r199. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1456281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 932486] Re: showing quicklist from launcher keynav mode focuses last application
** Description changed: [ Impact ] Poor user experience due to the app window not being focused as expected. [ Test Case ] 0. Have at least one application window open 1. Enter launcher keynav mode with Alt+F1 2. Select a launcher icon with the Up or Down keys. 3. Show the quicklist by pressing Right. 4. Collapse the quicklist by pressing Left. 5. Observe that the app window never has focus during the above steps. [ Regression Potential ] None observed. + + Debdiff of the SRU is found here: + https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff Original Description: To reproduce: 0) Have at least one application window open 1) Enter launcher keynav mode with Alt+F1 * Note that when entering keynav mode, the application loses focus. THe triangle to the right of it's launcher icon is no longer drawn, and the window title is not displayed in the panel. 2) Select a launcher icon with the Up or Down keys. 3) Show the quicklist by pressing Right. * Note that the application becomes active again - it's window title is drawn to the panel, and the triangle to the right of the launcher icon is drawn again. 4) Collapse the quicklist by pressing Left. * The app loses focus again. This seems like inconsistent behavior to me... either the app should never lose focus when we enter keynav mode, or should not be activated when we show a quicklist. -- 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/932486 Title: showing quicklist from launcher keynav mode focuses last application Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: In Progress Bug description: [ Impact ] Poor user experience due to the app window not being focused as expected. [ Test Case ] 0. Have at least one application window open 1. Enter launcher keynav mode with Alt+F1 2. Select a launcher icon with the Up or Down keys. 3. Show the quicklist by pressing Right. 4. Collapse the quicklist by pressing Left. 5. Observe that the app window never has focus during the above steps. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff Original Description: To reproduce: 0) Have at least one application window open 1) Enter launcher keynav mode with Alt+F1 * Note that when entering keynav mode, the application loses focus. THe triangle to the right of it's launcher icon is no longer drawn, and the window title is not displayed in the panel. 2) Select a launcher icon with the Up or Down keys. 3) Show the quicklist by pressing Right. * Note that the application becomes active again - it's window title is drawn to the panel, and the triangle to the right of the launcher icon is drawn again. 4) Collapse the quicklist by pressing Left. * The app loses focus again. This seems like inconsistent behavior to me... either the app should never lose focus when we enter keynav mode, or should not be activated when we show a quicklist. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/932486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1029114] Re: With autohide and the HUD enabled the launcher can appear at incorrect times
** Description changed: [ Impact ] When the Launcher is suddenly revealed when it's not intended to can cause confusion and a poor user experience. [ Test Case ] 1. Turn on launcher auto hide 2. Display the HUD (tap Alt) 3. Move the mouse to the left side of the screen (as if you are showing the launcher) 4. Note the launcher is not displayed 5. Now hide the HUD (either tap Alt or select the X in the top left corner) 6. Observe the Launcher is not revealed. [ Regression Potential ] None observed. + + Debdiff of the SRU is found here: + https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Hi What Happened: 1) Turn on launcher auto hide 2) Display the HUD (tap Alt) 3) Move the mouse to the left side of the screen (as if you are showing the launcher) 4) Note the launcher is not displayed 5) Now hide the HUD (either tap Alt or select the X in the top left corner) 6) Note that the launcher is now displayed, after the HUD closes. What I expected to happen: - I expected that the launcher is not displayed at step 6. I expected for the launcher to not be displayed at step 6 because the user could have the HUD displayed for a long period of time then decide that they don't need the HUD. The launcher is then suddenly revealed to them as they moved their cursor to the left side of the screen a few minutes a ago. This could then confuse the user to why the launcher has appeared when all they did was close the HUD. Hope this can be fixed soon. Andy ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12.0-0ubuntu3~webapps7 [origin: LP-PPA-webapps-preview] ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,compiztoolbox,snap,resize,move,grid,imgpng,mousepoll,place,unitymtgrabhandles,wall,gnomecompat,session,regex,resizeinfo,animation,expo,fade,scale,ezoom,workarounds,unityshell] CrashDB: unity Date: Wed Jul 25 21:19:17 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1029114 Title: With autohide and the HUD enabled the launcher can appear at incorrect times Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: In Progress Bug description: [ Impact ] When the Launcher is suddenly revealed when it's not intended to can cause confusion and a poor user experience. [ Test Case ] 1. Turn on launcher auto hide 2. Display the HUD (tap Alt) 3. Move the mouse to the left side of the screen (as if you are showing the launcher) 4. Note the launcher is not displayed 5. Now hide the HUD (either tap Alt or select the X in the top left corner) 6. Observe the Launcher is not revealed. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Hi What Happened: 1) Turn on launcher auto hide 2) Display the HUD (tap Alt) 3) Move the mouse to the left side of the screen (as if you are showing the launcher) 4) Note the launcher is not displayed 5) Now hide the HUD (either tap Alt or select the X in the top left corner) 6) Note that the launcher is now displayed, after the HUD closes. What I expected to happen: - I expected that the launcher is not displayed at step 6. I expected for the launcher to not be displayed at step 6 because the user could have the HUD displayed for a long period of time then decide that they don't need the HUD. The launcher is then suddenly revealed to them as they moved their cursor to the left side of the screen a few minutes a ago. This could then confuse the user to why the launcher has appeared when all they did was close the HUD. Hope this can be fixed soon. Andy ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12.0-0ubuntu3~webapps7 [origin: LP-PPA-webapps-preview] ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,
[Touch-packages] [Bug 926979] Re: compiz crashed with SIGSEGV in nux::Property::operator=(bool const&) from unity::dash::DashView::AnalyseLensURI(std::string const&) from unity::dash::DashView::
** Description changed: [ Impact ] Certain cases when clicking on Dash items may cause a crash. [ Test Case ] It's not entirely clear how the crash is triggered, but no crash should be observed when clicking on Dash entries. [ Regression Potential ] The change is small and no regressions should be observed. + + Debdiff of the SRU is found here: + https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Clicked dash, Internet applications. Opened a new bug as the others appear to suggest a fix is released for those bugs. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.0.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4 Uname: Linux 3.2.0-3-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Sun Feb 5 14:51:39 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7eff5ff51d10 <_ZN3nux8PropertyIbEaSERKb+32>: mov 0x18(%rdi),%rdi PC (0x7eff5ff51d10) ok source "0x18(%rdi)" (0x03f0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: nux::Property::operator=(bool const&) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::AnalyseLensURI(std::string const&) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::OnActivateRequest(_GVariant*) () from /usr/lib/compiz/libunityshell.so unity::UBusManager::OnCallback(_GVariant*, void*) () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in nux::Property::operator=() UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo usrp video -- 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/926979 Title: compiz crashed with SIGSEGV in nux::Property::operator=(bool const&) from unity::dash::DashView::AnalyseLensURI(std::string const&) from unity::dash::DashView::OnActivateRequest(_GVariant*) Status in Unity: Fix Committed Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: Won't Fix Status in Unity 7.0 series: Invalid Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: In Progress Bug description: [ Impact ] Certain cases when clicking on Dash items may cause a crash. [ Test Case ] It's not entirely clear how the crash is triggered, but no crash should be observed when clicking on Dash entries. [ Regression Potential ] The change is small and no regressions should be observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Clicked dash, Internet applications. Opened a new bug as the others appear to suggest a fix is released for those bugs. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.0.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4 Uname: Linux 3.2.0-3-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Sun Feb 5 14:51:39 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7eff5ff51d10 <_ZN3nux8PropertyIbEaSERKb+32>: mov 0x18(%rdi),%rdi PC (0x7eff5ff51d10) ok source "0x18(%rdi)" (0x03f0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: nux::Property::operator=(bool const&) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::AnalyseLensURI(std::string const&) () from /usr/lib/compiz/libunityshell.so unity::dash::DashView::OnActivateRequest(_GVariant*) () from /usr/lib/compiz/libunityshell.so unity::UBusManager::OnCallback(_GVariant*, void*) () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in nux::Property::operator=() UpgradeStatus: Upgraded to precise on 2012-01-29 (6 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo usrp video To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/
[Touch-packages] [Bug 1313597] Re: Shortcut overlay cannot be closed by clicking the close button in 14.04
** Description changed: [ Impact ] Due to an input handling race, the first time users log into Unity on their system, the shortcut overlay may not close when clicking the "X" in the corner. This leads to a poor user experience. [ Test Case ] 1. Remove ~/.config/unity/first_run.stamp. 2. Log into Unity. 3. Shortcut hints overlay should be shown. 4. Click on "X" in the corner. [ Regression Potential ] This is a workaround for a race, so some users may never see the race to begin with. That said, no regression should be observed as in worse case, the shortcut hints still cannot be closed. + Debdiff of the SRU is found here: + https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff + --- Original Description: In 14.04, the shortcut overlay would pop-out automatically on first boot. Although there is a close button on the top-left corner, it cannot be closed by clicking it. (it could be dismissed by the super key, or open a new window) -- 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/1313597 Title: Shortcut overlay cannot be closed by clicking the close button in 14.04 Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: In Progress Bug description: [ Impact ] Due to an input handling race, the first time users log into Unity on their system, the shortcut overlay may not close when clicking the "X" in the corner. This leads to a poor user experience. [ Test Case ] 1. Remove ~/.config/unity/first_run.stamp. 2. Log into Unity. 3. Shortcut hints overlay should be shown. 4. Click on "X" in the corner. [ Regression Potential ] This is a workaround for a race, so some users may never see the race to begin with. That said, no regression should be observed as in worse case, the shortcut hints still cannot be closed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff --- Original Description: In 14.04, the shortcut overlay would pop-out automatically on first boot. Although there is a close button on the top-left corner, it cannot be closed by clicking it. (it could be dismissed by the super key, or open a new window) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1246891] Re: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher
** Description changed: [ Impact ] Users the use Launcher keynav mode may end up with a Launcher that is not displayed correctly, leaving a poor user experience. [ Test Case ] 1. Make sure there are enough icons in the Launcher to cause the Launcher to fold. 2. Press Alt+F1 3. Press right-key 4. Press left-key 5. Observe the Launcher is not folder while still in keynav mode. [ Regression Potential ] None observed. + Debdiff of the SRU is found here: + https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff + - Original Description: - 1) Press Alt+F1 2) Press right-key 3) Press left-key Expected result: 3) The launcher goes back to keynav mode and unfolds completely. -- 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/1246891 Title: Going back from quicklist to launcher in key-nav mode doesn't unfold the launcher Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: In Progress Bug description: [ Impact ] Users the use Launcher keynav mode may end up with a Launcher that is not displayed correctly, leaving a poor user experience. [ Test Case ] 1. Make sure there are enough icons in the Launcher to cause the Launcher to fold. 2. Press Alt+F1 3. Press right-key 4. Press left-key 5. Observe the Launcher is not folder while still in keynav mode. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: 1) Press Alt+F1 2) Press right-key 3) Press left-key Expected result: 3) The launcher goes back to keynav mode and unfolds completely. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1246891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308265] Re: First password letter not registered in lockscreen if screen off
** Description changed: [ Impact ] Not having the first character registered when trying to unlock the lockscreen can most definitely lead to frustration and thus, poor user experience. [ Test Case ] 1. Lock the screen and let the monitor blank as well. 2. Try unlocking the screen by typing your password. 3. Observe lockscreen unlocks. [ Regression Potential ] None observed. + + Debdiff of the SRU is found here: + https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: With the new lockscreen, if my screen is off, I just start typing, every time my password is too short. It looks like the first key only triggers the screen on and does not go to the input field. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140414.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 23:59:08 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1308265 Title: First password letter not registered in lockscreen if screen off Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: In Progress Bug description: [ Impact ] Not having the first character registered when trying to unlock the lockscreen can most definitely lead to frustration and thus, poor user experience. [ Test Case ] 1. Lock the screen and let the monitor blank as well. 2. Try unlocking the screen by typing your password. 3. Observe lockscreen unlocks. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: With the new lockscreen, if my screen is off, I just start typing, every time my password is too short. It looks like the first key only triggers the screen on and does not go to the input field. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140414.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 23:59:08 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436095] Re: AP test failure: unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
** Description changed:
[ Impact ]
Failed Autopilot tests are not good.
[ Test Case ]
1. Run 'autopilot run
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click'
2. Run 'autopilot run
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click'
3. Observe that the tests don't fail.
[ Regression Potential ]
None observed.
+
+ Debdiff of the SRU is found here:
+
https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff
-
Original Description:
The following two AP tests consistently ERROR during regular Unity
testing.
==
ERROR:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_middle_click
--
Empty attachments:
/var/log/syslog
unity-log: {{{WARN 2015-03-24 13:43:02 nux.inputmethod.ibus
InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
128, in test_scaled_window_closes_on_middle_click
self.assertWindowIsScaledEquals(target_xid, False)
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
68, in assertWindowIsScaledEquals
self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 421, in
assertThat
mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 471, in
_matchHelper
mismatch = matcher.match(matchee)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py",
line 113, in match
wait_fun(self.matcher, self.timeout)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py",
line 129, in _callable_wait_for
new_value = refresh_fn()
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
67, in
refresh_fn = lambda: xid in [w.xid for w in
self.unity.screen.scaled_windows]
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 520, in __getattr__
self.refresh_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 474, in refresh_state
_, new_state = self.get_new_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 564, in get_new_state
raise StateNotFoundError(self.__class__.__name__, id=self.id)
StateNotFoundError: Object not found with name 'Window' and properties {'id':
148832}.
==
ERROR:
unity.tests.test_spread.SpreadTests.test_scaled_window_closes_on_close_button_click
--
Empty attachments:
/var/log/syslog
unity-log: {{{WARN 2015-03-24 14:00:34 nux.inputmethod.ibus
InputMethodIBus.cpp:63 Impossible to connect to connect to ibus}}}
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
148, in test_scaled_window_closes_on_close_button_click
self.assertWindowIsScaledEquals(target_xid, False)
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
68, in assertWindowIsScaledEquals
self.assertThat(refresh_fn, Eventually(Equals(scaled)))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 421, in
assertThat
mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 471, in
_matchHelper
mismatch = matcher.match(matchee)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py",
line 113, in match
wait_fun(self.matcher, self.timeout)
File "/usr/lib/python2.7/dist-packages/autopilot/matchers/__init__.py",
line 129, in _callable_wait_for
new_value = refresh_fn()
File "/usr/lib/python2.7/dist-packages/unity/tests/test_spread.py", line
67, in
refresh_fn = lambda: xid in [w.xid for w in
self.unity.screen.scaled_windows]
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 520, in __getattr__
self.refresh_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 474, in refresh_state
_, new_state = self.get_new_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 564, in get_new_state
raise StateNotFoundError(self.__class__.__name__, id=self.id)
StateNotFoundError: Object not found with name 'Window' and properties {'id':
224517}.
=
[Touch-packages] [Bug 886478] Re: New Alt + tab switcher doesn't follow system font
Attached is the debdiff for the SRU. ** Patch added: "unity.7.2.5.debdiff" https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff ** Description changed: [ Impact ] Users who switch the system font and then use Alt+Tab will see a jarring effect when the Ubuntu font is displayed. This can also lead to not fully supported language issues. [ Test Case ] 1. Switch the system font to something else besides Ubuntu. 2. Use Alt+Tab. 3. Observe any fonts displayed in Alt+Tab follow the system font. [ Regression Potential ] None observed. + + Debdiff of the SRU is found here: + https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff -- Original Description: In my laptop, I have to change from default ubuntu font to droid font because the default one doesn't fully support vietnamese. Let it sit there will make the overall system feel awkward. And now, while the whole system is in droid, only the switcher is still using the ubuntu font. Plz make the switcher follow the system font or at least, make a way to configure its appearance. -- Desired solution: - Alt+tab switcher should use the system font - This change should result in ZERO change to the appearance of the font in Alt+Tab on a fresh installation of Ubuntu. -- 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/886478 Title: New Alt + tab switcher doesn't follow system font Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: In Progress Bug description: [ Impact ] Users who switch the system font and then use Alt+Tab will see a jarring effect when the Ubuntu font is displayed. This can also lead to not fully supported language issues. [ Test Case ] 1. Switch the system font to something else besides Ubuntu. 2. Use Alt+Tab. 3. Observe any fonts displayed in Alt+Tab follow the system font. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff -- Original Description: In my laptop, I have to change from default ubuntu font to droid font because the default one doesn't fully support vietnamese. Let it sit there will make the overall system feel awkward. And now, while the whole system is in droid, only the switcher is still using the ubuntu font. Plz make the switcher follow the system font or at least, make a way to configure its appearance. -- Desired solution: - Alt+tab switcher should use the system font - This change should result in ZERO change to the appearance of the font in Alt+Tab on a fresh installation of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/886478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
** Description changed: [ Impact ] Users of the on-screen keyboard cannot properly use the Dash and the on- screen keyboard at the same time. [ Test Case ] 1. Install and start the on-screen keyboard Onboard. 2. Open the Dash. 3. Ensure you can interact with Onboard as you would expect. [ Regression Potential ] None observed. + + Debdiff of the SRU is found here: + https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: In Progress Bug description: [ Impact ] Users of the on-screen keyboard cannot properly use the Dash and the on-screen keyboard at the same time. [ Test Case ] 1. Install and start the on-screen keyboard Onboard. 2. Open the Dash. 3. Ensure you can interact with Onboard as you would expect. [ Regression Potential ] None observed. Debdiff of the SRU is found here: https://bugs.launchpad.net/unity/+bug/886478/+attachment/4401967/+files/unity.7.2.5.debdiff - Original Description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449394] Re: Crash 854d2ed5e61bf3647f46bb17bb41958c97c4f58d
Customer Confirmed fixed in both 12.04 and 14.04. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1449394 Title: Crash 854d2ed5e61bf3647f46bb17bb41958c97c4f58d Status in apt package in Ubuntu: Fix Released Status in apt source package in Precise: Fix Committed Status in apt source package in Trusty: Fix Committed Bug description: [Impact]The apt version 1.0.1ubuntu2.7 from trusty-proposed has a regression for some users: """ ConfigValueInSubTree → pkgDepCache → → MarkInstall → pkgDepCache → → MarkInstall → pkgDepCache → → MarkInstall → doAutoInstall: #0 __strcmp_ssse3 () at ../sysdeps/i386/i686/multiarch/strcmp-ssse3.S:241 No locals. #1 0xb7656e25 in ConfigValueInSubTree (SubTree=SubTree@entry=0xb771edc3 "APT::Never-MarkAuto-Sections", needle=0x0) at depcache.cc:59 Opts = 0x99bec98 #2 0xb765d3d6 in pkgDepCache::MarkInstall (this=0x99c1738, Pkg=..., AutoInst=AutoInst@entry=true, Depth=2, FromUser=FromUser@entry=false, ForceImportantDeps=false) at depcache.cc:1228 """ Errors Bucket - https://errors.ubuntu.com/problem/854d2ed5e61bf3647f46bb17bb41958c97c4f58d [Test Case] Install deb package that has no section in instVersion, see if program crashes. [Regression Potential] Adds an additional check to if statement to ensure InstVer->Section != 0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1449394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 932486] Re: showing quicklist from launcher keynav mode focuses last application
** Description changed: [ Impact ] Poor user experience due to the app window not being focused as expected. [ Test Case ] 0. Have at least one application window open 1. Enter launcher keynav mode with Alt+F1 2. Select a launcher icon with the Up or Down keys. 3. Show the quicklist by pressing Right. 4. Collapse the quicklist by pressing Left. - 5. Observe that the app window has focus. + 5. Observe that the app window never has focus during the above steps. [ Regression Potential ] None observed. Original Description: To reproduce: 0) Have at least one application window open 1) Enter launcher keynav mode with Alt+F1 * Note that when entering keynav mode, the application loses focus. THe triangle to the right of it's launcher icon is no longer drawn, and the window title is not displayed in the panel. 2) Select a launcher icon with the Up or Down keys. 3) Show the quicklist by pressing Right. * Note that the application becomes active again - it's window title is drawn to the panel, and the triangle to the right of the launcher icon is drawn again. 4) Collapse the quicklist by pressing Left. * The app loses focus again. This seems like inconsistent behavior to me... either the app should never lose focus when we enter keynav mode, or should not be activated when we show a quicklist. -- 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/932486 Title: showing quicklist from launcher keynav mode focuses last application Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: In Progress Bug description: [ Impact ] Poor user experience due to the app window not being focused as expected. [ Test Case ] 0. Have at least one application window open 1. Enter launcher keynav mode with Alt+F1 2. Select a launcher icon with the Up or Down keys. 3. Show the quicklist by pressing Right. 4. Collapse the quicklist by pressing Left. 5. Observe that the app window never has focus during the above steps. [ Regression Potential ] None observed. Original Description: To reproduce: 0) Have at least one application window open 1) Enter launcher keynav mode with Alt+F1 * Note that when entering keynav mode, the application loses focus. THe triangle to the right of it's launcher icon is no longer drawn, and the window title is not displayed in the panel. 2) Select a launcher icon with the Up or Down keys. 3) Show the quicklist by pressing Right. * Note that the application becomes active again - it's window title is drawn to the panel, and the triangle to the right of the launcher icon is drawn again. 4) Collapse the quicklist by pressing Left. * The app loses focus again. This seems like inconsistent behavior to me... either the app should never lose focus when we enter keynav mode, or should not be activated when we show a quicklist. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/932486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1238302] Re: Category reordering causing column "shifting" in overridden result model
That doesn't exist anymore ** Changed in: unity8 (Ubuntu) Status: Triaged => 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/1238302 Title: Category reordering causing column "shifting" in overridden result model Status in unity8 package in Ubuntu: Invalid Bug description: I noticed that the Applications category in Home scope (which is overridden with a hardcoded QtQuick model) gets "shifted". Steps to reproduce: 1) Perform search for something that returns only one result from the server, for example "dsfljkhlas" (the only result will be from the server "search more scopes..."). 2) When you see only this result, swipe away from the home dash page and back 3) Now the applications results should have their columns shifted - the titles will be showing application mimetypes instead of titles and icons will be empty (because they will point to the desktop files). If a new search is performed which returns _no results_ and you repeat the swipe back and forth, the overridden category will fix itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1238302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353855] Re: Explicit g++ 4.9 dependency breaks cross-building
** Changed in: mir Status: Confirmed => Fix Released ** Changed in: mir (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1353855 Title: Explicit g++ 4.9 dependency breaks cross-building Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: With the new explicit g++ 4.9 dependency apt falls over when trying to install cross-dependencies for e.g. Mir: The following packages have unmet dependencies: g++-4.9:armhf : Depends: gcc-4.9:armhf (= 4.9.1-4ubuntu3) but it is not going to be installed E: Build-dependencies for sbuild-build-depends-mir-dummy could not be satisfied. This means cross-building doesn't work for any packages that have that dependency added. We were told it's going to be fine due to 4.9 becoming default, but it is now, and the situation remains. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1353855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425307] Re: [regression] Exception when running phablet-screenshot [std::exception::what: Attempt to set swap interval on screencast is invalid]
It's just a log now right? -- 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/1425307 Title: [regression] Exception when running phablet-screenshot [std::exception::what: Attempt to set swap interval on screencast is invalid] Status in Mir: Confirmed Status in Mir 0.12 series: Confirmed Status in Mir 0.13 series: Confirmed Status in Mir 0.14 series: Confirmed Status in mir package in Ubuntu: Confirmed Status in phablet-tools package in Ubuntu: New Bug description: current build number: 110 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2015-02-24 22:35:35 version version: 110 version ubuntu: 20150224 version device: 20150210 version custom: 20150224 rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png I: Dumping fb0 ... [1424817826.846470] Loader: Loading modules from: /usr/lib/arm-linux-gnueabihf/mir/client-platform/ [1424817826.847569] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so [1424817826.848393] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so [1424817826.849583] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so [1424817826.944654] mircommon: Caught exception at Mir/EGL driver boundary (in setSwapInterval): /build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): Throw in function virtual void mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error std::exception::what: Attempt to set swap interval on screencast is invalid 3004 KB/s (3932160 bytes in 1.278s) I: Done phablet-tools - 1.1+15.04.20150218-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1425307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1235430] Re: [dash] Should support previews of different height.
invalid in unity8 as per ubuntu ux decision ** Changed in: unity8 (Ubuntu) Status: Triaged => 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/1235430 Title: [dash] Should support previews of different height. Status in Ubuntu UX bugs: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: When the scope does not specify a picture for the preview, the outline of the Ubuntu shape should not be shown. Attached is a screenshot that shows this error. Visual design for "small" previews: https://lh6.googleusercontent.com /wsm0GaijMdBH64pqJsSIH8NzjU5JBI21C05YcgrUf176YSa_- yO86ADvfgS7rvBj_FmHx3WyCN4Tgg7u7wKfWKJ8HEgipRgV3OmUHrlLYcyjWfQMEB3Rg_3PmyM Design solution - Marking this as fix released as problem is outdated now that previews are full screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1235430/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1234920] Re: focus issue after clicking on scope results
Set to fix released according cwayne ** Changed in: unity8 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1234920 Title: focus issue after clicking on scope results Status in The Savilerow project: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: Image 79 + customized scopes. 1) Run an app, dialer, reddit, whatever. 2) Swipe app to the side. 3) Click on a scope result, I've tried ones that open webpages and music tracks. 4) Instead of showing the app that the search result should show, you get the app you last used. For example, if you had the dialer open and click on a result, the dialer comes back to the foreground. I tried this using our customized scopes and regular scopes like local music. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1234920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449594] Re: messaging app missing some messages and showing duplicates
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1449594
Title:
messaging app missing some messages and showing duplicates
Status in the base for Ubuntu mobile products:
Fix Released
Status in messaging-app package in Ubuntu:
In Progress
Status in messaging-app source package in Vivid:
New
Bug description:
Found this on arale r185
Open a message thread for User1
Lock the phone
Send 4 sms messages from another phone to User1 ("one", "two", "three",
"four")
Unlock the phone
Expected results:
- message thread for User1 should show "one", "two", "three", 'four"
- messaging indicator should be cleared
Actual results:
- message thread shows "two", "two", "three", "four"
- messaging indicator shows "one" still in the indicator
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449594/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442962] Re: Dialer app reports "No network" even though cellular is connected
** Changed in: canonical-devices-system-image Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1442962 Title: Dialer app reports "No network" even though cellular is connected Status in the base for Ubuntu mobile products: Fix Released Status in dialer-app package in Ubuntu: Confirmed Status in telepathy-ofono package in Ubuntu: In Progress Status in telepathy-ofono source package in Vivid: New Bug description: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 It happens almost daily to me that the dialer app decides that there's no network available. Indicator says the correct network is connected, and I can even use GSM data, but no telephony apps work. When this happens, my `mc-tool dump` looks somewhere along the lines of (this is modified from memory, will update when happens again): Account: ofono/ofono/account0 Display Name: Nju Enabled: enabled Icon: im-ofono Connects: automatically Service: ofono Presences: Automatic: available (2) "" Current: offline (1) "" Requested: available (2) "online" Changing: yes (string) modem-objpath = /ril_0 Stopping/starting the dialer doesn't help, only thing that does is killing mission-control (or well, restarting lightdm or the phone). Please let me know what else to collect when this happens again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20150330-0ubuntu1 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu1 Architecture: armhf Date: Sat Apr 11 22:34:04 2015 InstallationDate: Installed on 2015-04-08 (3 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150408-020203) SourcePackage: dialer-app SystemImageInfo: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449598] Re: messages not getting cleared from messaging indicator
** Changed in: canonical-devices-system-image Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1449598 Title: messages not getting cleared from messaging indicator Status in the base for Ubuntu mobile products: Fix Released Status in history-service package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: New Status in messaging-app source package in Vivid: New Bug description: on arale r185 Not sure exact steps to reproduce, but sometimes when reading a message in the messaging app it still remains in the messaging menu. It does not get cleared as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1214422] Re: Missing Combo Button for Actions in the Preview
What do you mean missing combo button? We've always had one. Can you please comment on what you find missing? ** Changed in: unity8 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1214422 Title: Missing Combo Button for Actions in the Preview Status in unity8 package in Ubuntu: Incomplete Bug description: This bug depends on: https://bugs.launchpad.net/ubuntu-ui- toolkit/+bug/1214421 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1214422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1087650] Re: Index view (collapsed categories) is missing
Is this something we still want? Looks like a 2013 thing that may just be out of trend anymore? ** Changed in: ubuntu-ux Status: Fix Committed => Confirmed ** Changed in: unity8 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1087650 Title: Index view (collapsed categories) is missing Status in Ubuntu UX bugs: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: In the Dash it should be possible to swipe from the bottom and collapse all the category headers. Mika, can you add more detail here too, link to spec? desired solution See prototype by Vesa (vesar on IRC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1087650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1083221] Re: [Dash] Touchdown effect kicks in too soon
There's no People Scope anymore ** Changed in: unity8 (Ubuntu) Status: Triaged => Invalid -- 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/1083221 Title: [Dash] Touchdown effect kicks in too soon Status in Ubuntu UI Toolkit: Incomplete Status in Ubuntu UX bugs: Fix Released Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Invalid Bug description: When scrolling the People Scope, the list cells under the finger flash grey as soon as the finger touches the screen. This is distracting, when the user's intention is to scroll instead of tapping. Expected result: Some sort of threshold should be introduced, so that generally tap on cell results in the cell darkening and scrolling does not. That means possibly adding a delay into the effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1083221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444883] Re: Emergency numbers for China (110, 119) are not available in emergency mode
How about we start with what SIM card is installed in the phone? Is CMCC, China Mobile? When ofono starts, if a valid SIM is inserted in the phone, ofono will try to read the emergency numbers from the file EF_ECC ( emergency number list ). It tries two different formats to ensure that it's able to read the file from a wide variety of SIM cards. When one of these reads completes, ofono builds a composite emergency number list using: - the list of emergency numbers read from the network ( always empty, as RIL/rilmodem don't support this ) - if a valid SIM is present, the numbers read from the SIM EF_ECC file - if a SIM is not present, the numbers "119, 118, 999, 110, 08, and 000" are added - finally the default numbers "911" and "112" are added Also, please note that bug #1334860 discusses a similar problem with operators in Brazil. Their SIMs are not programmed property, and the emergency numbers are found in the 'ServiceNumbers' list from the SIM instead. The only plausible solution for this was the idea that maybe we should instead be using libphonenumber to provide a canonical list of emergency operators vs. relying on SIM cards. I checked, and there are no ServiceNumbers present on the SIM either ( see list-modems output ). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1444883 Title: Emergency numbers for China (110,119) are not available in emergency mode Status in the base for Ubuntu mobile products: New Status in ofono package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: New Bug description: arale device, r177, ubuntu-touch/vivid-proposed Steps 1. Emergency mode (e.g. Lock phone with a passcode, slide left, tap on "Emergency Call") 2. try input 911, 112 ==> OK 2. try input 110, 119 ==> "Dial" button is inactive after number is input Expect Allow these numbers in emergency mode To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes
Would it be possible to upload a screenshot of the folder? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1457101 Title: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes Status in Ubuntu One Infrastructure: New Status in powerd package in Ubuntu: Confirmed Bug description: After two last updates (I remember second one was also a kernel update) my Ubuntu has started sudden crashing, either desktop view freezes, sometimes sound which was played goes to fast circuit. Sometimes it crashes to full terminal screen, reporting kernel panic mode. I'm sorry I dont know how to find these crash reports from my Ubuntu, hope you can advice me. After crash, only thing possible is to reset my laptop manually. Ubuntu has also started to inform internal failure with powerd, and asks to report them to developers. I think I have send that report three times now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes
You could also add any files in the folder to this bug's attachments -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1457101 Title: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes Status in Ubuntu One Infrastructure: New Status in powerd package in Ubuntu: Confirmed Bug description: After two last updates (I remember second one was also a kernel update) my Ubuntu has started sudden crashing, either desktop view freezes, sometimes sound which was played goes to fast circuit. Sometimes it crashes to full terminal screen, reporting kernel panic mode. I'm sorry I dont know how to find these crash reports from my Ubuntu, hope you can advice me. After crash, only thing possible is to reset my laptop manually. Ubuntu has also started to inform internal failure with powerd, and asks to report them to developers. I think I have send that report three times now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457047] Re: Autopilot helper to change scope is unreliable
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Richard Huddie (rhuddie) ** Changed in: unity8 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1457047 Title: Autopilot helper to change scope is unreliable Status in unity8 package in Ubuntu: In Progress Bug description: When using the autopilot helpers to swipe to a different scope I have seen failures where the swipe operation sometimes does not work and so the scope does not change. I've seen this on both krillin and mako. The methods used are _scroll_to_left_scope() and _scroll_to_right_scope() in: http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tests/autopilot/unity8/shell/emulators/dash.py I found that by slowing down the speed of the swipe (using rate of 5 instead of 10) that the swipe operation was reliable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1457047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426851] Re: Power button shuts down computer if a Qt application is running
The same behavior on 14.04 and 15.04 - if QT app is open, all windows for it are closed, like Keepassx, skype, WPS office asks whether to save the contents of documents (this kinda seems like pressing Alt+F4). 14.10, which was troublesome to use for me so I don't use it, didn't have this problem. I'm running Dell, XPS 15 L521X model, can't verify on any other computer. -- 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/1426851 Title: Power button shuts down computer if a Qt application is running Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04, the usual behavior of the power button is bringing a dialog with options (Lock, Suspend, Restart, Shutdown) and waiting for the user's choice. When a Qt application is running, for instance Qt Creator or Texmaker, (but not VLC, Clementine or Skype) and the power button is pressed, it instantly closes that Qt app (http://qt- project.org/forums/viewthread/47632/), brings the shut down dialog and then shuts down the computer without waiting for the user’s choice. I first asked about this on this forum: http://qt-project.org/forums/viewthread/53243/#222409 and reported it at Qt Creator, thinking it was the only application causing it, where they told me to report it to Canonical: https://bugreports.qt.io/browse/QTCREATORBUG-14030 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1426851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378095] Re: aa-complain traceback when marking multiple profiles
I have reproduced this issue with apparmor 2.8.95~2430-0ubuntu5.1 from
trusty-updates, and have verified that apparmor 2.8.95~2430-0ubuntu5.2
fixes the issue. Marking verification-done.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1378095
Title:
aa-complain traceback when marking multiple profiles
Status in AppArmor Linux application security framework:
Fix Released
Status in AppArmor 2.9 series:
Fix Released
Status in AppArmor master series:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
Fix Committed
Bug description:
[SRU justification]
[Impact]
$ sudo aa-complain /etc/apparmor.d/usr.lib.postfix.*
Setting /etc/apparmor.d/usr.lib.postfix.anvil to complain mode.
Traceback (most recent call last):
File "/usr/sbin/aa-complain", line 30, in
tool.cmd_complain()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 171, in
cmd_complain
apparmor.read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2573, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2599, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2853, in
parse_profile_data
store_list_var(filelist[file]['lvar'], list_var, value, var_operation,
file)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3277, in
store_list_var
raise AppArmorException(_('Redefining existing variable %s: %s in %s') %
(list_var, value, filename))
apparmor.common.AppArmorException: 'Redefining existing variable @{TFTP_DIR}:
/var/tftp /srv/tftpboot in /etc/apparmor.d/usr.sbin.dnsmasq'
$ sudo grep -R TFTP_DIR /etc/apparmor.d/
/etc/apparmor.d/usr.sbin.dnsmasq:@{TFTP_DIR}=/var/tftp /srv/tftpboot
/etc/apparmor.d/usr.sbin.dnsmasq: @{TFTP_DIR}/ r,
/etc/apparmor.d/usr.sbin.dnsmasq: @{TFTP_DIR}/** r,
Looks like the tools are re-parsing everything, but not resetting
whatever is storing the variable declarations.
[Test Case]
sudo aa-enforce /etc/apparmor.d/*
got error
[Regression Potential]
[Other Info]
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1378095/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457400] Re: Ubuntu taking long to shutdown
c2 - johny (1000) Since: Thu 2015-05-21 20:02:35 CEST; 1min 18s ago Leader: 1297 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: ubuntu State: closing Unit: session-c2.scope `-2398 python2 linconnect_server.py May 21 20:03:27 johny-laptop sudo[3055]: pam_unix(sudo:session): session closed for user root May 21 20:03:32 johny-laptop systemd[1]: Stopping Session c2 of user johny. May 21 20:03:32 johny-laptop org.freedesktop.Notifications[1774]: loading icon 'notification-info' caused error: 'Icon 'notification-info' not present in theme' May 21 20:03:32 johny-laptop ca.desrt.dconf[2922]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. May 21 20:03:32 johny-laptop org.gnome.zeitgeist.Engine[2922]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. May 21 20:03:32 johny-laptop org.gnome.zeitgeist.Engine[2922]: [18:03:32.644653 WARNING] zeitgeist-daemon.vala:449: The connection is closed May 21 20:03:32 johny-laptop sudo[2911]: pam_unix(sudo:session): session closed for user root May 21 20:03:32 johny-laptop org.gnome.evolution.dataserver.Sources3[1774]: (evolution-source-registry:2011): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed May 21 20:03:32 johny-laptop org.gnome.evolution.dataserver.Sources3[1774]: (evolution-source-registry:2011): GLib-CRITICAL **: Source ID 1 was not found when attempting to remove it May 21 20:03:32 johny-laptop org.gnome.evolution.dataserver.Sources3[1774]: (evolution-source-registry:2011): GLib-CRITICAL **: Source ID 2 was not found when attempting to remove it This is linconnect. https://github.com/hauckwill/linconnect-server It used to work fine. Suddenly this happened. I use it for mirroring Android Notifications. I have enabled it in start up applications, when I removed it from start up applications the shut down time is back to normal. Why is this happening ? Why is shutdown process not able to kill it. ? -- 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/1457400 Title: Ubuntu taking long to shutdown Status in systemd package in Ubuntu: Incomplete Bug description: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426851] Re: Power button shuts down computer if a Qt application is running
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed -- 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/1426851 Title: Power button shuts down computer if a Qt application is running Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04, the usual behavior of the power button is bringing a dialog with options (Lock, Suspend, Restart, Shutdown) and waiting for the user's choice. When a Qt application is running, for instance Qt Creator or Texmaker, (but not VLC, Clementine or Skype) and the power button is pressed, it instantly closes that Qt app (http://qt- project.org/forums/viewthread/47632/), brings the shut down dialog and then shuts down the computer without waiting for the user’s choice. I first asked about this on this forum: http://qt-project.org/forums/viewthread/53243/#222409 and reported it at Qt Creator, thinking it was the only application causing it, where they told me to report it to Canonical: https://bugreports.qt.io/browse/QTCREATORBUG-14030 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1426851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455408] Re: Recent call not cleared from indicator
** Branch linked: lp:~boiko/telephony-service/clear_call_notifications ** Branch linked: lp:~boiko/dialer-app/clear_call_notifications -- 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/1455408 Title: Recent call not cleared from indicator Status in the base for Ubuntu mobile products: Confirmed Status in dialer-app package in Ubuntu: Confirmed Bug description: $ system-image-cli -i current build number: 42 device name: arale channel: ubuntu-touch/tangxi/devel-proposed last update: 2015-05-15 04:19:20 version version: 42 version device: 1e1b1cebe8900f5b62bed050a5c23a7765e62600d394cba528169d257e6ab36c version custom: 8274419d06b4da1424e7f7339ff2f8276b38951951d8900e148a4fdfce8fba0d Steps to reproduce: 1.Make a call from another device to this DUT, but don't answer it 2.Hang up the call from remote end 3.Swipe down on the Notification indicator, make sure the Notification indicator opens and shows the missed call 4.Switch to Phone app to check the missed call Launcher/System Settings--->Phone-->Recent(Swip up from bottom)-->Missed 5.Tap on the missed call body 6.The missed call will shown in Dialer 7.Back to check the state of Notifications indicator Expected results: The missed call should not be displayed in Notifications indicator anymore Actual results: The missed call will not disappear in Notifications indicator unless tap on call back or send message or clear all Additional information: This issue could also be reproduced on Krillin r276 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1455408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457170] Re: Usage of cmake-extras is out of date
** Changed in: unity-scope-click (Ubuntu) Status: New => In Progress ** Changed in: unity-scope-click (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1457170 Title: Usage of cmake-extras is out of date Status in unity-scope-click package in Ubuntu: In Progress Bug description: The API of cmake-extras' EnableCoverageReport changed from 0.3 to 0.4, from an enable_coverage variable to using the coverage build type. The usage within unity-scope-click needs to be updated to 0.4 to be useful in vivid overlay and wily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1457170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449594] Re: messaging app missing some messages and showing duplicates
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Released
** Changed in: canonical-devices-system-image
Status: Fix Released => In Progress
--
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/1449594
Title:
messaging app missing some messages and showing duplicates
Status in the base for Ubuntu mobile products:
In Progress
Status in messaging-app package in Ubuntu:
In Progress
Status in messaging-app source package in Vivid:
New
Bug description:
Found this on arale r185
Open a message thread for User1
Lock the phone
Send 4 sms messages from another phone to User1 ("one", "two", "three",
"four")
Unlock the phone
Expected results:
- message thread for User1 should show "one", "two", "three", 'four"
- messaging indicator should be cleared
Actual results:
- message thread shows "two", "two", "three", "four"
- messaging indicator shows "one" still in the indicator
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449594/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304447] Re: apport-bug crashing on server install
Thanks, Brad. Marking verification-done. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1304447 Title: apport-bug crashing on server install Status in apparmor package in Ubuntu: Fix Released Bug description: [impact] This bug prevents apport from reporting apparmor bugs on systems with non-UTF-8 characters showing up in syslog (the kernel reporting raw information from hardware is a common culprit). [steps to reproduce] 1) on a system with non-UTF-8 characters in syslog, run 'apport -p apparmor -f' if the bug has been addressed, this should generate a report as expected instead of causing apport to crash. [regression potential] The change in the patch for this bug solely modifies the apparmor apport hook. It could potentially introduce more breakage there (but couldn't affect apparmor mediation); also the lp:qa-regression-testign test-apparmor.py attempts to exercise the apport hook, and this is exercised in as part of every linux kernel update by the kernel team (who frequently hit this issue due to the quirkiness of some of their hardware). [original description] jenkins@dagmar:~$ sudo apport-bug apparmor --save testlib.apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .ERROR: hook /usr/share/apport/package-hooks/source_apparmor.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook symb['add_info'](report, ui) TypeError: add_info() takes 1 positional argument but 2 were given During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 202, in _run_hook symb['add_info'](report) File "/usr/share/apport/package-hooks/source_apparmor.py", line 48, in add_info report['KernLog'] = recent_kernlog(sec_re) File "/usr/share/apport/package-hooks/source_apparmor.py", line 24, in recent_kernlog for line in open(file): File "/usr/lib/python3.4/codecs.py", line 313, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd2 in position 6574: invalid continuation byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1304447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449598] Re: messages not getting cleared from messaging indicator
for tracking ... ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Milestone: None => ww22-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to history-service in Ubuntu. https://bugs.launchpad.net/bugs/1449598 Title: messages not getting cleared from messaging indicator Status in the base for Ubuntu mobile products: In Progress Status in history-service package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: New Status in messaging-app source package in Vivid: New Bug description: on arale r185 Not sure exact steps to reproduce, but sometimes when reading a message in the messaging app it still remains in the messaging menu. It does not get cleared as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1449598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
