[Touch-packages] [Bug 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes
last file, others are size zero. ** Attachment added: last file https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+attachment/4402221/+files/_usr_bin_compiz.1000.crash -- 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
** Attachment added: _sbin_init.1001.crash https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+attachment/4402227/+files/_sbin_init.1001.crash -- 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 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Fix Committed = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1457528
Title:
Theme.createStyleComponent deprecation useless warnings are displayed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
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 1457754] Re: E: Method http has died unexpectedly when run under lxc on wily apt 1.0.9.9ubuntu1
It's not about the apt version. I just got it with the downgraded apt, and something apt does when installing the packages fixes it, since it started working once I re-installed the older packages... if you don't believe, here's a bit cut-off but copy-pasted output from my lxc: --- root@wily-gui:~# apt-get autoremove --purge unity.* Luetaan pakettiluetteloita... Valmis ... 0 päivitetty, 14 uutta asennusta, 106 poistettavaa ja 16 päivittämätöntä. Noudettavaa arkistoa 3 375 kt. Toiminnon jälkeen vapautuu 79,8 M t levytilaa. Haluatko jatkaa? [K/e] E: Method http has died unexpectedly! E: Aliprosessi http aiheutti suojausvirheen. root@wily-gui:~# apt-get autoremove --purge unity.* Luetaan pakettiluetteloita... Valmis ... 0 päivitetty, 14 uutta asennusta, 106 poistettavaa ja 16 päivittämätöntä. Noudettavaa arkistoa 3 375 kt. Toiminnon jälkeen vapautuu 79,8 M t levytilaa. Haluatko jatkaa? [K/e] k E: Method http has died unexpectedly! E: Aliprosessi http aiheutti suojausvirheen. root@wily-gui:/# dpkg -i libapt-* apt* (Reading database ... 118694 files and directories currently installed.) Preparing to unpack libapt-inst1.5_1.0.9.7ubuntu4_amd64.deb ... Unpacking libapt-inst1.5:amd64 (1.0.9.7ubuntu4) over (1.0.9.7ubuntu4) ... Preparing to unpack libapt-pkg4.12_1.0.9.7ubuntu4_amd64.deb ... Unpacking libapt-pkg4.12:amd64 (1.0.9.7ubuntu4) over (1.0.9.7ubuntu4) ... Preparing to unpack apt_1.0.9.7ubuntu4_amd64.deb ... Unpacking apt (1.0.9.7ubuntu4) over (1.0.9.7ubuntu4) ... Preparing to unpack apt-utils_1.0.9.7ubuntu4_amd64.deb ... Unpacking apt-utils (1.0.9.7ubuntu4) over (1.0.9.7ubuntu4) ... Setting up libapt-pkg4.12:amd64 (1.0.9.7ubuntu4) ... Setting up apt (1.0.9.7ubuntu4) ... Setting up libapt-inst1.5:amd64 (1.0.9.7ubuntu4) ... Setting up apt-utils (1.0.9.7ubuntu4) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for libc-bin (2.21-0ubuntu4) ... root@wily-gui:/# apt-get autoremove --purge unity.* Luetaan pakettiluetteloita... Valmis Muodostetaan riippuvuussuhteiden puu Luetaan tilatiedot... Valmis ... 0 päivitetty, 14 uutta asennusta, 106 poistettavaa ja 16 päivittämätöntä. Noudettavaa arkistoa 3 375 kt. Toiminnon jälkeen vapautuu 79,8 M t levytilaa. Haluatko jatkaa? [K/e] Nouda:1 http://archive.ubuntu.com/ubuntu/ wily/universe gnome-control-center amd64 1:3.14.2-2ubuntu3 [1 464 kB] Nouda:2 http://archive.ubuntu.com/ubuntu/ wily/main libcolord-gtk1 amd64 0.1.25-1.1build2 [16,7 kB] Nouda:3 http://archive.ubuntu.com/ubuntu/ wily/main libgnome-control-center1 amd64 1:3.14.2-2ubuntu3 [90,1 kB] ... ** Also affects: lxc (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/ + https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged- 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 Status in lxc 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/ + https://www.stgraber.org/2014/01/17/lxc-1-0 -unprivileged-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 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 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-settings (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-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: Fix Committed 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 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 1451808] Re: apport-collect broken in kubuntu vivid
Seems to work launching sudo apport-collect but then starts web browser as root... -- 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/1451808 Title: apport-collect broken in kubuntu vivid Status in apport package in Ubuntu: New Bug description: In kubuntu vivid, apport reacts as follows: apport-collect 1451277 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:35:33 2015 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1451808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431564] Re: [switcher] Can't use mouse to access spread or bottom edge
Ok, i see,the window spread use hotcorners, when hover on it, spread all windows. Is there anyanother design for this? -- 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/1431564 Title: [switcher] Can't use mouse to access spread or bottom edge Status in Ubuntu UX bugs: In Progress Status in unity8 package in Ubuntu: New Bug description: If I connect my BT mouse to my Nexus 4 running devel-proposed with silo 0 (the MWC demo), I can neither open the app spread nor the manage scopes overview. Using the touch screen, both actions work fine, even when the mouse is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1431564/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 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 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 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 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 1457101] Re: Ubuntu 14.04 LTS with kernel 3.13.0-53 crashes
** Attachment added: _usr_bin_signon-ui.1001.crash https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+attachment/4402231/+files/_usr_bin_signon-ui.1001.crash -- 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
** Attachment added: _usr_lib_upower_upowerd.0.crash https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+attachment/4402228/+files/_usr_lib_upower_upowerd.0.crash -- 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
** Attachment added: linux-image-3.13.0-52-generic.234760.crash https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+attachment/4402229/+files/linux-image-3.13.0-52-generic.234760.crash -- 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
** Attachment added: linux-image-3.13.0-52-generic.228614.crash https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+attachment/4402230/+files/linux-image-3.13.0-52-generic.228614.crash -- 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
** Attachment added: _usr_bin_compiz.1001.crash https://bugs.launchpad.net/ubuntuone-infrastructure/+bug/1457101/+attachment/4402237/+files/_usr_bin_compiz.1001.crash -- 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 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed
Thanks, but as discussed on IRC as a code writer it doesn't help me
much, see the example in the bug description, it's trivial and doesn't
use Theme, I don't even know how Theming work. The warning should
point that possible reasons include use of outdated components
--
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:
Confirmed
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 1010349] Re: Evolution address book inaccessible without killing one time e-addressbook-factory
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1010349 Title: Evolution address book inaccessible without killing one time e -addressbook-factory Status in evolution-data-server package in Ubuntu: Confirmed Bug description: After a fresh boot of my system, Evolution is not able to access my work address book on LDAP and my personnal address book on Google. With Google address book I get the error Cannot open book: Source already loaded! After shutting down Evolution and killing by hand : /usr/lib/evolution/e-addressbook-factory. I relaunch Evolution and everything go right. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution-data-server 3.2.3-0ubuntu7 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: Fri Jun 8 09:07:18 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1010349/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: Upstart packaging conflicts with man Xsession
** Also affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ltsp (Ubuntu)
Importance: Undecided = High
** Changed in: ltsp (Ubuntu)
Status: New = Fix Committed
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) = Alkis Georgopoulos (alkisg)
--
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 ltsp package in Ubuntu:
Fix Committed
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/ltsp/+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 1390625] Re: mouse cursor gets corrupted
The xserver-xorg installiation fixes the issue but, in my case, it introduces another issue. A great number of artifacts, little white or black horizontal lines sometimes appear/disappear on the screen in relation with the mouse movement. The solution of changing the intel method of accelleration to uxa works too, but it has the same side effects. I suspect that installing xserver-xorg in some way changes the accelleration to uxa... -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1293168] [NEW] nautilus crashed with SIGSEGV in compute_drop_position()
You have been subscribed to a public bug: * Select Recent * Try to drag a PDF file from the recent view into Gmail * Nautilus crashes before the pointer leaves the nautilus window. I'm able to reproduce it about 50% of the time a drag a file and 100% of the time if the drag is over the Desktop item in the left pane. Desktop is set to Home dir. Ubuntu Gnome 14.04 beta 16 mar 2014. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 16 17:44:56 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-03-06 (9 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) ProcCmdline: nautilus --new-window SegvAnalysis: Segfault happened at: 0x7f97d7a3546e: repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0x7f97d7a3546e) ok source %es:(%rdi) (0x7f97d7ba4b30) ok destination %ds:(%rsi) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo ** Affects: gtk+3.0 (Ubuntu) Importance: Medium Status: Fix Released ** Tags: amd64 apport-crash trusty -- nautilus crashed with SIGSEGV in compute_drop_position() https://bugs.launchpad.net/bugs/1293168 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1293168] Re: nautilus crashed with SIGSEGV in compute_drop_position()
there is currently a SRU in trusty-proposed that needs to be validated/copied to updates, then we can look at backporting those changes ** Package changed: nautilus (Ubuntu) = gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1293168 Title: nautilus crashed with SIGSEGV in compute_drop_position() Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: * Select Recent * Try to drag a PDF file from the recent view into Gmail * Nautilus crashes before the pointer leaves the nautilus window. I'm able to reproduce it about 50% of the time a drag a file and 100% of the time if the drag is over the Desktop item in the left pane. Desktop is set to Home dir. Ubuntu Gnome 14.04 beta 16 mar 2014. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 16 17:44:56 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-03-06 (9 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) ProcCmdline: nautilus --new-window SegvAnalysis: Segfault happened at: 0x7f97d7a3546e:repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0x7f97d7a3546e) ok source %es:(%rdi) (0x7f97d7ba4b30) ok destination %ds:(%rsi) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1293168/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 1457730] Re: Upstart packaging conflicts with man Xsession
To work around the issue from the LTSP side, I pushed the following changes:
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/revision/1577
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2646
Anyone interested in getting Unity to work with LTSP in Ubuntu 14.04 should
apply for an SRU,
either for upstart if this bug is accepted and fixed, or for LTSP.
In the meantime, I've upload patched LTSP and LDM packages for LTS versions
only to the Greek schools PPA:
https://launchpad.net/~ts.sch.gr/+archive/ppa
--
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 1030542] Re: Evince doesn't appear on Launcher or Alt+Tab
The way I reproduced this problem: 1) Unlock evince icon from the launcher. 2) Open any pdf document using evince. You will notice the icon for the opened application does not appear in the launcher. 3) Navigate to any other open window/application. You will not get back to evince using ALT+TAB You need to keep evince icon added in launcher to prevent this problem from happening. -- 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/1030542 Title: Evince doesn't appear on Launcher or Alt+Tab Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: Evince doesn't appear on Launcher or Alt+Tab (see screenshot). Unity version: 5.12-0ubuntu1.1 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evince 3.4.0-0ubuntu1.1 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 Date: Sun Jul 29 17:04:03 2012 ExecutablePath: /usr/lib/evince/evinced InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) KernLog: ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1030542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window
The bug affects unity via compiz (which uses libnux). Version: compiz 1:0.9.12+14.10.20140918-0ubuntu1 -- 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/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window Status in Compiz: New Status in Nux: New Status in Unity: New Status in unity package in Ubuntu: New Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window
This is a bug in libnux-4.0-0 on amd64, caused by the code in GraphicsDisplay::MousePress (NuxGraphics/GraphicsDisplayX11.cpp) which converts the unsigned long timestamp to a signed int: if ((double_click_counter_ == 1) ((int)current_time - (int)last_click_time_ double_click_time_delay)) The timestamp is in milliseconds, so it becomes negative after about 24.86 days. The comparison works ok until the final click on the title bar, when last_click_time_ is 0. Subtracting 0 from the negative current_time results in a value that is always less than double_click_time_delay. The unnecessary cast to int should be removed. Version: libnux-4.0-0 4.0.7+14.10.20141007-0ubuntu1 ** Also affects: nux Importance: Undecided Status: New ** Also affects: compiz Importance: Undecided Status: New -- 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/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window Status in Compiz: New Status in Nux: New Status in Unity: New Status in unity package in Ubuntu: New Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435088] Re: Crash of media-hub opening a .avi file
This bug was fixed in the package media-hub - 3.1.0+15.10.20150522-0ubuntu1 --- media-hub (3.1.0+15.10.20150522-0ubuntu1) wily; urgency=medium [ Jim Hodapp ] * Fix issues with not reporting failed decoding error to the client. (LP: #1435088) media-hub (3.1.0+15.04.20150511-0ubuntu1) vivid; urgency=medium [ Jim Hodapp ] * Make sure recorded videos are able to play. (LP: #1451816) -- CI Train Bot ci-train-...@canonical.com Fri, 22 May 2015 17:36:27 + ** Changed in: media-hub (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1435088 Title: Crash of media-hub opening a .avi file Status in the base for Ubuntu mobile products: Confirmed Status in Media Hub: Fix Committed Status in media-hub package in Ubuntu: Fix Released Status in mediaplayer-app package in Ubuntu: Fix Released Status in qtubuntu-media package in Ubuntu: Fix Committed Bug description: I tried to open two .avi videos on BQ Aquaris E4.5 running Ubuntu Touch using the Media Player app: one simply prints Video format not supported while the second shows only a black screen. Then if I close the player I can't open any video and I get the error: Error playing video Fail to connect with playback backend. and trying to play some audio files simply doesn't do anything. I uploaded the second video here: http://uz.sns.it/~ilario/utouch-media-hub.avi ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: media-hub 2.0.0+15.04.20150120~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Sun Mar 22 23:32:09 2015 InstallationDate: Installed on 2015-03-12 (10 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150312-002053) SourcePackage: media-hub 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/1435088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340927] Re: libapparmor aalogparse memory leak
I reproduced the memory leaks with libapparmor from apparmor 2.8.95~2430-0ubuntu5.1 from trusty-updates, and verified that libapparmor from apparmor 2.8.95~2430-0ubuntu5.2 in trusty-proposed fixes the issue. I did this by running valgrind on aa-notify against each version of the library after having run apparmor regressions tests to generate a lot of events in syslog. Valgrind reported before updating: definitely lost: 11,586,610 bytes in 1,005,004 blocks after updating, valgrind reported: definitely lost: 40,263 bytes in 824 blocks with the remaining leaked memory looking to be in perl itself. 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/1340927 Title: libapparmor aalogparse memory leak Status in AppArmor Linux application security framework: Fix Released Status in AppArmor 2.8 series: Fix Released Status in apparmor package in Ubuntu: Fix Released Bug description: My kern.log is filled by lots of messages so aa-notify tries to parse them on first run. My OS is going down when there's no memory left because aa-notify leaks. I've found that leak is in /usr/bin/aa-notify file in function parse_message. If I comment lines from my ($test) = LibAppArmorc::parse_record($msg); to LibAppArmorc::free_record($test); then all goes fine. Program parses file and no memory leak is happened. Do I've got sources of my version (libapparmor-perl (2.8.0-5.1) from ubuntu) and found that some variables from aa_log_record struct were not freed by the free_record function. These are char *net_local_addr; char *net_foreign_addr; Could this be a reason of a leak? I haven't much time right now to compile and run tests. So I posted just information I've found and commented lines in bugged function to get my system working. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1340927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435088] Re: Crash of media-hub opening a .avi file
This bug was fixed in the package mediaplayer-app - 0.20.5+15.10.20150522-0ubuntu1 --- mediaplayer-app (0.20.5+15.10.20150522-0ubuntu1) wily; urgency=medium [ Jim Hodapp ] * Quit playback after fatal playback error. (LP: #1435088) -- CI Train Bot ci-train-...@canonical.com Fri, 22 May 2015 17:36:44 + ** Changed in: mediaplayer-app (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1435088 Title: Crash of media-hub opening a .avi file Status in the base for Ubuntu mobile products: Confirmed Status in Media Hub: Fix Committed Status in media-hub package in Ubuntu: Fix Released Status in mediaplayer-app package in Ubuntu: Fix Released Status in qtubuntu-media package in Ubuntu: Fix Committed Bug description: I tried to open two .avi videos on BQ Aquaris E4.5 running Ubuntu Touch using the Media Player app: one simply prints Video format not supported while the second shows only a black screen. Then if I close the player I can't open any video and I get the error: Error playing video Fail to connect with playback backend. and trying to play some audio files simply doesn't do anything. I uploaded the second video here: http://uz.sns.it/~ilario/utouch-media-hub.avi ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: media-hub 2.0.0+15.04.20150120~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Sun Mar 22 23:32:09 2015 InstallationDate: Installed on 2015-03-12 (10 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150312-002053) SourcePackage: media-hub 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/1435088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451200] Re: package libffi6:i386 3.2.1-2 failed to install/upgrade: package libffi6:i386 is already installed and configured
*** This bug is a duplicate of bug 1407757 *** https://bugs.launchpad.net/bugs/1407757 ** This bug is no longer a duplicate of bug 1446880 Package x is already installed and configured ** This bug has been marked a duplicate of bug 1407757 multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1451200 Title: package libffi6:i386 3.2.1-2 failed to install/upgrade: package libffi6:i386 is already installed and configured Status in libffi package in Ubuntu: New Bug description: is bug broken..please help my os.. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libffi6:i386 3.2.1-2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3 Architecture: amd64 CrashReports: 600:0:118:384892:2015-05-02 03:53:18.129973888 +0700:2015-05-02 03:53:19.129973888 +0700:/var/crash/libexpat1:i386.0.crash 600:0:118:384882:2015-05-02 03:53:18.161973953 +0700:2015-05-02 03:53:19.161973953 +0700:/var/crash/libffi6:i386.0.crash Date: Sat May 2 03:53:19 2015 Dependencies: gcc-5-base 5.1~rc1-0ubuntu1 libc6 2.21-0ubuntu4 libgcc1 1:5.1~rc1-0ubuntu1 multiarch-support 2.21-0ubuntu4 DuplicateSignature: package:libffi6:i386:3.2.1-2:package libffi6:i386 is already installed and configured ErrorMessage: package libffi6:i386 is already installed and configured InstallationDate: Installed on 2015-05-01 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: libffi Title: package libffi6:i386 3.2.1-2 failed to install/upgrade: package libffi6:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1451200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445557] Re: package session-migration 0.2.2 failed to install/upgrade: package session-migration is already installed and configured
*** This bug is a duplicate of bug 1407757 *** https://bugs.launchpad.net/bugs/1407757 ** This bug is no longer a duplicate of bug 1446880 Package x is already installed and configured ** This bug has been marked a duplicate of bug 1407757 multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to session-migration in Ubuntu. https://bugs.launchpad.net/bugs/1445557 Title: package session-migration 0.2.2 failed to install/upgrade: package session-migration is already installed and configured Status in session-migration package in Ubuntu: New Bug description: critical error ProblemType: Package DistroRelease: Ubuntu 15.04 Package: session-migration 0.2.2 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic i686 ApportVersion: 2.17.2-0ubuntu1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3 Architecture: i386 Date: Fri Apr 17 14:11:38 2015 DuplicateSignature: package:session-migration:0.2.2:package session-migration is already installed and configured ErrorMessage: package session-migration is already installed and configured InstallationDate: Installed on 2014-12-10 (128 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141209) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: session-migration Title: package session-migration 0.2.2 failed to install/upgrade: package session-migration is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/session-migration/+bug/1445557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 641225] Re: tracker-miner-fs crashed with SIGSEGV in g_slice_alloc()
Same bug in Trusty with amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/641225 Title: tracker-miner-fs crashed with SIGSEGV in g_slice_alloc() Status in tracker package in Ubuntu: Confirmed Bug description: Binary package hint: tracker unexpected crash ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: tracker-miner-fs 0.8.17-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4 Uname: Linux 2.6.35-21-generic i686 NonfreeKernelModules: slamr Architecture: i386 Date: Fri Sep 17 13:31:32 2010 ExecutablePath: /usr/lib/tracker/tracker-miner-fs ProcCmdline: /usr/lib/tracker/tracker-miner-fs ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x9c3c7b g_slice_alloc+251: mov0x4(%eax),%edx PC (0x009c3c7b) ok source 0x4(%eax) (0x0044) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: g_slice_alloc () from /lib/libglib-2.0.so.0 g_slist_prepend () from /lib/libglib-2.0.so.0 ?? () from /usr/lib/libtracker-miner-0.8.so.0 ?? () from /usr/lib/libgio-2.0.so.0 g_simple_async_result_complete () from /usr/lib/libgio-2.0.so.0 Title: tracker-miner-fs crashed with SIGSEGV in g_slice_alloc() UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare scanner scard tape uml-net video x2gousers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/641225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427264] Re: using ecryptfs, creating frameworks fail to bind mount issues
I've submitted a proposed fix for this bug to schroot upstream/Debian and linked the bug to this one. ** Bug watch added: Debian Bug tracker #786566 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786566 ** Also affects: schroot (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786566 Importance: Unknown Status: Unknown -- 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/1427264 Title: using ecryptfs, creating frameworks fail to bind mount issues Status in click package in Ubuntu: Triaged Status in schroot package in Ubuntu: In Progress Status in schroot package in Debian: Unknown Bug description: Using vivid creating framework fails for ecryptfs users, the issue is similar to bug #769595 The userdir is mounted in a way which makes unmounts fail E: 10mount: umount: /var/lib/schroot/mount/click-ubuntu-sdk-14.10 -armhf-ec6aaf62-31e0-47e9-b2f8-73f0b038fb4d/home/user: target is busy E: 10mount: (In some cases useful info about processes that E: 10mount: use the device is found by lsof(8) or fuser(1).) changing the fstab line to be /home/user /home/user none rw,bind0 0 workarounds the issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435088] Re: Crash of media-hub opening a .avi file
This bug was fixed in the package qtubuntu-media - 0.7.1+15.10.20150522-0ubuntu1 --- qtubuntu-media (0.7.1+15.10.20150522-0ubuntu1) wily; urgency=medium [ Jim Hodapp ] * Make sure that stopped and ready (same state for QMediaPlayer) are reported to the client app. (LP: #1435088) qtubuntu-media (0.7.1+15.04.20150513.1-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Jim Hodapp ] * Fix duration() not getting reported after playback starts. (LP: #1438115) -- CI Train Bot ci-train-...@canonical.com Fri, 22 May 2015 17:36:57 + ** Changed in: qtubuntu-media (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1435088 Title: Crash of media-hub opening a .avi file Status in the base for Ubuntu mobile products: Confirmed Status in Media Hub: Fix Committed Status in media-hub package in Ubuntu: Fix Released Status in mediaplayer-app package in Ubuntu: Fix Released Status in qtubuntu-media package in Ubuntu: Fix Released Bug description: I tried to open two .avi videos on BQ Aquaris E4.5 running Ubuntu Touch using the Media Player app: one simply prints Video format not supported while the second shows only a black screen. Then if I close the player I can't open any video and I get the error: Error playing video Fail to connect with playback backend. and trying to play some audio files simply doesn't do anything. I uploaded the second video here: http://uz.sns.it/~ilario/utouch-media-hub.avi ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: media-hub 2.0.0+15.04.20150120~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Sun Mar 22 23:32:09 2015 InstallationDate: Installed on 2015-03-12 (10 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150312-002053) SourcePackage: media-hub 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/1435088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)
This bug was fixed in the package systemd-shim - 9-1bzr3 --- systemd-shim (9-1bzr3) wily; urgency=medium * debian/patches/lp1390120.patch - Cherrypicked: Use the ntp support for 'systemd-timesyncd.service' too (LP: #1390120) -- Ken VanDine ken.vand...@canonical.com Mon, 18 May 2015 10:43:32 -0400 ** Changed in: systemd-shim (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1390120 Title: Manually set time and date reverts to Automatically on restart (Ubuntu Phone) Status in the base for Ubuntu mobile products: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in systemd-shim package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: 1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open Time Date settings and select Manually under Set the time and date: 2a - I set the time manually from Old_Time to New_Time and wait for New_Time to display in the Date Time Indicator at top-right 3a - Then restart Ubuntu Phone and Date Time Indicator shows New_Time for 10 seconds and then reverts to Old_Time 4a - Time Date settings agree with Old_Time and Automatically has been selected under Set the time and date: To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458031] Re: sudo not properly cleaning out timestamp directory
** Changed in: sudo (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1458031 Title: sudo not properly cleaning out timestamp directory Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Wily: Confirmed Status in sudo package in Debian: New Bug description: Sudo 1.8.10 switched to a new time stamp file format that uses the monotonic clock. Timestamp files moved from /var/lib/sudo to /var/lib/sudo/ts. At boot, the contents of the /var/lib/sudo/ts directory needs to be deleted, as per the warning in the build log: configure: Warning: the /var/lib/sudo/ts directory must be cleared at boot time. configure: You may need to create a startup item to do this. The sudo package ships with both an init script and a systemd unit file. Unfortunately, the init script sets the date on the timestamp files to epoch, which is no longer the proper way to invalidate them. The systemd unit file doesn't seem to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1458031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
** Changed in: gdm
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
Confirmed
Status in gdm package in Ubuntu:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in gdm source package in Trusty:
Fix Released
Status in lightdm source package in Trusty:
Fix Released
Status in gdm source package in Utopic:
Fix Released
Status in lightdm source package in Utopic:
Fix Released
Status in gdm package in Debian:
New
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458014] Re: audit_printk_skb slowing down boot
Here are the outputs of 2 consecutive boots for dmesg | less, they both indicate 26 lost CPU seconds: [ 12.580984] vboxdrv: Successfully loaded version 4.3.10_Ubuntu (interface 0x001a0007). [ 12.593834] vboxpci: IOMMU not found (not registered) [ 13.307547] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 13.307807] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 13.671770] r8169 :04:00.0 eth0: link down [ 13.671790] r8169 :04:00.0 eth0: link down [ 13.671819] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 13.672126] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 15.219548] r8169 :04:00.0 eth0: link up [ 15.219570] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 15.687163] init: plymouth-upstart-bridge main process ended, respawning [ 41.953317] audit_printk_skb: 177 callbacks suppressed [ 41.953319] type=1400 audit(1432326862.429:71): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2677 comm=apparmor_parser [ 41.953324] type=1400 audit(1432326862.429:72): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2677 comm=apparmor_parser [ 41.953664] type=1400 audit(1432326862.429:73): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2677 comm=apparmor_parser (END) [ 12.716182] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 12.861751] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 12.864483] vboxdrv: Found 4 processor cores. [ 12.864950] vboxdrv: fAsync=0 offMin=0x214 offMax=0x1658 [ 12.865004] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 12.865006] vboxdrv: Successfully loaded version 4.3.10_Ubuntu (interface 0x001a0007). [ 12.878317] vboxpci: IOMMU not found (not registered) [ 14.374026] r8169 :04:00.0 eth0: link up [ 14.374033] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 15.556422] init: plymouth-upstart-bridge main process ended, respawning [ 41.489482] audit_printk_skb: 159 callbacks suppressed [ 41.489484] type=1400 audit(1432327140.961:65): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2788 comm=apparmor_parser [ 41.489489] type=1400 audit(1432327140.961:66): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2788 comm=apparmor_parser [ 41.489832] type=1400 audit(1432327140.961:67): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2788 comm=apparmor_parser (END) The PC is a Dell Inspiron 660 Core i5-3330 quad core (physical, not virtual) all running at 3GHz. 26 lost CPU seconds on this machine is a long time. Is this ok? -- 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/1458014 Title: audit_printk_skb slowing down boot Status in apparmor package in Ubuntu: New Bug description: Subjectively, my system slowed down after the recent GRUB update. As you can see from the following, audit_printk_skb is consuming a lot of boot time: [ 13.243280] vboxdrv: Successfully loaded version 4.3.10_Ubuntu (interface 0x001a0007). [ 13.257947] vboxpci: IOMMU not found (not registered) [ 13.862999] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 13.865996] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 14.195776] r8169 :04:00.0 eth0: link down [ 14.195796] r8169 :04:00.0 eth0: link down [ 14.195827] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 14.196138] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 15.769090] r8169 :04:00.0 eth0: link up [ 15.769097] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 16.223084] init: plymouth-upstart-bridge main process ended, respawning [ 42.424836] audit_printk_skb: 195 callbacks suppressed [ 42.424839] type=1400 audit(1431891089.974:77): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2632 comm=apparmor_parser [ 42.424844] type=1400 audit(1431891089.974:78): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2632 comm=apparmor_parser [ 42.425185] type=1400 audit(1431891089.974:79): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2632 comm=apparmor_parser (END) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apparmor 2.8.95~2430-0ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CurrentDesktop: Unity Date: Fri May 22 14:18:46 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-29 (388 days ago)
[Touch-packages] [Bug 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
** Summary changed: - Menu interaction in fully maximised window causes the next click on the title bar to restore the window + Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) ** Patch added: Patch for nux-4.0.7+14.10.20141007 https://bugs.launchpad.net/nux/+bug/1379960/+attachment/4402675/+files/launchpad-bug-1379960.patch -- 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/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) Status in Compiz: New Status in Nux: New Status in Unity: New Status in unity package in Ubuntu: New Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458063] Re: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
Oh... Maybe the problem is lxcbr0 is up'ed before named starts. Then if named listens on 0.0.0.0 makes sense it would glom onto the lxcbr0 address too. I'll modify named's config files + reboot + see if this fixes the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1458063 Title: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address Status in lxc package in Ubuntu: New Bug description: This is a clean Vivid install (rather than upgrade). Maybe I munged something + for the life of me nothing comes to mind. /var/log/syslog shows somehow bind is polluted with dnsmasq addresses? All packages updated. net8-rmt# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid net8-rmt# uname -a Linux ns515383.ip-167-114-159.net 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux net8-rmt# pkg-list | egrep -e lxc -e cgroup cgroup-bin 0.38-1ubuntu2 cgroup-lite 1.10 libcgroup1 0.38-1ubuntu2 liblxc1 1.1.2-0ubuntu3 lxc 1.1.2-0ubuntu3 lxc-templates 1.1.2-0ubuntu3 lxcfs 0.7-0ubuntu4 lxctl 0.3.1+debian-3 python3-lxc 1.1.2-0ubuntu3 Behavior is this. 1) After reboot, lxcbr0 is missing 2) /usr/lib/x86_64-linux-gnu/lxc/lxc-net restart reports 10.0.3.1 (set in /etc/default/lxc-net ) as being in use. 3) netstat reports bind/named has the address, at least UDP, no TCP. 4) /var/log/syslog from last boot shows this... net8-rmt# grep 10.0.3.1 /var/log/syslog May 22 16:03:01 ns515383 named[1355]: listening on IPv4 interface lxcbr0, 10.0.3.1#53 May 22 16:03:02 ns515383 ntpd[1453]: Listen normally on 5 lxcbr0 10.0.3.1 UDP 123 May 22 16:03:04 ns515383 lxc-net[1360]: dnsmasq: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:03:04 ns515383 dnsmasq[1768]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:03:06 ns515383 ntpd[1453]: Deleting interface #5 lxcbr0, 10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=4 secs May 22 16:21:04 ns515383 dnsmasq[10991]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:21:30 ns515383 dnsmasq[11156]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:24:15 ns515383 dnsmasq[12092]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:25:36 ns515383 dnsmasq[12576]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:29:54 ns515383 dnsmasq[14015]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:34:55 ns515383 named[1355]: no longer listening on 10.0.3.1#53 May 22 16:35:10 ns515383 ntpd[1453]: Listen normally on 9 lxcbr0 10.0.3.1 UDP 123 May 22 16:35:26 ns515383 ntpd[1453]: Deleting interface #9 lxcbr0, 10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=16 secs May 22 16:52:50 ns515383 ntpd[1453]: Listen normally on 11 lxcbr0 10.0.3.1 UDP 123 5) Nothing in named config referencing the LXC IP. 6) Then after server minutes, named stops listening to this address, at which time /usr/lib/x86_64-linux-gnu/lxc/lxc-net restart begins working as expected. 7) If /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop is issued + service bind9 restart issued, named no longer attempts to connect to 10.0.3.1 so all's well. Any suggestions on why named might be grabbing the LXC address at boot time are appreciated. I reported this as a bug, because none of the named config files reference the LXC IP address, so to me, named should never touch this address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458063] [NEW] Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
Public bug reported: This is a clean Vivid install (rather than upgrade). Maybe I munged something + for the life of me nothing comes to mind. /var/log/syslog shows somehow bind is polluted with dnsmasq addresses? All packages updated. net8-rmt# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid net8-rmt# uname -a Linux ns515383.ip-167-114-159.net 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux net8-rmt# pkg-list | egrep -e lxc -e cgroup cgroup-bin 0.38-1ubuntu2 cgroup-lite 1.10 libcgroup1 0.38-1ubuntu2 liblxc1 1.1.2-0ubuntu3 lxc 1.1.2-0ubuntu3 lxc-templates 1.1.2-0ubuntu3 lxcfs 0.7-0ubuntu4 lxctl 0.3.1+debian-3 python3-lxc 1.1.2-0ubuntu3 Behavior is this. 1) After reboot, lxcbr0 is missing 2) /usr/lib/x86_64-linux-gnu/lxc/lxc-net restart reports 10.0.3.1 (set in /etc/default/lxc-net ) as being in use. 3) netstat reports bind/named has the address, at least UDP, no TCP. 4) /var/log/syslog from last boot shows this... net8-rmt# grep 10.0.3.1 /var/log/syslog May 22 16:03:01 ns515383 named[1355]: listening on IPv4 interface lxcbr0, 10.0.3.1#53 May 22 16:03:02 ns515383 ntpd[1453]: Listen normally on 5 lxcbr0 10.0.3.1 UDP 123 May 22 16:03:04 ns515383 lxc-net[1360]: dnsmasq: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:03:04 ns515383 dnsmasq[1768]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:03:06 ns515383 ntpd[1453]: Deleting interface #5 lxcbr0, 10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=4 secs May 22 16:21:04 ns515383 dnsmasq[10991]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:21:30 ns515383 dnsmasq[11156]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:24:15 ns515383 dnsmasq[12092]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:25:36 ns515383 dnsmasq[12576]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:29:54 ns515383 dnsmasq[14015]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:34:55 ns515383 named[1355]: no longer listening on 10.0.3.1#53 May 22 16:35:10 ns515383 ntpd[1453]: Listen normally on 9 lxcbr0 10.0.3.1 UDP 123 May 22 16:35:26 ns515383 ntpd[1453]: Deleting interface #9 lxcbr0, 10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=16 secs May 22 16:52:50 ns515383 ntpd[1453]: Listen normally on 11 lxcbr0 10.0.3.1 UDP 123 5) Nothing in named config referencing the LXC IP. 6) Then after server minutes, named stops listening to this address, at which time /usr/lib/x86_64-linux-gnu/lxc/lxc-net restart begins working as expected. 7) If /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop is issued + service bind9 restart issued, named no longer attempts to connect to 10.0.3.1 so all's well. Any suggestions on why named might be grabbing the LXC address at boot time are appreciated. I reported this as a bug, because none of the named config files reference the LXC IP address, so to me, named should never touch this address. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time + Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening on LXC address ** Summary changed: - Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening on LXC address + Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1458063 Title: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address Status in lxc package in Ubuntu: New Bug description: This is a clean Vivid install (rather than upgrade). Maybe I munged something + for the life of me nothing comes to mind. /var/log/syslog shows somehow bind is polluted with dnsmasq addresses? All packages updated. net8-rmt# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid net8-rmt# uname -a Linux ns515383.ip-167-114-159.net 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux net8-rmt# pkg-list | egrep -e lxc -e cgroup cgroup-bin 0.38-1ubuntu2 cgroup-lite
[Touch-packages] [Bug 1453285] Re: Emergency numbers for France (15, 17 and 18) are not available in emergency mode
Please see bug #1444883 for a description of how emergency numbers currently work in Ubuntu's version of ofono. -- 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/1453285 Title: Emergency numbers for France (15, 17 and 18) are not available in emergency mode Status in ofono package in Ubuntu: New Status in telephony-service package in Ubuntu: Incomplete Bug description: Emergency numbers for France (15, 17 and 18) are not available in emergency mode. Dial button is inactive after these numbers are input. For information, emergency number for Europe (112) is available !! This number (112) is used for europeans who are not in their country. Example : a french who is located in Germany. In fact, a French who is located in France should call 15, 17 or 18 !!! That's why I consider it as a bug, because it doesn't work.because To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1453285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452119] Re: ethernet interface broken after upgrade from 14.10 to 15.04
See the attached /var/log/syslog. Configuration of ethernet fails: May 22 15:10:33 bonobo NetworkManager[1053]: error [1432332633.395458] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 10.0.0.0/22 via 10.0.1.1 dev eth0 metric 100 mss 0 src user: Unspecific failure May 22 15:10:33 bonobo NetworkManager[1053]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) failed May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): device state change: ip-config - failed (reason 'config-failed') [70 120 4] May 22 15:10:33 bonobo NetworkManager[1053]: warn Activation (eth0) failed for connection 'Auto Ethernet' May 22 15:10:33 bonobo NetworkManager[1053]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): device state change: failed - disconnected (reason 'none') [120 30 0] May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): deactivating device (reason 'none') [0] ** Attachment added: syslog file https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452119/+attachment/4402722/+files/syslog -- 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/1452119 Title: ethernet interface broken after upgrade from 14.10 to 15.04 Status in network-manager package in Ubuntu: New Bug description: After upgrading, the ethernet connection doesn't connect. If I run ifconfig with the ethernet unplugged, I get: % ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:293047 errors:0 dropped:1 overruns:0 frame:0 TX packets:341795 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75754614 (75.7 MB) TX bytes:77108082 (77.1 MB) Interrupt:38 With the ethernet plugged in, I get: % ifconfig eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:293286 errors:0 dropped:1 overruns:0 frame:0 TX packets:342195 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75797513 (75.7 MB) TX bytes:77249665 (77.2 MB) Interrupt:38 The differences in the outputs are that (a) RUNNING, (b) packets received and transmitted after plugging it in, although no ip address is reported. % lspci -nnk | grep -iEA3 (ethernet|network) 03:00.0 Ethernet controller [0200]: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller [197b:0250] (rev 05) Subsystem: CLEVO/KAPOK Computer Device [1558:7100] Kernel driver in use: jme 03:00.1 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2392] (rev 90) -- 04:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] [8086:0091] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6230 AGN [8086:5201] Kernel driver in use: iwlwifi 05:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (rev 30) If I run % sudo ifconfig eth0 down % sudo ifconfig eth0 up System Settings/Network/Wired show the interface activate briefly, then go back to the disconnected state. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 5 10:38:15 2015 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2013-05-02 (733 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-control-center UpgradeStatus: Upgraded to vivid on 2015-04-26 (8 days ago) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452119] Re: ethernet interface broken after upgrade from 14.10 to 15.04
See the attached /var/log/syslog. Configuration of ethernet fails: May 22 15:10:33 bonobo NetworkManager[1053]: error [1432332633.395458] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 10.0.0.0/22 via 10.0.1.1 dev eth0 metric 100 mss 0 src user: Unspecific failure May 22 15:10:33 bonobo NetworkManager[1053]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) failed May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): device state change: ip-config - failed (reason 'config-failed') [70 120 4] May 22 15:10:33 bonobo NetworkManager[1053]: warn Activation (eth0) failed for connection 'Auto Ethernet' May 22 15:10:33 bonobo NetworkManager[1053]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): device state change: failed - disconnected (reason 'none') [120 30 0] May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): deactivating device (reason 'none') [0] ** Attachment added: syslog file https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452119/+attachment/4402693/+files/syslog -- 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/1452119 Title: ethernet interface broken after upgrade from 14.10 to 15.04 Status in network-manager package in Ubuntu: New Bug description: After upgrading, the ethernet connection doesn't connect. If I run ifconfig with the ethernet unplugged, I get: % ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:293047 errors:0 dropped:1 overruns:0 frame:0 TX packets:341795 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75754614 (75.7 MB) TX bytes:77108082 (77.1 MB) Interrupt:38 With the ethernet plugged in, I get: % ifconfig eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:293286 errors:0 dropped:1 overruns:0 frame:0 TX packets:342195 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75797513 (75.7 MB) TX bytes:77249665 (77.2 MB) Interrupt:38 The differences in the outputs are that (a) RUNNING, (b) packets received and transmitted after plugging it in, although no ip address is reported. % lspci -nnk | grep -iEA3 (ethernet|network) 03:00.0 Ethernet controller [0200]: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller [197b:0250] (rev 05) Subsystem: CLEVO/KAPOK Computer Device [1558:7100] Kernel driver in use: jme 03:00.1 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2392] (rev 90) -- 04:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] [8086:0091] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6230 AGN [8086:5201] Kernel driver in use: iwlwifi 05:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (rev 30) If I run % sudo ifconfig eth0 down % sudo ifconfig eth0 up System Settings/Network/Wired show the interface activate briefly, then go back to the disconnected state. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 5 10:38:15 2015 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2013-05-02 (733 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-control-center UpgradeStatus: Upgraded to vivid on 2015-04-26 (8 days ago) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452119/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
@Alfonso - I just checked my Nexus5 and it the Emergency Dialer rejects the call immediately if the number entered is not an emergency number. I didn't go so far as checking the RIL trace, but as the dialog pops up right away, it's doubtful it initiated a call and got a response from the network that quickly. Also re: comment #8 items 2 3, I'm not sure I agree with your 'no restrictions' proposal. Again, I think at minimum before going down this path, we should research using libphonenumber as previously discussing with the dialer-app developers. I think we also should further investigate Android as you and I have seen quite different behavior. Let's put this on the agenda for next week's network/telephony meeting and ask the dialer-app devs to join. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1444883 Title: Emergency numbers for China (110,119) are not available in emergency mode Status in the base for Ubuntu mobile products: New Status in dialer-app package in Ubuntu: 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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
Simon: excellent work. I have a particular fondness for reading the write-ups on this time of bug. It reminds me a little of the infamous Doesn't print on Tuesdays (bug #248619). Once again, kudos to gradually narrowing down how to replicate it, then finding it and finally offering the patch. ** Changed in: nux Status: New = Confirmed ** Package changed: unity (Ubuntu) = nux (Ubuntu) ** Changed in: nux (Ubuntu) Status: New = Confirmed ** Changed in: nux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) Status in Compiz: New Status in Nux: Confirmed Status in Unity: New Status in nux package in Ubuntu: Confirmed Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370791] Re: [system-settings] When brightness is set to automatic, the slider doesn't show current value
This bug was fixed in the package indicator-power - 12.10.6+15.10.20150522-0ubuntu1 --- indicator-power (12.10.6+15.10.20150522-0ubuntu1) wily; urgency=medium [ Charles Kerr ] * When powerd updates the backlight brightness, update the indicator slider to show the new value. (LP: #1370791) -- CI Train Bot ci-train-...@canonical.com Fri, 22 May 2015 17:54:53 + ** Changed in: indicator-power (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1370791 Title: [system-settings] When brightness is set to automatic, the slider doesn't show current value Status in the base for Ubuntu mobile products: Fix Released Status in The Power Indicator: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in indicator-power package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in indicator-power source package in Vivid: New Status in powerd source package in Vivid: New Bug description: On the brightness page, there is a slider to set brightness and a checkbox to set it automatically. When I select the automatic brightness, I was expecting the slider to show the current brightness level. Instead, it just keeps the old value manually set. I find this a little confusing: I have a slider whose value I can change, but will do nothing while the checkbox is marked, and the value it shows is different from the current brightness of the screen. https://wiki.ubuntu.com/BrightnessAndDisplays#Phone: Because users have different preferences, the function should also be user- adjustable. This should be achieved by altering the display brightness manually while 'Adjust automatically' is checked. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370791/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Description changed: 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 + + + + Here is the original report from Sander Bos (now with the CVE number + included): + + OVERVIEW + + + Date: 2015-05-05 + Bug name: SCORE: Simple Coredump-Oriented Root Exploit + CVE: CVE-2015-1324 + Author: Sander Bos + Author's e-mail address: sbos _at_ sbosnet _dot_ nl + + + SUMMARY + --- + + I found a combination of vulnerabilities to lead to privilege escalation + (root exploitation) by local users in Ubuntu releases 12.04 up to and + including 15.04. Depending on configuration, remote exploitation might + be possible as well. Local exploitation can even be done as the local, + passwordless LightDM Guest account user on systems supporting it -- + indeed: from anonymous guest user to root. + + + DESCRIPTION + --- + + The Apport package creates user core dumps in the crashed process' + CWD, and does so since Bazaar revision number 602 [1] / release 0.59. + This is okay, but not always: there is a flaw in the fact that Apport + also does this, as root, for tainted/protected binaries (setuid() and + friends, capabilities(7) enabled binaries, non-readable binaries) when + the sysctl(8)'s fs.suid_dumpable variable is set to 2 (see core(5)). + This means that users can create core dumps as root, in arbitrary + directories which are otherwise write-protected for those users. + + In short: Apport should _not_ create user core dumps in the CWD in dump + mode 2 for such tainted binaries; it should either not make user core + dumps at all then, or if possible use a designated and safe directory + for that. + + All Ubuntu releases starting with 12.04 have the Apport service enabled by + default [2] (and Ubuntu has Apport installed by default for much longer). + + All Ubuntu releases starting with 12.04 (or patched that way after + their release) have sysctl(8)'s fs.suid_dumpable set to 2 by default, + through the Apport package; see bug #1194541, Create core dumps for + setuid binaries, 2013-06-25 [3]. + + Along with solving that bug (that is, adding the missing feature of + setuid core dumps), the patch to that bug report actually created a root + exploit hole in the upcoming release 13.10, as well as being backported + into the at that time supported Ubuntu releases 12.04, 12.10 and 13.04. + + The exact Apport package versions (with their Ubuntu releases) that were + patched to have fs.suid_dumpable set to 2 are: + + 2.0.1-0ubuntu17.4 (Ubuntu 12.04) + 2.6.1-0ubuntu12 (Ubuntu 12.10) + 2.9.2-0ubuntu8.3 (Ubuntu 13.04) + + The value fs.suid_dumpable=2 remained in Ubuntu ever since. The exception + to this is the systemd Apport script in Ubuntu 15.04: the option setting + fs.suid_dumpable to 2 was forgotten to be enabled here, although in the + Upstart script in Ubuntu 15.04 the option is still enabled. I recently + contacted the Apport package maintainer to make sure the systemd script + will not enable the option, as that would enable the root hole in 15.04 + with systemd (which is the default init system) as well. Please note: + 15.04 with systemd being safe regarding this vulnerabilty has nothing + to do with systemd itself. + + Please note that even though Ubuntu has the value of fs.suid_dumpable set + to 2 in releases 12.04 and later, Apport itself has been creating user + coredumps (to CWD, and also with fs.suid_dumpable=2) since Ubuntu 7.04, + which has Apport package release 0.76/0.76.1. Any system since Ubuntu + 7.04 that has had fs.suid_dumpable set to 2, even though it wasn't + Ubuntu's default, has been exploitable. Thus, the proof of concept + attached will and should essentially work on any Ubuntu release starting + with 7.04; it was in fact tested and found to be working on 7.04 itself, + but later releases until 12.04 were not tested. + + + + VULNERABLE RELEASES + --- + + The proof of concept attached should work out of the box on (and is in + fact tested to work on most of them) all of the following releases: + + 12.04 LTS + 12.04.1 LTS + 12.04.2 LTS + 12.04.3 LTS + 12.04.4 LTS + 12.04.5 LTS + 12.10 (EOL) + 13.04 (EOL) + 13.10 (EOL) +
[Touch-packages] [Bug 1445540] Re: GTK draws its own (double) window decorations under Mir
*** This bug is a duplicate of bug 1398849 *** https://bugs.launchpad.net/bugs/1398849 ** This bug has been marked a duplicate of bug 1398849 support client-side window decorations ** Tags added: gtk-mir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1445540 Title: GTK draws its own (double) window decorations under Mir Status in Mir: New Status in gtk+3.0 package in Ubuntu: Triaged Bug description: GTK draws its own window decorations under Mir. This is not ideal. It should default to letting the shell decorate all windows. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1445540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398849] Re: support client-side window decorations
Per the duplicate bug we should probably use mir_surface_type_freestyle ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided = Wishlist ** Summary changed: - support client-side window decorations + support client-side window decorations (GTK on Mir) ** Changed in: gtk+3.0 (Ubuntu) Status: New = Triaged ** Tags added: snappyrdp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1398849 Title: support client-side window decorations (GTK on Mir) Status in Mir: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Bug description: I can't find a way for telling Mir that we have decorations drawn client-side and the result is that we have two sets of decorations (and shadows) when running Gtk applications under the demo server. It would be nice if we could tell the display server that we are drawing the decorations. Also up for discussion: if the client is going to be drawing the shadows then we also need a frame extents sort of mechanism that we can use to tell Mir how large the shadows are. This needs to be compensated for when performing various window management tasks (eg: snap to edge). To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1398849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447282] Re: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs)
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1447282 Title: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) Status in ecryptfs-utils: New Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: New Bug description: I'm still sorting out the details and eliminating variables, but as far as I can tell: Steps to reproduce === 1) Install Ubuntu using GPT partitioning for the OS drive[*] 2) Choose require my password to login, and check encrypt my home directory Expected behavior === No special user interaction should be required to initialized the crytposwap other than normally logging in Actual behavior Prior to lightdm coming up, you will be prompted to enter your passphrase to unlock the cryptoswap, similar to how you would be prompted to unlock the OS drive when using full disk encryption (see attached photo). When lightdm comes up, you have to enter your password/passphrase again to login. Work-arounds === 1) This only seems to happen when using GTP partitioning, not MBR... so use MBR if you can 2) Even with GTP partitioning, booting with init=/sbin/upstart seems to reliably fix the problem, so it certainly seems systemd related Notes = * As far as I can tell, there isn't a way to force Ubiquity to create a GPT partition table when the OS drive is 2TB, but it will automatically use GPT partitioning when the OS drive is = 2TB. My particular test was done using the System76 imaging server, which by default uses GPT partitioning even when the OS drive is 2TB. SRU INFORMATION Regression potential: This is delicate as we need to fix existing installations with a post-install script. This needs to happen as defensively as possible, but errors in this can still potentially completely break your partition information. Apart from testing that in the above scenario the unencrypted swap partition is marked as no-auto and thus after a new boot you are actually using the cryptswap1 one, we also need to verify that it does not destroy working systems. Test case: (1) Install an EFI system with encrypt my home directory (You can do this in QEMU with -bios OVMF.fd); after booting the first time you will be asked to enter a passprase for the swap partition, just press enter. sudo swapon -s will say something like /dev/sda3, i. e. using unencrypted swap. After installing this update and rebooting, the bogus passphrase prompt on boot should be gone, and sudo swapon -s should say /dev/dm-0, i. e. using encrypted swap. In all these other cases the update should not do anything and booting continues to work: (2) In the above system, sudo apt-get install --reinstall ecryptfs-utils should not change partitions again, but say something like is already marked as no-auto. (3) Install an EFI system without home dir encryption (4) Install an MBR system with home dir encryption (5) Install an MBR system without home dir encryption ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:40:29 2015 EcryptfsInUse: Yes MachineType: System76, Inc. Kudu Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e6c5aea5-d57c-410d-abce-66e96175e946 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Kudu Professional dmi.board.vendor: System76, Inc. dmi.board.version: kudp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: kudp1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnKuduProfessional:pvrkudp1:rvnSystem76,Inc.:rnKuduProfessional:rvrkudp1:cvnSystem76,Inc.:ct9:cvrkudp1: dmi.product.name: Kudu Professional dmi.product.version: kudp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs-utils/+bug/1447282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1442962] Re: Dialer app reports No network even though cellular is connected
** Changed in: telepathy-ofono (Ubuntu Vivid) Importance: Undecided = Critical ** Changed in: telepathy-ofono (Ubuntu Vivid) Status: New = Confirmed ** Changed in: telepathy-ofono (Ubuntu Vivid) Status: Confirmed = In Progress ** Changed in: telepathy-ofono (Ubuntu Vivid) Assignee: (unassigned) = Tiago Salem Herrmann (tiagosh) ** Also affects: dialer-app Importance: Undecided Status: New ** Changed in: dialer-app Status: New = Confirmed ** Also affects: telepathy-ofono Importance: Undecided Status: New ** Changed in: telepathy-ofono Assignee: (unassigned) = Tiago Salem Herrmann (tiagosh) ** Changed in: telepathy-ofono Status: New = In Progress ** Changed in: dialer-app (Ubuntu) Status: Confirmed = Triaged -- 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 for Ubuntu Touch: Confirmed Status in Telepathy Ofono: In Progress Status in dialer-app package in Ubuntu: Triaged Status in telepathy-ofono package in Ubuntu: In Progress Status in telepathy-ofono source package in Vivid: In Progress 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 1458063] Re: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
Adding the following to /etc/named/named.conf.options seems to have
fixed this problem:
listen-on { 127.0.0.1; 167.114.159.29; };
This seems like a bug to me. Maybe switching to systemd created a subtle
change in order of network config + named + lxc-net start.
This is the first time I've had to edit bind's config files to have LXC
networking start at boot time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458063
Title:
Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because
named listening to UDP on LXC address
Status in lxc package in Ubuntu:
New
Bug description:
This is a clean Vivid install (rather than upgrade).
Maybe I munged something + for the life of me nothing comes to mind.
/var/log/syslog shows somehow bind is polluted with dnsmasq addresses?
All packages updated.
net8-rmt# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid
net8-rmt# uname -a
Linux ns515383.ip-167-114-159.net 3.19.0-18-generic #18-Ubuntu SMP Tue May 19
18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
net8-rmt# pkg-list | egrep -e lxc -e cgroup
cgroup-bin 0.38-1ubuntu2
cgroup-lite 1.10
libcgroup1 0.38-1ubuntu2
liblxc1 1.1.2-0ubuntu3
lxc 1.1.2-0ubuntu3
lxc-templates 1.1.2-0ubuntu3
lxcfs 0.7-0ubuntu4
lxctl 0.3.1+debian-3
python3-lxc 1.1.2-0ubuntu3
Behavior is this.
1) After reboot, lxcbr0 is missing
2) /usr/lib/x86_64-linux-gnu/lxc/lxc-net restart
reports 10.0.3.1 (set in /etc/default/lxc-net ) as being in use.
3) netstat reports bind/named has the address, at least UDP, no TCP.
4) /var/log/syslog from last boot shows this...
net8-rmt# grep 10.0.3.1 /var/log/syslog
May 22 16:03:01 ns515383 named[1355]: listening on IPv4 interface lxcbr0,
10.0.3.1#53
May 22 16:03:02 ns515383 ntpd[1453]: Listen normally on 5 lxcbr0 10.0.3.1 UDP
123
May 22 16:03:04 ns515383 lxc-net[1360]: dnsmasq: failed to create listening
socket for 10.0.3.1: Address already in use
May 22 16:03:04 ns515383 dnsmasq[1768]: failed to create listening socket for
10.0.3.1: Address already in use
May 22 16:03:06 ns515383 ntpd[1453]: Deleting interface #5 lxcbr0,
10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=4 secs
May 22 16:21:04 ns515383 dnsmasq[10991]: failed to create listening socket
for 10.0.3.1: Address already in use
May 22 16:21:30 ns515383 dnsmasq[11156]: failed to create listening socket
for 10.0.3.1: Address already in use
May 22 16:24:15 ns515383 dnsmasq[12092]: failed to create listening socket
for 10.0.3.1: Address already in use
May 22 16:25:36 ns515383 dnsmasq[12576]: failed to create listening socket
for 10.0.3.1: Address already in use
May 22 16:29:54 ns515383 dnsmasq[14015]: failed to create listening socket
for 10.0.3.1: Address already in use
May 22 16:34:55 ns515383 named[1355]: no longer listening on 10.0.3.1#53
May 22 16:35:10 ns515383 ntpd[1453]: Listen normally on 9 lxcbr0 10.0.3.1 UDP
123
May 22 16:35:26 ns515383 ntpd[1453]: Deleting interface #9 lxcbr0,
10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=16
secs
May 22 16:52:50 ns515383 ntpd[1453]: Listen normally on 11 lxcbr0 10.0.3.1
UDP 123
5) Nothing in named config referencing the LXC IP.
6) Then after server minutes, named stops listening to this address, at which
time
/usr/lib/x86_64-linux-gnu/lxc/lxc-net restart begins working as expected.
7) If /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop is issued + service bind9
restart issued,
named no longer attempts to connect to 10.0.3.1 so all's well.
Any suggestions on why named might be grabbing the LXC address at boot
time are appreciated.
I reported this as a bug, because none of the named config files reference
the LXC IP address,
so to me, named should never touch this address.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458092] [NEW] [GA-A55M-DS2, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
Public bug reported: Sound was fine until latest Kernel update ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: terrykscott 3221 F pulseaudio CurrentDesktop: Unity Date: Sat May 23 01:26:45 2015 InstallationDate: Installed on 2015-04-01 (51 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: terrykscott 3221 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [GA-A55M-DS2, Realtek ALC887-VD, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/29/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-A55M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd02/29/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A55M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A55M-DS2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1458092 Title: [GA-A55M-DS2, Realtek ALC887-VD, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Sound was fine until latest Kernel update ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: terrykscott 3221 F pulseaudio CurrentDesktop: Unity Date: Sat May 23 01:26:45 2015 InstallationDate: Installed on 2015-04-01 (51 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: terrykscott 3221 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [GA-A55M-DS2, Realtek ALC887-VD, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/29/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-A55M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd02/29/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A55M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A55M-DS2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1458092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416652] Re: Auto Completion Not Working on Upstart Job Names
Cannot select the Won't Fix option. -- 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/1416652 Title: Auto Completion Not Working on Upstart Job Names Status in upstart package in Ubuntu: New Bug description: Yes, I did report a bug with a same title. And yes, I did close it. And no, I didn't figure out why it doesn't work by digging into .bashrc .profile. So, here we are again. Sorry... To Reproduce: In Gnome Terminal: $ sudo touch /etc/init/foobar.conf $ sudo start footab Expected: foobar is auto-completed. Actually: Nothing happens. Additional Information: Upstart auto completion script uses 'initctl list' to do the trick, and running 'initctl list' as non-root only shows the session jobs. $ initctl list | grep foo $ However, it is not the case if running in a login shell. $ ssh localhost initctl list | grep foo foobar stop/waiting $ I used 'dbus-monitor --system' to see if there is something unusual. Here is what I see when I run 'initctl list' in an SSH session, but not in a non-login session. But I actually know nothing about DBus, so I don't even know for sure whether this information is relevant or not. signal sender=org.freedesktop.DBus - dest=(null destination) serial=185 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string org.freedesktop.systemd1 string :1.162 string signal sender=org.freedesktop.DBus - dest=(null destination) serial=186 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.162 string :1.162 string ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 31 19:31:21 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-27 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1416652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416652] Re: Auto Completion Not Working on Upstart Job Names
Alright. I'm closing this since we have switched to Systemd now. -- 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/1416652 Title: Auto Completion Not Working on Upstart Job Names Status in upstart package in Ubuntu: New Bug description: Yes, I did report a bug with a same title. And yes, I did close it. And no, I didn't figure out why it doesn't work by digging into .bashrc .profile. So, here we are again. Sorry... To Reproduce: In Gnome Terminal: $ sudo touch /etc/init/foobar.conf $ sudo start footab Expected: foobar is auto-completed. Actually: Nothing happens. Additional Information: Upstart auto completion script uses 'initctl list' to do the trick, and running 'initctl list' as non-root only shows the session jobs. $ initctl list | grep foo $ However, it is not the case if running in a login shell. $ ssh localhost initctl list | grep foo foobar stop/waiting $ I used 'dbus-monitor --system' to see if there is something unusual. Here is what I see when I run 'initctl list' in an SSH session, but not in a non-login session. But I actually know nothing about DBus, so I don't even know for sure whether this information is relevant or not. signal sender=org.freedesktop.DBus - dest=(null destination) serial=185 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string org.freedesktop.systemd1 string :1.162 string signal sender=org.freedesktop.DBus - dest=(null destination) serial=186 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.162 string :1.162 string ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 31 19:31:21 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-27 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1416652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458100] [NEW] Samba shares in fstab fail to mount on boot
Public bug reported: I recently upgraded Ubuntu from 14.10 to 15.04. I have 2 samba shares in /etc/fstab that used to be mounted automatically during boot. After the upgrade, the shares are no longer mounted after boot. Content of /etc/fstab : //192.168.2.3/Data /media/Data cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm 0 0 //192.168.2.3/Backups /media/Backups cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm 0 0 When booting with the default options (systemd), these two shares are not mounted after boot. But they mount properly when manually doing : mount -a The shares get mounted properly when booting if I select Upstart in GRUB. It seems that systemd does not wait for the network to be up before trying to establish the shares (and I imagine Upstart does wait for the network). Adding the option _netdev in /etc/fstab did not solve the problem. I fixed the problem by setting the shares as automount in /etc/fstab : //192.168.2.3/Data /media/Data cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm,auto,x-systemd.automount 0 0 //192.168.2.3/Backups /media/Backups cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm,auto,x-systemd.automount 0 0 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) = systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1458100 Title: Samba shares in fstab fail to mount on boot Status in systemd package in Ubuntu: New Bug description: I recently upgraded Ubuntu from 14.10 to 15.04. I have 2 samba shares in /etc/fstab that used to be mounted automatically during boot. After the upgrade, the shares are no longer mounted after boot. Content of /etc/fstab : //192.168.2.3/Data /media/Data cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm 0 0 //192.168.2.3/Backups /media/Backups cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm 0 0 When booting with the default options (systemd), these two shares are not mounted after boot. But they mount properly when manually doing : mount -a The shares get mounted properly when booting if I select Upstart in GRUB. It seems that systemd does not wait for the network to be up before trying to establish the shares (and I imagine Upstart does wait for the network). Adding the option _netdev in /etc/fstab did not solve the problem. I fixed the problem by setting the shares as automount in /etc/fstab : //192.168.2.3/Data /media/Data cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm,auto,x-systemd.automount 0 0 //192.168.2.3/Backups /media/Backups cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm,auto,x-systemd.automount 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1458100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458081] [NEW] apt-get update filling disk
Public bug reported: Cron job running apt-get update fills 200GBs of free diskspace. Cron from command line also has problem most of the time. However, some runs of apt-get update work OK. (~1/5 of the time) Sources.list: # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://archive.ubuntu.com/ubuntu vivid main restricted universe ## Major bug fix updates produced after the final release of the ## distribution. deb http://archive.ubuntu.com/ubuntu vivid-updates main restricted universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb http://archive.ubuntu.com/ubuntu vivid multiverse deb http://archive.ubuntu.com/ubuntu vivid-updates multiverse deb http://security.ubuntu.com/ubuntu/ vivid-security multiverse ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb http://archive.ubuntu.com/ubuntu vivid-backports main restricted universe #deb http://archive.ubuntu.com/ubuntu vivid-backports multiverse ## Uncomment the following two lines to add software from Canonical's ## 'partner' repository. ## This software is not part of Ubuntu, but is offered by Canonical and the ## respective vendors as a service to Ubuntu users. deb http://archive.canonical.com/ubuntu vivid partner # deb-src http://archive.canonical.com/ubuntu utopic partner deb http://security.ubuntu.com/ubuntu/ vivid-security main restricted universe (/home/wdeutsch) wdeutsch@wdeutsch-desk2%lsb_release -rd Description:Ubuntu 15.04 Release:15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri May 22 16:09:04 2015 InstallationDate: Installed on 2014-11-11 (192 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: apt UpgradeStatus: Upgraded to vivid on 2015-04-27 (25 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1458081 Title: apt-get update filling disk Status in apt package in Ubuntu: New Bug description: Cron job running apt-get update fills 200GBs of free diskspace. Cron from command line also has problem most of the time. However, some runs of apt-get update work OK. (~1/5 of the time) Sources.list: # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://archive.ubuntu.com/ubuntu vivid main restricted universe ## Major bug fix updates produced after the final release of the ## distribution. deb http://archive.ubuntu.com/ubuntu vivid-updates main restricted universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb http://archive.ubuntu.com/ubuntu vivid multiverse deb http://archive.ubuntu.com/ubuntu vivid-updates multiverse deb http://security.ubuntu.com/ubuntu/ vivid-security multiverse ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb http://archive.ubuntu.com/ubuntu vivid-backports main restricted universe #deb http://archive.ubuntu.com/ubuntu vivid-backports multiverse ## Uncomment the following two lines to add software from Canonical's
[Touch-packages] [Bug 1423770] Re: Dialer + Messages fail to send
It was on a Nexus 5, and the issue rendered the phone unusable, so I uninstalled for the time being. -- 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/1423770 Title: Dialer + Messages fail to send Status in dialer-app package in Ubuntu: Incomplete Bug description: Running on Nexus 5 Attempts to make a call, or to send a text message both fail. When making a call, it will just hang for a few seconds, then tell me call failed. When sending a text message, I can type the whole thing out, but when I press send, it just goes into thin air. Does not show up in the messages app, and the receiver does not receive anything. I also tested calling the phone from my wifes phone, and I was able to receive the call, though it didn't really recognize I was in a call, allowing me to still use the dial pad and such, until I swiped away from the dialer and then it showed green at the top saying to return to call. I tried ending the phone call from my phone and it said call failed, though they were still connected and talking to each other, so I had to cancel it on my wifes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1423770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449117] [NEW] [Ubuntu 14.04] gcc 4.8: Improve vector performance by removing unnecessary swap optimizations
You have been subscribed to a public bug: For vector memory operations, GCC generates less efficient code for little endian POWER than for big endian POWER. This is because the VSX vector loads and stores (lxvd2x, stxvd2x, lxvw4x, stxvw4x) assume a vector register element ordering where the lowest-numbered element resides in the most significant portion of the register. That is, they operate according to a big-endian element ordering no matter what endian mode the machine is running in. To generate correct code regardless of this, GCC will generate a lxvd2x/xxswapd pair of instructions for each load, and an xxswapd/stxvd2x pair of instructions for each store. The extra xxswapd instructions force the vector elements into the proper lanes, but at a cost in performance. In August 2014, I added a pass to GCC that removes the extra swap operations when they are not necessary for correctness. This greatly improves vector performance for ppc64el. This optimization can be done for computations where all of the vector operations are lane- insenstive; that is, they don't care which lanes the computations are performed in, so long as values are stored back to memory in the correct order. To take advantage of this improved performance, I've backported the swap optimization pass to GCC 4.8 in revision r221713. I would like to see this included in the next service release of 14.04 LTS. I believe this is the only Ubuntu release using GCC 4.8. A separate feature request has been opened for GCC 4.9. ** Affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bot-comment bugnameltc-123278 severity-medium targetmilestone-inin14043 -- [Ubuntu 14.04] gcc 4.8: Improve vector performance by removing unnecessary swap optimizations https://bugs.launchpad.net/bugs/1449117 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1406804] Re: Freezes when update to release 14.04 LTS
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1406804 Title: Freezes when update to release 14.04 LTS Status in xorg package in Ubuntu: Expired Bug description: When updated to release 14.04 LTS something is not working properly, the PC freezes after login and after a few minutes the screen shows crazy colors. I tried it a lot of times, downloading the iso file a few times to check if anything got corrupted. I had to reinstall release 12.04 LTS back. Last note, release 14 freezes even when I lounch live CD, not only installing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.17 ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 31 17:31:37 2014 GsettingsChanges: com.ubuntu.update-manager check-new-release-ignore 'trusty' com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1420053951 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Symptom: ubuntu-release-upgrader-core UpgradeStatus: No upgrade log present (probably fresh install) --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: versão do gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 11.405490] forcedeth :00:07.0 eth0: MSI enabled [ 50.030311] audit_printk_skb: 171 callbacks suppressed [ 50.030316] type=1400 audit(1427111674.315:69): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/usr/share/gvfs/remote-volume-monitors/ pid=2150 comm=mission-control requested_mask=r denied_mask=r fsuid=1000 ouid=0 DistUpgraded: Fresh install DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.13.0-32-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-43-generic, x86_64: installed nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) JockeyStatus: xorg:nvidia_304 - Driver de aceleração de vídeo NVIDIA (Proprietário, Habilitado, Em uso) xorg:nvidia_304_updates - Driver gráfico de aceleração NVIDIA (atualizações pós instalação) (Proprietário, Desativado, Não está em uso) Lsusb: Bus 002 Device 003: ID 1c4f:0003 SiGma Micro HID controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: xorg 1:7.6+12ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=07b50d8a-8bbe-4ec1-a9ea-5293a74a135f ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13 Tags: precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM SE2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890
[Touch-packages] [Bug 1445271] Re: Try to preview multiple pages per sheet into print dialog does not work.
** Changed in: gtk Status: Unknown = Confirmed ** Changed in: gtk Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1445271 Title: Try to preview multiple pages per sheet into print dialog does not work. Status in GTK+ GUI Toolkit: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Ubuntu 14.10 (Unity) amd64 Cups: 1.7.5-3ubuntu3.1 hplip: 3.14.6-1ubuntu1 libgtk-3-0:amd 3.12.2-0ubun amd64 Example with Evince program: I try to preview into print dialog 2 (or more) pages per sheet.With a PDF file, the opened preview windows shows only an empty page when I choose 2 pages per sheet, and only shows one miniature page ( but several pages are show stacked on top of each other, overlapping ) when choose 4 or more pages per sheet . The same file, but convert to POSTSCRIPT (with pdftops ), shows always only 1 page, no matter what number of pages per sheet I choose. The same behaviors occurs with GEdit program for example. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1445271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
The attachment Patch for nux-4.0.7+14.10.20141007 seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) Status in Compiz: New Status in Nux: Confirmed Status in Unity: New Status in nux package in Ubuntu: Confirmed Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449051]
Thank you! Pushed with trivial fix for this warning:
up-device-supply.c: In function 'up_device_supply_coldplug':
up-device-supply.c:989:6: warning: suggest parentheses around assignment used
as truth value [-Wparentheses]
if (dir = g_dir_open (subdir, 0, error)) {
^
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1449051
Title:
Upower doesn't handle bluetooth mice properly
Status in Upower:
Fix Released
Status in upower package in Ubuntu:
Fix Committed
Bug description:
I have a bluetooth Logitech M557, and it is being mis-detected by
Upower as a battery instead of a mouse:
Device: /org/freedesktop/UPower/devices/battery_hid_00o1fo20of5oabob5_battery
native-path: hid-00:1f:20:f5:ab:b5-battery
model:Bluetooth Mouse M557
power supply: no
updated: Mon 27 Apr 2015 10:05:22 AM EDT (13 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable:yes
state: discharging
warning-level: none
energy: 0 Wh
energy-empty:0 Wh
energy-full: 0 Wh
energy-full-design: 0 Wh
energy-rate: 0 W
percentage: 100%
capacity:100%
icon-name: 'battery-full-symbolic'
History (charge):
1430143522100.000 discharging
The patch available in the upstream bug improves the situation by parsing it
as a hid device, but then mistakes it for a keyboard:
https://bugs.freedesktop.org/show_bug.cgi?id=86510
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: upower 0.99.2-2
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 27 10:04:20 2015
InstallationDate: Installed on 2013-11-26 (516 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64
(20131016.1)
SourcePackage: upower
UpgradeStatus: Upgraded to vivid on 2015-03-07 (50 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1449051/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427264] Re: using ecryptfs, creating frameworks fail to bind mount issues
** Changed in: schroot (Debian) Status: Unknown = Confirmed -- 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/1427264 Title: using ecryptfs, creating frameworks fail to bind mount issues Status in click package in Ubuntu: Triaged Status in schroot package in Ubuntu: In Progress Status in schroot package in Debian: Confirmed Bug description: Using vivid creating framework fails for ecryptfs users, the issue is similar to bug #769595 The userdir is mounted in a way which makes unmounts fail E: 10mount: umount: /var/lib/schroot/mount/click-ubuntu-sdk-14.10 -armhf-ec6aaf62-31e0-47e9-b2f8-73f0b038fb4d/home/user: target is busy E: 10mount: (In some cases useful info about processes that E: 10mount: use the device is found by lsof(8) or fuser(1).) changing the fstab line to be /home/user /home/user none rw,bind0 0 workarounds the issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264/+subscriptions -- Mailing list: https://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 1456863] Re: package gir1.2-gdata-0.0 0.16.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Good Day Marc, I thank you for your response and this type of communication we all need because it brings comradely, trust and stability to the whole Linux and Ubuntu crew. I for one will and is part of the crew and wanting to learn more from Oracles of knowledge. Thank you much this meant a lot to me the communication line is what will come us together. MCGO On Fri, May 22, 2015 at 7:18 AM, Marc Deslauriers marc.deslauri...@canonical.com wrote: Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1456863 Title: package gir1.2-gdata-0.0 0.16.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libgdata package in Ubuntu: New Bug description: Error in terminal ProblemType: Package DistroRelease: Ubuntu 15.10 Package: gir1.2-gdata-0.0 0.16.1-1 ProcVersionSignature: Ubuntu 3.19.0-17.17-lowlatency 3.19.6 Uname: Linux 3.19.0-17-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue May 19 23:40:59 2015 DuplicateSignature: package:gir1.2-gdata-0.0:0.16.1-1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-05-20 (0 days ago) InstallationMedia: Ubuntu-Studio 15.10 Wily Werewolf - Alpha amd64 (20150517) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.9ubuntu1 SourcePackage: libgdata Title: package gir1.2-gdata-0.0 0.16.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgdata/+bug/1456863/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgdata in Ubuntu. https://bugs.launchpad.net/bugs/1456863 Title: package gir1.2-gdata-0.0 0.16.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libgdata package in Ubuntu: New Bug description: Error in terminal ProblemType: Package DistroRelease: Ubuntu 15.10 Package: gir1.2-gdata-0.0 0.16.1-1 ProcVersionSignature: Ubuntu 3.19.0-17.17-lowlatency 3.19.6 Uname: Linux 3.19.0-17-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue May 19 23:40:59 2015 DuplicateSignature: package:gir1.2-gdata-0.0:0.16.1-1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-05-20 (0 days ago) InstallationMedia: Ubuntu-Studio 15.10 Wily Werewolf - Alpha amd64 (20150517) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.9ubuntu1 SourcePackage: libgdata Title: package gir1.2-gdata-0.0 0.16.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgdata/+bug/1456863/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Branch linked: lp:~michihenning/unity-scopes-api/loop-fix -- 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 the base for Ubuntu mobile products: Confirmed Status in unity-scopes-api package in Ubuntu: In Progress 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/canonical-devices-system-image/+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] Re: Aggregator can't subsearch the same child twice to get different depts
See the linked branch. The loop detector now triggers only if the query is identical in all respects, that is, query string, department, filter state, user data, and metadata are identical. If any of these differ, the query is forwarded as usual. -- 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 the base for Ubuntu mobile products: Confirmed Status in unity-scopes-api package in Ubuntu: In Progress 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/canonical-devices-system-image/+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 1449051] Re: Upower doesn't handle bluetooth mice properly
** Changed in: upower Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1449051 Title: Upower doesn't handle bluetooth mice properly Status in Upower: Fix Released Status in upower package in Ubuntu: Fix Committed Bug description: I have a bluetooth Logitech M557, and it is being mis-detected by Upower as a battery instead of a mouse: Device: /org/freedesktop/UPower/devices/battery_hid_00o1fo20of5oabob5_battery native-path: hid-00:1f:20:f5:ab:b5-battery model:Bluetooth Mouse M557 power supply: no updated: Mon 27 Apr 2015 10:05:22 AM EDT (13 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 0 Wh energy-empty:0 Wh energy-full: 0 Wh energy-full-design: 0 Wh energy-rate: 0 W percentage: 100% capacity:100% icon-name: 'battery-full-symbolic' History (charge): 1430143522100.000 discharging The patch available in the upstream bug improves the situation by parsing it as a hid device, but then mistakes it for a keyboard: https://bugs.freedesktop.org/show_bug.cgi?id=86510 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upower 0.99.2-2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 27 10:04:20 2015 InstallationDate: Installed on 2013-11-26 (516 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: upower UpgradeStatus: Upgraded to vivid on 2015-03-07 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1449051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458100] [NEW] Samba shares in fstab fail to mount on boot
You have been subscribed to a public bug: I recently upgraded Ubuntu from 14.10 to 15.04. I have 2 samba shares in /etc/fstab that used to be mounted automatically during boot. After the upgrade, the shares are no longer mounted after boot. Content of /etc/fstab : //192.168.2.3/Data /media/Data cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm 0 0 //192.168.2.3/Backups /media/Backups cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm 0 0 When booting with the default options (systemd), these two shares are not mounted after boot. But they mount properly when manually doing : mount -a The shares get mounted properly when booting if I select Upstart in GRUB. It seems that systemd does not wait for the network to be up before trying to establish the shares (and I imagine Upstart does wait for the network). Adding the option _netdev in /etc/fstab did not solve the problem. I fixed the problem by setting the shares as automount in /etc/fstab : //192.168.2.3/Data /media/Data cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm,auto,x-systemd.automount 0 0 //192.168.2.3/Backups /media/Backups cifs guest,uid=htpc,gid=htpc,iocharset=utf8,dir_mode=0777,noperm,auto,x-systemd.automount 0 0 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- Samba shares in fstab fail to mount on boot https://bugs.launchpad.net/bugs/1458100 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
** Branch linked: lp:~bregma/nux/lp-1379960 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) Status in Compiz: New Status in Nux: Confirmed Status in Unity: New Status in nux package in Ubuntu: Confirmed Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Changed in: unity-scopes-api (Ubuntu) Status: New = In Progress -- 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 the base for Ubuntu mobile products: Confirmed Status in unity-scopes-api package in Ubuntu: In Progress 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/canonical-devices-system-image/+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 1449117] Re: [Ubuntu 14.04] gcc 4.8: Improve vector performance by removing unnecessary swap optimizations
** Package changed: ubuntu = gcc-4.8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1449117 Title: [Ubuntu 14.04] gcc 4.8: Improve vector performance by removing unnecessary swap optimizations Status in gcc-4.8 package in Ubuntu: New Bug description: For vector memory operations, GCC generates less efficient code for little endian POWER than for big endian POWER. This is because the VSX vector loads and stores (lxvd2x, stxvd2x, lxvw4x, stxvw4x) assume a vector register element ordering where the lowest-numbered element resides in the most significant portion of the register. That is, they operate according to a big-endian element ordering no matter what endian mode the machine is running in. To generate correct code regardless of this, GCC will generate a lxvd2x/xxswapd pair of instructions for each load, and an xxswapd/stxvd2x pair of instructions for each store. The extra xxswapd instructions force the vector elements into the proper lanes, but at a cost in performance. In August 2014, I added a pass to GCC that removes the extra swap operations when they are not necessary for correctness. This greatly improves vector performance for ppc64el. This optimization can be done for computations where all of the vector operations are lane- insenstive; that is, they don't care which lanes the computations are performed in, so long as values are stored back to memory in the correct order. To take advantage of this improved performance, I've backported the swap optimization pass to GCC 4.8 in revision r221713. I would like to see this included in the next service release of 14.04 LTS. I believe this is the only Ubuntu release using GCC 4.8. A separate feature request has been opened for GCC 4.9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1449117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458014] Re: audit_printk_skb slowing down boot
It's highly unlikely that the audit_printk_skb() function is itself slowing down your boot; it is designed to operate with extremely low overhead, and the ratelimiting that is in effect here means that the slowest portion of the function, actually writing characters to the system log, is skipped entirely. Probably what is actually slow is recompiling AppArmor policies; this is an extremely computational heavy task that has been subject to extensive optimization. We're planning further caching efforts in the future to reduce the number of times that the policies must be recomputed. Chances are quite good a second reboot, immediately after this one, would run faster, since the profiles would probably not need to be rebuilt immediately. Thanks -- 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/1458014 Title: audit_printk_skb slowing down boot Status in apparmor package in Ubuntu: New Bug description: Subjectively, my system slowed down after the recent GRUB update. As you can see from the following, audit_printk_skb is consuming a lot of boot time: [ 13.243280] vboxdrv: Successfully loaded version 4.3.10_Ubuntu (interface 0x001a0007). [ 13.257947] vboxpci: IOMMU not found (not registered) [ 13.862999] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 13.865996] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 14.195776] r8169 :04:00.0 eth0: link down [ 14.195796] r8169 :04:00.0 eth0: link down [ 14.195827] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 14.196138] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 15.769090] r8169 :04:00.0 eth0: link up [ 15.769097] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 16.223084] init: plymouth-upstart-bridge main process ended, respawning [ 42.424836] audit_printk_skb: 195 callbacks suppressed [ 42.424839] type=1400 audit(1431891089.974:77): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2632 comm=apparmor_parser [ 42.424844] type=1400 audit(1431891089.974:78): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2632 comm=apparmor_parser [ 42.425185] type=1400 audit(1431891089.974:79): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2632 comm=apparmor_parser (END) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apparmor 2.8.95~2430-0ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CurrentDesktop: Unity Date: Fri May 22 14:18:46 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-29 (388 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=8cf458ab-4ff9-4505-9a16-27da1ea7ec10 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1458014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458046] [NEW] [touch] NetworkManager needs to inhibit sleep if hotspot is active
Public bug reported: As Ubuntu touch uses an auto-suspend model, it's possible for the system to be suspended while a user has a hotspot active and in use. In order to prevent such behavior, we should modify NetworkManager to inhibit suspend via powerd's DBus interface when hotspot is active and one or more clients are connected to the hotspot. As a first pass, inhibiting suspend when hotspot is active would probably be sufficient. This could probably be implemented via a NM dispatcher script, which would run when the hotspot is activated. ** Affects: network-manager (Ubuntu) Importance: Undecided Assignee: Tony Espy (awe) Status: Confirmed ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Tony Espy (awe) ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1458046 Title: [touch] NetworkManager needs to inhibit sleep if hotspot is active Status in network-manager package in Ubuntu: Confirmed Bug description: As Ubuntu touch uses an auto-suspend model, it's possible for the system to be suspended while a user has a hotspot active and in use. In order to prevent such behavior, we should modify NetworkManager to inhibit suspend via powerd's DBus interface when hotspot is active and one or more clients are connected to the hotspot. As a first pass, inhibiting suspend when hotspot is active would probably be sufficient. This could probably be implemented via a NM dispatcher script, which would run when the hotspot is activated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1458046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442105] Re: GPS not working on my BQ Ubuntu Touch
How I made my Ubuntu BQ GPS to work (with advices from BQ Support) First I have gone outside and check this on the phone: System Settings Security and Privacy Location access Using GPS, anonymized Wi-Fi and cellular network info. And after that I reboot. I checked again that all location setting to be enabled and in 2 minutes the GPS worked for the first time I bought the phone. I supose there will be more updates on software that we will not need to reboot to make something to work properly. Another tool that can help you with checking hardware problem on GPS is Sensor status from Ubuntu store. Repeat the above steps and check the GPS status on that app. This steps helped me and in my opinion this bug is closed using those sugestion I described. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1442105 Title: GPS not working on my BQ Ubuntu Touch Status in indicator-location package in Ubuntu: Confirmed Bug description: Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch from BQ (I am on update 20), but the app dont detect my location. I have to mention that I check Here terms Condition and GPS and location are checked. I attached some screenshot from what I did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file
We're having the same problem running dhcpd under trusty. As a workaround, if we make the file attribute changes in #25, is this the only thing that needs to be done? Can we also change chown root:root to dhcpd:dhcpd for /var/lib/dhcp/* in isc-dhcp-server.conf, too? Thanks. -John -- 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/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp source package in Trusty: Confirmed Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432413] Re: Synaptic Touchpad xevents are hijacked under X
I have to get another disk to test with vivid so it will take a few days but my plan is to keep the 14.02 LTS for another few years and for the moment does the problem occur only after a few minutes with an active program on the desktop (if all windows are minimized does the problem not occur) so it is not difficult to recreate it for troubleshooting purpose. -- 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/1432413 Title: Synaptic Touchpad xevents are hijacked under X Status in xorg package in Ubuntu: Incomplete Bug description: Synaptic Touchpad xevents are hijacked under X11. I have a problem with the synaptic touch-pad on my Acer Aspire that started around a week ago. The problem can be described as that there is a massive amount of xevents being generated and appearing to originate from the touch-pad even though the touch-pad is not used. I have tested the HW which seems to work fine. The test performed is to start a terminal session (Ctrl + Alt + 2) before the fault occurs and check the xevents by running ~$ sudo evtest /dev/input/eventX where the X to use is found in /proc/bus/input/devices and found by running ~$ cat /proc/bus/input/devices |grep mouse No matter how much the touch-pad is used will the console show the corresponding events which indicates that HW and driver works OK as long it is not under X When the problem has occurred (in Desktop mode) is it easy (but inconvenient) to get back to normal by key combo Fn+F7 twice, turn off touch-pad and then turn on again. And more, one can get unlucky in the sense that the generated events could click somewhere one do not want to click. During the problem is it impossible to use the mouse since it flies around (mostly going in a bottom to top of screen direction) but one can check the generated events using evtest again. How can I help troubleshooting the problem? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 19:51:13 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0933] InstallationDate: Installed on 2015-02-21 (22 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Acer Aspire E3-112 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=a97d0b51-4244-48ca-ba87-bc3a38a8b62d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-112 dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Mar 15 18:59:07 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1576 vendor BOE xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1447654] Re: installing policykit-1 hangs under systemd
Hi, I just encountered this bug on a mini computer board (Intel Celeron J1900 x4, 2GHz with 4096 MB of RAM). Ubuntu 15.04 Server for AMD64 I can give you every details for having this reproduced With a minimalist installation as I always do with Debian (approximately nothing is installed but Linux Kernel and apt-get - then I choose what I need and nothing else) For doing that : - I used expert mode by pressing F6 at the boot of the installer (Legacy mode, not UEFI). - I didn't execute Select and Install software. (because it loads and install many things I'm not going to use) I use the following sources.list : http://62.210.206.25:82/html/sources.list (extracted from a fully installed Ubuntu server 15.04 amd64) because when Select and Install software is not done, sources.list is keept untouched (so I replaced it manually from a live usb stick) Then I typed the following commands apt-get update apt-get upgrade apt-get install mate-desktop-environment lightdm Then it's freezing many times, whatever I try it always fails returning the same error : Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) also : error calling StartServiceByName for org.freedesktop.PolicyKit or also : cannot open /run/systemd/was-enabled no such file But it continues after a while and then finish by Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: installing policykit-1 hangs under systemd Status in policykit-1 package in Ubuntu: Confirmed Status in policykit-1 source package in Vivid: Fix Released Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. SRU INFORMATION === Test case: - Boot a minimal VM and purge apport policykit-1, or do the above netboot installation. - sudo apt-get install policykit-1 apport - The above hangs on the systemd triggers and eventually fails in vivid final. It should succeed fine with this update. Regression potential: Very low: polkitd does not keep state, so one can restart it fine. The postinst shell modification is simple and obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+subscriptions -- Mailing list: https://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 1390625] Re: mouse cursor gets corrupted
Thanks for the feedback. Yes I read the xorg patch can help. I also read that updating the linux kernel can help. Like I mentioned I've switched back to Luna for now, and if the xorg update causes a few other things I think Luna will do just fine. I will certainly check back and see how things are moving. Sent from Samsung Mobile on O2 Original message From: Alessandro alessandro.olivi...@gmail.com Date: 22/05/2015 08:28 (GMT+00:00) To: ljo...@gmail.com Subject: [Bug 1390625] Re: mouse cursor gets corrupted The xserver-xorg installiation fixes the issue but, in my case, it introduces another issue. A great number of artifacts, little white or black horizontal lines sometimes appear/disappear on the screen in relation with the mouse movement. The solution of changing the intel method of accelleration to uxa works too, but it has the same side effects. I suspect that installing xserver-xorg in some way changes the accelleration to uxa... -- You received this bug notification because you are subscribed to a duplicate bug report (1455603). https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC
[Touch-packages] [Bug 1383213] Re: [Dash] Categorydropbox touch state
It should inherit the standard list item pressed state. ** Changed in: ubuntu-ux 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/1383213 Title: [Dash] Categorydropbox touch state Status in Ubuntu UX bugs: Fix Released Status in unity8 package in Ubuntu: New Bug description: A touch state is needed. Light grey colour, same as on the rest of the UI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413801] Re: TextField's placeHolderText invisible inside a dialog
Hi guys, The issue in this case is the text color. Can we use this color instead, please? #5D5D5D Would you mind to provide a screenshot when ready, please? Thank you very much, indeed. Olivia -- 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/1413801 Title: TextField's placeHolderText invisible inside a dialog Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Using a dark background in an application, a Dialog and a TextField inside that Dialog renders the placeholderText nearly invisible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1413801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422700] Re: 'Dash search' option makes no sense, and may be obsolete
I sympathize with Iain's viewpoint, and I look forward to seeing whether https://fixubuntu.com/ is updated to cover Ubuntu Touch. However, the breadth of the Dash in Ubuntu Touch makes a global Dash setting infeasible. If it existed and was set to local searches only, the Ubuntu Store, News, Today, and NearBy [sic] scopes would not work at all, and the Videos scope would usually be a wasteland. If those were standalone apps, as their equivalents are on other mobile platforms, then a Dash privacy setting would become feasible. Anyway, this does not require any design work: for the reason I just described, I removed the Dash search setting from the design in April 2014. https://wiki.ubuntu.com/SecurityAndPrivacySettings?action=diffrev2=39rev1=38 (It's nice to be wanted, but the design specification is the #1 result in a Google search for Ubuntu Security Privacy settings. If anyone has ideas for how to make it even easier for people to check the spec, before saying things like Worth checking with mpt or this needs some sort of review by design, please let me know.) ** Changed in: ubuntu-system-settings (Ubuntu) Status: In Progress = Triaged ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: Matthew Paul Thomas (mpt) = (unassigned) ** No longer affects: ubuntu-ux -- 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/1422700 Title: 'Dash search' option makes no sense, and may be obsolete Status in the base for Ubuntu mobile products: New Status in ubuntu-system-settings package in Ubuntu: Triaged Status in unity-scopes-api package in Ubuntu: In Progress Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: ubuntu-touch/stable/bq-aquaris #17 In system settings | Security Privacy, there is a setting 'Dash Search', with the options 'phone only' and 'phone and internet'. This used to releate to whether remote searches were included by the managed dash when it searched the whole phone. It no longer does this, so this setting may be obsolete. Flipping it to phone only did not prevent scopes from searching the internet. Should this setting still exist? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457840] Re: 5.4.1+dfsg-4ubuntu1 causes dependencies to complain about the -fPIC required for reduce-relocations
** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided = Critical -- 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/1457840 Title: 5.4.1+dfsg-4ubuntu1 causes dependencies to complain about the -fPIC required for reduce-relocations Status in qtbase-opensource-src package in Ubuntu: New Bug description: Causes autopkgtests to fail. So the enabling of patches is not currently good for us because we need to actually keep -fPIC out of ARM builds and keep -fPIE enabled there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1457840/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Package changed: xorg (Ubuntu) = gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1453703 Title: Gnome Shell Status in gnome-shell package in Ubuntu: New 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/gnome-shell/+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 1457810] [NEW] Fail to remove package fron system
Public bug reported: Hi installed one package eg network-extra but apt is unable to remove from system. Alls apt command reveals presence an network-extra on system; $ dpkg -L network-extra /. /usr /usr/share /usr/share/doc /usr/share/doc/network-extra /usr/share/doc/network-extra/copyright /usr/share/doc/network-extra/changelog.Debian.gz /etc /etc/NetworkManager /etc/NetworkManager/dispatcher.d /etc/NetworkManager/dispatcher.d/pre-down.d /etc/NetworkManager/dispatcher.d/pre-down.d/99check_interface /etc/NetworkManager/dispatcher.d/pre-down.d/00check_interface /etc/NetworkManager/dispatcher.d/pre-up.d /etc/NetworkManager/dispatcher.d/pre-up.d/99check_interface /etc/NetworkManager/dispatcher.d/pre-up.d/00check_interface /etc/NetworkManager/dispatcher.d/pre-up.d/98set_param /etc/NetworkManager/dispatcher.d/99check_interface /etc/default /etc/default/network-extra $ dpkg -s network-extra Package: network-extra Status: install ok installed Priority: optional Section: net Installed-Size: 51 Maintainer: Corcodel Marian corcodel.mar...@gmail.com Architecture: all Version: 1.0-1 Depends: network-manager (= 0.9.10.0-4ubuntu15.1) Conffiles: /etc/NetworkManager/dispatcher.d/99check_interface a43b3564528c4774d8c96d7614c24eb9 /etc/NetworkManager/dispatcher.d/pre-down.d/00check_interface 03d39e429a308b0d40b829bdef1b72c3 /etc/NetworkManager/dispatcher.d/pre-down.d/99check_interface 09250e07bfa15f1268d7f02aaf9190e0 /etc/NetworkManager/dispatcher.d/pre-up.d/00check_interface 0542b5a201a0a339fceb964398d3800c /etc/NetworkManager/dispatcher.d/pre-up.d/98set_param 37eec2043ddc45771f22fcb1ab1b /etc/NetworkManager/dispatcher.d/pre-up.d/99check_interface 1c8e358376e940befaa59d3cf95ecda8 /etc/default/network-extra ad8095f0112fa512896c6ea5d711f997 Description: Correct missing interfaces when NetworkManager working insert long description, indented with spaces Homepage: insert the upstream URL, if relevant But when want to remove fails ocurred. Solved on least but only when run : dpkg -L network-extra ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CurrentDesktop: Unity Date: Fri May 22 12:41:50 2015 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- 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/1457810 Title: Fail to remove package fron system Status in apt package in Ubuntu: New Bug description: Hi installed one package eg network-extra but apt is unable to remove from system. Alls apt command reveals presence an network-extra on system; $ dpkg -L network-extra /. /usr /usr/share /usr/share/doc /usr/share/doc/network-extra /usr/share/doc/network-extra/copyright /usr/share/doc/network-extra/changelog.Debian.gz /etc /etc/NetworkManager /etc/NetworkManager/dispatcher.d /etc/NetworkManager/dispatcher.d/pre-down.d /etc/NetworkManager/dispatcher.d/pre-down.d/99check_interface /etc/NetworkManager/dispatcher.d/pre-down.d/00check_interface /etc/NetworkManager/dispatcher.d/pre-up.d /etc/NetworkManager/dispatcher.d/pre-up.d/99check_interface /etc/NetworkManager/dispatcher.d/pre-up.d/00check_interface /etc/NetworkManager/dispatcher.d/pre-up.d/98set_param /etc/NetworkManager/dispatcher.d/99check_interface /etc/default /etc/default/network-extra $ dpkg -s network-extra Package: network-extra Status: install ok installed Priority: optional Section: net Installed-Size: 51 Maintainer: Corcodel Marian corcodel.mar...@gmail.com Architecture: all Version: 1.0-1 Depends: network-manager (= 0.9.10.0-4ubuntu15.1) Conffiles: /etc/NetworkManager/dispatcher.d/99check_interface a43b3564528c4774d8c96d7614c24eb9 /etc/NetworkManager/dispatcher.d/pre-down.d/00check_interface 03d39e429a308b0d40b829bdef1b72c3 /etc/NetworkManager/dispatcher.d/pre-down.d/99check_interface 09250e07bfa15f1268d7f02aaf9190e0 /etc/NetworkManager/dispatcher.d/pre-up.d/00check_interface 0542b5a201a0a339fceb964398d3800c /etc/NetworkManager/dispatcher.d/pre-up.d/98set_param 37eec2043ddc45771f22fcb1ab1b /etc/NetworkManager/dispatcher.d/pre-up.d/99check_interface 1c8e358376e940befaa59d3cf95ecda8 /etc/default/network-extra ad8095f0112fa512896c6ea5d711f997 Description: Correct missing interfaces when NetworkManager working insert long description, indented with spaces Homepage: insert the upstream URL, if relevant But when want to remove fails ocurred. Solved on least but only when run : dpkg -L network-extra ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu4 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1443843] Re: [clock-app] Time picker width too small leading to accidental changes in other columns
Time picker is being redesigned and prototyped. ** Changed in: ubuntu-ux Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1443843 Title: [clock-app] Time picker width too small leading to accidental changes in other columns Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UX bugs: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Ubuntu Touch 14.10 (r20) running on BQ Ubuntu Edition. Issue: The time picker occupies the entire width of the alarm page and yet the actual dials occupy only a fraction of that width resulting in users accidentally changing other column values. May be we should increase the width of the dials? Screenshot: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui- toolkit/+bug/1443843/+attachment/4375026/+files/timepicker.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1443843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 998223] Re: Turns on IPv6 privacy extensions regardless of settings in 10-ipv6-privacy.conf
Also in 15.04. -- 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/998223 Title: Turns on IPv6 privacy extensions regardless of settings in 10-ipv6-privacy.conf Status in network-manager package in Ubuntu: Fix Released Bug description: After installing the latest network-manager package that fixes bug 990011, I noticed that my IPv6 address was suddenly different because IPv6 privacy extensions had been turned on. Turning them off in /etc/sysctl.d/10-ipv6-privacy.conf doesn't stop network-manager from enabling it. I'm using the default automatically generated wired connection, so there are no connection settings in /etc/NetworkManager /system-connections. If I change some settings so that NM writes the connection to system- connections and then add ip6-privacy=0 to the configuration the privacy extensions are turned off, but it would be nice if that was also the case when it is turned of using /etc/sysctl.d/10-ipv6-privacy.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/998223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450031] Re: On daily anti-virus run with Clam TK
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1450031 Title: On daily anti-virus run with Clam TK Status in xorg package in Ubuntu: New Bug description: I conisistently get xorg's when I run the Clam TK program and it is often related to either of the web browsers that I use- FireFox or Chrome ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-49.83-lowlatency 3.13.11-ckt17 Uname: Linux 3.13.0-49-lowlatency i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Apr 29 06:49:08 2015 DistUpgraded: 2014-05-03 05:34:08,374 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01ad] Subsystem: Dell Device [1028:01ad] InstallationDate: Installed on 2014-04-21 (372 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. OptiPlex GX620 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-lowlatency root=UUID=1c46af73-b8d1-43cf-9a92-0d05e5542590 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-03 (361 days ago) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0PJ149 dmi.board.vendor: Dell Inc. dmi.chassis.type: 16 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PJ149:rvr:cvnDellInc.:ct16:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 28 19:47:12 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 768 vendor ACR xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1450031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457853] [NEW] package apport 2.17.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Durante un aggiornamento il sistema mi segnala di non poter eseguire l'aggiornamento. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 ApportLog: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CrashReports: 600:0:118:276857:2015-05-22 11:19:33.174982070 +0200:2015-05-22 11:19:34.174982070 +0200:/var/crash/apport.0.crash 640:1000:118:887216:2015-05-16 21:00:39.485809979 +0200:2015-05-17 16:23:08.241841979 +0200:/var/crash/_usr_bin_openbox.1000.crash Date: Fri May 22 11:19:33 2015 DuplicateSignature: package:apport:2.17.2-0ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-15 (6 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Release i386 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: apport Title: package apport 2.17.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 vivid -- 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/1457853 Title: package apport 2.17.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: Durante un aggiornamento il sistema mi segnala di non poter eseguire l'aggiornamento. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 ApportLog: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CrashReports: 600:0:118:276857:2015-05-22 11:19:33.174982070 +0200:2015-05-22 11:19:34.174982070 +0200:/var/crash/apport.0.crash 640:1000:118:887216:2015-05-16 21:00:39.485809979 +0200:2015-05-17 16:23:08.241841979 +0200:/var/crash/_usr_bin_openbox.1000.crash Date: Fri May 22 11:19:33 2015 DuplicateSignature: package:apport:2.17.2-0ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-15 (6 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Release i386 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: apport Title: package apport 2.17.2-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1457853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)
This is still broken in 14.04. The workaround from point #4 fixes the issue for me: pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg -- 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/769314 Title: System bell broken in Natty/Unity (despite heroic...) Status in Unity: Invalid Status in gnome-media package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Bug description: Binary package hint: unity This bug is about problems using the system bell in Unity or another Compiz-based environment. For problems using the system bell in Ubuntu Classic/Metacity or another Metacity-based environment, please see bug #486154. The system bell (that beep when you backspace on an empty line on a terminal, i.e.) is badly broken using the Unity environment in the Natty beta 2. By default, no sound is produced, and several misconfigurations make it difficult to produce sound either from the PC speaker or Pulse Audio's module-x11-bell. Not knowing what the desired behavior is, I can't say exactly what needs to be fixed. But the combination of the following issues makes the system quite obviously broken. 1) pcskpr is blacklisted. The pcspkr module is necessary for the PC speaker to produce sound. It is blacklisted, so regular users cannot turn the bell on. It would be nice for this to be fixed, but the attitudes displayed in #77010 suggest that it won't be. Nonetheless, I note it here because it interacts with some of the following. 2) The X bell volume is set to 0. As reported by `xset q`, the bell volume is 0 when Unity is started. Both the PC speaker and module-x11-bell respect this setting, so the volume must be turned up (with `xset b on` or `xset b 100`) for either to work. Since both the PC speaker and module-x11-bell are disabled by default, this setting only serves to frustrate attempts to turn them on; it never prevents unwanted sound. 3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11 This is a system file, not a user file, so users cannot decide whether they want this module loaded or not. They could write a script to unload the module at login (and hope the module number doesn't vary between boots), but it would be much cleaner to have the modules loaded from a user file, possibly with defaults if the user file doesn't exist. 4) Sample bell.ogg is not loaded. When module-x11-bell is loaded, it is told to use the sample bell.ogg. But no sample is loaded into Pulse Audio. Thus, module-x11-bell traps system bell events (keeping them from going to the PC speaker) without producing any sound. If module-x11-bell is loaded, the sample it calls on should be loaded as well. (To fix this, run `pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.) 5) gnome-volume-control doesn't. The Sound Effects tab of gnome-volume-control offers to set the volume and sound for system bell events, but these have no effect. This is because gnome-volume-control is trying to control system bells through metacity. Ideally, it should be rewritten to control module-x11-bell instead, but a temporary fix could be to simply disable this tab. 6) System bell settings don't transfer to the Ubuntu Classic environment. Because that is using metacity, which has it's own set of problems. See bug #486154. This has been from testing in a VM (virtualbox), but all of these behaviors have also been seen in Compiz in various previous versions of Ubuntu running on various hardware. I have reported this bug against several components, as it is really an integration issue. The eventual fix may not involve your component, but please do not mark this bug as invalid until we have at least a roadmap for fixing it. Otherwise, I fear responsibility will be passed from component to component without anything being fixed. Rationales: Unity - As the overarching environment, Unity should be responsible for getting everything integrated. Additionally, some of the problems relate to session startup settings. Pulse Audio - module-x11-bell is not loaded intelligently or correctly. Gnome Media - Own gnome-volume-control. Versions (but note the same behavior has been seen in many earlier versions): unity: 3.8.10-0ubuntu2 pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3 gnome-media: 2.32.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/769314/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app 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 dialer-app package in Ubuntu: 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 1428779] Re: [SDK] Tooltips
** Changed in: ubuntu-ux Assignee: Alex Milazzo (digitalalex) = Olga Kemmet (olga-kemmet) -- 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/1428779 Title: [SDK] Tooltips Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Point Click UIs will need a tooltip component, positioning a popover next to the cursor when Hovering the originating component UX here https://www.dropbox.com/s/rvs88whk2mjeap4/050315_Convergence%20-%20Tooltips_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422700] Re: 'Dash search' option makes no sense, and may be obsolete
** Changed in: ubuntu-system-settings (Ubuntu) Assignee: (unassigned) = Matthew Paul Thomas (mpt) -- 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/1422700 Title: 'Dash search' option makes no sense, and may be obsolete Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-system-settings package in Ubuntu: In Progress Status in unity-scopes-api package in Ubuntu: In Progress Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: ubuntu-touch/stable/bq-aquaris #17 In system settings | Security Privacy, there is a setting 'Dash Search', with the options 'phone only' and 'phone and internet'. This used to releate to whether remote searches were included by the managed dash when it searched the whole phone. It no longer does this, so this setting may be obsolete. Flipping it to phone only did not prevent scopes from searching the internet. Should this setting still exist? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1255889] Re: [system settings] Disabling scope online search in systemsettings makes it impossible to install new apps
*** This bug is a duplicate of bug 1422700 *** https://bugs.launchpad.net/bugs/1422700 ** This bug has been marked a duplicate of bug 1422700 'Dash search' option makes no sense, and may be obsolete -- 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/1255889 Title: [system settings] Disabling scope online search in systemsettings makes it impossible to install new apps Status in Ubuntu UX bugs: Fix Committed Status in unity-scope-click package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: The heated discussions regarding the online search capabilities in the Dash have led to the possibility to disable that in through systemsettings which many people use. On Touch, this introduces the problem that a user cannot browse/install any new apps any more. I think there is the need to have a dedicated application for the app store which allows to find and install new apps without having to enable full Dash online search capabilities. - Desired resolution: - In the new Unity8 Dash architecture, there is no longer a global search, users choose which lens they would like to search before performing a search. This means the issue privacy issue from Unity7 is no longer present, therefore this setting can be removed from System Settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1255889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
