[Touch-packages] [Bug 1347837] Re: can't install or remove powerd (even when with --force-all)
That looks like a systemd message. I fixed this on my own system by making a systemd config for it. Not sure if I did it right. /etc/systemd/system$ ls -l powerd.service lrwxrwxrwx 1 root root 34 Oct 26 22:26 powerd.service - /lib/systemd/system/powerd.service /etc/systemd/system$ cat powerd.service [Unit] Description=Power daemon to monitor and control system power state [Service] Type=dbus BusName=com.canonical.powerd Restart=always Environment=ANDROID_ROOT=/system ExecStart=/usr/bin/powerd -- 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/1347837 Title: can't install or remove powerd (even when with --force-all) Status in “powerd” package in Ubuntu: Invalid Bug description: powerd and ofono not correctly installed, when i tried to install unity8. Then I remove it(unity8) but ofono and powerd don't want to delete. Failed to issue method call: Unit powerd.service not loaded. invoke-rc.d: initscript powerd, action stop failed. dpkg: ошибка при обработке пакета powerd (--remove): подпроцесс установлен сценарий pre-removal возвратил код ошибки 5 (transtlate: subprocess install scenario pre-removal returned error code 5) Failed to issue method call: Unit powerd.service failed to load: No such file or directory. invoke-rc.d: initscript powerd, action start failed. dpkg: ошибка при очистке: подпроцесс установлен сценарий post-installation возвратил код ошибки 6 (transtlate: subprocess install scenario post-installation returned error code 6) При обработке следующих пакетов произошли ошибки: powerd ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: powerd 0.16+14.10.20140707-0ubuntu1 Uname: Linux 3.15-6.dmz.2-liquorix-amd64 x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 Date: Wed Jul 23 21:37:05 2014 InstallationDate: Installed on 2014-06-20 (32 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) ProcEnviron: LANGUAGE=ru TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: powerd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1347837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283826] Re: lightdm hangs after updates
Hi I very much appreciate the assistance. Im ok getting into terminal as long as its a copy and paste kinda deal, Im a gui user having moved over from windows but over the last few years I have gotten fairly familiar with what does what when it comes to ubuntu/linux... and have no problem busting out terminal or opening this or that in kate and doing some editing... I do not however have the ability to just buts out a terminal window and know what to type natively. here you go thank you.. took a while to figure out how to get into the log files as root :) thanks again :) * lightdm.conf*** [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu greeter-show-manual-login=true **end **lightdm.log* [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.10.1, UID=0 PID=1296 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/10-xubuntu.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Registered seat module xlocal [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Registered seat module surfaceflinger [+0.00s] DEBUG: Adding default seat [+0.00s] DEBUG: Seat: Starting [+0.00s] DEBUG: Seat: Creating greeter session [+0.00s] DEBUG: Seat: Creating display server of type x [+0.01s] DEBUG: Quitting Plymouth [+0.02s] DEBUG: Using VT 7 [+0.02s] DEBUG: Seat: Starting local X display on VT 7 [+0.02s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log [+0.02s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0 [+0.02s] DEBUG: DisplayServer x-0: Launching X Server [+0.02s] DEBUG: Launching process 1309: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+0.02s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0 [+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.05s] DEBUG: Loading users from org.freedesktop.Accounts [+0.05s] DEBUG: User /org/freedesktop/Accounts/User1001 added [+0.08s] DEBUG: User /org/freedesktop/Accounts/User1003 added [+0.10s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+0.11s] DEBUG: User /org/freedesktop/Accounts/User1002 added [+2.09s] DEBUG: Got signal 10 from process 1309 [+2.09s] DEBUG: DisplayServer x-0: Got signal from X server :0 [+2.09s] DEBUG: DisplayServer x-0: Connecting to XServer :0 [+2.09s] DEBUG: Launching process 1499: /sbin/prime-offload [+2.09s] DEBUG: Process 1499 exited with return value 0 [+2.09s] DEBUG: Seat: Exit status of /sbin/prime-offload: 0 [+2.10s] DEBUG: Seat: Display server ready, starting session authentication [+2.10s] DEBUG: Session pid=1505: Started with service 'lightdm-greeter', username 'lightdm' [+2.16s] DEBUG: Session pid=1505: Authentication complete with return value 0: Success [+2.16s] DEBUG: Seat: Session authenticated, running command [+2.16s] DEBUG: Session pid=1505: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter [+2.16s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+2.16s] DEBUG: Session pid=1505: Logging to /var/log/lightdm/x-0-greeter.log [+2.17s] DEBUG: Activating VT 7 [+2.17s] DEBUG: Activating login1 session /org/freedesktop/login1/session/c1 [+2.34s] DEBUG: Session pid=1505: Greeter connected version=1.10.1 [+2.71s] DEBUG: Session pid=1505: Greeter start authentication [+2.71s] DEBUG: Session pid=1748: Started with service 'lightdm', username '(null)' [+2.72s] DEBUG: Session pid=1748: Got 1 message(s) from PAM [+2.72s] DEBUG: Session pid=1505: Prompt greeter with 1 message(s) [+2.76s] DEBUG: User /org/freedesktop/Accounts/User1003 changed [+2.81s] DEBUG: User /org/freedesktop/Accounts/User1000 changed [+6.27s] DEBUG: Session pid=1505: Greeter start authentication
[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
Ryan, upstream has questions on https://bugreports.qt- project.org/browse/QTBUG-42189 please can you answer them there? -- 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/1384776 Title: Occasional hang in unity 8 dash on the phone Status in “network-manager” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Triaged Bug description: The dash is sometimes hanging on the phone. See the attached backtrace. The issue is as follows: we are maintaining a client-side tree of all NetworkManager devices. When we see that a new device has been added, we query its properties in order to build our local proxy. Doing this means that we are making QtDBus calls from a signal handler. Due to a bug in QtDBus this is not safe. libdbus-1 has a recursive lock on its DBusConnection. When the signal arrives, the lock is acquired and the sginal handler is run. The signal handler can make DBus calls (which also require the lock) because the lock is recursive. QtDBus also has a lock that is always acquired before the libdbus-1 connection lock is acquired. Unfortuntaely, the QtDBus lock is not acquired in the case of the incoming call from DBus -- only the DBus lock is. If another thread tries to do an unrelated DBus call meanwhile, it will acquire the QtDBus lock first and then the DBus lock (which is held because of the signal that arrived). Once the signal handler gets to the point of wanting to make a DBus call (in order to query the properties of the just-added network device) it will attempt to acquire the QtDBus lock. This is a lock-inversion deadlock. There are at least three bugs here: 1) QtDBus should be fixed in order to avoid this sort of lock inversion problem. Even if we fix this one situation, it seems quite likely that issues like this will arise again. 2) QNetworkManager should avoid the issue in QtDBus until such a time as it is fixed. This could be done by dispatching to a worker thread on receipt of signals so that the queries are done in a fresh call stack (without the libdbus-1 lock held). 3) Apparently the only reason we are using NetworkManager at all is in order to know if we are on a 3G connection or not (in order to avoid too much data charges). This would be much easier to do if NetworkManager provided a property that we could watch directly instead of bringing up an entire tree of objects in order to answer a very simple question. To that end I've filed https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can hopefully get addressed relatively quickly. I consider 3) to be the real fix as far as we are concerned, but we should probably ensure that the Qt people know about 1) and 2). Either of those could function as a workaround for us in the meantime, but the idea that we are creating this complex object tree to answer a simple question is ridiculous, so we should really fix that directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385793] Re: Merge 1.6-4 from debian
** Changed in: gzip (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1385793 Title: Merge 1.6-4 from debian Status in “gzip” package in Ubuntu: Fix Committed Bug description: Please merge gzip 1.6-4 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1385793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1297302] Re: Orange squares around checkboxes and radio buttons
Just installed Ubuntu 14.10 and the problem is also in that version! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1297302 Title: Orange squares around checkboxes and radio buttons Status in “ubuntu-themes” package in Ubuntu: Triaged Bug description: Checkboxes (especially in update-manager) have a red square around it. This seems wrong. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-themes 14.04+14.04.20140324-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 25 14:28:31 2014 InstallationDate: Installed on 2013-02-16 (401 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130216) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to trusty on 2014-01-22 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1297302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351939] Re: Sending USSD message does not work
Yes, it is. We should have an upstream bug report. ** Changed in: modem-manager-gui Status: Confirmed = Invalid ** Also affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Also affects: modemmanager Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351939 Title: Sending USSD message does not work Status in Modem Manager Gui: Invalid Status in ModemManager (with NetworkManager support): New Status in “modem-manager-gui” package in Ubuntu: New Status in “modemmanager” package in Ubuntu: New Bug description: The error message says: Error sending USSD GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5 This is reported upstream here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1162408] Re: little horizontal black lines sporadically appear
I have this on Trusty, on HP Folio 9670m (intel graphics). -- 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/1162408 Title: little horizontal black lines sporadically appear Status in “xorg” package in Ubuntu: Incomplete Bug description: Some little horizontal black lines sometimes appear on the Ubuntu desktop. They disappear quickly, and there seems no obvious way to force the event to occur predictably. The problem occurs with libgl1-mesa-dri-experimental but, unless I'm mistaken, occurred also with the nonexperimental branch. Furthermore, I'm running Ubuntu Classic and was not using 3d effects when the problem occurred (was simply typing text in LibreOffice). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.25-lowlatency 3.5.7.4 Uname: Linux 3.5.0-25-lowlatency i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sun Mar 31 06:55:41 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-25-lowlatency, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-26-generic, i686: installed virtualbox, 4.1.18, 3.5.0-25-lowlatency, i686: installed virtualbox, 4.1.18, 3.5.0-26-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (9 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0JF77M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd12/10/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0JF77M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.libdrm2: libdrm2 2.4.43+git1303291653.ca678b~gd~q version.libgl1-mesa-dri: libgl1-mesa-dri 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-glx: libgl1-mesa-glx 9.2~git1303291656.5f41e0~gd~q version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0+git1303291654.6e74aa~gd~q version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5+git1303291654.431816~gd~q version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7+git1303271126.677142~gd~q --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2013-11-19 15:54:14,165 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (302 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.8-lowlatency 3.11.10 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-15-lowlatency i686 UpgradeStatus: Upgraded to saucy on 2013-11-19 (59 days ago) UserGroups: adm audio debian-tor kismet
[Touch-packages] [Bug 1162408] Re: little horizontal black lines sporadically appear
Mistake in above, I have HP Folio 9470m (not 9670) -- 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/1162408 Title: little horizontal black lines sporadically appear Status in “xorg” package in Ubuntu: Incomplete Bug description: Some little horizontal black lines sometimes appear on the Ubuntu desktop. They disappear quickly, and there seems no obvious way to force the event to occur predictably. The problem occurs with libgl1-mesa-dri-experimental but, unless I'm mistaken, occurred also with the nonexperimental branch. Furthermore, I'm running Ubuntu Classic and was not using 3d effects when the problem occurred (was simply typing text in LibreOffice). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.25-lowlatency 3.5.7.4 Uname: Linux 3.5.0-25-lowlatency i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sun Mar 31 06:55:41 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-25-lowlatency, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-26-generic, i686: installed virtualbox, 4.1.18, 3.5.0-25-lowlatency, i686: installed virtualbox, 4.1.18, 3.5.0-26-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (9 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0JF77M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd12/10/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0JF77M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.libdrm2: libdrm2 2.4.43+git1303291653.ca678b~gd~q version.libgl1-mesa-dri: libgl1-mesa-dri 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-glx: libgl1-mesa-glx 9.2~git1303291656.5f41e0~gd~q version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0+git1303291654.6e74aa~gd~q version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5+git1303291654.431816~gd~q version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7+git1303271126.677142~gd~q --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 DistUpgraded: 2013-11-19 15:54:14,165 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (302 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.8-lowlatency 3.11.10 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-15-lowlatency i686 UpgradeStatus: Upgraded to saucy on 2013-11-19 (59 days ago) UserGroups: adm audio debian-tor kismet lpadmin
[Touch-packages] [Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Same here on 14.10 coming from 14.04. I also updated the tags to reflect the affected releases. ** Tags added: trusty ** Tags added: utopic -- 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/1240336 Title: Not authorized to perform operation / Unable to determine the session we are in: No session for pid Status in “gdm” package in Ubuntu: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lxdm” package in Ubuntu: Confirmed Status in “policykit-desktop-privileges” package in Ubuntu: Confirmed Bug description: After a new install of 64 bit Ubuntu 13.10 on my second partition, I used dpkg to reinstall all the same packages I had on my 32 bit 13.04 partition. I copied all my home directory files over and updated all the packages. I now find that I don't have permissions to change the network settings; I can't mount my other hard drive or any USB stick using nautilus, or (udisks without using sudo)' I can't run synaptic by clicking on the GUI (I have to go to a terminal and sudo synaptic); etc. I can't find any documentation on the configuration of policykit-desktop-privileges, so I'm filing this bug. For me it appears to be totally broken. Maybe someone can help me out. Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
This bug occured to me also in Utopic (14.10). Running dual monitor setup using radeonsi. After multiple screen locks and unlocks the bug reappeared. Is this bug supposed to be fixed in Unity 7.3.1 on Utopic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
** Branch linked: lp:~aacid/unity8/networkingstatus -- 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/1384776 Title: Occasional hang in unity 8 dash on the phone Status in “network-manager” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Triaged Bug description: The dash is sometimes hanging on the phone. See the attached backtrace. The issue is as follows: we are maintaining a client-side tree of all NetworkManager devices. When we see that a new device has been added, we query its properties in order to build our local proxy. Doing this means that we are making QtDBus calls from a signal handler. Due to a bug in QtDBus this is not safe. libdbus-1 has a recursive lock on its DBusConnection. When the signal arrives, the lock is acquired and the sginal handler is run. The signal handler can make DBus calls (which also require the lock) because the lock is recursive. QtDBus also has a lock that is always acquired before the libdbus-1 connection lock is acquired. Unfortuntaely, the QtDBus lock is not acquired in the case of the incoming call from DBus -- only the DBus lock is. If another thread tries to do an unrelated DBus call meanwhile, it will acquire the QtDBus lock first and then the DBus lock (which is held because of the signal that arrived). Once the signal handler gets to the point of wanting to make a DBus call (in order to query the properties of the just-added network device) it will attempt to acquire the QtDBus lock. This is a lock-inversion deadlock. There are at least three bugs here: 1) QtDBus should be fixed in order to avoid this sort of lock inversion problem. Even if we fix this one situation, it seems quite likely that issues like this will arise again. 2) QNetworkManager should avoid the issue in QtDBus until such a time as it is fixed. This could be done by dispatching to a worker thread on receipt of signals so that the queries are done in a fresh call stack (without the libdbus-1 lock held). 3) Apparently the only reason we are using NetworkManager at all is in order to know if we are on a 3G connection or not (in order to avoid too much data charges). This would be much easier to do if NetworkManager provided a property that we could watch directly instead of bringing up an entire tree of objects in order to answer a very simple question. To that end I've filed https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can hopefully get addressed relatively quickly. I consider 3) to be the real fix as far as we are concerned, but we should probably ensure that the Qt people know about 1) and 2). Either of those could function as a workaround for us in the meantime, but the idea that we are creating this complex object tree to answer a simple question is ridiculous, so we should really fix that directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377813] Re: tzdata SRU to 2014f because of law changes in Russia
** Changed in: tzdata (Ubuntu Precise) Assignee: Adam Conrad (adconrad) = ekzorchik (ekzorchik) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1377813 Title: tzdata SRU to 2014f because of law changes in Russia Status in “tzdata” package in Ubuntu: Fix Released Status in “tzdata” source package in Lucid: Fix Released Status in “tzdata” source package in Precise: Fix Released Status in “tzdata” source package in Trusty: Fix Released Status in “tzdata” package in Debian: Fix Released Bug description: Tzdata in 12.04 (Precise) and 14.04 (Trusty) needs to be updated to version 2014f or newer. Timezone assignment in Russia has changed in 2014-07-01. The changes are published in Olson 2014f. Timezone changes will take effect in 2014-10-26. Please release package updates before this date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1377813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1083084] Re: add option for alt-tab window grouping disable
WIth the release of 14.10, compiz-plugin-extras are not packaged anymore and fallback to the static window switcher (recommended everywhere when this issue is mentionned) is not easily feasible anymore. Users are bound to the default unity switcher's painful time delay. This switcher behavior is ridiculous and counterproductive, as mentionned many times in this thread, there should be an option to disable grouping and/or have a way to go back to a switcher that resembles the static one (live preview yet no grouping). -- 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/1083084 Title: add option for alt-tab window grouping disable Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Good day, thank you for your wonderful work on Unity, I find it very usable. The only thing that bothers me is the window grouping, as described here: http://ubuntuforums.org/showthread.php?t=1826736 quote: MY Question is if its possible to disable the Grouping part... such as having multiple nautilus windows. Primarily thunderbird is the largest annoyance.. if im writing an email on my laptop and accedentally (touchpad 'palming') off the 'compose message' window; by default and second nature, my brain tells my fingers to alt-tab back into it. unfortunately, this DOES NOT WORK! Basically, I am trying to restore Alt+Tab functionality from Unity 2D. I tried number of other switchers, all have their separate issues. For example, Static Application Switcher does not show minimalized windows (or windows hidden by the show desktop shortcut), etc. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,move,regex,gnomecompat,vpswitch,mousepoll,resize,place,grid,compiztoolbox,snap,imgpng,unitymtgrabhandles,session,animation,workarounds,wall,expo,ezoom,fade,scale,unityshell] Date: Mon Nov 26 10:06:10 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-05-17 (924 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-03 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1083084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385793] Re: Merge 1.6-4 from debian
This bug was fixed in the package gzip - 1.6-4ubuntu1
---
gzip (1.6-4ubuntu1) vivid; urgency=medium
* Merge from Debian unstable (lp: #1385793). Remaining changes:
- debian/{control,rules}: Remove the Win32 build and mingw64
build-dependency, since mingw is in universe, and will remain so for
the forseeable future.
- Added autopkgtest tests
gzip (1.6-4) unstable; urgency=low
* fix typo in man page, closes: #738546
* specify /bin/sh as shell for wrapper scripts, closes: #762915
-- Jackson Doak nosk...@ubuntu.com Sun, 26 Oct 2014 13:16:56 +1100
** Changed in: gzip (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 gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1385793
Title:
Merge 1.6-4 from debian
Status in “gzip” package in Ubuntu:
Fix Released
Bug description:
Please merge gzip 1.6-4 from debian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1385793/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361447] Re: Cannot examine crash report locally: Error while creating the child process: (No such file or directory)
Mark as high because I can no more open bug reports. Best regards ** Tags added: utopic vivid ** Changed in: apport (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1361447 Title: Cannot examine crash report locally: Error while creating the child process: (No such file or directory) Status in “apport” package in Ubuntu: Confirmed Bug description: When using Examine locally after ubuntu-bug /var/crash/... and selecting to run a gdb session, the following error dialog pops up: Error while creating the child process: Failed to execute child process apport-retrace --gdb '/var/crash/crash' (No such file or directory) It looks like apport is calling the process wrong: instead of as a command plus arguments, the whole string might get used as command. It works fine from the shell. (btw: it would be nice, if copy'n'paste would work for the text of such popups) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.3 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CrashReports: 640:0:114:198430:2014-08-17 16:42:49.715965167 +0200:2014-08-17 16:42:49.711965167 +0200:/var/crash/susres.2014-08-17_16:42:49.718598.crash 640:1000:114:185625:2014-08-20 18:38:13.700118400 +0200:2014-08-20 18:38:13.520118396 +0200:/var/crash/_usr_bin_redshift.1000.crash 640:1000:114:5702851:2014-08-26 02:18:55.313115119 +0200:2014-08-26 02:19:13.153115552 +0200:/var/crash/_usr_bin_vim.gnome.1000.crash CurrentDesktop: GNOME Date: Tue Aug 26 02:20:45 2014 InstallationDate: Installed on 2012-05-28 (819 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-05-01 (116 days ago) mtime.conffile..etc.apport.crashdb.conf: 2014-05-07T17:51:23.631588 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1361447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
Same here while running Ubuntu 14.10 server in a VirtualBox VM: [ 62.851445] systemd-logind[1191]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 62.854044] systemd-logind[1191]: failed to start user service: Unknown unit: user@1000.service This happens after a clean standard install; selected packages is the minimum base install plus openssh-server. Any idea how to fix this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in “systemd-shim” package in Ubuntu: Triaged Status in “systemd-shim” package in Debian: Incomplete Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307118] Re: Unity freezes on resuming from suspend
I'm able to restore mouse funtionality with: rmmod psmouse; modprobe psmouse -- 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/1307118 Title: Unity freezes on resuming from suspend Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: After suspending laptop (by closing the laptop screen) and then resuming, the screen is black and doesn't seem to take any keyboard or mouse input. As a result, the only way to fix the situation is to hard reboot the system. Steps to reproduce: 1. Suspend laptop 2. Wait for at least 10-15 minutes 3. Try resuming What happens: Black screen with the mouse cursor visible. However the whole screen is frozen. No keyboard or mouse input is accepted. As a result, I cannot switch to any vt to reboot or restart the lightdm process What should happen: Unity lockscreen is shown where one can enter the password and return to the user session gnome-screensaver: 3.6.1-0ubuntu13 amd64 [Installed] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 13 13:56:56 2014 DistUpgraded: 2014-02-27 11:46:48,360 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2013-09-18 (207 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=63532c2e-8584-466e-8215-2d6770489a00 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-27 (45 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN32WW(V2.02) dmi.board.asset.tag: YB00228460 dmi.board.name: 20217 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: YB00228460 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 13 13:51:07 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 489 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386127] [NEW] mouse does not work correctly after suspend
Public bug reported: Afer waking from suspend mouse does not work correctly. I'm able to move pointer but am not able to move, resize or select windows with mouse. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 27 12:28:24 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.18, 3.16.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:15e9] InstallationDate: Installed on 2014-10-24 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: FUJITSU LIFEBOOK S761 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed root=UUID=cc6f31be-38e2-4958-96cd-fa3c122fa5ca ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.12 dmi.board.name: FJNB22E dmi.board.vendor: FUJITSU dmi.board.version: A1 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK S761 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.12:bd03/14/2012:svnFUJITSU:pnLIFEBOOKS761:pvr10601186096:rvnFUJITSU:rnFJNB22E:rvrA1:cvnFUJITSU:ct10:cvrLIFEBOOKS761: dmi.product.name: LIFEBOOK S761 dmi.product.version: 10601186096 dmi.sys.vendor: FUJITSU 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: Mon Oct 27 11:46:51 2014 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14164 vendor SEC xserver.version: 2:1.16.0-1ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386127 Title: mouse does not work correctly after suspend Status in “xorg” package in Ubuntu: New Bug description: Afer waking from suspend mouse does not work correctly. I'm able to move pointer but am not able to move, resize or select windows with mouse. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 27 12:28:24 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.18, 3.16.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:15e9] InstallationDate: Installed on 2014-10-24 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: FUJITSU LIFEBOOK S761 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed root=UUID=cc6f31be-38e2-4958-96cd-fa3c122fa5ca ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2012 dmi.bios.vendor: FUJITSU //
[Touch-packages] [Bug 1386127] Re: mouse does not work correctly after suspend
I'm able to fix mouse by: sudo rmmod psmouse;sudo modprobe psmouse -- 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/1386127 Title: mouse does not work correctly after suspend Status in “xorg” package in Ubuntu: New Bug description: Afer waking from suspend mouse does not work correctly. I'm able to move pointer but am not able to move, resize or select windows with mouse. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 27 12:28:24 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.18, 3.16.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:15e9] InstallationDate: Installed on 2014-10-24 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: FUJITSU LIFEBOOK S761 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed root=UUID=cc6f31be-38e2-4958-96cd-fa3c122fa5ca ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.12 dmi.board.name: FJNB22E dmi.board.vendor: FUJITSU dmi.board.version: A1 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK S761 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.12:bd03/14/2012:svnFUJITSU:pnLIFEBOOKS761:pvr10601186096:rvnFUJITSU:rnFJNB22E:rvrA1:cvnFUJITSU:ct10:cvrLIFEBOOKS761: dmi.product.name: LIFEBOOK S761 dmi.product.version: 10601186096 dmi.sys.vendor: FUJITSU 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: Mon Oct 27 11:46:51 2014 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14164 vendor SEC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312260] Re: [browser] There is no search in page option in webbrowser-app (like ctrl+F)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: webbrowser-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1312260 Title: [browser] There is no search in page option in webbrowser-app (like ctrl+F) Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: Triaged Status in “webbrowser-app” package in Ubuntu: Confirmed Bug description: Users will be able to find text in page (partialexact match) - Function will be available in the Action Drawer UX Spec here https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g187f4edfe_50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1312260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316259] Re: rtsp URL's not supported
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1316259 Title: rtsp URL's not supported Status in Oxide Webview: Invalid Status in Web Browser App: In Progress Status in “webbrowser-app” package in Ubuntu: In Progress Bug description: Go to URL www.espn.com and click on one of the videos at the bottom of the NHL sports page. On the device you get a Network Error page saying URL not supported and on the desktop you get the video thumbnail but it does not play. It seems the URL is an rtsp trying to play a 3gp video. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1316259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386158] [NEW] Please sync fonts-android 1:4.4.4r2-4 from Debian sid
Public bug reported: Both the Ubuntu changes in version 1:4.3-3ubuntu2 have been applied upstream and can safely be overridden. ** Affects: fonts-android (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1386158 Title: Please sync fonts-android 1:4.4.4r2-4 from Debian sid Status in “fonts-android” package in Ubuntu: New Bug description: Both the Ubuntu changes in version 1:4.3-3ubuntu2 have been applied upstream and can safely be overridden. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1386158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 826702] Re: crontab cuts off file names at 100 characters
This bug was fixed in the package cron - 3.0pl1-127ubuntu1 --- cron (3.0pl1-127ubuntu1) vivid; urgency=low * Merge from Debian unstable. Remaining changes: - debian/control: + Move MTA to Suggests field. - debian/cron.upstart: Add Upstart script. - debian/rules: Call dh_installinit to install Upstart job properly. - d/cron.default: change to a deprecated message to make it clear that the file is no longer in use. cron (3.0pl1-127) unstable; urgency=medium * Drop $READ_ENV from cron's command line. It does not belong there. Closes: #766779 cron (3.0pl1-126) unstable; urgency=low * Packaging (general): removed unused files from the source that had been already removed in 3.0pl1-117 but got reintroduced due to a merge. cron (3.0pl1-125) unstable; urgency=medium * Acknowledge NMUs. Thanks, Laurent Bigonville and Ansgar Burchardt. Closes: #749271 [ Christian Kastner ] * debian/control: - Bump Standards-Version to 3.9.6 (no changes needed) - Canonicalize Vcs-* URLs * debian/copyright: - Bump years - Don't use spaces in License short name * debian/source/lintian-overrides: - Drop overrides from pre-UTF-8 debian/control era * debian/rules: - Extend documentation * debian/cron.init: - Include winbind in Should-Start/Stop. Closes: #732203 * crontab.5: - Don't use hyphen as a minus sign * cron.8: - Drop stray words in cron.8. Thanks, Regid Ichira! Closes: #702091 - Fix misspelled 'sytem'. Thanks, green! Closes: #753775 * cron.c,crontab.c: - Use basename of argv[0] as syslog tag. Closes: #752750 * cron.c: - Use case-insensitive comparison in charset selection. Thanks, Malcolm Scott! LP: #1169160 * entry.c: - Detect invalid entry: step specified without a range. Thanks, Justin T. Pryzby! Closes: #733478 - Error out when a command field is too long instead of silently truncating it. Closes: #686223, LP: #826702 * do_command.c: - Fix initialization and increment of mailed bytes counter. Closes: #691488 * cron.c, do_command.c: - Add an option -n to include FQDN in mail subject. Closes: #570423 [ brian m. carlson ] * config.h, do_command.c: - Send proper 8-bit emails by including an appropriate MIME-Version and adjusting the Content-Transfer-Encoding header accordingly. Closes: #694686 [ Javier Fernández-Sanguino ] * Change systemd definition in order for the daemon to read an honor /etc/default/cron (Closes: #754279) cron (3.0pl1-124.2) unstable; urgency=medium * Non-maintainer upload. * debian/cron.service: Set IgnoreSIGPIPE=false. (Closes: #756047) * debian/cron.service: Add Documentation field. -- Michael Vogt michael.v...@ubuntu.com Mon, 27 Oct 2014 10:19:21 +0100 ** Changed in: cron (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 cron in Ubuntu. https://bugs.launchpad.net/bugs/826702 Title: crontab cuts off file names at 100 characters Status in “cron” package in Ubuntu: Fix Released Bug description: The crontab command silently cuts off file names after 100 characters. This means that it won't work if you have a file with a path longer than 100 characters, and want to feed it into crontab. Example: $ crontab _123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_this_will_be_cut_off _123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_12345678: No such file or directory This is due to a MAX_FNAME constant set to 100 characters in cron.h. I updated the code to use PATH_MAX instead. This will still cut off the paths, but at least after a more reasonable number of characters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/826702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1169160] Re: cron: non-canonical MIME charset used in mail
This bug was fixed in the package cron - 3.0pl1-127ubuntu1 --- cron (3.0pl1-127ubuntu1) vivid; urgency=low * Merge from Debian unstable. Remaining changes: - debian/control: + Move MTA to Suggests field. - debian/cron.upstart: Add Upstart script. - debian/rules: Call dh_installinit to install Upstart job properly. - d/cron.default: change to a deprecated message to make it clear that the file is no longer in use. cron (3.0pl1-127) unstable; urgency=medium * Drop $READ_ENV from cron's command line. It does not belong there. Closes: #766779 cron (3.0pl1-126) unstable; urgency=low * Packaging (general): removed unused files from the source that had been already removed in 3.0pl1-117 but got reintroduced due to a merge. cron (3.0pl1-125) unstable; urgency=medium * Acknowledge NMUs. Thanks, Laurent Bigonville and Ansgar Burchardt. Closes: #749271 [ Christian Kastner ] * debian/control: - Bump Standards-Version to 3.9.6 (no changes needed) - Canonicalize Vcs-* URLs * debian/copyright: - Bump years - Don't use spaces in License short name * debian/source/lintian-overrides: - Drop overrides from pre-UTF-8 debian/control era * debian/rules: - Extend documentation * debian/cron.init: - Include winbind in Should-Start/Stop. Closes: #732203 * crontab.5: - Don't use hyphen as a minus sign * cron.8: - Drop stray words in cron.8. Thanks, Regid Ichira! Closes: #702091 - Fix misspelled 'sytem'. Thanks, green! Closes: #753775 * cron.c,crontab.c: - Use basename of argv[0] as syslog tag. Closes: #752750 * cron.c: - Use case-insensitive comparison in charset selection. Thanks, Malcolm Scott! LP: #1169160 * entry.c: - Detect invalid entry: step specified without a range. Thanks, Justin T. Pryzby! Closes: #733478 - Error out when a command field is too long instead of silently truncating it. Closes: #686223, LP: #826702 * do_command.c: - Fix initialization and increment of mailed bytes counter. Closes: #691488 * cron.c, do_command.c: - Add an option -n to include FQDN in mail subject. Closes: #570423 [ brian m. carlson ] * config.h, do_command.c: - Send proper 8-bit emails by including an appropriate MIME-Version and adjusting the Content-Transfer-Encoding header accordingly. Closes: #694686 [ Javier Fernández-Sanguino ] * Change systemd definition in order for the daemon to read an honor /etc/default/cron (Closes: #754279) cron (3.0pl1-124.2) unstable; urgency=medium * Non-maintainer upload. * debian/cron.service: Set IgnoreSIGPIPE=false. (Closes: #756047) * debian/cron.service: Add Documentation field. -- Michael Vogt michael.v...@ubuntu.com Mon, 27 Oct 2014 10:19:21 +0100 ** Changed in: cron (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1169160 Title: cron: non-canonical MIME charset used in mail Status in “cron” package in Ubuntu: Fix Released Bug description: cron sends mail with the following header: Content-Type: text/plain; charset=ANSI_X3.4-1968 This is a non-canonical alias for the preferred charset name us- ascii [1]. A previous changelog entry (for 3.0pl1-101) states that this was previously fixed: - Do not use ANSI_x3.4-1968 but US-ASCII instead since it is the preferred MIME name as per http://www.iana.org/assignments/character-sets; (Closes: #415302) However the code to do this translation is not currently working due to an incorrect assumption about the case of nl_langinfo's output (it currently returns ANSI_X3.4-1968, whereas the code checks case- sensitively for ANSI_x3.4-1968). [1] http://www.iana.org/assignments/character-sets/character-sets.xml ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cron 3.0pl1-120ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Mon Apr 15 13:03:04 2013 MarkForUpload: True ProcEnviron: TERM=screen-bce PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: Upgraded to precise on 2013-01-10 (94 days ago) modified.conffile..etc.crontab: [modified] mtime.conffile..etc.crontab: 2013-04-14T09:07:44.212020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1169160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373985] Re: unity8-dash doesn't seem to get activated after we leave the lock screen
I can confirm that this is definitely a maliit issue, working on a patch now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1373985 Title: unity8-dash doesn't seem to get activated after we leave the lock screen Status in “maliit-framework” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Bug description: Steps to reproduce the issue: 1 - lock the phone (reboot or have the display off and then turn it back on) 2 - type you password [you're brought to unity8-dash] 3 - tap on the looking glass icon in the top right [search bar text entry shows up with Search apps written on it] Expected outcome: A blinking cursor caret is displayed on the app search text entry and the VKB comes up. Actual outcome: Nothing happens. Causing unity-8 dash to be refocused, such as bringing the indicators panel down and then back up solves it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1373985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386011] Re: Wrong time is shown after switch to daylight savings time
** Package changed: unity (Ubuntu) = indicator-datetime (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1386011 Title: Wrong time is shown after switch to daylight savings time Status in “indicator-datetime” package in Ubuntu: New Bug description: After switch to daylight savings time, the time at top right corner is not updated. However it is shown correct elsewhere. see the screenshot https://dl.dropboxusercontent.com/u/13590393/ubuntu-bug.png at the corner the old time is shown, at the dropdown window - updated time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1386011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
As an update, I found this post :- http://ubuntuforums.org/showthread.php?t=2217890 and bug report https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1302885 Stating The problem is that an incorrect string is set in dconf key: (Example) Original (working) value: ~$ gsettings get org.gnome.settings-daemon.plugins.media-keys volume-up 'XF86AudioRaiseVolume' After running unity-control-center keyboard, and setting the shortcut for volume-up key: ~$ gsettings get org.gnome.settings-daemon.plugins.media-keys volume-up 'AudioRaiseVolume' When I checked with dconf, my media keys were indeed screwed up as in this post. I added the XF86 prefix and they now work. However, this is only one small part of the bug. (in fact a different bug) If I try to capture keyboard events with xev, I am not getting any keypresses for keys I have assigned in the control centre gui. For example, Brightness Up and Down keys - instead of triggering keypress and keyrelease events, instead trigger Mapping notify, focusout, focusout, focusin and keymapnotify events. I have also found that I can get the unresponsive keys to trigger the correct events in xev by pressing them with another key, e.g. press eject and F12, and I will get keypress events for both (and the shortcut assigned to a key sometimes will execute too) In desperation I have even installed xbindkeys and configured it, but it seems to be too far up the keyboard handling chain to receive the keys before something else has stolen them and done nothing with them. ** Also affects: gnome-control-center Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in GNOME Control Center: New Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “libxkbcommon” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372860] Re: Contacts app sends you to Online Accounts and strands you there
This bug definitely needs to be sorted. Is there now agreement on the user flow and work items list? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1372860 Title: Contacts app sends you to Online Accounts and strands you there Status in Online Accounts setup for Ubuntu Touch: Incomplete Status in Ubuntu UX bugs: In Progress Status in “address-book-app” package in Ubuntu: Triaged Bug description: First time in contacts when asked to add an account to sync. You are taken into settings and add an account which returns to main settings screen. This should take you into the new account to tick the contacts sync check box! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings-online-accounts 0.4+14.10.20140908~rtm-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Tue Sep 23 11:54:02 2014 InstallationDate: Installed on 2014-09-16 (7 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-030205) SourcePackage: ubuntu-system-settings-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1372860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348784] Re: thermald prevents unmounting /dev/sda1 in recovery mode
Did we conclude this is more of a misconfiguration rather than a thermald issue pe se, if so, I may remove thermald from the bug and rename it -- 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/1348784 Title: thermald prevents unmounting /dev/sda1 in recovery mode Status in “thermald” package in Ubuntu: In Progress Status in “upstart” package in Ubuntu: New Bug description: I'm using Ubuntu 14.10 dev with thermald 1.2-1 and if the system is started in the recovery mode it is not possible to unmount /dev/sda1 because thermald is running. Interestingly lsof hasn't even showed that something has a file descriptor on /dev/sda1 open but executing stop thermald has worked as a workaround. --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes NonfreeKernelModules: fglrx Package: upstart 1.13.2-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic root=UUID=af27feae-4c9e-4b5f-a1e1-900c0e71c5cb ro elevator=cfq ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Tags: utopic Uname: Linux 3.16.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.13.2) UserGroups: _MarkForUpload: True modified.conffile..etc.lxdm.lxdm.conf: [modified] mtime.conffile..etc.init.control.alt.delete.conf: 2012-05-05T17:10:11.434470 mtime.conffile..etc.init.tty2.conf: 2014-05-29T05:14:16.791093 mtime.conffile..etc.init.tty3.conf: 2012-05-05T17:10:49.238469 mtime.conffile..etc.init.tty4.conf: 2012-05-05T17:10:58.066468 mtime.conffile..etc.init.tty5.conf: 2012-05-05T17:11:02.938468 mtime.conffile..etc.init.tty6.conf: 2012-05-05T17:11:09.442468 mtime.conffile..etc.lxdm.lxdm.conf: 2012-12-23T19:04:26.948844 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1348784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378043] Re: [TOPBLOCKER] Phone is getting locked during a call
** Changed in: powerd (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1378043 Title: [TOPBLOCKER] Phone is getting locked during a call Status in Dialer app for Ubuntu Touch: Invalid Status in “powerd” package in Ubuntu: Fix Committed Bug description: The phone is getting lock during a call. How to reproduce 1 - Open dialer app 2 - Type a number 3 - Click to call 4 - Cover the proximity sensor 5 - Uncover the proximity sensor Expected The phone shows the active call information Current results === The phone get locked and you need to type your password to unlock it OBS: If you wait the call complete for about 3~ secs everything works nice. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1378043/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348784] Re: thermald prevents unmounting /dev/sda1 in recovery mode
This seems to be plausible as thermald would not start if dbus would not start (which is the bug here (or probably a configuration issue)). -- 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/1348784 Title: thermald prevents unmounting /dev/sda1 in recovery mode Status in “thermald” package in Ubuntu: In Progress Status in “upstart” package in Ubuntu: New Bug description: I'm using Ubuntu 14.10 dev with thermald 1.2-1 and if the system is started in the recovery mode it is not possible to unmount /dev/sda1 because thermald is running. Interestingly lsof hasn't even showed that something has a file descriptor on /dev/sda1 open but executing stop thermald has worked as a workaround. --- ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes NonfreeKernelModules: fglrx Package: upstart 1.13.2-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic root=UUID=af27feae-4c9e-4b5f-a1e1-900c0e71c5cb ro elevator=cfq ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Tags: utopic Uname: Linux 3.16.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.13.2) UserGroups: _MarkForUpload: True modified.conffile..etc.lxdm.lxdm.conf: [modified] mtime.conffile..etc.init.control.alt.delete.conf: 2012-05-05T17:10:11.434470 mtime.conffile..etc.init.tty2.conf: 2014-05-29T05:14:16.791093 mtime.conffile..etc.init.tty3.conf: 2012-05-05T17:10:49.238469 mtime.conffile..etc.init.tty4.conf: 2012-05-05T17:10:58.066468 mtime.conffile..etc.init.tty5.conf: 2012-05-05T17:11:02.938468 mtime.conffile..etc.init.tty6.conf: 2012-05-05T17:11:09.442468 mtime.conffile..etc.lxdm.lxdm.conf: 2012-12-23T19:04:26.948844 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1348784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386158] Re: Please sync fonts-android 1:4.4.4r2-4 from Debian sid
This bug was fixed in the package fonts-android - 1:4.4.4r2-4 Sponsored for Gunnar Hjalmarsson (gunnarhj) --- fonts-android (1:4.4.4r2-4) unstable; urgency=low * Team upload * No longer use xz extreme compression for deb packages * Move DroidSansFallback.ttf and DroidSansFallbackLegacy.ttf in /usr/share/fonts-droid/truetype which is not monitored by fontconfig, leaving DroidSansFallbackFull.ttf as the only font file to provide Droid Sans Fallback Closes: #762296 Thanks to Jonas Smedegaard and Gunnar Hjalmarsson for their input about this issue. * Use machine-readable copyright format * Update Standards to 3.9.6 (checked) -- Christian Perrier bubu...@debian.org Sat, 18 Oct 2014 15:31:51 +0200 fonts-android (1:4.4.4r2-3) unstable; urgency=low * Drop the symlink in conf.avail and clean it out for upgrades * Drop the mention of 65-droid-sans-fonts.conf in debian/copyright -- Christian Perrier bubu...@debian.org Sat, 20 Sep 2014 14:08:04 +0200 fonts-android (1:4.4.4r2-2) unstable; urgency=low * Team upload * Patch from Ubuntu * debian/local/65-droid-sans-fonts.conf: - Dropped. We want to cherry pick Droid Sans Fallback for rendering Chinese content, and 65-droid-sans-fonts.conf has defeated that purpose and caused confusion (LP: #1334495, LP: #1351092). Closes: #762237, #729752, #661235 -- Christian Perrier bubu...@debian.org Sat, 20 Sep 2014 08:32:02 +0200 fonts-android (1:4.4.4r2-1) unstable; urgency=medium * Imported Upstream version 4.4.4r2 Closes: bug#733077, Thanks to Chris Lawrence. -- Vasudev Kamath kamathvasu...@gmail.com Thu, 14 Aug 2014 17:08:29 +0530 fonts-android (1:4.4.3r1.1-1) unstable; urgency=medium * Update create_orig_source script to 4.4.3_r1.1 version * Imported Upstream version 4.4.3r1.1. * Add extra fontconfig recipe for making Droid Sans as the default font for Chinese content. Closes: bug#750884, Thanks to Gunnar Hjalmarsson. * Upload to unstable * Update README.source suggesting use of uscan, now that uscan scans upstream git repository tags for new release. * Drop Roboto-BlackItalic.ttf Roboto-Black.ttf Roboto-Medium.ttf Roboto-MediumItalic.ttf RobotoCondensed-Light.ttf RobotoCondensed-LightItalic.ttf RobotoSpecimenBook.pdf variants which are not in upstream tarball. * Use regexp to install all Droid fonts available in upstream. Closes: bug#737105, Thanks to Hideki Yamane. -- Vasudev Kamath kamathvasu...@gmail.com Tue, 17 Jun 2014 19:42:14 +0530 ** Changed in: fonts-android (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1386158 Title: Please sync fonts-android 1:4.4.4r2-4 from Debian sid Status in “fonts-android” package in Ubuntu: Fix Released Bug description: Both the Ubuntu changes in version 1:4.3-3ubuntu2 have been applied upstream and can safely be overridden. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1386158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386194] [NEW] openLDAP creates persistent connections into universisty LDAP- this is unwanted by university administrators
Public bug reported: openLDAP creates persistent connections into universisty LDAP- this is unwanted by university administrators. I have ldap.conf cat /etc/ldap.conf ###DEBCONF### ## ## Configuration of this file will be managed by debconf as long as the ## first line of the file says '###DEBCONF###' ## ## You should use dpkg-reconfigure to configure this file via debconf ## # # @(#)$Id: ldap.conf,v 1.38 2006/05/15 08:13:31 lukeh Exp $ # # This is the configuration file for the LDAP nameservice # switch library and the LDAP PAM module. # # PADL Software # http://www.padl.com # # Your LDAP server. Must be resolvable without using LDAP. # Multiple \hosts may be specified, each separated by a # space. How long nss_ldap takes to failover depends on # whether your LDAP client library supports configurable # network or connect timeouts (see bind_timelimit). #host 127.0.0.1 #host ldap.stuba.sk ldap2.stuba.sk host ldap.stuba.sk # The distinguished name of the search base. base ou=People,dc=stuba,dc=sk pam_template_login_attribute uid # Another way to specify your LDAP server is to provide an #uri ldapi://ldap.stuba.sk ldapi://ldap2.stuba.sk #uri ldaps://ldap.stuba.sk ldaps://ldap2.stuba.sk #TLS_REQCERT allow # Unix Domain Sockets to connect to a local LDAP Server. #uri ldap://127.0.0.1/ #uri ldaps://127.0.0.1/ #uri ldapi://%2fvar%2frun%2fldapi_sock/ # Note: %2f encodes the '/' used as directory separator # The LDAP version to use (defaults to 3 # if supported by client library) ldap_version 3 REFERRALS off TIMEOUT 60 NETWORK_TIMEOUT 60 TIMELIMIT 60 refferrals off timeout 60 network_timeout 60 timelimit 60 persistent-search off # The distinguished name to bind to the server with. # Optional: default is to bind anonymously. #binddn uid=fodrek,ou=People,dc=stuba,dc=sk # The credentials to bind with. # Optional: default is no credential. #bindpw secret # The distinguished name to bind to the server with # if the effective user ID is root. Password is # stored in /etc/ldap.secret (mode 600) #rootbinddn cn=manager,dc=padl,dc=com # The port. # Optional: default is 389. #port 389 # The search scope. #scope sub #scope one scope base # Search timelimit timelimit 1 # Bind/connect timelimit bind_timelimit 12 # Reconnect policy: hard (default) will retry connecting to # the software with exponential backoff, soft will fail # immediately. #bind_policy hard bind_policy soft # Idle timelimit; client will close connections # (nss_ldap only) if the server has not been contacted # for the number of seconds specified below. #idle_timelimit 3600 idle_timelimit 60 debug 99 # Filter to AND with uid=%s #pam_filter objectclass=account #pam_filter objectclass=posixAccount # The user ID attribute (defaults to uid) pam_login_attribute uid # Search the root DSE for the password policy (works # with Netscape Directory Server) #pam_lookup_policy yes # Check the 'host' attribute for access control # Default is no; if set to yes, and user has no # value for the host attribute, and pam_ldap is # configured for account management (authorization) # then the user will not be allowed to login. pam_check_host_attr no # Check the 'authorizedService' attribute for access # control # Default is no; if set to yes, and the user has no # value for the authorizedService attribute, and # pam_ldap is configured for account management # (authorization) then the user will not be allowed # to login. #pam_check_service_attr yes # Group to enforce membership of #pam_groupdn ou=People,dc=stuba,dc=sk # Group member attribute #pam_member_attribute uniquemember #pam_member_attribute uid # Specify a minium or maximum UID number allowed #pam_min_uid 0 #pam_max_uid 0 # Template login attribute, default template user # (can be overriden by value of former attribute # in user's entry) #pam_login_attribute userPrincipalName #pam_template_login_attribute uid #pam_template_login nobody # HEADS UP: the pam_crypt, pam_nds_passwd, # and pam_ad_passwd options are no # longer supported. # # Do not hash the password at all; presume # the directory server will do it, if # necessary. This is the default. pam_password md5 # Hash password locally; required for University of # Michigan LDAP server, and works with Netscape # Directory Server if you're using the UNIX-Crypt # hash mechanism and not using the NT Synchronization # service. #pam_password crypt # Remove old password first, then update in # cleartext. Necessary for use with Novell # Directory Services (NDS) #pam_password clear_remove_old #pam_password nds # RACF is an alias for the above. For use with # IBM RACF #pam_password racf # Update Active Directory password, by # creating Unicode password and updating # unicodePwd attribute. #pam_password ad # Use the OpenLDAP password change # extended operation to update the password. #pam_password exop # Redirect users to a URL or somesuch on password # changes. #pam_password_prohibit_message Please visit http://internal to change
[Touch-packages] [Bug 1383773] Re: [design] Edges Demo doesn't include a lot of steps and is missing new design
** Tags added: ota-1 -- 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/1383773 Title: [design] Edges Demo doesn't include a lot of steps and is missing new design Status in Ubuntu UX bugs: Triaged Status in “unity8” package in Ubuntu: New Bug description: INFO: Edges Demo needs to include mid screen swipe for scope switch, swipe up in app for new page and edge swipe for app switch. Added by design: We conducted user research on the OOBE and edge education experience and while people didn't have problems to walk through the OOBE set up the edge education was considered by users as confusing. One of the main issue was that the current one is not explaining what exactly is triggered by carrying out the edge swipes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386203] [NEW] Plantronics C620 - Mouse buttons freeze
Public bug reported: Confirmed occurrence of bug reported in: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/993655 Ubuntu 12.04 - Plantronics C620 Headset ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-61.93-generic 3.2.55 Uname: Linux 3.2.0-61-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Oct 27 14:42:31 2014 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: LANGUAGE=en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/1386203 Title: Plantronics C620 - Mouse buttons freeze Status in “xorg” package in Ubuntu: New Bug description: Confirmed occurrence of bug reported in: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/993655 Ubuntu 12.04 - Plantronics C620 Headset ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-61.93-generic 3.2.55 Uname: Linux 3.2.0-61-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Oct 27 14:42:31 2014 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: LANGUAGE=en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 868395] Re: Bug in Europe/Russia timezones
Year 2014. Bug is still here.
Buggy version:
keyd@keyd-desktop:~$ dpkg -l | grep tzdata
ii tzdata 2014i-0ubuntu0.12.04
time zone and daylight-saving time data
ii tzdata-java2014i-0ubuntu0.12.04
time zone and daylight-saving time data for use by java runtimes
keyd@keyd-desktop:~$ time ./a.out
Mon Oct 27 16:46:13 2014
real0m4.061s
user0m4.048s
sys 0m0.000s
keyd@keyd-desktop:~$
Patched version:
keyd@keyd-desktop:~$ dpkg -l | grep tzdata
ii tzdata 2014i-0ubuntu0.12.04-yandex1
time zone and daylight-saving time data
ii tzdata-java2014i-0ubuntu0.12.04-yandex1
time zone and daylight-saving time data for use by java runtimes
keyd@keyd-desktop:~$ time ./a.out
Mon Oct 27 16:47:58 2014
real0m1.263s
user0m1.256s
sys 0m0.000s
keyd@keyd-desktop:~$
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/868395
Title:
Bug in Europe/Russia timezones
Status in “tzdata” package in Ubuntu:
Confirmed
Bug description:
In version tzdata-2011j (tzdata-2011k also affected) was founded strange bug
in russian timezones.
Because of a law On the Calculation of Time there were changes in zone like:
3:00 Russia MSK/MSD 2011
changed to:
3:00 Russia MSK/MSD 2011 Mar 27 2:00s
4:00 - MSK
But if no rule used for this change (using - instead of rule Russia),
calling of system function localtime_r() takes more time (takes more than 40%
time longer).
I used following code for measuring:
==
#include time.h
#include stdio.h
int main() {
time_t t = time(0);
int i;
struct tm result;
for(i=0; i 1000; i++)
localtime_r(t, result);
puts(ctime(t));
return 0;
}
==
and also this sql code in mysql db:
select benchmark(100, from_unixtime(1317044847));
For example, when I'm using new tzdata-2011j results are:
1. time ./a.out (c code)
real 0m5.165s
user 0m5.140s
sys 0m0.000s
2. sql query
mysql select benchmark(100, from_unixtime(1317044847));
+---+
| benchmark(100, from_unixtime(1317044847)) |
+---+
| 0 |
+---+
1 row in set (1.03 sec).
And when I'm using old tzdata-2008b:
1. time ./a.out (c code)
real 0m1.675s
user 0m1.450s
sys 0m0.000s
2. sql query
mysql select benchmark(100, from_unixtime(1317044847));
+---+
| benchmark(100, from_unixtime(1317044847)) |
+---+
| 0 |
+---+
1 row in set (0.65 sec)
This bug seemed critical on high loaded systems (for example, for
databases that using unix timestamps).
My configuration was:
Description: Ubuntu 8.04.1
Release: 8.04
Packages: 2011j~repack-0ubuntu0.8.04 and 2008b-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386194] Re: openLDAP creates persistent connections into universisty LDAP- this is unwanted by university administrators
Hi, Thank you for reporting this and helping to make Ubuntu better. Peter Fodrek wrote: cat /etc/ldap.conf This is the configuration file for libnss-ldap, which is not part of OpenLDAP. If you need assistance with configuring libnss-ldap or libpam- ldap, I suggest contacting the support channels for that software, or asking on answers.ubuntu.com. You might also wish to try libnss-ldapd /libpam-ldapd and see whether they have the same problem. If you are experiencing a bug in OpenLDAP, please try to provide more evidence of such; or if you are experiencing a bug (and are certain it's a bug, not a misconfiguration) in libnss-ldap, please reassign this to the appropriate package. Thanks! ** Changed in: openldap (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1386194 Title: openLDAP creates persistent connections into universisty LDAP- this is unwanted by university administrators Status in “openldap” package in Ubuntu: Incomplete Bug description: openLDAP creates persistent connections into universisty LDAP- this is unwanted by university administrators. I have ldap.conf cat /etc/ldap.conf ###DEBCONF### ## ## Configuration of this file will be managed by debconf as long as the ## first line of the file says '###DEBCONF###' ## ## You should use dpkg-reconfigure to configure this file via debconf ## # # @(#)$Id: ldap.conf,v 1.38 2006/05/15 08:13:31 lukeh Exp $ # # This is the configuration file for the LDAP nameservice # switch library and the LDAP PAM module. # # PADL Software # http://www.padl.com # # Your LDAP server. Must be resolvable without using LDAP. # Multiple \hosts may be specified, each separated by a # space. How long nss_ldap takes to failover depends on # whether your LDAP client library supports configurable # network or connect timeouts (see bind_timelimit). #host 127.0.0.1 #host ldap.stuba.sk ldap2.stuba.sk host ldap.stuba.sk # The distinguished name of the search base. base ou=People,dc=stuba,dc=sk pam_template_login_attribute uid # Another way to specify your LDAP server is to provide an #uri ldapi://ldap.stuba.sk ldapi://ldap2.stuba.sk #uri ldaps://ldap.stuba.sk ldaps://ldap2.stuba.sk #TLS_REQCERT allow # Unix Domain Sockets to connect to a local LDAP Server. #uri ldap://127.0.0.1/ #uri ldaps://127.0.0.1/ #uri ldapi://%2fvar%2frun%2fldapi_sock/ # Note: %2f encodes the '/' used as directory separator # The LDAP version to use (defaults to 3 # if supported by client library) ldap_version 3 REFERRALS off TIMEOUT 60 NETWORK_TIMEOUT 60 TIMELIMIT 60 refferrals off timeout 60 network_timeout 60 timelimit 60 persistent-search off # The distinguished name to bind to the server with. # Optional: default is to bind anonymously. #binddn uid=fodrek,ou=People,dc=stuba,dc=sk # The credentials to bind with. # Optional: default is no credential. #bindpw secret # The distinguished name to bind to the server with # if the effective user ID is root. Password is # stored in /etc/ldap.secret (mode 600) #rootbinddn cn=manager,dc=padl,dc=com # The port. # Optional: default is 389. #port 389 # The search scope. #scope sub #scope one scope base # Search timelimit timelimit 1 # Bind/connect timelimit bind_timelimit 12 # Reconnect policy: hard (default) will retry connecting to # the software with exponential backoff, soft will fail # immediately. #bind_policy hard bind_policy soft # Idle timelimit; client will close connections # (nss_ldap only) if the server has not been contacted # for the number of seconds specified below. #idle_timelimit 3600 idle_timelimit 60 debug 99 # Filter to AND with uid=%s #pam_filter objectclass=account #pam_filter objectclass=posixAccount # The user ID attribute (defaults to uid) pam_login_attribute uid # Search the root DSE for the password policy (works # with Netscape Directory Server) #pam_lookup_policy yes # Check the 'host' attribute for access control # Default is no; if set to yes, and user has no # value for the host attribute, and pam_ldap is # configured for account management (authorization) # then the user will not be allowed to login. pam_check_host_attr no # Check the 'authorizedService' attribute for access # control # Default is no; if set to yes, and the user has no # value for the authorizedService attribute, and # pam_ldap is configured for account management # (authorization) then the user will not be allowed # to login. #pam_check_service_attr yes # Group to enforce membership of #pam_groupdn ou=People,dc=stuba,dc=sk # Group member attribute #pam_member_attribute uniquemember #pam_member_attribute uid # Specify a
[Touch-packages] [Bug 1385339] Re: The system-image based phone does not display a channel in its version UI
This information should come from the version scheme ** Changed in: system-image (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1385339 Title: The system-image based phone does not display a channel in its version UI Status in “system-image” package in Ubuntu: Incomplete Bug description: Using ubuntu-touch/ubuntu-rtm/14.09-proposed #123 on a krillin Open System Settings | About This Phone or System Settings | About This Phone | OS There are various version numbers displayed. Expected result: The channel name (ubuntu-touch/ubuntu-rtm/14.09-proposed) is visible Actual result: No UI exposes the channel used by the device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1385339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385464] Re: logrotate fails to run, if status file is corrupt (logrotate running during reboot?)
** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1385464 Title: logrotate fails to run, if status file is corrupt (logrotate running during reboot?) Status in “logrotate” package in Ubuntu: New Bug description: phablet@ubuntu-phablet:~$ du -h /var/log/syslog 654M /var/log/syslog phablet@ubuntu-phablet:~$ sudo logrotate -f /etc/logrotate.conf error: bad top line in state file /var/lib/logrotate/status phablet@ubuntu-phablet:~$ cat /var/lib/logrotate/status /opt/click.ubuntu.com/com.ubuntu.developer.webapps.webapp-gmail/1.0.25phablet@ubuntu-phablet:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373985] Re: unity8-dash doesn't seem to get activated after we leave the lock screen
please bring up again when a fix is available so we can assess impact -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1373985 Title: unity8-dash doesn't seem to get activated after we leave the lock screen Status in “maliit-framework” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Bug description: Steps to reproduce the issue: 1 - lock the phone (reboot or have the display off and then turn it back on) 2 - type you password [you're brought to unity8-dash] 3 - tap on the looking glass icon in the top right [search bar text entry shows up with Search apps written on it] Expected outcome: A blinking cursor caret is displayed on the app search text entry and the VKB comes up. Actual outcome: Nothing happens. Causing unity-8 dash to be refocused, such as bringing the indicators panel down and then back up solves it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1373985/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Branch linked: lp:~gunnarhj/ubuntu/vivid/gdm/config-error-dialog
--
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:
New
Status in Light Display Manager:
Fix Committed
Status in Light Display Manager 1.10 series:
Fix Committed
Status in Light Display Manager 1.12 series:
Fix Committed
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
In Progress
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 1385339] Re: The system-image based phone does not display a channel in its version UI
Who's coming up with that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1385339 Title: The system-image based phone does not display a channel in its version UI Status in “system-image” package in Ubuntu: Incomplete Bug description: Using ubuntu-touch/ubuntu-rtm/14.09-proposed #123 on a krillin Open System Settings | About This Phone or System Settings | About This Phone | OS There are various version numbers displayed. Expected result: The channel name (ubuntu-touch/ubuntu-rtm/14.09-proposed) is visible Actual result: No UI exposes the channel used by the device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1385339/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 (Ubuntu)
Status: Triaged = In Progress
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) = Gunnar Hjalmarsson (gunnarhj)
--
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:
New
Status in Light Display Manager:
Fix Committed
Status in Light Display Manager 1.10 series:
Fix Committed
Status in Light Display Manager 1.12 series:
Fix Committed
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
In Progress
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 1361221] Re: Manage Dash does not notice when the phone comes online
please fix _after_ RTM, i.e via OTA-1 ** Tags removed: touch-2014-10-30 ** Tags added: ota-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1361221 Title: Manage Dash does not notice when the phone comes online Status in “unity-scope-scopes” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: In Progress Status in “unity-scopes-shell” package in Ubuntu: In Progress Bug description: Steps: 1. Start the phone with no Internet (i.e. no wireless or 2g/3g/4g) 2. From the Dash, swipe from the bottom to get to Manage Dash 3. Click All 4. Note there are no internet based scopes available (which makes sense since you are not online) 5. Click Done to go back to the dash 6. Use the network indicator to get online 7. After getting online, go back to Manage Dash Observed: The online scopes are still hidden Expected: After getting online you can see the online scopes Note that after a reboot and being online, the online scopes are visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-scopes/+bug/1361221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386127] Re: mouse does not work correctly after suspend
I was able to fix (workaround) the issue with following /etc/pm/sleep.d
script:
#!/bin/sh
# restart psmouse after waking from suspend
. ${PM_FUNCTIONS}
restart_mouse()
{
rmmod psmouse
modprobe psmouse
}
case $1 in
thaw|resume)
restart_mouse
;;
esac
--
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/1386127
Title:
mouse does not work correctly after suspend
Status in “xorg” package in Ubuntu:
New
Bug description:
Afer waking from suspend mouse does not work correctly. I'm able to
move pointer but am not able to move, resize or select windows with
mouse.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Oct 27 12:28:24 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.3.18, 3.16.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Fujitsu Limited. Device [10cf:15e9]
InstallationDate: Installed on 2014-10-24 (2 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
MachineType: FUJITSU LIFEBOOK S761
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed
root=UUID=cc6f31be-38e2-4958-96cd-fa3c122fa5ca ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2012
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.12
dmi.board.name: FJNB22E
dmi.board.vendor: FUJITSU
dmi.board.version: A1
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: LIFEBOOK S761
dmi.modalias:
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.12:bd03/14/2012:svnFUJITSU:pnLIFEBOOKS761:pvr10601186096:rvnFUJITSU:rnFJNB22E:rvrA1:cvnFUJITSU:ct10:cvrLIFEBOOKS761:
dmi.product.name: LIFEBOOK S761
dmi.product.version: 10601186096
dmi.sys.vendor: FUJITSU
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: Mon Oct 27 11:46:51 2014
xserver.configfile: default
xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 14164
vendor SEC
xserver.version: 2:1.16.0-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386127/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383279] Re: power button events queued, should probably be dropped
** Changed in: unity-system-compositor Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1383279 Title: power button events queued, should probably be dropped Status in Unity System Compositor: In Progress Status in “unity-system-compositor” package in Ubuntu: Confirmed Bug description: Lock phone Repeatedly and rapidly press the power button. Wait Observe the screen blink on and off for some seconds after you finish pressing the power button. The presses after the first few should probably be dropped? To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1383279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
** Description changed: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags - SRU curtin - == - - [Impact] - - As the original bug report description mentions, curtin's extraction - needs to use xattr/acl flags. - - [Test Case] - - To reproduce this bug, use curtin extraction without the extended file - attributes. - - [Regression Potential] - - Since the patch for this bug fix *looks* to see if there are extended - file attributes, it should work in the event that they are there or are - not there or are. More specifically, if tar cmd supports xattrs, curtin - will return the required flags to extract them. This lowers the - probability of introducing a regression. + Related Bugs: + * bug 1382632: horizon insecure key file permissions + * bug 1386237: tar strange behavior with --acl + * bug 1313550: ping broken (xattrs lost in tar extraction) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Won't Fix Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl * bug 1313550: ping broken (xattrs lost in tar extraction) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386237] Re: tar acl support has strange behaviors
heres output of a run of 'tmp-acl-bavior': ** Attachment added: example output of running https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1386237/+attachment/4246269/+files/out ** Description changed: as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl has unexpected behaviors. The one that caught us there was that extracting a tar file with '--acl' that was created without '--acl' results in default acl being set on the top level extracted directory. One would expect that if the source tar file had no acl information that the extracted directory would have no 'default' acl. I'll attach a script here that shows behavior of multiple combinations of: - tar -c [--acl / -no-acl / default] - tar -x [--acl / --no-acl / default ] + tar -c [--acl / -no-acl / default] + tar -x [--acl / --no-acl / default ] and source directories with acl, without acl and with default default acl. + + Related Bugs: + * bug 1382632: horizon insecure key file permissions + * bug 1386237: tar strange behavior with --acl + * bug 1313550: ping broken (xattrs lost in tar extraction) + ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: tar 1.27.1-2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 09:42:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1104 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: tar UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1386237 Title: tar acl support has strange behaviors Status in “tar” package in Ubuntu: New Bug description: as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl has unexpected behaviors. The one that caught us there was that extracting a tar file with '--acl' that was created without '--acl' results in default acl being set on the top level extracted directory. One would expect that if the source tar file had no acl information that the extracted directory would have no 'default' acl. I'll attach a script here that shows behavior of multiple combinations of: tar -c [--acl / -no-acl / default] tar -x [--acl / --no-acl / default ] and source directories with acl, without acl and with default default acl. Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl * bug 1313550: ping broken (xattrs lost in tar extraction) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: tar 1.27.1-2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 09:42:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1104 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: tar UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1386237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367696] Re: spinning Ubuntu logo on update boot feels frantic and not very classy
Actually, those don't cover all the issues. One issue is the consistency (or intentional inconsistency) of the activity notification. The other issue is the use of a spinning logo at all (regardless of size and speed). I believe the spinning logo is overly simplistic, not very classy and doesn't live up to the standard of design elsewhere in the product. I think we can do better than that (and have done so in the desktop start up/shut down images as an example). Un-duped, and original description edited to reflect the design question rather than the implementation of size/speed. ** Description changed: - There is a large spinning Ubuntu logo during updates and a small spinning Ubuntu logo during the boot process. I think there are two problems with this: - - whatever the progress indicator is should be consistent (not one large and one small), - - more importantly, this progress indicator feels frantic, cheap and off brand to me. The desktop has the word Ubuntu with dots which change colour to indicate progress. That feels classier to me. Is there a specific reason we have diverged from an existing (and excellent) solution? Isn't this unnecessary divergence for the phone? + There is a large spinning Ubuntu logo during updates and a small + spinning Ubuntu logo during the boot process. There are several bugs + already filed regarding the inconsistency in size and speed (see bug + 1355093 1335789 1350348) + + Regardless of the size/speed of the spinner, I this progress indicator + feels frantic, cheap and off brand to me. It is an obvious and + simplistic device, and one which we have tried to avoid as a core part + of the user experience. We have always been able to develop classier + options. E.g., the desktop has the word Ubuntu with dots which change + colour to indicate progress. Is there a specific reason we have + diverged from an existing (and excellent) solution? Isn't this + unnecessary divergence for the phone? And if there is a good reason for + a new solution (i.e, different than the desktop), then I think it needs + more work to reach the standard of beautiful design elsewhere in the + product. ** This bug is no longer a duplicate of bug 1355093 Inconsistent spinning-logo screens for startup and system image update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1367696 Title: spinning Ubuntu logo on update boot feels frantic and not very classy Status in Ubuntu UX bugs: Triaged Status in “unity-system-compositor” package in Ubuntu: New Bug description: There is a large spinning Ubuntu logo during updates and a small spinning Ubuntu logo during the boot process. There are several bugs already filed regarding the inconsistency in size and speed (see bug 1355093 1335789 1350348) Regardless of the size/speed of the spinner, I this progress indicator feels frantic, cheap and off brand to me. It is an obvious and simplistic device, and one which we have tried to avoid as a core part of the user experience. We have always been able to develop classier options. E.g., the desktop has the word Ubuntu with dots which change colour to indicate progress. Is there a specific reason we have diverged from an existing (and excellent) solution? Isn't this unnecessary divergence for the phone? And if there is a good reason for a new solution (i.e, different than the desktop), then I think it needs more work to reach the standard of beautiful design elsewhere in the product. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1367696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358310] Re: using umount with bash wildcard ends in device is busy for mount of parent directory
I'm not able to reproduce it here. Did you get any error messages from umount? ** Changed in: util-linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1358310 Title: using umount with bash wildcard ends in device is busy for mount of parent directory Status in “util-linux” package in Ubuntu: Incomplete Bug description: hi, i've run into a problem on ubuntu 14.04 while mounting an ganeti instance for doing some chroot stuff. but the problem itself not related to ganeti or any other virtualization. its just a problem while mounting/unmounting some devices. so heres an example how to reproduce the problem: lvcreate -L 1G -n test system lvcreate -L 1G -n test2 system mkfs.ext4 /dev/system/test mkfs.ext4 /dev/system/test2 mount /dev/system/test /mnt/ mkdir /mnt/test2 mount /dev/system/test2 /mnt/test2/ ln -sf /etc/issue /mnt/ umount /mnt/* umount /mnt/ lvremove -f /dev/system/test2 lvremove -f /dev/system/test if i run this commands /mnt/ is still mounted and it is only possible to umount it using -l switch. but after this it is still not possible to remove the logical volume because it says Logical volume system/test contains a filesystem in use. if i run the same commands but without the ln -sf /etc/issue /mnt/ everything is okay. also if i replace umount /mnt/* with umount /mnt/boot everything works. so it seems like umount ist opening /etc/issue for some reason if a bash wildcard is used and not releasing it. checking with lsof or fuser does not show any open files under /mnt/ nor for /etc/issue. the problem does not exist with ubuntu 12.04. a solution for this problem would be great because if you often do some chroot stuff it is easier to use umount /mnt/* to umount all bind mounts like /proc/ or /sys/ than running a umount command for each mount. also i havent found a way, other than reboot, to remove an open logical volume if it was hit by this problem. lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 regards the2nd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1358310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383297] Re: Edge intro/demo redesign
Olga, another aspect of this redesign that Saviq brought to my attention: translations for the fake apps during the right-edge swipe tutorial. Currently, they show English wording. If we're going to use screenshots that look like fake apps, we'd need to include translated screenshots. Which sounds like a pain. Maybe we could change the fake apps to not have visible text or temperatures or anything that needs localization? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383297 Title: Edge intro/demo redesign Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: A while ago, Design gave me new visuals for the edge demo [1], but it kept getting put off for other work. I'm filing a bug here to help it not get forgotten and so it can be assigned a priority. [1] https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386237] Re: tar acl support has strange behavior when used with --xattr
Just to demonstrate a particularly odd behavior: #!/bin/bash set -e; set -o pipefail tmpd=$(mktemp -d) trap rm -Rf $tmpd EXIT cd $tmpd; mkdir defaults ex setfacl --default --modify u::rwx --modify g::r-x --modify other::r-x defaults setfacl --remove-default ex xattr_args=--xattrs --xattrs-include=* ( set -x; tar $xattr_args --no-acl -cpf - defaults | tar -C ex $xattr_args --no-acl -xpf - ) for d in defaults ex/defaults; do echo === $d === echo == getfacl $d ==; getfacl $d | sed 's,^, ,' echo == ls -l $d == ; ls -l $d | sed 's,^, ,' echo == ls -ld $d == ; ls -ld $d | sed 's,^, ,' echo done ## end script / begin output ## + tar --xattrs '--xattrs-include=*' --no-acl -cpf - defaults + tar -C ex --xattrs '--xattrs-include=*' --no-acl -xpf - === defaults === == getfacl defaults == # file: defaults # owner: smoser # group: smoser user::rwx group::rwx other::r-x default:user::rwx default:group::r-x default:other::r-x == ls -l defaults == total 0 == ls -ld defaults == drwxrwxr-x+ 2 smoser smoser 4096 Oct 27 11:18 defaults === ex/defaults === == getfacl ex/defaults == # file: ex/defaults # owner: smoser # group: smoser user::rwx group::rwx other::r-x default:user::rwx default:group::r-x default:other::r-x == ls -l ex/defaults == total 0 == ls -ld ex/defaults == drwxrwxr-x+ 2 smoser smoser 4096 Oct 27 11:18 ex/defaults ** Summary changed: - tar acl support has strange behaviors + tar acl support has strange behavior when used with --xattr -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1386237 Title: tar acl support has strange behavior when used with --xattr Status in “tar” package in Ubuntu: New Bug description: as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl has unexpected behaviors. The one that caught us there was that extracting a tar file with '--acl' that was created without '--acl' results in default acl being set on the top level extracted directory. One would expect that if the source tar file had no acl information that the extracted directory would have no 'default' acl. I'll attach a script here that shows behavior of multiple combinations of: tar -c [--acl / -no-acl / default] tar -x [--acl / --no-acl / default ] and source directories with acl, without acl and with default default acl. Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl * bug 1313550: ping broken (xattrs lost in tar extraction) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: tar 1.27.1-2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 09:42:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1104 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: tar UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1386237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
** Description changed: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags Related Bugs: - * bug 1382632: horizon insecure key file permissions - * bug 1386237: tar strange behavior with --acl - * bug 1313550: ping broken (xattrs lost in tar extraction) + * bug 1382632: horizon insecure key file permissions + * bug 1386237: tar strange behavior with --acl and xattr + * bug 1313550: ping broken (xattrs lost in tar extraction) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Won't Fix Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl and xattr * bug 1313550: ping broken (xattrs lost in tar extraction) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
** Also affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Also affects: cups (Ubuntu) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Importance: Undecided = High ** Changed in: system-config-printer (Ubuntu) Importance: Undecided = High ** Also affects: system-config-printer (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cups-filters (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: cups (Ubuntu Trusty) Importance: Undecided = High ** Changed in: cups-filters (Ubuntu Trusty) Importance: Undecided = High ** Changed in: system-config-printer (Ubuntu Trusty) Importance: Undecided = High ** Changed in: cups (Ubuntu) Status: New = Fix Released ** Changed in: cups-filters (Ubuntu) Status: New = Fix Released ** Changed in: system-config-printer (Ubuntu) Status: New = Fix Released ** Changed in: cups-filters (Ubuntu Trusty) Milestone: None = trusty-updates ** Changed in: cups-filters (Ubuntu) Milestone: trusty-updates = None ** Changed in: cups (Ubuntu Trusty) Milestone: None = trusty-updates ** Changed in: system-config-printer (Ubuntu Trusty) Milestone: None = trusty-updates ** Changed in: cups (Ubuntu Trusty) Status: New = Triaged ** Changed in: cups-filters (Ubuntu Trusty) Status: New = Triaged ** Changed in: system-config-printer (Ubuntu Trusty) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: Triaged Status in “cups-filters” source package in Trusty: Triaged Status in “system-config-printer” source package in Trusty: Triaged Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no Generic IPP Everywhere Printer). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features.
[Touch-packages] [Bug 1336715] Re: switch-items in indicators sometimes get out of sync with system-settings
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- 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/1336715 Title: switch-items in indicators sometimes get out of sync with system- settings Status in Display Indicator: Invalid Status in Indicator Location: Invalid Status in Network Menu: Invalid Status in Sound Menu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376707] Re: Launcher needs to dynamically respond to reset
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- 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/1376707 Title: Launcher needs to dynamically respond to reset Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: Currently the reset launcher action initiated from the system settings app requires the user to reboot the device. The intended design is for the launcher to dynamically reset to the initial state and briefly reveal itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1376707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376044] Re: [scopes] Ubuntu button on launcher is hardcoded to click scope
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1376044 Title: [scopes] Ubuntu button on launcher is hardcoded to click scope Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: In Progress Bug description: The Ubuntu button should bring the user to their first favorite scope, rather than always the click scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 (not installed) ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 19:11:58 2014 InstallationDate: Installed on 2013-04-26 (522 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1376044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333187] Re: [Dash] [design] Preview images display as black thumbnails
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- 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/1333187 Title: [Dash] [design] Preview images display as black thumbnails Status in The Savilerow project: New Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Bug description: If the image is large, the Ubuntu shape rounded corners become very little, hardly noticable. REQUESTED UX SOLUTION Updated spec so images only zoomable once full screen. For all other instances of ubuntu shape, SDK documentation should be used (see link from Jouni in comments) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1333187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378872] Re: [emergency call] active call panel not displayed when phone locked
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- 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/1378872 Title: [emergency call] active call panel not displayed when phone locked Status in Dialer app for Ubuntu Touch: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: New Bug description: rtm build 88 on krillin Steps to reproduce: 1) lock phone (with passcode enabled) 2) call phone 3) answer call 4) dialer is displayed (in limited mode as phone is locked) 5) press back button in dialer header so that phone can be unlocked while on the call 6) greeter is displayed 7) now try to get back to active call Expected results: - the active call panel should be displayed on the greeter screen to allow user to go directly back to the call without having to unlock the phone Actual results: - the active call panel is not displayed. The only way to get back to the active call is to unlock the phone (or press the emergency call button), neither which is obvious To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1378872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381930] Re: 7digital previews do not play in the scope
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: New Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379786] Re: Processes out of pgroup don't get stopped
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- 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/1379786 Title: Processes out of pgroup don't get stopped Status in Qt integration with the Mir display server: In Progress Status in “qtmir” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “qtmir” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: If an application has processes that are not in the process group of the primary process the application lifecycle will not stop or resume them, effectively leaving them unmanaged. The most obvious cause of this is any web app or the browser which has processes started by the sandbox. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1379786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379788] Re: Oxide processes don't get OOM adjusted
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- 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/1379788 Title: Oxide processes don't get OOM adjusted Status in Qt integration with the Mir display server: In Progress Status in “qtmir” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “qtmir” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: OOM adjustment is important to the lifecycle because it makes it so that the focused application actually gets the full usage of the device. By not OOM adjusting the Oxide renders, some of the largest processes in the system aren't killed appropriately by the OOM killer. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1379788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383297] Re: Edge tutorial's redesign: new gestures
I've split this bug in two: - This bug, which is about adding new gestures to the tutorial (right edge swipe, bottom edge swipe, long vs short swipes). - And bug 1386268, which is just about the new look and feel (and dropping the greeter swipe page). This way, we can schedule the two changes separately. ** Summary changed: - Edge intro/demo redesign + Edge tutorial's redesign: new gestures -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383297 Title: Edge tutorial's redesign: new gestures Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: The first-boot edge tutorial should cover a wider range of gestures than it currently does. Things like right edge swipe, bottom edge swipe, and long vs short swipes. Visual designs (not entirely finished yet): https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1335761] Re: [Dash] Activating a preview with a scope URI for the current scope doesn't send you back to the results view
** Tags removed: touch-2014-10-09 ** Tags added: touch-2014-11-13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1335761 Title: [Dash] Activating a preview with a scope URI for the current scope doesn't send you back to the results view Status in “unity-scopes-shell” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: You'll have to compile (prototype) the Youtube scope from source (https://launchpad.net/unity-scope-youtube/), as it's not in distro yet. Basically the workflow is: 1) Search for something that has a result with a scope URI for the current scope. In the case of Youtube, search for queenofficial to get Queen's music channel. 2) Preview the first item (the channel itself), and click the search button. 3) This runs a new query for the current scope, but doesn't switch away from the preview view). 4) You will see a preview of the first video in the new results list. Like when searching other scopes, the view should be returned to the results list, instead of saying in the preview view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1335761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378872] Re: [emergency call] active call panel not displayed when phone locked
** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378872 Title: [emergency call] active call panel not displayed when phone locked Status in Dialer app for Ubuntu Touch: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: rtm build 88 on krillin Steps to reproduce: 1) lock phone (with passcode enabled) 2) call phone 3) answer call 4) dialer is displayed (in limited mode as phone is locked) 5) press back button in dialer header so that phone can be unlocked while on the call 6) greeter is displayed 7) now try to get back to active call Expected results: - the active call panel should be displayed on the greeter screen to allow user to go directly back to the call without having to unlock the phone Actual results: - the active call panel is not displayed. The only way to get back to the active call is to unlock the phone (or press the emergency call button), neither which is obvious To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1378872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon
This has only been a cosmetic bug for me for a long time. However, I took the ping as an opportunity to try a few of the things in comment #6. Changing managed=false to managed=true was the only change necessary to fix the icon in Utopic. I consider this bug fixed. ** Changed in: network-manager (Ubuntu) Status: Triaged = Fix Released -- 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/751939 Title: Wired-only machine has empty volcano icon Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/751939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
For the SRU team: debdiff for system-config-printer ** Patch added: system-config-printer_1.4.3+20140219-0ubuntu2.2_1.4.3+20140219-0ubuntu2.3.debdiff https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+attachment/4246319/+files/system-config-printer_1.4.3%2B20140219-0ubuntu2.2_1.4.3%2B20140219-0ubuntu2.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no Generic IPP Everywhere Printer). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
For the SRU team: debdiff for cups-filters ** Patch added: cups-filters_1.0.52-0ubuntu1.2_1.0.52-0ubuntu1.3.debdiff https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+attachment/4246318/+files/cups-filters_1.0.52-0ubuntu1.2_1.0.52-0ubuntu1.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no Generic IPP Everywhere Printer). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
Daniel, I am very grateful if you could test the IPP-over-USB support with these updates on a Trusty system and with your IPP-over-USB printer. You can already start testing before SRU -proposed approval by applying the three debdiffs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no Generic IPP Everywhere Printer). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
For the SRU team: debdiff for cups ** Patch added: cups_1.7.2-0ubuntu1.2_1.7.2-0ubuntu1.3.debdiff https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+attachment/4246320/+files/cups_1.7.2-0ubuntu1.2_1.7.2-0ubuntu1.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no Generic IPP Everywhere Printer). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
Note for everyone who wants to test and for the SRU team. The SRU works only by updating all three packages, especially the binary package system-config-printer-udev needs the new cups-filters-ippusbxd package now. ** Changed in: cups (Ubuntu Trusty) Status: Triaged = In Progress ** Changed in: cups-filters (Ubuntu Trusty) Status: Triaged = In Progress ** Changed in: system-config-printer (Ubuntu Trusty) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no Generic IPP Everywhere Printer). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
Uploaded fixed versions of the cups-filters, system-config-printer, and cups packages to trusty-proposed now. As soon as they get approved they get available for installation and instructions for installing them get posted here. Please update all the packages and test the IPP Everywhere support. Report your results here as this is required for the update getting into the official updates or Trusty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no Generic IPP Everywhere Printer). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373985] Re: unity8-dash doesn't seem to get activated after we leave the lock screen
** Branch linked: lp:~michael-sheldon/ubuntu/utopic/maliit- framework/fix-1373985 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1373985 Title: unity8-dash doesn't seem to get activated after we leave the lock screen Status in “maliit-framework” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Bug description: Steps to reproduce the issue: 1 - lock the phone (reboot or have the display off and then turn it back on) 2 - type you password [you're brought to unity8-dash] 3 - tap on the looking glass icon in the top right [search bar text entry shows up with Search apps written on it] Expected outcome: A blinking cursor caret is displayed on the app search text entry and the VKB comes up. Actual outcome: Nothing happens. Causing unity-8 dash to be refocused, such as bringing the indicators panel down and then back up solves it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1373985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336715] Re: switch-items in indicators sometimes get out of sync with system-settings
** Also affects: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Nick Dedekind (nick-dedekind) -- 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/1336715 Title: switch-items in indicators sometimes get out of sync with system- settings Status in Display Indicator: Invalid Status in Indicator Location: Invalid Status in Network Menu: Invalid Status in Sound Menu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu RTM: New Status in “unity8” package in Ubuntu RTM: In Progress Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383702] Re: Welcome Wizard: Passphrase has no obvious way to continue
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Michael Terry (mterry) ** Also affects: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: New = In Progress ** Changed in: ubuntu-system-settings (Ubuntu RTM) Assignee: (unassigned) = Michael Terry (mterry) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383702 Title: Welcome Wizard: Passphrase has no obvious way to continue Status in Ubuntu Touch System Settings: New Status in “ubuntu-system-settings” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: STEPS: 1. Flash a fresh image 2. Select a language 3. Select passphrase 4. Add a passphrase EXPECTED: Every other page has a back and continue/skip buttons, I expect to see a continue button on the page ACTUAL: You have no obvious way to continue, there is no text saying to hit enter after the passphrase is completed nor is there a continue button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1383702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333187] Re: [Dash] [design] Preview images display as black thumbnails
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Andrea Cimitan (cimi) -- 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/1333187 Title: [Dash] [design] Preview images display as black thumbnails Status in The Savilerow project: New Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: If the image is large, the Ubuntu shape rounded corners become very little, hardly noticable. REQUESTED UX SOLUTION Updated spec so images only zoomable once full screen. For all other instances of ubuntu shape, SDK documentation should be used (see link from Jouni in comments) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1333187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon
** Changed in: network-manager (Ubuntu) Status: Fix Released = New -- 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/751939 Title: Wired-only machine has empty volcano icon Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/751939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376044] Re: [scopes] Ubuntu button on launcher is hardcoded to click scope
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Michael Zanetti (mzanetti) ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1376044 Title: [scopes] Ubuntu button on launcher is hardcoded to click scope Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: The Ubuntu button should bring the user to their first favorite scope, rather than always the click scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 (not installed) ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 19:11:58 2014 InstallationDate: Installed on 2013-04-26 (522 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1376044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355173] Re: Switching windows with a Trusted Prompt Session active loses the trusted prompt session
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Nick Dedekind (nick-dedekind) ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu RTM) Status: In Progress = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1355173 Title: Switching windows with a Trusted Prompt Session active loses the trusted prompt session Status in Qt integration with the Mir display server: In Progress Status in Online Accounts setup for Ubuntu Touch: Confirmed Status in “pay-service” package in Ubuntu: New Status in “trust-store” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: When we create a trusted prompt session over an application, let's say a small dialog, and then switch applications, when we switch back to the original application the dialog is not overlayed on top of the original application. The program providing the dialog seems happy, and is still running, but visually it is not there. We notice this when using the payments UI which overlays ontop of the dash. In some cases we need to show Online Accounts which runs as an independent application and causes a switching behavior. When returning back to the dash the Payment UI is not visible. It also happens if the Payment UI is visible and you switch applications using the right swipe. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1355173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358343] Re: [TOPBLOCKER] too easy to answer a call by accident
** Also affects: unity-notifications (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity-notifications (Ubuntu RTM) Assignee: (unassigned) = Mirco Müller (macslow) ** Changed in: unity-notifications (Ubuntu RTM) Status: New = In Progress ** Changed in: unity-notifications (Ubuntu RTM) Importance: Undecided = Critical ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Mirco Müller (macslow) ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1358343 Title: [TOPBLOCKER] too easy to answer a call by accident Status in Telephony Service: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: Confirmed Status in “telephony-service” package in Ubuntu: New Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: If you put the phone in your pocket with locked screen and you receive a call is too easy to answer or reject that by mistake. Or pressing the screen while trying to get the phone or the call can be answered without you noticed by your pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1358343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385630] Re: New systemd (215) does not boot very well
I downgraded systemd to the version 208 in official Vivid repos. Now booting works perfectly and fast. It may be worthwhile to tell that I have purged systemd-shim, cgmanager and libcgmanager0 from my setup. So this really is a pure systemd booting setup now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1385630 Title: New systemd (215) does not boot very well Status in “systemd” package in Ubuntu: New Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378462] Re: cannot reply to second notification
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Nick Dedekind (nick-dedekind) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1378462 Title: cannot reply to second notification Status in “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: build 88, rtm on krillin - unlock the phone - make sure messaging-app is not running - send two sms messages to the phone - once they appear, open the messaging-menu - reply to the first message by clicking the message which makes it expand to reveal the send field - this works - attempt to reply to the second message by clicking the message to make it expand Expected results: the item should expand and allow you to send a message Actual results: the item cannot be expanded and you can't reply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378827] Re: [notification] incoming call snap decision should prevent edge interaction on greeter
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Mirco Müller (macslow) ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378827 Title: [notification] incoming call snap decision should prevent edge interaction on greeter Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: rtm build 88 on krillin Steps to reproduce: - unlock the phone - call the phone - when the incoming call snap decision is displayed, all access to the edges is blocked and the dialog is modal, as it should be - now lock the phone - call the phone Expected results: - all access to the edges is blocked and the snap-decision is modal, as is the case when the phone is unlocked Actual results: - the launcher can be swiped and the top panel can be interacted with. the edges are not blocked as they should be This is related to #1358343 [notifications] [design] too easy to answer a call by accident. We need this to be fixed so users don't inadavertently interact with the indicators or launcher when the phone is there pocket and an incoming call arrives. This fix, coupled with the fix to the snap decision to have a swipe to answer would prevent most of the problems that can occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381930] Re: 7digital previews do not play in the scope
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) 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/1381930 Title: 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: New Status in “unity8” package in Ubuntu RTM: New Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon
I take that back. Setting managed=true breaks the networking. Even though I get the proper icon and all the network connection information appears to be correct (both as displayed by ifconfig and through the NM u/i), I cannot ping or connect to any service outside my LAN. Gateway and DNS services, IPv4 address and netmask all *look* right, but nothing gets outside the LAN. Setting it back to managed=false fixes this but of course volcano-izes the icon. I'll take functional networking over cosmetics. :) -- 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/751939 Title: Wired-only machine has empty volcano icon Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/751939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278193] Re: logrotate skip the rotation of many files under /var/log due to bad group ownership
I've went through this problem just now. The changes described in #5 solved the problem for me as well. The fix released in LP: #1258202 (logrotate version 3.8.6-1ubuntu2) adds those lines to the default logrotate.conf file, but I got some custom configs in mine and so I had to manually change it. Of course it only works when it reads logrotate.conf, which I guess is not the case when you run this way: logrotate -df /etc/logrotate.d/rsyslog Running either /etc/cron.daily/logrotate or /usr/sbin/logrotate /etc/logrotate.conf works fine. Maybe the config su root syslog should be the compile-time-default in Ubuntu so to avoid this situation. Don't know if it is possible. Also, from what I understand reading man logrotate.conf, the su root syslog line only changes the user/group that the process of rotation will run as, which does not (necessarily) affect the owner and group of the log files: that is defined by the create directive (see the logrotate.conf man for that directive). That's why you don't see any files with group syslog, Uwe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1278193 Title: logrotate skip the rotation of many files under /var/log due to bad group ownership Status in “logrotate” package in Ubuntu: Confirmed Bug description: With the latest update to logrotate (3.8.7-1ubuntu1), the group ownership of /var/log was changed to syslog causing this kind of problem: # logrotate -df /etc/logrotate.d/rsyslog reading config file /etc/logrotate.d/rsyslog Handling 2 logs rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog error: skipping /var/log/syslog because parent directory has insecure permissions (It's world writable or writable by group which is not root) Set su directive in config file to tell logrotate which user/group should be used for rotation. ... # ls -la /var/ | grep log drwxrwxr-x 17 root syslog 4096 Feb 9 10:58 log $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ apt-cache policy logrotate logrotate: Installed: 3.8.7-1ubuntu1 Candidate: 3.8.7-1ubuntu1 Version table: *** 3.8.7-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: logrotate 3.8.7-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 17:19:41 2014 InstallationDate: Installed on 2014-01-26 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) SourcePackage: logrotate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1278193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374721] Re: ibus-daemon uses 100% CPU when using gnome-calculator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1374721 Title: ibus-daemon uses 100% CPU when using gnome-calculator Status in “ibus” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open gnome-calculator 2. Enter 3*7 3. Notice that ibus-daemon and ibus-x11 are using 100+% CPU ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 27 20:32:05 2014 InstallationDate: Installed on 2014-09-03 (24 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1374721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351939] Re: Sending USSD message does not work
** Changed in: modem-manager-gui (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351939 Title: Sending USSD message does not work Status in Modem Manager Gui: Invalid Status in ModemManager (with NetworkManager support): New Status in “modem-manager-gui” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: New Bug description: The error message says: Error sending USSD GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5 This is reported upstream here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270245] Re: Backward frame jumps on mali (Nexus 10 krillin)
In krillin you can still see frame jumps or out of order frames with: sudo stop lightdm sudo mir_demo_server_basic --disable-overlays=true --launch-client mir_demo_client_egltriangle -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1270245 Title: Backward frame jumps on mali (Nexus 10 krillin) Status in Mir: Confirmed Status in “mir” package in Ubuntu: Confirmed Bug description: Alexandros, Andreas, and I have noted at different points that we see frame skips on the nexus 10. The frames look like they move in a 1,3,2 pattern, particularly when unlocking the device. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1270245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386323] [NEW] is friend app not available in 14.10?
Public bug reported: is friend app not available in 14.10. I used to get notifications in the previous versions of ubuntu. Its not working in 14.10. I was using the friends app till ubuntu 14.04 as soon as I updated to ubuntu 14.10, the friends app is not working. I used to get notifications (notify osd) in the previous version. Neither the app is getting updated with the latest feeds from twitter and facebook nor I am getting any notifications. I tried uninstalling and reinstalling as well as remove the online accounts from the systems settings menu and added the accounts again. Neither way it doesnt seems to work. It was reallt a very good application. Please some one help me on this. Is the friends app still supported in the latest version of ubuntu? ** Affects: friends-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 friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1386323 Title: is friend app not available in 14.10? Status in “friends-app” package in Ubuntu: New Bug description: is friend app not available in 14.10. I used to get notifications in the previous versions of ubuntu. Its not working in 14.10. I was using the friends app till ubuntu 14.04 as soon as I updated to ubuntu 14.10, the friends app is not working. I used to get notifications (notify osd) in the previous version. Neither the app is getting updated with the latest feeds from twitter and facebook nor I am getting any notifications. I tried uninstalling and reinstalling as well as remove the online accounts from the systems settings menu and added the accounts again. Neither way it doesnt seems to work. It was reallt a very good application. Please some one help me on this. Is the friends app still supported in the latest version of ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1386323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Fix works for me too, but it obviously isn't the proper solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 Status in “openssh” package in Ubuntu: Confirmed Bug description: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270245] Re: Backward frame jumps on mali (Nexus 10 krillin)
See backwards frame jumps at 0:04 and 0:24 marks in the attached video. ** Attachment added: IMG_1038.MOV https://bugs.launchpad.net/mir/+bug/1270245/+attachment/4246372/+files/IMG_1038.MOV -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1270245 Title: Backward frame jumps on mali (Nexus 10 krillin) Status in Mir: Confirmed Status in “mir” package in Ubuntu: Confirmed Bug description: Alexandros, Andreas, and I have noted at different points that we see frame skips on the nexus 10. The frames look like they move in a 1,3,2 pattern, particularly when unlocking the device. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1270245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I have a workaround for this, use Gnome instead of Unity. It took me a while to realize/figure out that it's pretty painless to just run a different window manager on Ubuntu. I did look at maybe switching to a different lock screen but there was no straightforward way to do that. It turns out you just use apt to install gnome-shell and then from the login screen you have the option to run Gnome instead of Unity (click the little icon on that line with your name when you're logging in to select the window manager you want). The bug makes Unity so inconvenient to use that I was considering switching to another Linux distribution. I don't see any downside to switching to Gnome so far, so this seems like a reasonable workaround until the problem is resolved. Or maybe forever, I don't care about Gnome vs. Unity and Gnome seems to work just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270245] Re: Backward frame jumps on mali (Nexus 10 krillin)
I've was also able to reproduce the frame jump issue today, so my theories in comment #32 don't have a bearing on the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1270245 Title: Backward frame jumps on mali (Nexus 10 krillin) Status in Mir: Confirmed Status in “mir” package in Ubuntu: Confirmed Bug description: Alexandros, Andreas, and I have noted at different points that we see frame skips on the nexus 10. The frames look like they move in a 1,3,2 pattern, particularly when unlocking the device. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1270245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381041] Re: Network indicator is sometimes blank
approved https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-1361642 in https://bugs.launchpad.net/dbus-cpp/+bug/1361642 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1381041 Title: Network indicator is sometimes blank Status in “indicator-network” package in Ubuntu: In Progress Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: This is on krillin r103, but it has been happening for a while. See attached photo. I am not certain what triggers it. but I think it may happen when wifi APs become in and out of range while walking around town (as if the list does not refresh reliably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1381041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Here's an article with screenshots of how to actually find the icon that lets you choose your shell: http://www.howtogeek.com/112620/how-to-install-use-gnome-shell-on-ubuntu/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Sorry, one more thing... I think the correct matepackage is ubuntu- gnome-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 305546] Re: Nautilus crashing/freezing when opening folder with svg file
This bug is back -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/305546 Title: Nautilus crashing/freezing when opening folder with svg file Status in libRSVG - SVG Rendering Library: Invalid Status in “librsvg” package in Ubuntu: Fix Released Status in Debian GNU/Linux: Invalid Bug description: Strange thing started happening a few days ago: When I access nautilus from the Places menu and open my home directory (named eric) nautilus always freezes. I can open subdirectories and other bookmarks such as Documents, Pictures, etc and browse files, but the second I browse to my main home directory, nautilus freezes. I can click any icons for sub- folders in my home folder, but nautilus will hang and, within a few seconds, turn grey and stay that way. The only way to get nautilus to close is by forcing a quit. I can access any of the files and folders by CLI, or by using emelFM2. After much searching, I found an old bug report at: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/30010 . . . which seemed to blame the crashiness on folders containing an svg image. Interestingly enough, I was messing around in Inkscape the other day trying to create a business card and saved my work into my home folder as an svg. As soon as I deleted or moved that file Nautilus no longer crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/305546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385572] Re: gnome-session not shutting down cleanly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (Ubuntu) Status: New = Confirmed -- 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/1385572 Title: gnome-session not shutting down cleanly Status in Ubuntu GNOME: New Status in “upstart” package in Ubuntu: Confirmed Bug description: We have had reports going back to 13.10 that gnome-shell extensions are disabled after restart (LP: #1236749), I've only just managed to reproduce this and have discovered that gnome-session is not shutting down cleanly. Basically, X gets shutdown, which causes gnome-shell to abort, following this gnome-session tries to respawn gnome-shell which fails and due to this failure disables all shell extensions. I don't know enough about upstart to really understand what is going on but it appears this also affects unity and it just hasnt been noticed since there are probably no such side-effects happening there. Filing this against upstart since this is not reproducible when using systemd init, though it may well be a bug in gnome-session, but related to upstart user sessions. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 25 14:05:24 2014 InstallationDate: Installed on 2012-09-23 (762 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha amd64(20120922) SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1385572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386359] [NEW] [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all
Public bug reported: When I select a music file or a video file, no sound comes from the speakers, although when I checked the speakers, it worked fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vientozur 1794 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 27 14:48:38 2014 InstallationDate: Installed on 2014-01-16 (283 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Audio Interno - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vientozur 1794 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-10-23 (3 days ago) dmi.bios.date: 03/26/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd03/26/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXV2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** 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/1386359 Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: When I select a music file or a video file, no sound comes from the speakers, although when I checked the speakers, it worked fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vientozur 1794 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 27 14:48:38 2014 InstallationDate: Installed on 2014-01-16 (283 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Audio Interno - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vientozur 1794 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-10-23 (3 days ago) dmi.bios.date: 03/26/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd03/26/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXV2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1386359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
