[Touch-packages] [Bug 1348883] [NEW] Password field on login does not respond to keyboard
*** This bug is a security vulnerability *** Public security bug reported: After closing my laptop and reopening it again, Ubuntu asks for my password. The input field is selected, but when I type nothing happens. Clicking around and back on the input also has no effect. I could solve it so far in 2 ways; restart, and select 'switch user'. On the second approach I found that the text I had entered now appeared in the text editor that was open, when I closed the laptop. Further info: this was an online text editor ( Just checked, also occurs when closing with this specific inout field (in which I'm currently entering this text) selected). Problem doesn't occur in Sublime Text, haven't checked other text editors. Reason I select this as a safety threat; I am inputting my Password unknowingly on an online form... ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1348883 Title: Password field on login does not respond to keyboard Status in “initramfs-tools” package in Ubuntu: New Bug description: After closing my laptop and reopening it again, Ubuntu asks for my password. The input field is selected, but when I type nothing happens. Clicking around and back on the input also has no effect. I could solve it so far in 2 ways; restart, and select 'switch user'. On the second approach I found that the text I had entered now appeared in the text editor that was open, when I closed the laptop. Further info: this was an online text editor ( Just checked, also occurs when closing with this specific inout field (in which I'm currently entering this text) selected). Problem doesn't occur in Sublime Text, haven't checked other text editors. Reason I select this as a safety threat; I am inputting my Password unknowingly on an online form... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1348883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341205] Re: Top left icon of my apps can be placed in the middle of the apps
Also you can now trigger it even more easily on r152 Go to apps scope click on see all scroll all the way down click on ubuntu store click on the back button on the header of ubuntu store bug -- 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/1341205 Title: Top left icon of my apps can be placed in the middle of the apps Status in “unity8” package in Ubuntu: Confirmed Bug description: Top left icon of my apps can be placed in the middle of the apps Image of bug http://i.imgur.com/nceYuBL.png How to trigger go to the app scop click on my apps to see all the apps go to the media player app click on it (no video should be available on the device) message appear saying that there is no file to play click ok bug triggered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1341205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340386] Re: x-ofono-unknown displayed in msg menu and call log
** Branch linked: lp:ubuntu/utopic-proposed/dialer-app ** Branch linked: lp:ubuntu/utopic-proposed/telephony-service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1340386 Title: x-ofono-unknown displayed in msg menu and call log Status in Dialer app for Ubuntu Touch: New Status in Telephony Service: New Status in “dialer-app” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: New Bug description: If you get a call from an line with blocked caller id, it correctly shows in the notification as Unknown caller but is not correct in the messaging menu or dialer-app recent call logs. There is incorrectly shows x-ofono-unknown. Desired solution is this string should be replaced by unknown caller or blocked string. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1340386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347079] Re: Incoming Photo MMS from T-Mobile includes smil in message text
** Branch linked: lp:ubuntu/utopic-proposed/telephony-service ** Branch linked: lp:ubuntu/utopic-proposed/messaging-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1347079 Title: Incoming Photo MMS from T-Mobile includes smil in message text Status in Messaging App: New Status in “messaging-app” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: New Bug description: Running image #u144 on mako, I confirmed that MMS message can indeed be received on a phone with an ATT SIM ( see bug #1324157 ). That said, when the message was displayed in the messaging-app, the text smil was displayed, even though no text was sent with the photo. To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1347079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346995] Re: Could not unmute during a call
** Branch linked: lp:ubuntu/utopic-proposed/telephony-service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1346995 Title: Could not unmute during a call Status in “dialer-app” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: New Bug description: In the middle of a call Pressed mute, and set phone down for 5 mins returned to phone, greeter was showing Swiped away greeter to dialer Unmuted (button showed unmuted) Phone was still muted, and the button would not change state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1346995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 134955] Re: Tooltips frequently appear below menus
** Changed in: gtk Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/134955 Title: Tooltips frequently appear below menus Status in GTK+ GUI Toolkit: Won't Fix Status in “gtk+2.0” package in Ubuntu: Triaged Bug description: Open the Applications menu Highlight Accessories Wait for tooltip to appear Highlight Games, underneath Notice that the tooltip appears immediately, but the menu appears a short while later. The menu obscures the tooltip. This does not always happen the first time, try moving backwards and forwards between items and it will eventually happen. Tooltips should have the highest Z order than any other window class. ProblemType: Bug Architecture: i386 Date: Sun Aug 26 20:53:37 2007 DistroRelease: Ubuntu 7.10 Package: libgtk2.0-0 2.11.6-1ubuntu3 PackageArchitecture: i386 SourcePackage: gtk+2.0 Uname: Linux flash 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/134955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347085] Re: Voice message indication no longer invokes the dialer
This bug was fixed in the package telepathy-ofono - 0.2+14.10.20140725.2-0ubuntu1 --- telepathy-ofono (0.2+14.10.20140725.2-0ubuntu1) utopic; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Tiago Salem Herrmann ] * Add VoicemailNumberChanged() signal (LP: #1347085) * Fix PropertyChanged signal connection. Improve delivery report (LP: #1337597) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 25 Jul 2014 21:29:36 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1347085 Title: Voice message indication no longer invokes the dialer Status in The Messaging Menu: New Status in Telephony Service: New Status in “telepathy-ofono” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: Fix Released Bug description: Leave a voice message See it in the messaging indicator open the Voice message notification Click on phone The entry is cleared, but the dialer does not get invoked To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1347085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347079] Re: Incoming Photo MMS from T-Mobile includes smil in message text
This bug was fixed in the package messaging-app - 0.1+14.10.20140725-0ubuntu1 --- messaging-app (0.1+14.10.20140725-0ubuntu1) utopic; urgency=low [ Tiago Salem Herrmann ] * Ignore x-smil content-type. Enable spinner for mms (LP: #1347079) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 25 Jul 2014 20:19:55 + ** Changed in: messaging-app (Ubuntu) Status: New = Fix Released ** Changed in: telephony-service (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1347079 Title: Incoming Photo MMS from T-Mobile includes smil in message text Status in Messaging App: New Status in “messaging-app” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: Fix Released Bug description: Running image #u144 on mako, I confirmed that MMS message can indeed be received on a phone with an ATT SIM ( see bug #1324157 ). That said, when the message was displayed in the messaging-app, the text smil was displayed, even though no text was sent with the photo. To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1347079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347085] Re: Voice message indication no longer invokes the dialer
This bug was fixed in the package telephony-service - 0.1+14.10.20140725.2-0ubuntu1 --- telephony-service (0.1+14.10.20140725.2-0ubuntu1) utopic; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Tiago Salem Herrmann ] * Use correct label for blocked and private numbers on messaging-menu. (LP: #1340386) * Listen for VoicemailNumberChanged() signal (LP: #1347085) * Recover mute state. (LP: #1346995) * Fix smil file generation (LP: #1347079) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 25 Jul 2014 21:33:01 + ** Changed in: telephony-service (Ubuntu) Status: New = Fix Released ** Changed in: telepathy-ofono (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1347085 Title: Voice message indication no longer invokes the dialer Status in The Messaging Menu: New Status in Telephony Service: New Status in “telepathy-ofono” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: Fix Released Bug description: Leave a voice message See it in the messaging indicator open the Voice message notification Click on phone The entry is cleared, but the dialer does not get invoked To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1347085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346995] Re: Could not unmute during a call
This bug was fixed in the package telephony-service - 0.1+14.10.20140725.2-0ubuntu1 --- telephony-service (0.1+14.10.20140725.2-0ubuntu1) utopic; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Tiago Salem Herrmann ] * Use correct label for blocked and private numbers on messaging-menu. (LP: #1340386) * Listen for VoicemailNumberChanged() signal (LP: #1347085) * Recover mute state. (LP: #1346995) * Fix smil file generation (LP: #1347079) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 25 Jul 2014 21:33:01 + ** Changed in: telephony-service (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1346995 Title: Could not unmute during a call Status in “dialer-app” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: Fix Released Bug description: In the middle of a call Pressed mute, and set phone down for 5 mins returned to phone, greeter was showing Swiped away greeter to dialer Unmuted (button showed unmuted) Phone was still muted, and the button would not change state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1346995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340386] Re: x-ofono-unknown displayed in msg menu and call log
This bug was fixed in the package telephony-service - 0.1+14.10.20140725.2-0ubuntu1 --- telephony-service (0.1+14.10.20140725.2-0ubuntu1) utopic; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Tiago Salem Herrmann ] * Use correct label for blocked and private numbers on messaging-menu. (LP: #1340386) * Listen for VoicemailNumberChanged() signal (LP: #1347085) * Recover mute state. (LP: #1346995) * Fix smil file generation (LP: #1347079) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 25 Jul 2014 21:33:01 + ** Changed in: telephony-service (Ubuntu) Status: New = Fix Released ** Changed in: dialer-app (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1340386 Title: x-ofono-unknown displayed in msg menu and call log Status in Dialer app for Ubuntu Touch: New Status in Telephony Service: New Status in “dialer-app” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: Fix Released Bug description: If you get a call from an line with blocked caller id, it correctly shows in the notification as Unknown caller but is not correct in the messaging menu or dialer-app recent call logs. There is incorrectly shows x-ofono-unknown. Desired solution is this string should be replaced by unknown caller or blocked string. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1340386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340386] Re: x-ofono-unknown displayed in msg menu and call log
This bug was fixed in the package dialer-app - 0.1+14.10.20140725.1-0ubuntu1 --- dialer-app (0.1+14.10.20140725.1-0ubuntu1) utopic; urgency=low [ CI bot ] * Resync trunk [ Gustavo Pichorim Boiko ] * Set the bottom edge visibility directly and not using the QML states. For some reason the bottom edge widget doesn't like it. (LP: #1346996) * Fix the displayed label for unknown and private numbers, and also do not allow placing calls for those numbers. (LP: #1340386) [ Tiago Salem Herrmann ] * Use an empty filter to return all the entries [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 25 Jul 2014 18:49:41 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1340386 Title: x-ofono-unknown displayed in msg menu and call log Status in Dialer app for Ubuntu Touch: New Status in Telephony Service: New Status in “dialer-app” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: Fix Released Bug description: If you get a call from an line with blocked caller id, it correctly shows in the notification as Unknown caller but is not correct in the messaging menu or dialer-app recent call logs. There is incorrectly shows x-ofono-unknown. Desired solution is this string should be replaced by unknown caller or blocked string. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1340386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1337597] Re: [messaging] report errors when MMS message fails
This bug was fixed in the package telepathy-ofono - 0.2+14.10.20140725.2-0ubuntu1 --- telepathy-ofono (0.2+14.10.20140725.2-0ubuntu1) utopic; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Tiago Salem Herrmann ] * Add VoicemailNumberChanged() signal (LP: #1347085) * Fix PropertyChanged signal connection. Improve delivery report (LP: #1337597) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 25 Jul 2014 21:29:36 + ** Changed in: telepathy-ofono (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1337597 Title: [messaging] report errors when MMS message fails Status in Messaging App: New Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in “messaging-app” package in Ubuntu: New Status in “telepathy-ofono” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: New Bug description: with build 112 + updates (latest nuntium) you can send an MMS but it fails. User is never told that it fails. To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1337597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347079] Re: Incoming Photo MMS from T-Mobile includes smil in message text
This bug was fixed in the package telephony-service - 0.1+14.10.20140725.2-0ubuntu1 --- telephony-service (0.1+14.10.20140725.2-0ubuntu1) utopic; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Tiago Salem Herrmann ] * Use correct label for blocked and private numbers on messaging-menu. (LP: #1340386) * Listen for VoicemailNumberChanged() signal (LP: #1347085) * Recover mute state. (LP: #1346995) * Fix smil file generation (LP: #1347079) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 25 Jul 2014 21:33:01 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1347079 Title: Incoming Photo MMS from T-Mobile includes smil in message text Status in Messaging App: New Status in “messaging-app” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: Fix Released Bug description: Running image #u144 on mako, I confirmed that MMS message can indeed be received on a phone with an ATT SIM ( see bug #1324157 ). That said, when the message was displayed in the messaging-app, the text smil was displayed, even though no text was sent with the photo. To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1347079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346996] Re: Bottom edge controls not present after a call
This bug was fixed in the package dialer-app - 0.1+14.10.20140725.1-0ubuntu1 --- dialer-app (0.1+14.10.20140725.1-0ubuntu1) utopic; urgency=low [ CI bot ] * Resync trunk [ Gustavo Pichorim Boiko ] * Set the bottom edge visibility directly and not using the QML states. For some reason the bottom edge widget doesn't like it. (LP: #1346996) * Fix the displayed label for unknown and private numbers, and also do not allow placing calls for those numbers. (LP: #1340386) [ Tiago Salem Herrmann ] * Use an empty filter to return all the entries [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 25 Jul 2014 18:49:41 + ** Changed in: dialer-app (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1346996 Title: Bottom edge controls not present after a call Status in “dialer-app” package in Ubuntu: Fix Released Bug description: Made a call Held the phone away from face so proximity was not enabled Screen goes blank wake up phone to see the greeter return to the dialer, hang up the call Now the dialer shows no bottom edge controls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1346996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324257] Re: utopic lubuntu insserv error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1324257 Title: utopic lubuntu insserv error Status in “dbus” package in Ubuntu: Confirmed Bug description: Did apt-get update, apt-get dist-upgrade and got this error: Setting up lightdm (1.11.2-0ubuntu3) ... insserv: Service dbus has to be enabled to start service lightdm insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package lightdm (--configure): subprocess installed post-installation script returned error exit status 1 Did a fresh install May 27 lubuntu 32 bit, got the same error. jerry@Aspire1:~$ ./lsb DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.10 DISTRIB_CODENAME=utopic DISTRIB_DESCRIPTION=Ubuntu Utopic Unicorn (development branch) Linux Aspire1 3.15.0-3-generic #7-Ubuntu SMP Mon May 26 07:52:05 UTC 2014 i686 i686 i686 GNU/Linux Seems to be running. Let me try reboot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.15.0-3.7-generic 3.15.0-rc7 Uname: Linux 3.15.0-3-generic i686 ApportVersion: 2.14.2-0ubuntu4 Architecture: i386 Date: Wed May 28 16:49:36 2014 InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper iso-scan/filename=/utopic-desktop-i386.iso noprompt noeject InstallationDate: Installed on 2014-05-28 (0 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha i386 (20140527) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1324257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.
Maybe what I mentioned above (unrelated to this bug) is due to the fix to Bug #1170508. So, forget what I asked. Just to repeat what I wrote 2 comments above: this bug is fixed for me. -- 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/1243233 Title: Holding Super key doesn't bring up shortcut overlay. Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: After upgrading from 13.04 to 13.10, holding Super no longer brings up the help overlay. Holding Super worked before upgrading. Tapping the Super key still brings up the HUD, and holding it down still brings up the Launcher and after a second or so shows the numbers on the applications. In Compiz Config Manager, under Ubuntu Unity Plugin - Launcher, the Key to show the Dash, Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin - General, Enable Shortcut Hints Overlay is checked. This is also known to affect 14.04 (without compiz) when workspaces are enabled and screen resolution is 1024x768. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 746383] Re: fontconfig confuses bold and medium weights
** Bug watch added: GNOME Bug Tracker #733764 https://bugzilla.gnome.org/show_bug.cgi?id=733764 ** Also affects: pango via https://bugzilla.gnome.org/show_bug.cgi?id=733764 Importance: Unknown Status: Unknown ** Also affects: pango (Ubuntu) Importance: Undecided Status: New ** Changed in: pango (Ubuntu) Status: New = Triaged ** Changed in: pango (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/746383 Title: fontconfig confuses bold and medium weights Status in Fontconfig - Font Configuration Library: Confirmed Status in Pango - Layout and Text Rendering LIbrary: Unknown Status in “fontconfig” package in Ubuntu: Triaged Status in “pango” package in Ubuntu: Triaged Bug description: Attempts to set Ubuntu Bold in the Appearance settings fall back to Ubuntu Medium. In fact, in the font selection screen there seems to be no difference between bold and medium. Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is* installed and accessible. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Thu Mar 31 08:33:44 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: DBus communication problems affecting multiple packages
Related Xfce4-dev mailing list entry: https://mail.xfce.org/pipermail/xfce4-dev/2014-May/030715.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: DBus communication problems affecting multiple packages Status in “dbus” package in Ubuntu: Confirmed Bug description: I seem to be hitting transient DBus communication problems after a fresh install of Xubuntu 14.04 amd64 on my Thinkpad W510 with the latest nvidia binaries from the Ubuntu repos. Here are the related bugs. Sometimes rebooting fixes things for a while. If I understand correctly, at least one of the bug reports (Bug #1314782) suggests a race condition is to blame: Bug #976638 (pkexec does not find any authentication agent) Bug #1193236 (Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*) Bug #1239014 (xfsettingsd unable to daemonize properly when overlay scrollbars are activated) Bug #1048805 (xfce4-appfinder launches very slowly) Bug #1314782 (multimedia keys don't work when xfce4-volumed is run in daemon mode) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dbus 1.6.18-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jul 22 16:26:36 2014 InstallationDate: Installed on 2014-06-25 (27 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329289] Re: Messaging indicator sometimes fails to send a reply
I've seen similar issues recently. I'm pretty sure that this is not an issue in the service, but in the UI layer in unity8. ** Also affects: unity8 Importance: Undecided Status: New -- 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/1329289 Title: Messaging indicator sometimes fails to send a reply Status in The Unity 8 shell: New Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: STEPS: 1. Open the messaging app 2. Send a message to your own phone 3. Close the messaging app 4. Hit the power button 5. Drag down the indicator 6. Reply to the message 7 Repeat steps 5-6 until the indicator nolonger send the meassage and instead saves it. See attached screenshot note the greyed send button WORKAROUND: Remove all messages from the indicator and use the messaging app once to reply, you will then be good till your indicator locks up again. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140611-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Thu Jun 12 12:01:29 2014 InstallationDate: Installed on 2014-06-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140612) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1329289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 771929] Re: Window Decoration disappears after clicking on the top left icon
Is the issue fixed? Coz now i am running Ubuntu 14.04? with Unity 3d? eh? -- 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/771929 Title: Window Decoration disappears after clicking on the top left icon Status in Compiz: Incomplete Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: 1) Launch any window from you desktop or launcher, 2) Then click on that particulars software top left icon/logo 3) Upon clicking, it makes the window decorator disappear for all open software/windows. \ Refer to the attached screen shots, serious issue for me, may be other to? To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/771929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290847] Re: pyvenv fails due to mising ensurepip module
Pierre, this seemed to work for me: $ sudo apt-get install python-virtualenv $ virtualenv /desired/path/to/env $ which pip /desired/path/to/env/bin/pip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module Status in “python3-defaults” package in Ubuntu: Fix Released Status in “python3.4” package in Ubuntu: Fix Released Status in “python3.4” package in Debian: Fix Released Bug description: Hello, I noticed the following # fails python3.4 -m venv --clear python-venv Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 # works, but no pip python3.4 -m venv --clear --without-pip python-venv Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 746383] Re: fontconfig confuses bold and medium weights
** Changed in: pango Status: Unknown = Confirmed ** Changed in: pango Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/746383 Title: fontconfig confuses bold and medium weights Status in Fontconfig - Font Configuration Library: Confirmed Status in Pango - Layout and Text Rendering LIbrary: Confirmed Status in “fontconfig” package in Ubuntu: Triaged Status in “pango” package in Ubuntu: Triaged Bug description: Attempts to set Ubuntu Bold in the Appearance settings fall back to Ubuntu Medium. In fact, in the font selection screen there seems to be no difference between bold and medium. Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is* installed and accessible. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Thu Mar 31 08:33:44 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329939] Re: Service ssh stop/start/restart hangs
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
--
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/1329939
Title:
Service ssh stop/start/restart hangs
Status in “openssh” package in Ubuntu:
Confirmed
Bug description:
When using service ssh, all of the actions cause the service process
to hang, with varying results on the sshd process.
root@localdev14:~# ps -ef | grep ssh
root 28264 1 0 15:39 ?00:00:00 /usr/sbin/sshd -D
root 28353 28264 0 15:46 ?00:00:00 sshd: user [priv]
user 28402 28353 0 15:46 ?00:00:00 sshd: user@pts/0
root 28433 28418 0 15:47 pts/000:00:00 grep --color=auto ssh
root@localdev14:~# service ssh stop
(after a couple of minutes)
^C
root@localdev14:~# ps -ef | grep ssh
root 28264 1 0 15:39 ?00:00:00 /usr/sbin/sshd -D
root 28353 28264 0 15:46 ?00:00:00 sshd: user [priv]
user 28402 28353 0 15:46 ?00:00:00 sshd: user@pts/0
root 28444 28418 0 15:48 pts/000:00:00 grep --color=auto ssh
A trace on /usr/sbin/service shows that it's hanging at /sbin/stop;
root@localdev14:~# bash -x /usr/sbin/service ssh stop 21 | tee
/tmp/ssh.restart
++ basename /usr/sbin/service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename /usr/sbin/service
+ USAGE='Usage: service option | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case ${1} in
+ '[' -z '' -a 2 -eq 1 -a ssh = --status-all ']'
+ '[' 2 -eq 2 -a stop = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=ssh
+ shift
+ '[' 1 -gt 0 ']'
+ case ${1} in
+ '[' -z ssh -a 1 -eq 1 -a stop = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z ssh ']'
+ '[' -z '' ']'
+ ACTION=stop
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/ssh.conf ']'
+ which initctl
+ initctl version
+ grep -q upstart
+ case ${ACTION} in
+ exec stop ssh
^C
root@localdev14:~# ps -ef | grep sshd
root 28264 1 0 15:39 ?00:00:00 /usr/sbin/sshd -D
root 28353 28264 0 15:46 ?00:00:00 sshd: user [priv]
user 28402 28353 0 15:46 ?00:00:00 sshd: user@pts/0
root 28478 28418 0 15:54 pts/000:00:00 grep --color=auto sshd
Restarting the service gets a different error;
root@localdev14:~# bash -x /usr/sbin/service ssh restart 21 | tee
/tmp/ssh.restart
++ basename /usr/sbin/service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename /usr/sbin/service
+ USAGE='Usage: service option | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case ${1} in
+ '[' -z '' -a 2 -eq 1 -a ssh = --status-all ']'
+ '[' 2 -eq 2 -a restart = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=ssh
+ shift
+ '[' 1 -gt 0 ']'
+ case ${1} in
+ '[' -z ssh -a 1 -eq 1 -a restart = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z ssh ']'
+ '[' -z '' ']'
+ ACTION=restart
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/ssh.conf ']'
+ which initctl
+ initctl version
+ grep -q upstart
+ case ${ACTION} in
+ stop ssh
stop: Job has already been stopped: ssh
+ :
+ exec start ssh
^C
root@localdev14:~# ps -ef | grep sshd
root 28264 1 0 15:39 ?00:00:00 /usr/sbin/sshd -D
root 28353 28264 0 15:46 ?00:00:00 sshd: user [priv]
user 28402 28353 0 15:46 ?00:00:00 sshd: user@pts/0
root 28495 28418 0 15:56 pts/000:00:00 grep --color=auto sshd
As you can see from the PID, the sshd service was in fact not stopped.
If you kill the sshd manually, and try to use the service command to
start the process, that hangs as well, although the process is
actually started;
root@localdev14:~# bash -x /usr/sbin/service ssh start 21 | tee
/tmp/ssh.start
++ basename /usr/sbin/service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename /usr/sbin/service
+ USAGE='Usage: service option | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case ${1} in
+ '[' -z '' -a 2 -eq 1 -a ssh = --status-all ']'
+ '[' 2 -eq 2 -a start = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=ssh
+ shift
+ '[' 1 -gt 0 ']'
+ case ${1} in
+ '[' -z ssh -a 1 -eq 1 -a start = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z ssh ']'
+ '[' -z '' ']'
+ ACTION=start
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/ssh.conf ']'
+
[Touch-packages] [Bug 1348734] [NEW] SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) no sound at all
You have been subscribed to a public bug: ALSA info page http://www.alsa- project.org/db/?f=35e0e257c3193758fe2129db6d39552c1af3d687 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vladimir 1512 F pulseaudio /dev/snd/controlC1: vladimir 1512 F pulseaudio /dev/snd/pcmC1D0p: vladimir 1512 F...m pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 21:22:39 2014 HibernationDevice: RESUME=UUID=bf69b978-a32b-4de3-a839-4c1ef87ae5fd InstallationDate: Installed on 2014-07-24 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Acer Aspire One 522 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e2267848-1bb4-486d-81e0-ec8507180a34 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.09 dmi.board.name: Aspire One 522 dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrV1.09:bd03/21/2011:svnAcer:pnAspireOne522:pvrV1.09:rvnAcer:rnAspireOne522:rvrV1.09:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire One 522 dmi.product.version: V1.09 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 trusty -- SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) no sound at all https://bugs.launchpad.net/bugs/1348734 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348912] [NEW] [USB-Audio - FiiO USB DAC-E17, playback] crackling and distorted sound
Public bug reported: USB sound card worked fine until I installed software package updates. Not sure which one. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: matthew2924 F pulseaudio /dev/snd/controlC1: matthew2924 F pulseaudio /dev/snd/controlC0: matthew2924 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 26 07:14:23 2014 InstallationDate: Installed on 2014-05-01 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DACE17 failed Symptom_Card: FiiO USB DAC-E17 - FiiO USB DAC-E17 Symptom_Type: Underruns, dropouts, or crackling sound Title: [USB-Audio - FiiO USB DAC-E17, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11a:bd11/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1348912 Title: [USB-Audio - FiiO USB DAC-E17, playback] crackling and distorted sound Status in “alsa-driver” package in Ubuntu: New Bug description: USB sound card worked fine until I installed software package updates. Not sure which one. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: matthew2924 F pulseaudio /dev/snd/controlC1: matthew2924 F pulseaudio /dev/snd/controlC0: matthew2924 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 26 07:14:23 2014 InstallationDate: Installed on 2014-05-01 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DACE17 failed Symptom_Card: FiiO USB DAC-E17 - FiiO USB DAC-E17 Symptom_Type: Underruns, dropouts, or crackling sound Title: [USB-Audio - FiiO USB DAC-E17, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11a:bd11/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1348912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348734] Re: SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) no sound at all
** Package changed: linux (Ubuntu) = alsa-driver (Ubuntu) -- 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/1348734 Title: SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) no sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: ALSA info page http://www.alsa- project.org/db/?f=35e0e257c3193758fe2129db6d39552c1af3d687 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vladimir 1512 F pulseaudio /dev/snd/controlC1: vladimir 1512 F pulseaudio /dev/snd/pcmC1D0p: vladimir 1512 F...m pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 21:22:39 2014 HibernationDevice: RESUME=UUID=bf69b978-a32b-4de3-a839-4c1ef87ae5fd InstallationDate: Installed on 2014-07-24 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Acer Aspire One 522 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e2267848-1bb4-486d-81e0-ec8507180a34 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.09 dmi.board.name: Aspire One 522 dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrV1.09:bd03/21/2011:svnAcer:pnAspireOne522:pvrV1.09:rvnAcer:rnAspireOne522:rvrV1.09:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire One 522 dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1348734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329939] Re: Service ssh stop/start/restart hangs
Hi,
I have quite the same problem.
Only after a reboot the sshd is running, working and accepting connections.
Whatever I try:
stop ssh,
restart ssh,
start ssh
or with service like:
service ssh stop/start/restart
or with /etc/init.d/ssh, which isn't doing anything.
the daemon ist (maybe) started, but NOT accepting connections.
the command: start ssh
does NOT return. and ssh ist not started/running.
I have to press ^C, then the the service is started! wtf?!?!
and shows up with:/usr/sbin/sshd -D
but in this state it is not accepting connections.
I tries all combinations and methods.
nothing is working.
funny thing:
when i start it with: start ssh
the command returns, nothing is really started (ps -ef shows nothing)
BUT when i say: service ssh status
this happens:
ssh start/running, process 11633
ssh start/running, process 11633
[1]+ Donestart ssh
now sshd ist started AND accepting connections!
this really is a bug!
its the only way to start/restart the daemon without reboot :(
best regards
axel
--
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/1329939
Title:
Service ssh stop/start/restart hangs
Status in “openssh” package in Ubuntu:
Confirmed
Bug description:
When using service ssh, all of the actions cause the service process
to hang, with varying results on the sshd process.
root@localdev14:~# ps -ef | grep ssh
root 28264 1 0 15:39 ?00:00:00 /usr/sbin/sshd -D
root 28353 28264 0 15:46 ?00:00:00 sshd: user [priv]
user 28402 28353 0 15:46 ?00:00:00 sshd: user@pts/0
root 28433 28418 0 15:47 pts/000:00:00 grep --color=auto ssh
root@localdev14:~# service ssh stop
(after a couple of minutes)
^C
root@localdev14:~# ps -ef | grep ssh
root 28264 1 0 15:39 ?00:00:00 /usr/sbin/sshd -D
root 28353 28264 0 15:46 ?00:00:00 sshd: user [priv]
user 28402 28353 0 15:46 ?00:00:00 sshd: user@pts/0
root 28444 28418 0 15:48 pts/000:00:00 grep --color=auto ssh
A trace on /usr/sbin/service shows that it's hanging at /sbin/stop;
root@localdev14:~# bash -x /usr/sbin/service ssh stop 21 | tee
/tmp/ssh.restart
++ basename /usr/sbin/service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename /usr/sbin/service
+ USAGE='Usage: service option | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case ${1} in
+ '[' -z '' -a 2 -eq 1 -a ssh = --status-all ']'
+ '[' 2 -eq 2 -a stop = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=ssh
+ shift
+ '[' 1 -gt 0 ']'
+ case ${1} in
+ '[' -z ssh -a 1 -eq 1 -a stop = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z ssh ']'
+ '[' -z '' ']'
+ ACTION=stop
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/ssh.conf ']'
+ which initctl
+ initctl version
+ grep -q upstart
+ case ${ACTION} in
+ exec stop ssh
^C
root@localdev14:~# ps -ef | grep sshd
root 28264 1 0 15:39 ?00:00:00 /usr/sbin/sshd -D
root 28353 28264 0 15:46 ?00:00:00 sshd: user [priv]
user 28402 28353 0 15:46 ?00:00:00 sshd: user@pts/0
root 28478 28418 0 15:54 pts/000:00:00 grep --color=auto sshd
Restarting the service gets a different error;
root@localdev14:~# bash -x /usr/sbin/service ssh restart 21 | tee
/tmp/ssh.restart
++ basename /usr/sbin/service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename /usr/sbin/service
+ USAGE='Usage: service option | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case ${1} in
+ '[' -z '' -a 2 -eq 1 -a ssh = --status-all ']'
+ '[' 2 -eq 2 -a restart = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=ssh
+ shift
+ '[' 1 -gt 0 ']'
+ case ${1} in
+ '[' -z ssh -a 1 -eq 1 -a restart = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z ssh ']'
+ '[' -z '' ']'
+ ACTION=restart
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/ssh.conf ']'
+ which initctl
+ initctl version
+ grep -q upstart
+ case ${ACTION} in
+ stop ssh
stop: Job has already been stopped: ssh
+ :
+ exec start ssh
^C
root@localdev14:~# ps -ef | grep sshd
root 28264 1 0 15:39 ?00:00:00 /usr/sbin/sshd -D
root 28353 28264 0 15:46 ?00:00:00 sshd: user [priv]
user 28402 28353 0 15:46 ?00:00:00 sshd: user@pts/0
root 28495 28418 0 15:56 pts/000:00:00 grep --color=auto sshd
As you can see from the PID, the sshd service was in fact not stopped.
If you kill the sshd manually, and try to
[Touch-packages] [Bug 1348757] Re: invoke-rc.d gets stuck when trying to start gnukhata-core-engine during post install
Can someone else look at the package and suggest if we should change the wiring to something else? Consider this as a request for help. ** Bug watch added: Debian Bug tracker #756114 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756114 ** Also affects: sysvinit (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756114 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1348757 Title: invoke-rc.d gets stuck when trying to start gnukhata-core-engine during post install Status in “sysvinit” package in Ubuntu: Invalid Status in “sysvinit” package in Debian: Unknown Bug description: I'm packaging gnukhata (http://gnukhata.org) for debian and ubuntu but I cannot start the gnukhata-core-engine service during installation on ubuntu. It works fine on debian sid (using systemd). I tried both invoke-rc.d gnukhata-core-engine start as well as service gnukhata- core-engine start. It just go defunct after it actually starts the service. I have tested on Ubuntu 12.04 and 14.04 releases. You can test it using the packages from http://people.debian.org/~praveen/gnukhata/README (currently postinst doesn not start the service, you can edit debian/gnukhata-core- engine.postinst to start the service and test) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1348757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 682338]
I'm having trouble applying this patch to libcairo2 version 1.13.0 from
Ubuntu 14.04
Doing some tracing, it looks like display-buggy_repeat is accessed by
the function:
cairo_bool_t
_cairo_xlib_display_has_repeat (cairo_device_t *device)
{
return ! ((cairo_xlib_display_t *) device)-buggy_repeat;
}
However, I don't see that function called anywhere else in the code.
I'm still observing slowness for GTK programs using NX (both nx2go and
NoMachine).
Could anyone comment on the proper patch for libcairo2 version 1.13.0?
I'm also having trouble locating the callers of
_recategorize_composite_operation. Perhaps I have an incomplete source tree?
$ find -type f | xargs grep recategorize_composite
./cairo-xlib-render-compositor.c:operation =
_recategorize_composite_operation (dst, op, src, src_attr,
./cairo-xlib-render-compositor.c:operation =
_recategorize_composite_operation (dst, op, src,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/682338
Title:
GTK programs in Ubuntu 10.10 are sluggish over NX
Status in libcairo - cairo vector graphics library:
Confirmed
Status in “cairo” package in Ubuntu:
Triaged
Status in “cairo” source package in Precise:
Triaged
Bug description:
I use NX to connect to a work computer from home, over the Internet.
I recently upgraded to Ubuntu 10.10, and I noticed that GTK programs
became very sluggish.
I currently have 1.10.0-1ubuntu3 of libcairo2 installed. If I
override this with the Ubuntu 10.04 version of libcairo2,
1.8.10-2ubuntu1, performance is restored. I used LD_LIBRARY_PATH to
run GTK programs with the old libcairo2 package.
I'll attach a video demonstrating how much faster gedit is using the
old libcairo2 package.
Both my home and work computer run Ubuntu 10.10.
The work computer has these NX packages installed:
nxclient-3.4.0-7
nxnode-3.4.0-14
nxserver-3.4.0-14
The home computer only has the nxclient-3.4.0-7 package installed.
The ping times from my home computer to work computer are about 35ms.
I suspect this issue is related to, or a duplicate of, bug #595845.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libcairo2 1.10.0-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Nov 28 03:23:50 2010
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: cairo
To manage notifications about this bug go to:
https://bugs.launchpad.net/libcairo/+bug/682338/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
do the control allow you to turn ON more than one input capture switch at same time ? as I understand it don't allow it It is really hard to understand everything in your comments for me, because I am not so well versed in this. I am just affected with this bug and want it to be fixed. I can give any information and do any tests that you ask if you give me instructions for it. At the moment I don't understand correctly what are you asking me to do -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Microphone is not working on frontpanel of my soundcard Asus Xonar Essence STX. In windows it works normally. Ubuntu 13.04 x64 Tested on the latest kernel 3.9-rc8 With 3.8.0 kernel problem is the same. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.0-030900rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simplehuman 2394 F pulseaudio /dev/snd/pcmC0D0c: simplehuman 2394 F...m pulseaudio /dev/snd/controlC1: simplehuman 2394 F pulseaudio Date: Mon Apr 22 15:06:32 2013 InstallationDate: Installed on 2013-02-14 (67 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:STX failed Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia Symptom_Type: None of the above Title: [AV200 - Xonar STX, recording] Recording problem UpgradeStatus: Upgraded to raring on 2013-02-14 (67 days ago) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1284635] Re: IBus does not support certain keyboard layouts
2 fresh installs of lubuntu Trusty daily and lubuntu Utopic daily on a desktop and a laptop respectively with azerty keyboards. Both installs done twice with the following conditions : - English language selected in the installer qwerty keyboards during the install and after rebooting at the end of the install. Only installing the French language packs allow to choose azerty keyboards. iBus not removed or not exited. - French language selected in the installer azerty keyboards during the install procedure and after rebooting at the end of the install. The installer should ask for both the environment language AND the keyboard layout when English is selected. Some users are experimenting difficulties entering the wifi passphrase during the install procedure due to improper keyboard layout (using ethernet here for installs). Many users use English interfaces with keyboards that are not of a US layout. -- 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/1284635 Title: IBus does not support certain keyboard layouts Status in “ibus” package in Ubuntu: Triaged Status in “ibus” source package in Trusty: Triaged Bug description: installed trusty beta1 with keyboard layout set correctly during install install completes, login to new install - layout as set during install once logged in - layout set to US and keyboard layout set during install is missing from list ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: keyboard-configuration 1.70ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Feb 25 12:55:56 2014 InstallationDate: Installed on 2014-02-25 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1284635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323777] Re: /dev/dvd and /dev/dvdrw symlinks no longer created
The missing symlink is unrelated to the eject error. Installing udisks should correct the “no devices to eject - media monitor” error. Note: https://code.mythtv.org/trac/ticket/11699 ** Bug watch added: code.mythtv.org/trac/ #11699 http://code.mythtv.org/trac/ticket/11699 -- 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/1323777 Title: /dev/dvd and /dev/dvdrw symlinks no longer created Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in “systemd” package in Ubuntu: New Bug description: With a fresh Mythbuntu 14.04 installation AMD 64 bit combined frontend/backend , there are two issues with the internal DVD player. 1. It fails with the message: “failed to open device /dev/dvd”. In 12.04 there was a link /dev/dvd - /dev/sr0 which was created at each reboot. This link is missing in 14.04. Creating it with ‘sudo ln’ allows frontend to play DVDs but the link is removed at next reboot. A more lasting workaround is: Frontend setup Media settings Videos settings Player settings DVD Drive changed from /dev/dvd to /dev/sr0 2. Ejecting media fails with error message: “no devices to eject - media monitor” It does this with either the /dev/dvd link in place or with the settings changed as abov To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1323777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348940] [NEW] square in the left upper corner of the dash
Public bug reported: every time i want to start a programm from the dash i see this square in the left upper corner, i think its a graphic glitch ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.15.0-031500-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Sat Jul 26 17:01:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.14, 3.13.0-32-generic, x86_64: installed vboxhost, 4.3.14, 3.15.0-031500-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2014-05-31 (56 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-031500-generic root=UUID=11613522-e8b1-44ff-bf65-2c5ea7d100bd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54+git1407160630.c0b34d~gd~t version.libgl1-mesa-dri: libgl1-mesa-dri 10.3~git1407250730.cce581~gd~t version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3~git1407250730.cce581~gd~t version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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.4.99+git1407010730.c4ae0e~gd~t version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914+git1407241931.cac154~gd~t version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1407030730.edd160~gd~t xserver.bootTime: Sat Jul 26 16:32:14 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: intel: Failed to load module dri3 (module does not exist, 0) intel: Failed to load module present (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption third-party-packages trusty ubuntu ** Attachment added: graphic glitch https://bugs.launchpad.net/bugs/1348940/+attachment/4163320/+files/Bildschirmfoto%20vom%202014-07-26%2016%3A53%3A17.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1348940 Title: square in the left upper corner of the dash Status in “xorg” package in Ubuntu: New Bug description: every time i want to start a programm from the dash i see this square in the left upper corner, i think its a graphic glitch ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.15.0-031500-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Sat Jul 26 17:01:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.14, 3.13.0-32-generic, x86_64: installed vboxhost, 4.3.14, 3.15.0-031500-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2014-05-31 (56 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-031500-generic root=UUID=11613522-e8b1-44ff-bf65-2c5ea7d100bd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log
[Touch-packages] [Bug 1347272] Re: Applications appear to do nothing after communicating with the DBus fork() function
** Summary changed: - DBus communication problems affecting multiple packages + Applications appear to do nothing after communicating with the DBus fork() function ** Summary changed: - Applications appear to do nothing after communicating with the DBus fork() function + Applications appear to do nothing after communicating with DBus ** Summary changed: - Applications appear to do nothing after communicating with DBus + Several applications appear irresponsible after communicating with DBus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several applications appear irresponsible after communicating with DBus Status in “dbus” package in Ubuntu: Confirmed Bug description: ROOT CAUSE Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. ** RELATED BUGS ** Bug #973778: Unable to connect to Xfce Power Manager Bug #976638: pkexec does not find any authentication agent Bug #1048805: xfce4-appfinder launches very slowly) Bug #1193236: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Bug #1239014: xfsettingsd unable to daemonize properly when overlay scrollbars are activated Bug #1314782: multimedia keys don't work when xfce4-volumed is run in daemon mode (suggests a race condition is to blame) *** TECHNICAL DETAILS *** ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dbus 1.6.18-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jul 22 16:26:36 2014 InstallationDate: Installed on 2014-06-25 (27 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278569] Re: ibus breaks emacs and eclipse control-space keybinding
I think this is caused by setting Ctrl-Space as the default shortcut in ibus-setup's default configuration, that's a diff between Ubuntu and Debian because there was problem in switching the input method in Unity (where Super-Space is captured by gnome/unity-settings-daemon). I'll see if we can drop that with recent gnome/unity-settings-daemon updates. -- 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/1278569 Title: ibus breaks emacs and eclipse control-space keybinding Status in “ibus” package in Ubuntu: Confirmed Bug description: Installing ibus 1.5.5-1ubuntu1 breaks Emacs 24's control-space keybinding. I generally have that bound to a custom lisp function, but by default (e.g. starting with `emacs -Q`) it is bound to set- mark-command. After doing a dist-upgrade in Trusty which installs ibus 1.5.5-1ubuntu1, emacs no longer even sees the control-space key chord. My guess is that ibus is consuming this event, preventing emacs from seeing it. This is a critical regression that makes emacs almost unusable. By process of elimination, I've narrowed it down to one of these 4 binary packages. gir1.2-ibus-1.0 ibus ibus-gtk ibus-gtk3 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-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: Mon Feb 10 15:15:57 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-06 (66 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) 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/1278569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311403] Re: Can't type password after resume.
I've noticed that when this happens, if a text box was selected before closing my laptop's lid, when I open up again and try to enter in my password, it's entered into the text box, instead of into the password field. Needless to say, that's an incredibly disturbing behavior, especially when the text box behind the lock screen is an instant messaging service! This bug has, for whatever reason, just started to affect my system (an up-to-date Ubuntu 14.04 system) over the past day. -- 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/1311403 Title: Can't type password after resume. Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I couldn't type password after resume - no characters displayed this time. I had to Ctrl+alt+f2 and service lightdm restart. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Tue Apr 22 17:37:49 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (150 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242112] Re: Shutdown/restart dialogue is not working if Cairo-Dock and its Launcher-API-Deamon are running or if another app is registered to LauncherEntry interface of Unity DB
Added DockbarX and Plank projects to this bug report with 'Invalid' status: It seems this bug affects DockbarX and Plank users. ** Branch unlinked: lp:ubuntu/cairo-dock ** Description changed: - Using latest stable release (3.3.1). Just upgraded to Saucy Salamander - in Ubuntu. When cairo dock is set to automatically run at boot up the - options to shutdown/restart do not work from the top menu panel next to - the clock. When run manually after boot the shutdown/restart works fine. - The shutdown/restart options do work fine from cairo dock/terminal but - just mess up the shutdown/restart from the top menu panel + Unity's shutdown/restart dialogue is not working when another application is registered to LauncherEntry interface of Unity DBus. + It seems we have this bug when Cairo-Dock (and its Launcher-API-Deamon), DockbarX or Plank are launched before Unity. + + [How to reproduce this bug] + Simply launch this script at startup (launched before Unity). It will watch 'com.canonical.Unity.LauncherEntry' bus interface: https://bazaar.launchpad.net/~cairo-dock-team/cairo-dock-plug-ins/plug-ins/view/head:/Dbus/data/cairo-dock-launcher-API-daemon.py + + [Original description] + Using latest stable release (3.3.1). Just upgraded to Saucy Salamander in Ubuntu. When cairo dock is set to automatically run at boot up the options to shutdown/restart do not work from the top menu panel next to the clock. When run manually after boot the shutdown/restart works fine. The shutdown/restart options do work fine from cairo dock/terminal but just mess up the shutdown/restart from the top menu panel ** Also affects: dockbar Importance: Undecided Status: New ** Changed in: dockbar Status: New = Invalid ** Also affects: plank Importance: Undecided Status: New ** Changed in: plank Status: New = Invalid -- 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/1242112 Title: Shutdown/restart dialogue is not working if Cairo-Dock and its Launcher-API-Deamon are running or if another app is registered to LauncherEntry interface of Unity DBus Status in Cairo-Dock : Core: Invalid Status in DockbarX: Invalid Status in Plank: Invalid Status in Unity: Confirmed Status in “cairo-dock” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Status in “cairo-dock” source package in Trusty: Invalid Status in “unity” source package in Trusty: Confirmed Status in “cairo-dock” source package in Utopic: Invalid Status in “unity” source package in Utopic: Confirmed Bug description: Unity's shutdown/restart dialogue is not working when another application is registered to LauncherEntry interface of Unity DBus. It seems we have this bug when Cairo-Dock (and its Launcher-API-Deamon), DockbarX or Plank are launched before Unity. [How to reproduce this bug] Simply launch this script at startup (launched before Unity). It will watch 'com.canonical.Unity.LauncherEntry' bus interface: https://bazaar.launchpad.net/~cairo-dock-team/cairo-dock-plug-ins/plug-ins/view/head:/Dbus/data/cairo-dock-launcher-API-daemon.py [Original description] Using latest stable release (3.3.1). Just upgraded to Saucy Salamander in Ubuntu. When cairo dock is set to automatically run at boot up the options to shutdown/restart do not work from the top menu panel next to the clock. When run manually after boot the shutdown/restart works fine. The shutdown/restart options do work fine from cairo dock/terminal but just mess up the shutdown/restart from the top menu panel To manage notifications about this bug go to: https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
*** This bug is a duplicate of bug 1347272 *** https://bugs.launchpad.net/bugs/1347272 ** This bug has been marked a duplicate of bug 1347272 XFCE applications appear irresponsible after communicating with a daemon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in pixbuf library for gtk+: Fix Released Status in “gdk-pixbuf” package in Ubuntu: Fix Released Bug description: Since a few days, xsession-errors is fullfilled by that kind of errors: ** (nautilus:22621): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused Similar errors are reported all over the net, but Debian have tried to fix it already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517 But some other devs seems to blame an atk-bridge: https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA And some others suggest a dbus/gdbus race; the good thing is that seems not disturbing that much the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Fri Jun 21 08:35:40 2013 MarkForUpload: True SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1193236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 976638] Re: pkexec does not find any authentication agent
*** This bug is a duplicate of bug 1347272 *** https://bugs.launchpad.net/bugs/1347272 ** This bug has been marked a duplicate of bug 1347272 XFCE applications appear irresponsible after communicating with a daemon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in System policy: Confirmed Status in “policykit-1” package in Ubuntu: Triaged Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
** Bug watch added: GNOME Bug Tracker #733792 https://bugzilla.gnome.org/show_bug.cgi?id=733792 ** Also affects: gdk-pixbuf via https://bugzilla.gnome.org/show_bug.cgi?id=733792 Importance: Unknown Status: Unknown ** Bug watch added: freedesktop.org Bugzilla #81784 https://bugs.freedesktop.org/show_bug.cgi?id=81784 ** Also affects: policykit-1 via https://bugs.freedesktop.org/show_bug.cgi?id=81784 Importance: Unknown Status: Unknown ** Changed in: policykit-1 (Ubuntu) Status: Confirmed = Triaged ** Changed in: gdk-pixbuf (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: Unknown Status in System policy: Unknown Status in Thunar file manager: Unknown Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Confirmed Status in “xfce4-appfinder” package in Ubuntu: Confirmed Status in “xfce4-power-manager” package in Ubuntu: Confirmed Status in “xfce4-settings” package in Ubuntu: Confirmed Status in “xfce4-volumed” package in Ubuntu: Confirmed Status in “xfce4-volumed-pulse” package in Ubuntu: Confirmed Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348947] [NEW] useradd/groupadd existence check races
Public bug reported: useradd has a race between checking if a username is already in use and updating the pw database: getpwnam check http://anonscm.debian.org/cgit/pkg-shadow/shadow.git/tree/src/useradd.c#n2085 open_files lock on line 2127 of same groupadd has a race between checking if a groupname is already in use and updating the gr database: getgrnam check http://anonscm.debian.org/cgit/pkg-shadow/shadow.git/tree/src/groupadd.c#n483 open_files lock on line 609 of same This race is exhibited when multiple processes attempt to use the error return code of useradd/groupadd to indicate whether they have successfully created a unique user for themselves. If the race occurs, the uid/gid of the database entry may change out from under the first successful process as the second process finds an unused uid/gid and then updates the database using the same key (but the new uid/gid). I believe this bug exists since at least shadow 4.1.4.2 in both Ubuntu and Debian distributions. I don't believe this bug is a security vulnerability except in contexts where attackers may have control over user/group creation by applications assuming that the database locks ensure non-collision. Obligatory: 1)# lsb_release -rd Description:Ubuntu 10.04 LTS Release:10.04 2)# apt-cache policy passwd passwd: Installed: 1:4.1.4.2-1ubuntu2.2 Candidate: 1:4.1.4.2-1ubuntu2.2 Version table: *** 1:4.1.4.2-1ubuntu2.2 0 500 http://www-uxsup.csx.cam.ac.uk/pub/linux/ubuntu/ lucid-updates/main Packages 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 1:4.1.4.2-1ubuntu2 0 500 http://www-uxsup.csx.cam.ac.uk/pub/linux/ubuntu/ lucid/main Packages 3) groupadd/useradd should either consistently let the operator overwrite existing groups/users or should consistently produce a name collision error 4) groupadd/useradd sometimes exit due to name collisions and sometimes overwrite existing groups/users ** Affects: shadow Importance: Undecided Status: New ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Affects: shadow (Debian) Importance: Undecided Status: New ** Also affects: shadow Importance: Undecided Status: New ** Also affects: shadow (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1348947 Title: useradd/groupadd existence check races Status in The Shadow Password File Utilities: New Status in “shadow” package in Ubuntu: New Status in “shadow” package in Debian: New Bug description: useradd has a race between checking if a username is already in use and updating the pw database: getpwnam check http://anonscm.debian.org/cgit/pkg-shadow/shadow.git/tree/src/useradd.c#n2085 open_files lock on line 2127 of same groupadd has a race between checking if a groupname is already in use and updating the gr database: getgrnam check http://anonscm.debian.org/cgit/pkg-shadow/shadow.git/tree/src/groupadd.c#n483 open_files lock on line 609 of same This race is exhibited when multiple processes attempt to use the error return code of useradd/groupadd to indicate whether they have successfully created a unique user for themselves. If the race occurs, the uid/gid of the database entry may change out from under the first successful process as the second process finds an unused uid/gid and then updates the database using the same key (but the new uid/gid). I believe this bug exists since at least shadow 4.1.4.2 in both Ubuntu and Debian distributions. I don't believe this bug is a security vulnerability except in contexts where attackers may have control over user/group creation by applications assuming that the database locks ensure non-collision. Obligatory: 1)# lsb_release -rd Description: Ubuntu 10.04 LTS Release: 10.04 2)# apt-cache policy passwd passwd: Installed: 1:4.1.4.2-1ubuntu2.2 Candidate: 1:4.1.4.2-1ubuntu2.2 Version table: *** 1:4.1.4.2-1ubuntu2.2 0 500 http://www-uxsup.csx.cam.ac.uk/pub/linux/ubuntu/ lucid-updates/main Packages 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 1:4.1.4.2-1ubuntu2 0 500 http://www-uxsup.csx.cam.ac.uk/pub/linux/ubuntu/ lucid/main Packages 3) groupadd/useradd should either consistently let the operator overwrite existing groups/users or should consistently produce a name collision error 4) groupadd/useradd sometimes exit due to name collisions and sometimes overwrite existing groups/users To manage notifications about this bug go to: https://bugs.launchpad.net/shadow/+bug/1348947/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1346766] Re: Chinese in Ubuntu Touch should use Heiti style sans serif font
I support Noto Sans CJK or Source Han Sans (they share the same content of CJK part, while Adobe holds the copyright, licensed under Apache v2) regular style for default CJK displaying. That is absolutely better than Droid Sans Fallback because it takes care of various region-specif shapes well and fits CJK characters displaying better. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-meta” package in Ubuntu: Confirmed Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. fonts-droid (DroidSansFallbackFull.ttf, original): - Pros: - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. -Cons: - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. As an additional alternative, just a few days ago, Google released the Noto Sans CJK fonts [2][3]: fonts-noto (Noto Sans CJK fonts): - Pros: - It takes care of different writing standard of Traditional and Simplified Chinese - It covers Japanese and Korean as well - Cons: - Needs to be tested - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese - Not yet packaged [4] [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A [2] http://googledevelopers.blogspot.de/2014/07/noto-cjk-font-that-is-complete.html [3] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1346766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315733] Re: Python interactive interpreter does not indent with tabs, tries to tab-complete
this is done by intent. see http://bugs.python.org/issue5845 to remove this behaviour, use this in sitecustomize or usercustomize: try: del sys.__interactivehook__ except AttributeError: pass ** Bug watch added: Debian Bug tracker #750458 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750458 ** Also affects: python3.4 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750458 Importance: Unknown Status: Unknown ** Bug watch added: Python Roundup #5845 http://bugs.python.org/issue5845 ** Changed in: python3.4 (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1315733 Title: Python interactive interpreter does not indent with tabs, tries to tab-complete Status in “python3.4” package in Ubuntu: Won't Fix Status in “python3.4” package in Debian: Unknown Bug description: Using the python3 interactive interpreter, I can not use tabs to indent like I could on previous versions of Ubuntu (13.10 was what I was using before, now I'm using 14.04). When I try to indent on the python interpreter command line, it simply does nothing the first time I press the tab key. The second time I press it, it shows a bunch of autocomplete suggestions. For example if (True): ... tabprint(true!) File stdin, line 2 print(true!) ^ IndentationError: expected an indented block Could this be related to http://bugs.python.org/issue18988? Is the fix for that included in the version of python on 14.04? I also found http://stackoverflow.com/questions/4809820/tab-key-not- indenting-in-python, in which one of the comments to an answer suggests trying Ctrl-Vtab when you want to insert a tab. That does work for me: if (True): ... Ctrl-Vtabprint(true) ... true ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 3 11:36:57 2014 SourcePackage: python3-defaults UpgradeStatus: Upgraded to trusty on 2014-04-19 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1315733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
** Bug watch added: Xfce Bugzilla #11042 https://bugzilla.xfce.org/show_bug.cgi?id=11042 ** Also affects: thunar via https://bugzilla.xfce.org/show_bug.cgi?id=11042 Importance: Unknown Status: Unknown ** Bug watch added: Xfce Bugzilla #11043 https://bugzilla.xfce.org/show_bug.cgi?id=11043 ** Also affects: xfce4-appfinder via https://bugzilla.xfce.org/show_bug.cgi?id=11043 Importance: Unknown Status: Unknown ** Bug watch added: Xfce Bugzilla #11044 https://bugzilla.xfce.org/show_bug.cgi?id=11044 ** Also affects: xfce4-power-manager via https://bugzilla.xfce.org/show_bug.cgi?id=11044 Importance: Unknown Status: Unknown ** Changed in: thunar (Ubuntu) Status: Confirmed = Triaged ** Changed in: xfce4-appfinder (Ubuntu) Status: Confirmed = Triaged ** Changed in: xfce4-power-manager (Ubuntu) Status: Confirmed = Triaged ** Bug watch added: Xfce Bugzilla #11045 https://bugzilla.xfce.org/show_bug.cgi?id=11045 ** Also affects: xfce4-settings via https://bugzilla.xfce.org/show_bug.cgi?id=11045 Importance: Unknown Status: Unknown ** Changed in: xfce4-settings (Ubuntu) Status: Confirmed = Triaged ** Also affects: xfce4-volumed Importance: Undecided Status: New ** Changed in: xfce4-volumed (Ubuntu) Status: Confirmed = Triaged ** Changed in: xfce4-volumed Status: New = Confirmed ** Also affects: xfce4-volumed-pulse Importance: Undecided Status: New ** Changed in: xfce4-volumed-pulse Status: New = Confirmed ** No longer affects: xfce4-volumed-pulse (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: Unknown Status in System policy: Unknown Status in Thunar file manager: Unknown Status in xfce4-appfinder: Unknown Status in Xfce4 Power Manager: Unknown Status in xfce4-settings: Unknown Status in Volume management daemon for XFCE 4: Confirmed Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1264618] Re: Wrong OSError message from os.rename() when dst is a non-empty directory
3.4.0 has this fixed. resolutions in http://bugs.python.org/issue16074
and http://bugs.python.org/issue20517
** Bug watch added: Python Roundup #20517
http://bugs.python.org/issue20517
** Changed in: python3.4 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1264618
Title:
Wrong OSError message from os.rename() when dst is a non-empty
directory
Status in “python3.4” package in Ubuntu:
Fix Released
Bug description:
Under Python 3.3, if renaming a directory with `os.rename()` when the
destination is an existing, non-empty directory, like this:
os.rename('/tmp/foo', '/tmp/bar')
You'll get an OSError with a message like this:
OSError: [Errno 39] Directory not empty: '/tmp/bar'
However, in the current Python 3.4.0b1 package in Trusty, this error
message will contain the source directory name instead of the
destination directory name, like this:
OSError: [Errno 39] Directory not empty: '/tmp/foo'
I've attached a test case, which also covers renaming directories
relative to an open directory descriptor. This test case works on
Python 3.3, fails on Python 3.4.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python3.4 3.4~b1-0ubuntu3
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Dec 27 19:57:28 2013
SourcePackage: python3.4
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1264618/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312061] Re: IDLE hangs from time to time
no feedback, closing the issue ** Changed in: python3.4 (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1312061 Title: IDLE hangs from time to time Status in “python3.4” package in Ubuntu: Invalid Bug description: It hangs from time to time. I see no consistency. it is pretty often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: idle-python3.4 3.4.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 24 12:05:05 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2010-10-12 (1289 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) PackageArchitecture: all SourcePackage: python3.4 UpgradeStatus: Upgraded to trusty on 2013-10-26 (179 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1312061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348954] [NEW] update Python3 for trusty
Public bug reported: update Python3 for trusty ** Affects: python3.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1348954 Title: update Python3 for trusty Status in “python3.4” package in Ubuntu: New Bug description: update Python3 for trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1348954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Importance: Undecided = High ** Changed in: hundredpapercuts Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: Unknown Status in One Hundred Papercuts: Triaged Status in System policy: Unknown Status in Thunar file manager: Unknown Status in xfce4-appfinder: Unknown Status in Xfce4 Power Manager: Unknown Status in xfce4-settings: Unknown Status in Volume management daemon for XFCE 4: Confirmed Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348955] [NEW] update Python for trusty
Public bug reported: update Python for trusty ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1348955 Title: update Python for trusty Status in “python2.7” package in Ubuntu: New Bug description: update Python for trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1348955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
Thanks for the triaging effort! As far as I know xfce4-volumed-pulse has a fix committed already though I'll let mrpouit confirm. The ALSA xfce4-volumed never had the issue. ** Changed in: xfce4-volumed Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: Unknown Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Unknown Status in xfce4-appfinder: Unknown Status in Xfce4 Power Manager: Unknown Status in xfce4-settings: Unknown Status in Volume management daemon for XFCE 4: Invalid Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
Launchpad has imported 1 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=81784. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-07-26T15:53:03+00:00 Alberto Salvia Novella wrote: Several programs have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. Please check this bug is not affecting PolicyKit. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1347272/comments/6 ** Changed in: policykit-1 Status: Unknown = Confirmed ** Changed in: policykit-1 Importance: Unknown = High ** Changed in: gdk-pixbuf Status: Unknown = New ** Changed in: gdk-pixbuf Importance: Unknown = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Unknown Status in xfce4-appfinder: Unknown Status in Xfce4 Power Manager: Unknown Status in xfce4-settings: Unknown Status in Volume management daemon for XFCE 4: Invalid Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315733] Re: Python interactive interpreter does not indent with tabs, tries to tab-complete
Matthias, no, that was not apparently the intent, see the last two messages of that bug report: http://bugs.python.org/issue5845#msg215784 The bug report was tracking multiple issues, and someone forgot about this one (and later said that they did, and said should have gone back to being a release blocker after the alpha release to fix the tab-as-indent issue). The intent of that bug report was to enable tab to complete, but also still allow tab in the interpreter as indentation (so a tab at the start of a (continuation) line would indent, and a tab after a non-whitespace character would complete). They requested that this issue be raised in a new bugreport on the python bug tracker -- doing that now. Is it reasonable for me to set this bug back to confirmed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1315733 Title: Python interactive interpreter does not indent with tabs, tries to tab-complete Status in “python3.4” package in Ubuntu: Won't Fix Status in “python3.4” package in Debian: Unknown Bug description: Using the python3 interactive interpreter, I can not use tabs to indent like I could on previous versions of Ubuntu (13.10 was what I was using before, now I'm using 14.04). When I try to indent on the python interpreter command line, it simply does nothing the first time I press the tab key. The second time I press it, it shows a bunch of autocomplete suggestions. For example if (True): ... tabprint(true!) File stdin, line 2 print(true!) ^ IndentationError: expected an indented block Could this be related to http://bugs.python.org/issue18988? Is the fix for that included in the version of python on 14.04? I also found http://stackoverflow.com/questions/4809820/tab-key-not- indenting-in-python, in which one of the comments to an answer suggests trying Ctrl-Vtab when you want to insert a tab. That does work for me: if (True): ... Ctrl-Vtabprint(true) ... true ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 3 11:36:57 2014 SourcePackage: python3-defaults UpgradeStatus: Upgraded to trusty on 2014-04-19 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1315733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
Launchpad has imported 1 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=11042. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-07-26T15:58:29+00:00 Alberto Salvia Novella wrote: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1347272/comments/7 ** Changed in: thunar Status: Unknown = Confirmed ** Changed in: thunar Importance: Unknown = High ** Changed in: xfce4-appfinder Status: Unknown = Confirmed ** Changed in: xfce4-appfinder Importance: Unknown = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Confirmed Status in Volume management daemon for XFCE 4: Invalid Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
Launchpad has imported 1 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=11043. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-07-26T16:00:37+00:00 Alberto Salvia Novella wrote: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1347272/comments/8 ** Changed in: xfce4-power-manager Status: Unknown = Confirmed ** Changed in: xfce4-power-manager Importance: Unknown = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Confirmed Status in Volume management daemon for XFCE 4: Invalid Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
Launchpad has imported 1 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=11044. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-07-26T16:02:48+00:00 Alberto Salvia Novella wrote: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1347272/comments/9 ** Changed in: xfce4-settings Status: Unknown = Confirmed ** Changed in: xfce4-settings Importance: Unknown = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Confirmed Status in Volume management daemon for XFCE 4: Invalid Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
Launchpad has imported 1 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=11045. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-07-26T16:06:02+00:00 Alberto Salvia Novella wrote: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1347272/comments/10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Confirmed Status in Volume management daemon for XFCE 4: Invalid Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 762699] Re: Unity launcher and panel do not zoom alongsize the desktop with Enhanced Zoom Desktop
Is there anything else we can do to help fixing this bug? It's look like Ubuntu have lost interest on accessibility, this bug was reported over 3 years ago and it isn't fixed yet. In addition, the Unity menu stills not accessible from Orca Screen Reader -- 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/762699 Title: Unity launcher and panel do not zoom alongsize the desktop with Enhanced Zoom Desktop Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Binary package hint: compiz Unity's top panel and launcher are not zoomable when using Compiz's Enhanced Zoom Desktop feature. Futhermore, top panel's shadow creates a visual glitch when zooming (see bug 762247). In Maverick zooming gnome-panel worked well. See attached screenshot for what happens in Unity. Steps to reproduce: 1) (Note that this may break the desktop. Use caution.) Open CCSM and enable the Enhanced Zoom Desktop plugin, if not already enabled 2) Set the zoom in and zoom out hotkeys if needed 3) Zoom in to the desktop What should happen: All areas of the desktop zoom in together What happens instead: All areas of the desktop except for Unity (panel/dash/launcher) zoom in. Instead, Unity is overlayed on top of the zoomed area. A screenshot may be seen here: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/762699/+attachment/2788578/+files/bug.png Affected Ubuntu versions: Natty, Oneiric, Precise, and Quantal (as of 09 Nov. 2012) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/762699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315733] Re: Python interactive interpreter does not indent with tabs, tries to tab-complete
As requested in the upstream tracker, I've filed a bug in the upstream tracker: http://bugs.python.org/issue5845 ** Bug watch added: Python Roundup #5845 http://bugs.python.org/issue5845 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1315733 Title: Python interactive interpreter does not indent with tabs, tries to tab-complete Status in “python3.4” package in Ubuntu: Won't Fix Status in “python3.4” package in Debian: Unknown Bug description: Using the python3 interactive interpreter, I can not use tabs to indent like I could on previous versions of Ubuntu (13.10 was what I was using before, now I'm using 14.04). When I try to indent on the python interpreter command line, it simply does nothing the first time I press the tab key. The second time I press it, it shows a bunch of autocomplete suggestions. For example if (True): ... tabprint(true!) File stdin, line 2 print(true!) ^ IndentationError: expected an indented block Could this be related to http://bugs.python.org/issue18988? Is the fix for that included in the version of python on 14.04? I also found http://stackoverflow.com/questions/4809820/tab-key-not- indenting-in-python, in which one of the comments to an answer suggests trying Ctrl-Vtab when you want to insert a tab. That does work for me: if (True): ... Ctrl-Vtabprint(true) ... true ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 3 11:36:57 2014 SourcePackage: python3-defaults UpgradeStatus: Upgraded to trusty on 2014-04-19 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1315733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348963] [NEW] Xorg freeze login to Desktop 14.04
Public bug reported: 1) $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 2) $ apt-cache policy xorg xorg: Installed: 1:7.7+1ubuntu8 Candidate: 1:7.7+1ubuntu8 Version table: *** 1:7.7+1ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) I expect the system to not freeze at the very same point nearly every time. 4) Many times in less than 24 hours of installing the dual boot system, Ubuntu will freeze after logging in and just as the Desktop is coming to life. I always see the Unity bar on the left, but think sometimes the system tray at the top doesn't always show. The mouse will move, but no (visible) action can be made. Switching TTY doesn't make any difference since nothing visible happens except for the mouse will no longer move. No other CTRL-ALT-F# seems to happen after that. I am only left with the option of the reset button on the chassis. https://wiki.ubuntu.com/X/Troubleshooting/Freeze Attached file contains the 3 requested log files. Even though I couldn't do anything from the desktop, I was able to ssh from my smartphone (not fun) and collect the items during the freeze. At the end of the session, I tried to shutdown -r now from my ssh session, but that didn't complete. Eventually I couldn't run any other command and when I killed the client session, I was unable to re-enter a new one and that forced my to press the reset button on the desktop. This is my first dual boot and while Ubuntu has a handful of issues, I have been able to get around well enough. But this random freezing is enough to keep me on Vista for now. I say random because I haven't figured out what the constant is. I was looking in the logs for the last thing written before I did a cold boot and after disconnecting the bluetooth, scanner and usb tv tuner, and it STILL would freeze, I was left with the graphics based on online research. However, the more constant which may still only be coincidence is the freeze seems to happen with a normal shutdown/restart. Once I do a cold reset/boot, I may not have had any freezes (still unacceptable/not a solution). On the other hand I do believe I may have had a least one concurrent freeze, even after a cold boot. I have toyed with Ubuntu and Opensuse Live and in Virtualbox on Vista (host), but this is my first dual boot with the expectation that I will eventually move away from Windows. This is not a good start. Unrelated: just to put it out there, the 2 other things I'm dealing with that are deal-breakers are: 1) my tv tuner not being recognized as such, though I am looking around like linuxtv.org regarding my u6012a mygica/geniatech usb tv tuner. 2) My front microphone is not being detected as it should (not at all). Only if I: 2a) unplug the microphone and then plug it back in (jack detection) will available change from no. Or 2b) HDAJackRetask, where I Advance override Pink Mic, Front side, changing Jack detection to not present, but that brings up another issue where audio no longer plays on the rear green, but I just override that too and change Device to Headphone and then make it permanent with Install boot override. I guess the unrelated goes to show I am willing to go above and beyond to get a nice running system, so if there are things you want me to try, let me know. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Sat Jul 26 11:57:50 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:0042] InstallationDate: Installed on 2014-07-25 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=25c0ac47-cc19-471c-8938-f56214933a32 ro initrd=/ubuntu/initrd.lz quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably
[Touch-packages] [Bug 1315733] Re: Python interactive interpreter does not indent with tabs, tries to tab-complete
** Changed in: python3.4 (Debian) Status: Unknown = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1315733 Title: Python interactive interpreter does not indent with tabs, tries to tab-complete Status in “python3.4” package in Ubuntu: Won't Fix Status in “python3.4” package in Debian: Fix Released Bug description: Using the python3 interactive interpreter, I can not use tabs to indent like I could on previous versions of Ubuntu (13.10 was what I was using before, now I'm using 14.04). When I try to indent on the python interpreter command line, it simply does nothing the first time I press the tab key. The second time I press it, it shows a bunch of autocomplete suggestions. For example if (True): ... tabprint(true!) File stdin, line 2 print(true!) ^ IndentationError: expected an indented block Could this be related to http://bugs.python.org/issue18988? Is the fix for that included in the version of python on 14.04? I also found http://stackoverflow.com/questions/4809820/tab-key-not- indenting-in-python, in which one of the comments to an answer suggests trying Ctrl-Vtab when you want to insert a tab. That does work for me: if (True): ... Ctrl-Vtabprint(true) ... true ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 3 11:36:57 2014 SourcePackage: python3-defaults UpgradeStatus: Upgraded to trusty on 2014-04-19 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1315733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346766] Re: Chinese in Ubuntu Touch should use Heiti style sans serif font
The Chinese font package currently seeded in Ubuntu Touch is fonts- arphic-ukai. On the desktop, fonts-droid is now the default Chinese font package as a result of bug #1173571, and if we want this to be changed soon, I can think it would make sense to replace fonts-arphic-ukai with fonts-droid in the touch seed. As regards Noto, the new CJK fonts are not yet included in the fonts- noto package. There is a Debian bug about it: https://bugs.debian.org/754926 ** Bug watch added: Debian Bug tracker #754926 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 ** Package changed: ubuntu-meta (Ubuntu) = ubuntu-touch-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. fonts-droid (DroidSansFallbackFull.ttf, original): - Pros: - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. -Cons: - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. As an additional alternative, just a few days ago, Google released the Noto Sans CJK fonts [2][3]: fonts-noto (Noto Sans CJK fonts): - Pros: - It takes care of different writing standard of Traditional and Simplified Chinese - It covers Japanese and Korean as well - Cons: - Needs to be tested - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese - Not yet packaged [4] [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A [2] http://googledevelopers.blogspot.de/2014/07/noto-cjk-font-that-is-complete.html [3] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1346766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315733] Re: Python interactive interpreter does not indent with tabs, tries to tab-complete
Oops, meant to include a different link in that last comment: http://bugs.python.org/issue22086 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1315733 Title: Python interactive interpreter does not indent with tabs, tries to tab-complete Status in “python3.4” package in Ubuntu: Won't Fix Status in “python3.4” package in Debian: Fix Released Bug description: Using the python3 interactive interpreter, I can not use tabs to indent like I could on previous versions of Ubuntu (13.10 was what I was using before, now I'm using 14.04). When I try to indent on the python interpreter command line, it simply does nothing the first time I press the tab key. The second time I press it, it shows a bunch of autocomplete suggestions. For example if (True): ... tabprint(true!) File stdin, line 2 print(true!) ^ IndentationError: expected an indented block Could this be related to http://bugs.python.org/issue18988? Is the fix for that included in the version of python on 14.04? I also found http://stackoverflow.com/questions/4809820/tab-key-not- indenting-in-python, in which one of the comments to an answer suggests trying Ctrl-Vtab when you want to insert a tab. That does work for me: if (True): ... Ctrl-Vtabprint(true) ... true ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 3 11:36:57 2014 SourcePackage: python3-defaults UpgradeStatus: Upgraded to trusty on 2014-04-19 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1315733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348969] [NEW] totem crashes partway thru playing .MOV files
Public bug reported: Totem crashes at different points in all .MOV files with error: Failed to decode JPEG image, or GStreamer encountered a general stream error. On the same hardware, the same files play correctly in a VirtualBox VM running 12.04, so file itself is valid. lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 apt-cache policy totem totem: Installed: 3.10.1-1ubuntu4.1 Candidate: 3.10.1-1ubuntu4.1 Version table: *** 3.10.1-1ubuntu4.1 0 500 http://ppa.launchpad.net/mc3man/trusty-media/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3.10.1-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Expected behavior: Play the file. Actual behavior: Crashes with above messages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgstreamer1.0-0 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 26 13:51:28 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1348969 Title: totem crashes partway thru playing .MOV files Status in “gstreamer1.0” package in Ubuntu: New Bug description: Totem crashes at different points in all .MOV files with error: Failed to decode JPEG image, or GStreamer encountered a general stream error. On the same hardware, the same files play correctly in a VirtualBox VM running 12.04, so file itself is valid. lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 apt-cache policy totem totem: Installed: 3.10.1-1ubuntu4.1 Candidate: 3.10.1-1ubuntu4.1 Version table: *** 3.10.1-1ubuntu4.1 0 500 http://ppa.launchpad.net/mc3man/trusty-media/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3.10.1-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Expected behavior: Play the file. Actual behavior: Crashes with above messages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgstreamer1.0-0 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 26 13:51:28 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1348969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.
Confirming: This bug is fixed for me, too. Thanks! -- 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/1243233 Title: Holding Super key doesn't bring up shortcut overlay. Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: After upgrading from 13.04 to 13.10, holding Super no longer brings up the help overlay. Holding Super worked before upgrading. Tapping the Super key still brings up the HUD, and holding it down still brings up the Launcher and after a second or so shows the numbers on the applications. In Compiz Config Manager, under Ubuntu Unity Plugin - Launcher, the Key to show the Dash, Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin - General, Enable Shortcut Hints Overlay is checked. This is also known to affect 14.04 (without compiz) when workspaces are enabled and screen resolution is 1024x768. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346766] Re: Chinese in Ubuntu Touch should use Heiti style sans serif font
At this very moment, Source Sans is still not an option and there are also questions to be answered to determine whether it fits the requirement of DFSG. Comparing wqy-microhei and fonts-droid, there is no reason to continue using microhei anymore, because after several updates of Droid Sans, the coverage problem is already improved (and wqy-microhei stops its development right after this is the fact) to be wider than wqy-microhei. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. fonts-droid (DroidSansFallbackFull.ttf, original): - Pros: - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. -Cons: - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. As an additional alternative, just a few days ago, Google released the Noto Sans CJK fonts [2][3]: fonts-noto (Noto Sans CJK fonts): - Pros: - It takes care of different writing standard of Traditional and Simplified Chinese - It covers Japanese and Korean as well - Cons: - Needs to be tested - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese - Not yet packaged [4] [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A [2] http://googledevelopers.blogspot.de/2014/07/noto-cjk-font-that-is-complete.html [3] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1346766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348890] [NEW] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN
You have been subscribed to a public bug: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN https://bugs.launchpad.net/bugs/1348890 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348890] Re: Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN
acpi-support is not involved in management of brightness keys. Reassigning to udev. ** Package changed: acpi-support (Ubuntu) = systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1348890 Title: Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN Status in “systemd” package in Ubuntu: New Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1348890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1217407] Re: whoopsie spams the log with online messages
Well, I guess it's a little better than before. Fresh install of 14.04: Jul 26 00:18:18 vane whoopsie[996]: whoopsie 0.2.24.6 starting up. Jul 26 00:18:18 vane whoopsie[996]: Using lock path: /var/lock/whoopsie/lock Jul 26 00:18:18 vane whoopsie[1041]: offline Jul 26 00:18:22 vane whoopsie[1041]: message repeated 2 times: [ offline] Jul 26 00:18:22 vane whoopsie[1041]: online Jul 26 00:35:38 vane whoopsie[1041]: message repeated 6 times: [ online] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1217407 Title: whoopsie spams the log with online messages Status in Ubuntu error tracker client (whoopsie): Confirmed Status in “whoopsie” package in Ubuntu: Confirmed Bug description: It is mostly the online messages: $ grep whoopsie /var/log/syslog Aug 27 07:42:21 xango3 whoopsie[1832]: online Aug 27 07:42:27 xango3 whoopsie[1832]: online Aug 27 07:43:32 whoopsie[1832]: last message repeated 18 times Aug 27 07:44:50 whoopsie[1832]: last message repeated 17 times Aug 27 07:45:50 whoopsie[1832]: last message repeated 16 times Aug 27 07:46:50 whoopsie[1832]: last message repeated 16 times Aug 27 07:47:50 whoopsie[1832]: last message repeated 18 times Aug 27 07:48:50 whoopsie[1832]: last message repeated 15 times Aug 27 07:49:50 whoopsie[1832]: last message repeated 16 times Aug 27 07:50:50 whoopsie[1832]: last message repeated 21 times Aug 27 07:51:50 whoopsie[1832]: last message repeated 18 times Aug 27 07:52:50 whoopsie[1832]: last message repeated 20 times Aug 27 07:53:50 whoopsie[1832]: last message repeated 22 times Aug 27 07:54:50 whoopsie[1832]: last message repeated 15 times Aug 27 07:55:50 whoopsie[1832]: last message repeated 22 times Aug 27 07:56:50 whoopsie[1832]: last message repeated 20 times Aug 27 07:57:50 whoopsie[1832]: last message repeated 18 times Aug 27 07:58:51 whoopsie[1832]: last message repeated 16 times Aug 27 07:59:46 whoopsie[1832]: last message repeated 17 times Aug 27 07:59:47 xango3 whoopsie[1832]: online Aug 27 08:00:51 whoopsie[1832]: last message repeated 24 times Aug 27 08:01:51 whoopsie[1832]: last message repeated 24 times Aug 27 08:02:51 whoopsie[1832]: last message repeated 19 times Aug 27 08:03:51 whoopsie[1832]: last message repeated 19 times Aug 27 08:04:51 whoopsie[1832]: last message repeated 17 times Aug 27 08:05:51 whoopsie[1832]: last message repeated 19 times Aug 27 08:06:51 whoopsie[1832]: last message repeated 16 times Aug 27 08:07:51 whoopsie[1832]: last message repeated 18 times Aug 27 08:08:51 whoopsie[1832]: last message repeated 28 times Aug 27 08:09:51 whoopsie[1832]: last message repeated 21 times Aug 27 08:10:51 whoopsie[1832]: last message repeated 22 times Aug 27 08:11:51 whoopsie[1832]: last message repeated 20 times Aug 27 08:12:51 whoopsie[1832]: last message repeated 18 times Aug 27 08:13:51 whoopsie[1832]: last message repeated 16 times Aug 27 08:14:51 whoopsie[1832]: last message repeated 18 times Aug 27 08:15:51 whoopsie[1832]: last message repeated 18 times Aug 27 08:16:51 whoopsie[1832]: last message repeated 15 times Aug 27 08:17:01 whoopsie[1832]: last message repeated 2 times Aug 27 08:17:12 xango3 whoopsie[1832]: online Aug 27 08:18:21 whoopsie[1832]: last message repeated 22 times Aug 27 08:19:21 whoopsie[1832]: last message repeated 15 times Aug 27 08:19:44 whoopsie[1832]: last message repeated 5 times Aug 27 08:19:44 xango3 whoopsie[1832]: online Aug 27 08:20:48 whoopsie[1832]: last message repeated 29 times Aug 27 08:21:49 whoopsie[1832]: last message repeated 23 times Aug 27 08:22:50 whoopsie[1832]: last message repeated 24 times Aug 27 08:23:05 whoopsie[1832]: last message repeated 8 times Aug 27 08:23:10 xango3 whoopsie[1832]: online Aug 27 08:23:11 xango3 whoopsie[1832]: online Aug 27 08:23:15 xango3 whoopsie[1832]: online Aug 27 08:23:16 xango3 whoopsie[1832]: online Aug 27 08:24:17 whoopsie[1832]: last message repeated 22 times Aug 27 08:24:27 xango3 whoopsie[1832]: online Aug 27 08:24:28 xango3 whoopsie[1832]: online Aug 27 08:25:29 whoopsie[1832]: last message repeated 17 times Aug 27 08:25:40 whoopsie[1832]: last message repeated 3 times Aug 27 08:25:42 xango3 whoopsie[1832]: online Aug 27 08:25:42 xango3 whoopsie[1832]: online Aug 27 08:25:43 xango3 whoopsie[1832]: online Aug 27 08:26:44 whoopsie[1832]: last message repeated 15 times Aug 27 08:26:55 whoopsie[1832]: last message repeated 2 times Aug 27 08:26:56 xango3 whoopsie[1832]: online Aug 27 08:33:23 xango3 whoopsie[1568]: whoopsie 0.2.23 starting up. Aug 27 08:33:23 xango3 whoopsie[1568]: Using lock path: /var/lock/whoopsie/lock Aug 27 08:33:23 xango3 whoopsie[1794]: offline Aug 27 08:33:27 xango3 whoopsie[1794]: offline Aug 27 08:33:27 xango3
[Touch-packages] [Bug 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN
The network-manager-l2tp package in #37 works very well for me, using Ubuntu 14.04 to connect to a Cisco L2TP/IPsec VPN. (Just a couple of minor tweaks needed to get the IPsec part working, for me.) This project works, is well-integrated with Network Manager, and has an active and helpful developer. It should be added to Ubuntu ASAP, IMO. -- 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/264691 Title: Please add NM option for connecting to L2TP IPSEC VPN Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Status in “network-manager” package in Debian: Invalid Bug description: Binary package hint: network-manager Missing feature: You cannot connect to a (Microsoft) L2TP IPSEC VPN with Network Manager. The server I want to connect to expects a login / password and a PSK. When you do a connection in XP you can see the following details on a connection: Device name: L2TP Server type: PPP Authentication: MS CHAP v2 IPSEC Encryption: IPSEC ESP 3DES Compression: MPPC To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/264691/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 734908] Re: Unity is visible on top of fullscreen apps
** Tags removed: 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/734908 Title: Unity is visible on top of fullscreen apps Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity Distro Priority: Confirmed Status in “compiz” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Confirmed Status in “unity” source package in Precise: Fix Released Bug description: [Test Case] 1. Start a fullscreen application (e.g. Firefox in Fullscreen mode) - Verify that the panel is not visible [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: NOTE: This bug is only about the single monitor case. If you still have problems with multiple monitors, see bug 748539 instead. ORIGINAL DESCRIPTION: In natty alpha 3 up to date, I cannot get fullscreen in any application. Panels are still visible. Tested with: - totem - vlc - firefox - chrome - geany Unity panel and top bar are always on top. - Desired Solution: - When a window is fullscreen (note: this should not be confused with the *maximised* state) the menu bar should not be displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/734908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349011] [NEW] nm-l2tp-service needs exception in ppp ip-up/down scripts
Public bug reported:
There is an actively maintained NetworkManager L2TP VPN plugin,
available as an Ubuntu package here: https://launchpad.net/~seriy-
pr/+archive/ubuntu/network-manager-l2tp. Hopefully it will be a part of
Ubuntu soon.
Like nm-pptp-service, it needs an exception in
/etc/ppp/ip-{up,down}.d/000resolvconf (part of the resolvconf package)
as follows:
% diff /etc/ppp/ip-up.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-up
16c16
nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
% diff /etc/ppp/ip-down.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-down
16c16
nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
Since that's how it works for the PPTP plugin, could we add the L2TP one
as well so that it can work out of the box on Ubuntu?
** Affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1349011
Title:
nm-l2tp-service needs exception in ppp ip-up/down scripts
Status in “resolvconf” package in Ubuntu:
New
Bug description:
There is an actively maintained NetworkManager L2TP VPN plugin,
available as an Ubuntu package here: https://launchpad.net/~seriy-
pr/+archive/ubuntu/network-manager-l2tp. Hopefully it will be a part
of Ubuntu soon.
Like nm-pptp-service, it needs an exception in
/etc/ppp/ip-{up,down}.d/000resolvconf (part of the resolvconf package)
as follows:
% diff /etc/ppp/ip-up.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-up
16c16
nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
% diff /etc/ppp/ip-down.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-down
16c16
nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
Since that's how it works for the PPTP plugin, could we add the L2TP
one as well so that it can work out of the box on Ubuntu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 862339] Re: Grid placement is offset by 1px
** Also affects: ayatana-design Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/862339 Title: Grid placement is offset by 1px Status in Ayatana Design: New Status in Compiz: Fix Released Status in Compiz Grid Plugin: Fix Released Status in Compiz Main Plugins: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: New Bug description: Window placement is offset by 1px when the grid plugin maximizes a window TESTCASE Semi-maximize two terminals There should be no visible gap between them To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/862339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 832150] Re: ubuntu desktop unity. Mouse at the left side doesn't reveal launcher
It doesn't seem there was a unity package released. I'm not sure what the unity (Ubuntu) task in this bug is for. -- 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/832150 Title: ubuntu desktop unity. Mouse at the left side doesn't reveal launcher Status in Ayatana Design: New Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Oneiric: Fix Released Status in “unity” source package in Oneiric: New Bug description: TEST CASE: 1. Start a session (restarting Unity didn't do the trick). 2. Start gnome-terminal or gedit and maximize it (doesn't matter how, also works with other applications). RESULT: * The launcher does not reveal (hide mode 2 - Dodge Window). I'm not sure how, but it will eventually start working again after some window dragging/maximizing. Using Nux r483 and Unity r1628. =Original Report= Hello i am testing Ubuntu 11.10 alpha3 and i have a problem with unity. When i open a window, firefox for example, i cannot see the launcher when i move my cursor on the left side as i used to. This problem is not happening when i use unity2d. I can see the launcher by pressing alt+f1. I didn't had a clean install, i mean i upgraded to Ubuntu 11.10. Unity's package version is 4.8.2-0ubuntu4. Thank you in advance Vassilis ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,gnomecompat,imgpng,vpswitch,commands,grid,obs,compiztoolbox,place,mousepoll,move,regex,wall,session,unitymtgrabhandles,wobbly,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell] Date: Tue Aug 23 19:14:50 2011 InstallationMedia: Ubuntu 10.04.2 LTS Lucid Lynx - Release i386 (20110211.1) SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-08-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/832150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349015] [NEW] HUAWEI E5776 not detected
Public bug reported: dmesg [12852.415901] CPU: 2 PID: 783 Comm: ModemManager Tainted: GW 3.13.0-24-generic #47~precise2-Ubuntu [12852.415992] Hardware name: eMachines eME732/HM55_CP, BIOS V1.01 08/13/2010 [12852.416058] task: f53ab3c0 ti: ebaa6000 task.ti: ebaa6000 [12852.416112] EIP: 0060:[f881567e] EFLAGS: 00010283 CPU: 2 [12852.416168] EIP is at usb_wwan_write+0x10e/0x2c0 [usb_wwan] [12852.416222] EAX: 0001 EBX: e3c45240 ECX: 0001 EDX: f2708000 [12852.416283] ESI: EDI: EBP: ebaa7e9c ESP: ebaa7e50 [12852.416343] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [12852.416396] CR0: 80050033 CR2: 0040 CR3: 2ba46000 CR4: 07f0 [12852.416455] Stack: [12852.416477] ebcd1be8 ebaa7ea8 c13e26a0 0078 ebaa7e64 0001 1c04 [12852.416631] ebec6db8 e3c45288 ebec6c00 e3c45280 f2708000 f3ad2df0 0001 0001 [12852.416780] f8882000 f1f3c600 0007 ebaa7ed4 f856b751 0001 0296 c13e2bde [12852.416930] Call Trace: [12852.416983] [c13e26a0] ? tty_mode_ioctl+0xa0/0x510 [12852.417071] [f856b751] serial_write+0x51/0xd0 [usbserial] [12852.417159] [c13e2bde] ? n_tty_ioctl_helper+0x2e/0x70 [12852.417245] [c13dec13] n_tty_write+0x143/0x340 [12852.417325] [c1087930] ? try_to_wake_up+0x1a0/0x1a0 [12852.417409] [c13dbd11] tty_write+0x101/0x210 [12852.417480] [c13dead0] ? process_echoes+0x70/0x70 [12852.417558] [c13dbc10] ? tty_write_lock+0x50/0x50 [12852.417639] [c1181c9d] vfs_write+0x9d/0x1e0 [12852.417710] [c10b738b] ? ktime_get_ts+0x4b/0x120 [12852.417787] [c1182167] SyS_write+0x57/0xa0 [12852.417862] [c168d3cd] sysenter_do_call+0x12/0x28 [12852.417936] Code: 02 8b 40 08 e8 94 2e cb c8 85 c0 0f 88 fc 00 00 00 81 7c 24 3c 00 10 00 00 b8 00 10 00 00 0f 4e 44 24 3c 8b 54 24 30 89 44 24 38 8b 47 40 8b 4c 24 38 e8 c6 73 af c8 8b 54 24 38 8b 44 24 34 89 [12852.418518] EIP: [f881567e] usb_wwan_write+0x10e/0x2c0 [usb_wwan] SS:ESP 0068:ebaa7e50 [12852.418651] CR2: 0040 [12852.438142] ---[ end trace 930c0f6428b9e4a5 ]--- [12856.711325] ISO 9660 Extensions: Microsoft Joliet Level 1 [12856.712596] ISOFS: changing to secondary root [12868.212757] systemd-hostnamed[7469]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! [14286.575679] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [14286.575793] option 2-1.2:1.0: device disconnected [14286.578010] option1 ttyUSB1: option_instat_callback: error -108 [17268.800803] usb 2-1.2: USB disconnect, device number 6 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: 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/1349015 Title: HUAWEI E5776 not detected Status in “network-manager” package in Ubuntu: New Bug description: dmesg [12852.415901] CPU: 2 PID: 783 Comm: ModemManager Tainted: GW 3.13.0-24-generic #47~precise2-Ubuntu [12852.415992] Hardware name: eMachines eME732/HM55_CP, BIOS V1.01 08/13/2010 [12852.416058] task: f53ab3c0 ti: ebaa6000 task.ti: ebaa6000 [12852.416112] EIP: 0060:[f881567e] EFLAGS: 00010283 CPU: 2 [12852.416168] EIP is at usb_wwan_write+0x10e/0x2c0 [usb_wwan] [12852.416222] EAX: 0001 EBX: e3c45240 ECX: 0001 EDX: f2708000 [12852.416283] ESI: EDI: EBP: ebaa7e9c ESP: ebaa7e50 [12852.416343] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [12852.416396] CR0: 80050033 CR2: 0040 CR3: 2ba46000 CR4: 07f0 [12852.416455] Stack: [12852.416477] ebcd1be8 ebaa7ea8 c13e26a0 0078 ebaa7e64 0001 1c04 [12852.416631] ebec6db8 e3c45288 ebec6c00 e3c45280 f2708000 f3ad2df0 0001 0001 [12852.416780] f8882000 f1f3c600 0007 ebaa7ed4 f856b751 0001 0296 c13e2bde [12852.416930] Call Trace: [12852.416983] [c13e26a0] ? tty_mode_ioctl+0xa0/0x510 [12852.417071] [f856b751] serial_write+0x51/0xd0 [usbserial] [12852.417159] [c13e2bde] ? n_tty_ioctl_helper+0x2e/0x70 [12852.417245] [c13dec13] n_tty_write+0x143/0x340 [12852.417325] [c1087930] ? try_to_wake_up+0x1a0/0x1a0 [12852.417409] [c13dbd11] tty_write+0x101/0x210 [12852.417480] [c13dead0] ? process_echoes+0x70/0x70 [12852.417558] [c13dbc10] ? tty_write_lock+0x50/0x50 [12852.417639] [c1181c9d] vfs_write+0x9d/0x1e0 [12852.417710] [c10b738b] ? ktime_get_ts+0x4b/0x120 [12852.417787] [c1182167] SyS_write+0x57/0xa0 [12852.417862] [c168d3cd] sysenter_do_call+0x12/0x28 [12852.417936] Code: 02 8b 40 08 e8 94 2e cb c8 85 c0 0f 88 fc 00 00 00 81 7c 24 3c 00 10 00 00 b8 00 10 00 00 0f 4e 44 24 3c 8b 54 24 30 89 44 24 38 8b 47 40 8b 4c 24 38 e8 c6 73 af c8 8b 54 24 38 8b 44 24 34 89 [12852.418518] EIP: [f881567e] usb_wwan_write+0x10e/0x2c0 [usb_wwan] SS:ESP 0068:ebaa7e50 [12852.418651] CR2: 0040 [12852.438142]
[Touch-packages] [Bug 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken
This bug is marked Invalid for unity (Ubuntu) but Confrmed for unity (Ubuntu Trusty). I think that's mistake, and this bug should no longer affect the unity package. -- 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/727904 Title: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Committed Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Confirmed Bug description: To reproduce: Open two Chrome windows and two Firefox windows. Drag a .html file over the Chrome icon in the Launcher. A spread of the two Chrome windows should appear. Then continue the same drag, and drag the file over the Firefox icon in the Launcher. Nothing happens, the Chrome spread is still displayed. Desired behaviour; After a spread appears as a result of the user dragging a file over a application icon in the Launcher, if the user then drags the file over a different application icon (where the application is also a valid drop receptacle for the file type) the spread should switch to the newly selected application. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 866752] Re: Sometimes configure events are missed and windows move slow as a result
A task for the unity package was just added on 2014-07-24. Was that a mistake? It seems that this bug was fixed and should no longer affect the unity package. ** Changed in: unity (Ubuntu) Status: Invalid = New ** Changed in: unity (Ubuntu Oneiric) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/866752 Title: Sometimes configure events are missed and windows move slow as a result Status in Ayatana Design: New Status in Compiz: Fix Released Status in Compiz Core: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: New Status in “compiz” source package in Oneiric: Fix Released Status in “unity” source package in Oneiric: New Bug description: Our current method of tracking configure events is error prone since it's liable to interference from other plugins. A better solution is to use X Request serials like metacity does, since this is not prone to be interfered with. TESTCASE Move windows around, maximize, unmaximize, semi-maximize, use alt-tab Windows shouldn't move slowly To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/866752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 862339] Re: Grid placement is offset by 1px
A task for the unity package was just added on 2014-07-24. Was that a mistake? It seems that this bug was fixed and should no longer affect the unity package. -- 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/862339 Title: Grid placement is offset by 1px Status in Ayatana Design: New Status in Compiz: Fix Released Status in Compiz Grid Plugin: Fix Released Status in Compiz Main Plugins: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: New Bug description: Window placement is offset by 1px when the grid plugin maximizes a window TESTCASE Semi-maximize two terminals There should be no visible gap between them To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/862339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1212987] Re: Unity not starting after boot
I have the same problem. (Ubuntu 14.04 32-bit) I installed the most recent batch of updates (including one for compiz) and after the next reboot my system is effectively dead. After login I get wallpaper only. Ctrl-Alt-T doesn't get a terminal. Ctrl-Alt-F1 works OK. I installed ccsm. The unity plugin was disabled. I enabled it, but I still don't have a GUI after a reboot (even though the unity plugin is still enabled) -- 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/1212987 Title: Unity not starting after boot Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: After boot today. Unity was missing. Empty desktop. In ccsm is seems the unity plugin was disabled somehow, I re-enabled it. Unity came back but coudn't set launcher icon size in settings - appearance - look. I tried: (http://askubuntu.com/questions/17381/unity-doesnt-load-no-launcher-no-dash-appears/) dconf reset -f /org/compiz/ unity --reset-icons disown Unity did reset Still can set icon size in settings - appearance - look. Have to use Unity Tweak Tool for that to set icon size on 32. Then started Chromium and Unity crashed again. Restart and still can't set icon size or launcher to autohide. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Aug 16 10:24:51 2013 InstallationDate: Installed on 2013-04-26 (111 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1212987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310970] Re: Power-button alert when other users are logged in is ungrammatical
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-greeter (Ubuntu) Status: New = Confirmed -- 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/1310970 Title: Power-button alert when other users are logged in is ungrammatical Status in Unity: New Status in Unity Greeter: Invalid Status in “unity” package in Ubuntu: Confirmed Status in “unity-greeter” package in Ubuntu: Confirmed Bug description: 1. Log in as user A 2. Switch to user B 3. Press the power button. What you see: Other users are currently logged in to this computer, shutting down now will also close these other sessions. Goodbye XYZ, would you like to… What's wrong with this: * The first sentence is a run-on sentence, which is poor grammar. * The message singles out shutting down, when restarting also has the issue. * Close these other sessions is not the issue; potentially losing work is the issue. * Goodbye XYZ, would you like to... is even more of a cheery non-sequitur than usual following the warning. What you should see: Something like 2 other users are logged in. Restarting or shutting down will close their open applications and may cause them to lose work. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1310970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open
The warning (1st sentence) is not localized into ... at least french. -- 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/1281058 Title: [UIFe] The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: Confirmed Status in “systemd” source package in Trusty: Confirmed Status in “unity” source package in Trusty: Fix Released Status in “unity-greeter” source package in Trusty: Fix Released Bug description: [Impact] Other users logged into a system may loose work if another user shuts down/reboots a system. Data loss is not a Good Thing. [Test Case] Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost [ Regression Potential] None. -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be Other users are currently logged in to this computer, shutting down now will also close these other sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-session (Ubuntu Trusty) Status: New = Confirmed -- 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/1281058 Title: [UIFe] The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: Confirmed Status in “systemd” source package in Trusty: Confirmed Status in “unity” source package in Trusty: Fix Released Status in “unity-greeter” source package in Trusty: Fix Released Bug description: [Impact] Other users logged into a system may loose work if another user shuts down/reboots a system. Data loss is not a Good Thing. [Test Case] Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost [ Regression Potential] None. -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be Other users are currently logged in to this computer, shutting down now will also close these other sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Trusty) Status: New = Confirmed -- 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/1281058 Title: [UIFe] The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: Confirmed Status in “systemd” source package in Trusty: Confirmed Status in “unity” source package in Trusty: Fix Released Status in “unity-greeter” source package in Trusty: Fix Released Bug description: [Impact] Other users logged into a system may loose work if another user shuts down/reboots a system. Data loss is not a Good Thing. [Test Case] Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost [ Regression Potential] None. -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be Other users are currently logged in to this computer, shutting down now will also close these other sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot
Hi Marco, I downloaded the Hotkey app from Clevo and InitHeadphone.exe is still present. All it does is calling the function InitHeadphone from hp.dll. If you don't like the Hotkey app, I guess you can also fix the problem (on windows!) by saving hp.dll, uninstalling the Hotkey app and then schedule an new task On machine unlock with a command like rundll32 c:\path\to\hp.dll,InitHeadphone -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: When I boot Windows and then reboot into Ubuntu the sound is ok. But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. Also heaphone stop working after putting laptop to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
I'm kinda new at this. Do I understand you to be saying that, in order to free up space on my hdd, I can safely delete such items from my /boot file as abi 3.11.0-17-generic and abi 3.11.0-19-generic if abi 3.11.0-24-generic has been installed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in tools for generating an initramfs: New Status in “initramfs-tools” package in Ubuntu: Triaged Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349033] [NEW] LXC Error after launching the conatiner ubuntu 14.04
Public bug reported: Hi Guys, I have a container created in my ubuntu 14.04 that is running on oracle virtual box. once i start my container with below command i am getting the below error. lxc-start --name cn-01 init: setvtrgb main process (421) terminated with status 1 init: plymouth-upstart-bridge respawning too,fast After the above error there is no login prompt is visible. As a fix i need to hit 'Enter' key after that i get a prompt for Login. Is this a bug or Is there anything that i am missing during my installation? Thanks Sandeep ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Attachment added: Before_Hitting_Enter_Error_Screen.JPG https://bugs.launchpad.net/bugs/1349033/+attachment/4163600/+files/Before_Hitting_Enter_Error_Screen.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1349033 Title: LXC Error after launching the conatiner ubuntu 14.04 Status in “lxc” package in Ubuntu: New Bug description: Hi Guys, I have a container created in my ubuntu 14.04 that is running on oracle virtual box. once i start my container with below command i am getting the below error. lxc-start --name cn-01 init: setvtrgb main process (421) terminated with status 1 init: plymouth-upstart-bridge respawning too,fast After the above error there is no login prompt is visible. As a fix i need to hit 'Enter' key after that i get a prompt for Login. Is this a bug or Is there anything that i am missing during my installation? Thanks Sandeep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1349033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059872] Re: Error formatting disk using disk utility
Dimitri, are you going to revert that patch? I was going to revert it locally to verify that installing the new util-linux 2.24 from debian experimental fixed it, but it seems that the bzr branch is significantly out of date for some reason... -- 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/1059872 Title: Error formatting disk using disk utility Status in “udisks2” package in Ubuntu: Triaged Status in “util-linux” package in Ubuntu: Triaged Status in “util-linux” package in Debian: New Bug description: Formatting a SD card using the disk utility fails with an error message Error formatting disk - Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0) Steps to repro: Launch the disk utility Plug a SD card into the computer Select the SD card and click on the gears icon at the top right of the application From the drop down menu, select Format Disk maintain the default setting and select Format Acknowledge warnings After format process has been going for a while, the error message shown above pops up ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: udisks 1.0.4-6 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CustomUdevRuleFiles: 51-android.rules 51-android.rules~ Date: Mon Oct 1 15:07:46 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120720.1) MachineType: FOXCONN NT-A2400NT-A3500 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=fcc445e4-9662-47cc-855d-ca17ad1c2a87 ro quiet splash vt.handoff=7 SourcePackage: udisks UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd03/29/2011:svnFOXCONN:pnNT-A2400NT-A3500:pvrFAB1.0:rvnFOXCONN:rnNT-A2400NT-A3500:rvrFAB1.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400NT-A3500 dmi.product.version: FAB 1.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1059872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348954] Re: update Python3 for trusty
So is the plan to bring 3.4.1 into Trusty then? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1348954 Title: update Python3 for trusty Status in “python3.4” package in Ubuntu: New Bug description: update Python3 for trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1348954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305902] Re: indicator-sound-service crashed with SIGSEGV in g_variant_is_trusted()
Will this be backported to 14.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1305902 Title: indicator-sound-service crashed with SIGSEGV in g_variant_is_trusted() Status in “indicator-sound” package in Ubuntu: Fix Released Bug description: Happened when trying to play Pandora Radio using the Pithos client. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 10 09:58:34 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2014-04-08 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140407) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f892d60f9c0:mov0x20(%rdi),%eax PC (0x7f892d60f9c0) ok source 0x20(%rdi) (0x0020) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-sound StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () accounts_service_user_set_player () _start () Title: indicator-sound-service crashed with SIGSEGV in g_variant_builder_add_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1305902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323039] Re: [To be filled by O.E.M., Realtek ALC898, Blue Line In, Rear] Background noise or low volume
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1323039 Title: [To be filled by O.E.M., Realtek ALC898, Blue Line In, Rear] Background noise or low volume Status in “alsa-driver” package in Ubuntu: Expired Bug description: Since I upgraded to 14.04 (actually, re-installed Ubuntu because I had new disks) sound in doesn't work at computer startup. I have to type sudo pactl load-module module-loopback latency_msec=1 in order to get sound from my TV (blue audio plug). But then, there's a lot of crackle. I have to modify the input volume up and down, the output volume up and down, then the crackle has gone. I can probably put the module load in some startup script, but the crackle is annoying. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christine 2930 F pulseaudio /dev/snd/controlC0: christine 2930 F pulseaudio /dev/snd/pcmC0D0c: christine 2930 F...m pulseaudio /dev/snd/pcmC0D0p: christine 2930 F...m pulseaudio CurrentDesktop: Unity Date: Sun May 25 19:08:25 2014 InstallationDate: Installed on 2014-04-21 (34 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Blue Line In, Rear Symptom_Type: High background noise, or volume is too low Title: [To be filled by O.E.M., Realtek ALC898, Blue Line In, Rear] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CROSSHAIR V FORMULA-Z dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd11/15/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVFORMULA-Z:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1323039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349051] [NEW] Cannot stop cups-daemon, cups-browsed servers after upgrading certain packages 14.04
Public bug reported: Cups needs to be taken out of a default Ubuntu installation! (I don't know where to put this message, but here seems OK) When I upgraded some cup lib packages (not cups-daemon or cups-browsed), I couldn't stop cups: sudo stop cups sudo stop cups-browsed # they both say they've stopped.. sudo netstat -tapd #they're still running grrr Funny I had the same problem with 13.10 I'm running a Xubuntu 14.04 LiveUSB. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Cannot stop after upgrading certain packages + Cannot stop after upgrading certain packages 14.04 ** Summary changed: - Cannot stop after upgrading certain packages 14.04 + Cannot stop cups-daemon, cups-browsed servers after upgrading certain packages 14.04 ** Description changed: Cups needs to be taken out of a default Ubuntu installation! (I don't know where to put this message, but here seems OK) - When I upgraded some cup lib packages, I couldn't stop cups: + When I upgraded some cup lib packages (not cups-daemon or cups-browsed), I couldn't stop cups: sudo stop cups sudo stop cups-browsed sudo netstat -tapd #they're still running grrr + + Funny I had the same problem with 13.10 + + I'm running a Xubuntu 14.04 LiveUSB. -- 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/1349051 Title: Cannot stop cups-daemon, cups-browsed servers after upgrading certain packages 14.04 Status in “cups” package in Ubuntu: New Bug description: Cups needs to be taken out of a default Ubuntu installation! (I don't know where to put this message, but here seems OK) When I upgraded some cup lib packages (not cups-daemon or cups-browsed), I couldn't stop cups: sudo stop cups sudo stop cups-browsed # they both say they've stopped.. sudo netstat -tapd #they're still running grrr Funny I had the same problem with 13.10 I'm running a Xubuntu 14.04 LiveUSB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1349051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349051] Re: Cannot stop cups-daemon, cups-browsed servers after upgrading certain packages 14.04
** Description changed: Cups needs to be taken out of a default Ubuntu installation! (I don't know where to put this message, but here seems OK) When I upgraded some cup lib packages (not cups-daemon or cups-browsed), I couldn't stop cups: sudo stop cups - sudo stop cups-browsed + sudo stop cups-browsed # they both say they've stopped.. sudo netstat -tapd #they're still running grrr Funny I had the same problem with 13.10 I'm running a Xubuntu 14.04 LiveUSB. -- 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/1349051 Title: Cannot stop cups-daemon, cups-browsed servers after upgrading certain packages 14.04 Status in “cups” package in Ubuntu: New Bug description: Cups needs to be taken out of a default Ubuntu installation! (I don't know where to put this message, but here seems OK) When I upgraded some cup lib packages (not cups-daemon or cups-browsed), I couldn't stop cups: sudo stop cups sudo stop cups-browsed # they both say they've stopped.. sudo netstat -tapd #they're still running grrr Funny I had the same problem with 13.10 I'm running a Xubuntu 14.04 LiveUSB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1349051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
