[Touch-packages] [Bug 1384751] Re: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
The attachment "lxc.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384751 Title: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc- restore-net: not found Status in “lxc” package in Ubuntu: Confirmed Status in “lxc” source package in Utopic: Triaged Status in “lxc” source package in Vivid: Confirmed Bug description: A patch for this has been posted to the upstream LXC list here: https://lists.linuxcontainers.org/pipermail/lxc- devel/2014-October/010741.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359414] Re: I don't know
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1359414 Title: I don't know Status in “xorg” package in Ubuntu: Expired Bug description: ? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 20 23:25:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:817a] InstallationDate: Installed on 2002-01-01 (4614 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Olidata S.p.A. System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=f8ed6b3f-29c8-40b7-8ee0-dde0cfc75fc6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5L-VM GB dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.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.:bvr0303:bd01/21/2008:svnOlidataS.p.A.:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5L-VMGB:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: Olidata S.p.A. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 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.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jan 1 01:00:44 2002 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9056 vendor INL xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1359414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
Same thing - installed Ubuntu 14.10 server (x86_64). Base Install + SSH Server. On first boot, saw the errors just after logging in. [ 93.892769] systemd-logind[1148]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 93.892864] systemd-logind[1148]: failed to start user service: Unknown unit: user@1000.service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in “systemd-shim” package in Ubuntu: Triaged Status in “systemd-shim” package in Debian: Incomplete Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
This patch https://codereview.qt-project.org/#/c/98115/ and bug bugreports.qt-project.org/browse/QTBUG-40234 will probably effect/fix this bug as well as those other previous fixes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376240] Re: pressing power button should silence incoming call
Marking this as critical because all phones have a way to silence the call without rejecting it (which causes it to go immediately to voice mail). Pretty basic feature that we should have. -- 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/1376240 Title: pressing power button should silence incoming call Status in Telephony Service: Confirmed Status in Ubuntu UX bugs: In Progress Status in “unity8” package in Ubuntu: Confirmed Bug description: In the incoming call dialog there is no way to dismiss a call, only reject it. I would like a way to keep the calling active but in silent mode. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1376240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376240] Re: pressing power button should silence incoming call
We just need a signal we can listen for in telephony-service when the power button is pressed and then we can handle the rest. -- 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/1376240 Title: pressing power button should silence incoming call Status in Telephony Service: Confirmed Status in Ubuntu UX bugs: In Progress Status in “unity8” package in Ubuntu: Confirmed Bug description: In the incoming call dialog there is no way to dismiss a call, only reject it. I would like a way to keep the calling active but in silent mode. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1376240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376240] Re: pressing power button should silence incoming call
As agreed at the sprint in DC, pressing the power button when an incoming call is happening should cause the ringer and haptic feedback to stop immediately, effectively "dismissing" the call. ** Summary changed: - [incoming call snap] There is no way to dismiss a call + pressing power button should silence incoming call ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** No longer affects: unity-notifications (Ubuntu) ** Also affects: telephony-service Importance: Undecided Status: New ** No longer affects: dialer-app ** Changed in: telephony-service Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu) Importance: High => Critical ** Tags added: rtm14 ** Changed in: telephony-service Status: New => Confirmed ** Changed in: telephony-service Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1376240 Title: pressing power button should silence incoming call Status in Telephony Service: Confirmed Status in Ubuntu UX bugs: In Progress Status in “unity8” package in Ubuntu: Confirmed Bug description: In the incoming call dialog there is no way to dismiss a call, only reject it. I would like a way to keep the calling active but in silent mode. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1376240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362781] Re: After date recurrence end is not functioning.
** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1362781 Title: After date recurrence end is not functioning. Status in Qt Organizer - EDS plugin: In Progress Status in Calendar application for Ubuntu devices: In Progress Status in “qtorganizer5-eds” package in Ubuntu: In Progress Bug description: Just noticed that, Creating an event , which ends after certain date, is creating an event with infinity , no end dates. Expected : It should stop event from that date. To manage notifications about this bug go to: https://bugs.launchpad.net/qtorganizer5-eds/+bug/1362781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384830] Re: Event object's attendees does not contain email address
** Tags added: rtm14 ** Changed in: qtorganizer5-eds (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1384830 Title: Event object's attendees does not contain email address Status in “qtorganizer5-eds” package in Ubuntu: In Progress Bug description: Event object's attendees does not contain email address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtorganizer5-eds/+bug/1384830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384751] Re: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
Here's a debdiff for the patch. ** Patch added: "lxc.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+attachment/4246695/+files/lxc.debdiff -- 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/1384751 Title: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc- restore-net: not found Status in “lxc” package in Ubuntu: Confirmed Status in “lxc” source package in Utopic: Triaged Status in “lxc” source package in Vivid: Confirmed Bug description: A patch for this has been posted to the upstream LXC list here: https://lists.linuxcontainers.org/pipermail/lxc- devel/2014-October/010741.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307877] Re: Laptop Monitor Brightness reduced to minimum and disabled after disconnection from external monitor.
Same here. After connecting external monitor brightness control keys stop working. Althought I can change brightness "manually" on on "Brightness & Lock" settings. I'm using nvidia open source driver . -- 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/1307877 Title: Laptop Monitor Brightness reduced to minimum and disabled after disconnection from external monitor. Status in The Linux Kernel: New Status in “xorg” package in Ubuntu: Confirmed Bug description: Hi, I have the following problem under Ubuntu 14.04. As soon as I disconnect my external monitor from my Laptop (Lenovo X1 Carbon), the brigthness is reduced to minimum (backlight switches off) and I can not increase it again. When I use the brightness control keys the brightness bar shows that it is set to maximum even though it clearly is not. Using the control keys still changes the brightness bar but does nothing to the brightness itself. Upon a restart of the laptop the brightness returns to its maximum and is controllable again. I encountered this problem under the Unity version shipped with Ubuntu 14.04, but it might happen with other desktop managers as well. This problem did not exist when my Laptop was running under Ubuntu 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1307877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358343] Re: [TOPBLOCKER] too easy to answer a call by accident
** Changed in: telephony-service (Ubuntu) Status: New => Invalid ** Changed in: dialer-app (Ubuntu) Status: Confirmed => Invalid ** Changed in: telephony-service Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1358343 Title: [TOPBLOCKER] too easy to answer a call by accident Status in Telephony Service: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: Invalid Status in “telephony-service” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: If you put the phone in your pocket with locked screen and you receive a call is too easy to answer or reject that by mistake. Or pressing the screen while trying to get the phone or the call can be answered without you noticed by your pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1358343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386466] [NEW] alt-backtick switcher does not iterate through all windows
Public bug reported: There is a serious problem with how the alt-backtick (or alt-grave) switching works. Say I have 10 windows open in Firefox. It is almost impossible to iterate through all 10 of them. This is, I think, for 2 reasons. First, every time the "spread" comes up, the windows are in a different, and seemingly random, order. If I hit alt-grave over and over again, I just observed it cycling back and forth between 2 windows. It goes between the start window and another, and I have no idea how that window was chosen. How do I look at the 2nd window, then the 3rd, the the 4th, and so on? As of now, I have to look at the spread and, for each one, remember which one I have looked at and which I have not. If there are 3 windows, this is fine. But if there are 10 or 12? No. The fact that the windows come up in random order (mentioned above) makes this harder. I cannot even remember the positions of the windows I have examined. I have to actually find the window content. It would be nice if the job of remember which windows I have seen as I iterated through the available windows was not a job that I had to do, but a job that software could do for me. Is there software that can do this for me? If so, please let me know which it is. thanx - ray ps: I have read through these for help: http://www.reddit.com/r/Ubuntu/comments/jv5vy/ubuntu_1110_so_far_screenshot_tour_by_jono_bacon/c2fk1bs http://askubuntu.com/questions/28086/what-are-unitys-keyboard-and-mouse- shortcuts http://design.canonical.com/2012/03/task-switching-in-ubuntu-and-a -introduction-to-the-spread/ Let me know if there is other doc that shows how to configure window switching or what key-combo to use. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Oct 27 17:11:22 2014 InstallationDate: Installed on 2014-01-31 (269 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-08-14 (74 days ago) ** Affects: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1386466 Title: alt-backtick switcher does not iterate through all windows Status in “unity” package in Ubuntu: New Bug description: There is a serious problem with how the alt-backtick (or alt-grave) switching works. Say I have 10 windows open in Firefox. It is almost impossible to iterate through all 10 of them. This is, I think, for 2 reasons. First, every time the "spread" comes up, the windows are in a different, and seemingly random, order. If I hit alt-grave over and over again, I just observed it cycling back and forth between 2 windows. It goes between the start window and another, and I have no idea how that window was chosen. How do I look at the 2nd window, then the 3rd, the the 4th, and so on? As of now, I have to look at the spread and, for each one, remember which one I have looked at and which I have not. If there are 3 windows, this is fine. But if there are 10 or 12? No. The fact that the windows come up in random order (mentioned above) makes this harder. I cannot even remember the positions of the windows I have examined. I have to actually find the window content. It would be nice if the job of remember which windows I have seen as I iterated through the available windows was not a job that I had to do, but a job that software could do for me. Is there software that can do this for me? If so, please let me know which it is. thanx - ray ps: I have read through these for help: http://www.reddit.com/r/Ubuntu/comments/jv5vy/ubuntu_1110_so_far_screenshot_tour_by_jono_bacon/c2fk1bs http://askubuntu.com/questions/28086/what-are-unitys-keyboard-and- mouse-shortcuts http://design.canonical.com/2012/03/task-switching-in-ubuntu-and-a -introduction-to-the-spread/ Let me know if there is other doc that shows how to configure window switching or what key-combo to use. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,ses
[Touch-packages] [Bug 1381930] Re: 7digital previews do not play in the scope
After initial testing, it looks like something like this needs to get used: url.setPath(path,QUrl::DecodedMode); As the default mode, QUrl::TolerantMode as well as QUrl::StrictMode result in the '%3D' getting mangled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: New Status in “unity8” package in Ubuntu RTM: New Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 762349] Re: Difficult to distinguish which tab is selected
I would also like to see this issue fixed. It's not just gnome-terminal: some other applications with tabs, such as gedit, have thte same issue. I only noticed it in gnome-terminal because I use it all the time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/762349 Title: Difficult to distinguish which tab is selected Status in Ayatana Design: New Status in Themes for Ubuntu: Confirmed Status in “ubuntu-themes” package in Ubuntu: Confirmed Bug description: Binary package hint: unity In tabbed interfaces such as in gnome-terminal under unity it is difficult to visually distinguish the selected tab from the unselected ones. In the attached screenshot, gnome-terminal has three tabs open, and the third one is selected. If you look close you can see the text is slightly whiter than the other tabs, and the border is a little more prominent but to my old man eyes it's really hard to see it at a glance. Under metacity, the difference is more notable (or at least, the theme is different). My guess is this is a theme issue rather than unity, but I'm unsure. If it is just a theme issue please refile to the right project. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.8-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell] Date: Fri Apr 15 17:41:12 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to natty on 2011-04-04 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/762349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386456] [NEW] fglrx
Public bug reported: I am unable to select the fglrx or fglrx-updates package under additional drivers. The output from software-properties-gtk --debug is: Warning: install transaction not completed successfully: Transaction failed: Package dependencies cannot be resolved The following packages have unmet dependencies: fglrx: Depends: libqtcore4 (>= 4:4.8.4) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: xorg-video-abi-18 but it is a virtual package Warning: install transaction not completed successfully: Transaction failed: Package dependencies cannot be resolved The following packages have unmet dependencies: fglrx-updates: Depends: libqtcore4 (>= 4:4.8.4) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: xorg-video-abi-18 but it is a virtual package ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.94 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 28 01:19:41 2014 InstallationDate: Installed on 2014-03-10 (231 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to utopic on 2014-09-17 (40 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1386456 Title: fglrx Status in “software-properties” package in Ubuntu: New Bug description: I am unable to select the fglrx or fglrx-updates package under additional drivers. The output from software-properties-gtk --debug is: Warning: install transaction not completed successfully: Transaction failed: Package dependencies cannot be resolved The following packages have unmet dependencies: fglrx: Depends: libqtcore4 (>= 4:4.8.4) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: xorg-video-abi-18 but it is a virtual package Warning: install transaction not completed successfully: Transaction failed: Package dependencies cannot be resolved The following packages have unmet dependencies: fglrx-updates: Depends: libqtcore4 (>= 4:4.8.4) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: xorg-video-abi-18 but it is a virtual package ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.94 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 28 01:19:41 2014 InstallationDate: Installed on 2014-03-10 (231 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to utopic on 2014-09-17 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1386456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346633] Re: [enhancement] Autopilot testing needs to know screen coordinates of widgets on screen
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.9.0 ** Changed in: mir Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1346633 Title: [enhancement] Autopilot testing needs to know screen coordinates of widgets on screen Status in Autopilot: Won't Fix Status in Mir: Fix Committed Status in Qt integration with the Mir display server: Confirmed Status in “qtubuntu” package in Ubuntu: Fix Released Bug description: On phablet devices, Autopilot needs to determine the absolute coordinates of any item on screen, in order to generate input events to interact with those items. Most toolkits give AP the ability to calculate the coordinates of an item inside the surface, i.e. relative to the surface top-left corner, and then obtain the position of the window from the display server (X11 usually) to calculate the absolute position. However Mir does not have an API to let its clients find the surface position relative to the screen. There is also a desire from the Mir team not to supply this information. We need to discuss how to solve this problem in a way everyone is happy To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/1346633/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386427] Re: No background in gnome monitor
** Summary changed: - Task manager background transparent + No background in gnome monitor ** Description changed: - The Task Manager in the "resources" tab background is transparent - sometimes. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 27 19:21:07 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Elitegroup Computer Systems Device [1019:9981] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Elitegroup Computer Systems Device [1019:9981] InstallationDate: Installed on 2014-10-27 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141027) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=db0533ed-5554-4b73-890c-a4dda2110bd5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2011 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04.00.DEX dmi.board.name: MB40II dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04.00.DEX:bd08/11/2011:svn:pnMB40II:pvrNotApplicable:rvn:rnMB40II:rvrNotApplicable:cvn:ct9:cvrN/A: dmi.product.name: MB40II dmi.product.version: Not Applicable version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Oct 27 18:27:03 2014 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id1402 - vendor IVO + product id1402 + vendor IVO xserver.version: 2:1.16.1-1ubuntu1 ** Package changed: xorg (Ubuntu) => gnome-system-monitor -- 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/1386427 Title: No background in gnome monitor Status in The GNOME System Monitor: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 27 19:21:07 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Device [1019:9981] InstallationDate: Installed on 2014-10-27 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141027) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=db0533ed-5554-4b73-890c-a4dda2110bd5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2011 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04.00.DEX dmi.board.name: MB40II dmi.board.version: Not Applica
[Touch-packages] [Bug 1386437] [NEW] key `+space without function; ö,ä and ü in some programs
Public bug reported: after installing `language-pack-de` and `language-pack-gnome-de` and setting keyboard layout to `German` the key `+Space is dead (I have to insert ` by pasting). The keys `ö`, `ä` and `ü` work in some programs (e.g. `firefox`), but not in others (e.g. `gedit`). I installed all recommended packages for language support for german as suggested by `Language Support`. `German` is the only language and locale set up and the only keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 21:50:56 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Description changed: after installing `language-pack-de` and `language-pack-gnome-de` and setting keyboard layout to `German` the key `+Space is dead (I have to insert ` by pasting). The keys `ö`, `ä` and `ü` work in some programs (e.g. `firefox`), but - not in others (e.g. `gedit`). + not in others (e.g. `gedit`). I installed all recommended packages for + language support for german as suggested by `Language Support`. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 21:50:56 2014 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: after installing `language-pack-de` and `language-pack-gnome-de` and setting keyboard layout to `German` the key `+Space is dead (I have to insert ` by pasting). The keys `ö`, `ä` and `ü` work in some programs (e.g. `firefox`), but not in others (e.g. `gedit`). I installed all recommended packages for - language support for german as suggested by `Language Support`. + language support for german as suggested by `Language Support`. `German` + is the only language and locale set up and the only keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 21:50:56 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1386437 Title: key `+space without function; ö,ä and ü in some programs Status in “ibus” package in Ubuntu: New Bug description: after installing `language-pack-de` and `language-pack-gnome-de` and setting keyboard layout to `German` the key `+Space is dead (I have to insert ` by pasting). The keys `ö`, `ä` and `ü` work in some programs (e.g. `firefox`), but not in others (e.g. `gedit`). I installed all recommended packages for language support for german as suggested by `Language Support`. `German` is the only language and locale set up and the only keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 21:50:56 2014 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash 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/1386437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386427] [NEW] Task manager background transparent
Public bug reported: The Task Manager in the "resources" tab background is transparent sometimes. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 27 19:21:07 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Device [1019:9981] InstallationDate: Installed on 2014-10-27 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141027) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=db0533ed-5554-4b73-890c-a4dda2110bd5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2011 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04.00.DEX dmi.board.name: MB40II dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.04.00.DEX:bd08/11/2011:svn:pnMB40II:pvrNotApplicable:rvn:rnMB40II:rvrNotApplicable:cvn:ct9:cvrN/A: dmi.product.name: MB40II dmi.product.version: Not Applicable version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.1-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Oct 27 18:27:03 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1402 vendor IVO xserver.version: 2:1.16.1-1ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption third-party-packages ubuntu vivid ** Attachment added: "Captura de tela de 2014-10-27 19:22:53.png" https://bugs.launchpad.net/bugs/1386427/+attachment/4246566/+files/Captura%20de%20tela%20de%202014-10-27%2019%3A22%3A53.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/1386427 Title: Task manager background transparent Status in “xorg” package in Ubuntu: New Bug description: The Task Manager in the "resources" tab background is transparent sometimes. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Oct 27 19:21:07 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Device [1019:9981] InstallationDate: Installed on 2014-10-27 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141027) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=db0533ed-5554-4b73-890c-a4dda2110bd5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2011 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.04.00.DEX dmi.board.name: MB40II dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.version
[Touch-packages] [Bug 1386423] [NEW] [K55VD, Realtek ALC270, Black Headphone Out, Right] No sound at all
Public bug reported: It started to fail suddenly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jose 2580 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 27 16:46:39 2014 InstallationDate: Installed on 2014-08-06 (82 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 successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jose 2580 F pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [K55VD, Realtek ALC270, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.404 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VD.404:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** 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/1386423 Title: [K55VD, Realtek ALC270, Black Headphone Out, Right] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: It started to fail suddenly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jose 2580 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 27 16:46:39 2014 InstallationDate: Installed on 2014-08-06 (82 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 successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jose 2580 F pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [K55VD, Realtek ALC270, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.404 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VD.404:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1386423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313446] Re: window disappears on toggle shade
Hi all, (Checking back a month later.) Is there any way to get someone's attention regarding this bug? It is a very bad regression in the window shading feature for those of us who are heavily used to it. Thanks, Paarvai -- 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/1313446 Title: window disappears on toggle shade Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I used Unity Tweak Tool to enable Toggle Shade using middle click. When I click to top of the window, it rolls up and disappears. A "ghost" outline of the window appears and the only way to get the window back is by using Alt-tab. Sometimes, when reselecting the window using Alt-tab, Ubuntu freezes (crashes) and an internal error is generated. It seems to be related to Compiz but I'm not sure. An error report was generated and sent. Description: Ubuntu 14.04 LTS (64-bit) Release: 14.04 unity-tweak-tool 0.0.6ubuntu1 I expected the window would "roll up" and I'd be left with the window's top bar like with previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386415] [NEW] ubuntu 14.04 booting into tty1 - stuck there
Public bug reported: When booting into rescue mode, everything works excellent. If I try to boot into "normal" ubuntu, I am stuck in tty1. Nothing works here, and I have to make a brutal restart of the PC. I have of course tryed all combinations like ctrl+alt+Fx etc. No way to eacape except for the brutal restart. So far I have not found any usefull tricks on the web, and by now I think i have tried everything. What happened to the kernel or the upstart procedure from 13.10 to 14.04? As far as I can se, I am not alone with this problem. Regards Erling ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 27 21:48:46 2014 DistUpgraded: 2014-10-05 19:20:42,005 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 200 Series] [1002:130f] (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Device [1019:9a18] InstallationDate: Installed on 2014-03-02 (239 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MachineType: MEDION D3F3-EM ProcEnviron: LANGUAGE=da PATH=(custom, no user) LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=9a6bd4cf-a1bf-4415-9ba2-486240285264 rw recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-10-05 (22 days ago) dmi.bios.date: 05/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: D3EMW08.103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D3F3-EM dmi.board.vendor: MEDION dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.103:bd05/14/2014:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr: dmi.product.name: D3F3-EM dmi.product.version: 1.0 dmi.sys.vendor: MEDION version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Oct 27 21:37:53 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- 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/1386415 Title: ubuntu 14.04 booting into tty1 - stuck there Status in “xorg” package in Ubuntu: New Bug description: When booting into rescue mode, everything works excellent. If I try to boot into "normal" ubuntu, I am stuck in tty1. Nothing works here, and I have to make a brutal restart of the PC. I have of course tryed all combinations like ctrl+alt+Fx etc. No way to eacape except for the brutal restart. So far I have not found any usefull tricks on the web, and by now I think i have tried everything. What happened to the kernel or the upstart procedure from 13.10 to 14.04? As far as I can se, I am not alone with this problem. Regards Erling ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 27 21:48:46 2014 DistUpgraded: 2014-10-05 19:20:42,005 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 200 Series] [1002:130f] (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Device [1019:9a18] InstallationDat
[Touch-packages] [Bug 1385010] Re: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink
Thanks @jdthood ! I figured there could be some arcane reason why the symlink check would be there on Ubuntu but not Debian, but I couldn't fathom why after reading through the entire hook. Also, thanks for cleaning up the report! :D -- 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/1385010 Title: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink Status in “resolvconf” package in Ubuntu: New Bug description: The resolvconf package comes with /etc/dhcp/dhclient-enter- hooks.d/resolvconf which, if /sbin/resolvconf is present, redefines the make_resolv_conf function (previously defined by dhclient-script) to send nameserver information to resolvconf instead of writing it directly to /etc/resolv.conf. However, the hook also checks if /etc/resolv.conf is a symlink. This is problematic because if /etc/resolv.conf is not a symlink then the script does not redefine make_resolv_conf() and so dhclient will overwrite /etc/resolv.conf when it configures an interface, even though the resolvconf package is installed. The behavior I would expect would be /etc/resolv.conf never changing if resolvconf is installed and /etc/resolv.conf is not a symlink. Debian implements the behavior I would expect. At the very least, I think that the different behavior in Ubuntu should be documented in the man pages for resolvconf. As far as I can tell, there's no reason to check for /etc/resolv.conf being a symlink when resolvconf itself already does that. The patch was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp /dhclient-enter-hooks.d/resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1385010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385010] Re: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink
** Description changed: The resolvconf package comes with /etc/dhcp/dhclient-enter- - hooks.d/resolvconf which, if /sbin/resolvconf is present, undefines - make_resolv_conf() (previously defined by dhclient-script) and calls - resolvconf. + hooks.d/resolvconf which, if /sbin/resolvconf is present, redefines the + make_resolv_conf function (previously defined by dhclient-script) to + send nameserver information to resolvconf instead of writing it directly + to /etc/resolv.conf. - However, the hook checks if /etc/resolv.conf is a symlink even though - /sbin/resolvconf already handles this. + However, the hook also checks if /etc/resolv.conf is a symlink. This is + problematic because if /etc/resolv.conf is not a symlink then the script + does not redefine make_resolv_conf() and so dhclient will overwrite + /etc/resolv.conf when it configures an interface, even though the + resolvconf package is installed. - This is problematic because it never undefines the make_resolv_conf - function which dhclient-script defines itself. + The behavior I would expect would be /etc/resolv.conf never changing if + resolvconf is installed and /etc/resolv.conf is not a symlink. - For me, the expected behavior would be /etc/resolv.conf never changing - if resolvconf is installed and /etc/resolv.conf is not a symlink. + Debian implements the behavior I would expect. - At the very least, I think this behavior should be documented in the man - pages for resolvconf. Furthermore, debian does not implement this patch - and it exists starting in 12.04 until current. + At the very least, I think that the different behavior in Ubuntu should + be documented in the man pages for resolvconf. - As far as I can tell, there's absolutely no reason to check it twice if - resolvconf already implements it. + As far as I can tell, there's no reason to check for /etc/resolv.conf + being a symlink when resolvconf itself already does that. - It was introduced by: http://bazaar.launchpad.net/~ubuntu- + The patch was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp/dhclient- enter-hooks.d/resolvconf -- 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/1385010 Title: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink Status in “resolvconf” package in Ubuntu: New Bug description: The resolvconf package comes with /etc/dhcp/dhclient-enter- hooks.d/resolvconf which, if /sbin/resolvconf is present, redefines the make_resolv_conf function (previously defined by dhclient-script) to send nameserver information to resolvconf instead of writing it directly to /etc/resolv.conf. However, the hook also checks if /etc/resolv.conf is a symlink. This is problematic because if /etc/resolv.conf is not a symlink then the script does not redefine make_resolv_conf() and so dhclient will overwrite /etc/resolv.conf when it configures an interface, even though the resolvconf package is installed. The behavior I would expect would be /etc/resolv.conf never changing if resolvconf is installed and /etc/resolv.conf is not a symlink. Debian implements the behavior I would expect. At the very least, I think that the different behavior in Ubuntu should be documented in the man pages for resolvconf. As far as I can tell, there's no reason to check for /etc/resolv.conf being a symlink when resolvconf itself already does that. The patch was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp /dhclient-enter-hooks.d/resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1385010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386387] [NEW] Rhythmbox no reproduce sonido de música. Tampoco puede actualizar complementos
Public bug reported: Rhythmbox no reproduce sonido de música seleccionado. Cuando intento reproducir sonido, solicita descargar actualizaciones, pero al intentar actualizar, avisa un mensaje de que no se puede descargar complemento. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgstreamer1.0-0 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 16:09:19 2014 InstallationDate: Installed on 2014-01-16 (283 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to trusty on 2014-10-23 (3 days ago) ** 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/1386387 Title: Rhythmbox no reproduce sonido de música. Tampoco puede actualizar complementos Status in “gstreamer1.0” package in Ubuntu: New Bug description: Rhythmbox no reproduce sonido de música seleccionado. Cuando intento reproducir sonido, solicita descargar actualizaciones, pero al intentar actualizar, avisa un mensaje de que no se puede descargar complemento. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgstreamer1.0-0 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 16:09:19 2014 InstallationDate: Installed on 2014-01-16 (283 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to trusty on 2014-10-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1386387/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385010] Re: unexpected behavior: make_resolv_conf not undefined
You are right. In the Debian version, the script is activated by "test -x /sbin/resolvconf" where the presence of /sbin/resolvconf indicates that the resolvconf package is installed. The convention in Debian is: "If the resolvconf package is installed then disable your default resolv .conf-updating behaviors and instead send the information to /sbin/resolvconf". In Debian the convention is furthermore that other packages should NOT check whether or not /etc/resolv.conf is a symlink and do things to /etc/resolv.conf if it isn't a symlink. In Debian, installing resolvconf and deleting the symlink at /etc/resolv.conf is a way of configuring the system such that the file is not updated by anything. Unlike Debian, Ubuntu includes resolvconf in the base install. Furthermore Ubuntu has been afflicted by mysterious bug #1000244 which is the problem that in rare cases /etc/resolv.conf fails to be a symlink after resolvconf is installed. So perhaps there was a pragmatic reason for Ubuntu to make a change whose effect is to restore dhclient's default behavior when /etc/resolv.conf is not a symlink. Nevertheless, as the Debian maintainer of resolvconf, I agree with you. :) ** Summary changed: - unexpected behavior: make_resolv_conf not undefined + Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink -- 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/1385010 Title: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink Status in “resolvconf” package in Ubuntu: New Bug description: The resolvconf package comes with /etc/dhcp/dhclient-enter- hooks.d/resolvconf which, if /sbin/resolvconf is present, undefines make_resolv_conf() (previously defined by dhclient-script) and calls resolvconf. However, the hook checks if /etc/resolv.conf is a symlink even though /sbin/resolvconf already handles this. This is problematic because it never undefines the make_resolv_conf function which dhclient-script defines itself. For me, the expected behavior would be /etc/resolv.conf never changing if resolvconf is installed and /etc/resolv.conf is not a symlink. At the very least, I think this behavior should be documented in the man pages for resolvconf. Furthermore, debian does not implement this patch and it exists starting in 12.04 until current. As far as I can tell, there's absolutely no reason to check it twice if resolvconf already implements it. It was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp /dhclient-enter-hooks.d/resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1385010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386017] Re: vivid synaptic settings repositories crashed
jerrylamos, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386017/comments/4 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Package changed: linux (Ubuntu) => software-properties (Ubuntu) ** Changed in: software-properties (Ubuntu) Importance: Medium => Undecided ** Changed in: software-properties (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1386017 Title: vivid synaptic settings repositories crashed Status in “software-properties” package in Ubuntu: Invalid Bug description: Looks to me like the same failure I get with sudo software-properties-gtk How do I add Ubuntu Partners to Repositories? How do I change Update frequency from daily to never, I update frequently anyway when I want to, and don't want Update to come blasting in to what I'm doing with a deadly partial update. Thanks much ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 [modified: boot/vmlinuz-3.16.0-23-generic] ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 26 21:06:59 2014 InstallationDate: Installed on 2014-10-27 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141026) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=81fa31d4-972b-409f-9b0b-d34528ec9238 ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1386017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386380] [NEW] network-manager-openvpn leaks w/ IPv6
Public bug reported: To verify: 1. Connect to a Wifi network that assigns IPv6 addresses. 2. Open http://whatsmyipv6.org/ note down the address. 3. Connect to a VPN. 4. Open http://whatsmyipv6.org/ and compare with the result from step 2. Temporary fix: Set the "Method" dropdown under "IPv6 Settings" in your Wifi connection to "Ignore". I consider this a security bug since it endangers users relying on a working/leak-free VPN. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: ipv6 leak vpn ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags added: ipv6 leak vpn ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1386380 Title: network-manager-openvpn leaks w/ IPv6 Status in “network-manager” package in Ubuntu: New Status in “network-manager-openvpn” package in Ubuntu: New Bug description: To verify: 1. Connect to a Wifi network that assigns IPv6 addresses. 2. Open http://whatsmyipv6.org/ note down the address. 3. Connect to a VPN. 4. Open http://whatsmyipv6.org/ and compare with the result from step 2. Temporary fix: Set the "Method" dropdown under "IPv6 Settings" in your Wifi connection to "Ignore". I consider this a security bug since it endangers users relying on a working/leak-free VPN. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1386380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 640328] Re: Input device is not saved
*** This bug is a duplicate of bug 443306 *** https://bugs.launchpad.net/bugs/443306 ** This bug has been marked a duplicate of bug 443306 everytime i boot i have to select mic as my input device -- 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/640328 Title: Input device is not saved Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio Symptoms: In Sound Preferences -> Input I see "Internal Audio Analog Stereo" and "QuickCam Pro 5000 Analog Mono". Only the QuickCam captures input from an actual microphone, so I would like to use it, and it only. However, every time I reboot Pulseaudio somehow decides to use the "Internal Audio Analog Stereo" instead of my selected default. How to reproduce: 1. Select "QuickCam Pro 5000 Analog Mono" as the device for sound input in the Sound Preferences window. 2. Reboot and log in again What happens: "Internal Audio Analog Stereo" is selected as the Pulseaudio sound input device. What should happen: "QuickCam Pro 5000 Analog Mono" should still be selected as the Pulseaudio sound input device. 100% reproducible. Possible cause: Could it be that Pulseaudio starts before the webcam is initialized, so it shifts to "Internal Audio Analog Stereo" as a fallback on startup? Workaround: Select "QuickCam Pro 5000 Analog Mono" as the device for sound input in the Sound Preferences window after every reboot. Simple fix: Some way to disable the selection of individual devices, so they will not be used. Good fix: Save the selected device, and select that if it ever becomes available during a GNOME session. Better fix: Mix all input sources, and allow the user to disable those they don't want to capture from. Additional tweak: Monitor all input devices, and if there is a "better" input source, suggest to the user to change to it. "Better" could for example mean that it captures more input of a moderate level, such as 5-95%. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vengmark 1879 F pulseaudio /dev/snd/pcmC0D0p: vengmark 1879 F...m pulseaudio /dev/snd/controlC1: vengmark 1879 F pulseaudio /dev/snd/pcmC1D0c: vengmark 1879 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 22' Mixer name : 'Analog Devices AD1988B' Components : 'HDA:11d4198b,1043829b,00100300' Controls : 49 Simple ctrls : 27 Card1.Amixer.info: Card hw:1 'U0x46d0x8ce'/'USB Device 0x46d:0x8ce at usb-:00:1d.7-2, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:08ce' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 3072 Mono: Capture 3072 [100%] [30.00dB] [on] Date: Thu Sep 16 11:07:20 2010 ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: pulseaudio dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1305 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-E 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.:bvr1305:bd06/19/2009:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K-E 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/640328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386017] [NEW] vivid synaptic settings repositories crashed
You have been subscribed to a public bug: Looks to me like the same failure I get with sudo software-properties-gtk How do I add Ubuntu Partners to Repositories? How do I change Update frequency from daily to never, I update frequently anyway when I want to, and don't want Update to come blasting in to what I'm doing with a deadly partial update. Thanks much ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 [modified: boot/vmlinuz-3.16.0-23-generic] ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 26 21:06:59 2014 InstallationDate: Installed on 2014-10-27 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141026) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=81fa31d4-972b-409f-9b0b-d34528ec9238 ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO ** Affects: software-properties (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug vivid -- vivid synaptic settings repositories crashed https://bugs.launchpad.net/bugs/1386017 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties 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 1162408] Re: little horizontal black lines sporadically appear
Jacek, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal: ubuntu-bug xorg Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. For more on this, please see the official Ubuntu documentation: Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Please note, not filing a new report will delay your problem being addressed as quickly as possible. As well, please do not announce in this report you created a new bug report. Thank you for your understanding. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1162408 Title: little horizontal black lines sporadically appear Status in “xorg” package in Ubuntu: Incomplete Bug description: Some little horizontal black lines sometimes appear on the Ubuntu desktop. They disappear quickly, and there seems no obvious way to force the event to occur predictably. The problem occurs with libgl1-mesa-dri-experimental but, unless I'm mistaken, occurred also with the nonexperimental branch. Furthermore, I'm running Ubuntu Classic and was not using 3d effects when the problem occurred (was simply typing text in LibreOffice). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.25-lowlatency 3.5.7.4 Uname: Linux 3.5.0-25-lowlatency i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sun Mar 31 06:55:41 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-25-lowlatency, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-26-generic, i686: installed virtualbox, 4.1.18, 3.5.0-25-lowlatency, i686: installed virtualbox, 4.1.18, 3.5.0-26-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (9 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0JF77M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd12/10/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0JF77M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.libdrm2: libdrm2 2.4.43+git1303291653.ca678b~gd~q version.libgl1-mesa-dri: libgl1-mesa-dri 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-glx: libgl1-mesa-glx 9.2~git1303291656.5f41e0~gd~q version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0+git1303291654.6e74aa~gd~q version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5+git1303291654.431816~gd~q version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7+git1303271126.677142~gd~q --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-11-19 15:54:14,165 DEBUG enabling apt cron job DistroCodename: saucy Distro
[Touch-packages] [Bug 1385010] Re: unexpected behavior: make_resolv_conf not undefined
** Description changed: The resolvconf package comes with /etc/dhcp/dhclient-enter- - hooks.d/resolvconf which convieniently undefines make_resolve_conf - (previously defined by dhclient-script) and calls resolvconf. + hooks.d/resolvconf which, if /sbin/resolvconf is present, undefines + make_resolv_conf() (previously defined by dhclient-script) and calls + resolvconf. However, the hook checks if /etc/resolv.conf is a symlink even though /sbin/resolvconf already handles this. This is problematic because it never undefines the make_resolv_conf function which dhclient-script defines itself. - For me, the expect behavior would be /etc/resolv.conf never changing if - resolvconf is installed and the file is not a symlink. + For me, the expected behavior would be /etc/resolv.conf never changing + if resolvconf is installed and /etc/resolv.conf is not a symlink. At the very least, I think this behavior should be documented in the man pages for resolvconf. Furthermore, debian does not implement this patch and it exists starting in 12.04 until current. As far as I can tell, there's absolutely no reason to check it twice if resolvconf already implements it. It was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp/dhclient- enter-hooks.d/resolvconf -- 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/1385010 Title: unexpected behavior: make_resolv_conf not undefined Status in “resolvconf” package in Ubuntu: New Bug description: The resolvconf package comes with /etc/dhcp/dhclient-enter- hooks.d/resolvconf which, if /sbin/resolvconf is present, undefines make_resolv_conf() (previously defined by dhclient-script) and calls resolvconf. However, the hook checks if /etc/resolv.conf is a symlink even though /sbin/resolvconf already handles this. This is problematic because it never undefines the make_resolv_conf function which dhclient-script defines itself. For me, the expected behavior would be /etc/resolv.conf never changing if resolvconf is installed and /etc/resolv.conf is not a symlink. At the very least, I think this behavior should be documented in the man pages for resolvconf. Furthermore, debian does not implement this patch and it exists starting in 12.04 until current. As far as I can tell, there's absolutely no reason to check it twice if resolvconf already implements it. It was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp /dhclient-enter-hooks.d/resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1385010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311724] Re: Macbook Air resumes immidiately after suspend
This seems to work all the time when the computer is unplugged... when plugged in, it seems to work most of the time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1311724 Title: Macbook Air resumes immidiately after suspend Status in “pm-utils” package in Ubuntu: Confirmed Bug description: Computer model : Apple Macbook Air 6,2 (Mid 2013) BIOS version : MBA61.88Z.0099.B04 (dmidecode -s bios-version), Oct. 2013 version OS installed : Ubuntu 14.04, single boot Problem description: When closing lid on computer machine suspends. Within 8 to 10 seconds the machine resumes again with lid still closed. Imidiately opening an closing lid makes suspends the computer and it keeps suspended until lid is opened again. This behaviour is the same when entering a sudo pm-suspend from the terminal. Machine suspends. But resumes after 8 to 10 seconds. Immidiately doing a second sudo pm-suspend, suspends the machine and keeps it suspended. There is one case where the behaviour described above is different. That is in the situation where machine is put into suspend for the first time after a complete reboot. In this case the machine suspends correctly and stays suspended as expected. The problem is consistent and can be reproduced as desribed any number of times. Disabling wi-fi (using the Broadcom 802.11 Linux STA proprietary driver) doesn't alter the behaviour described above. cat /proc/acpi/wakeup DeviceS-state Status Sysfs node P0P2S3*disabled EC S3*disabled HDEFS3*disabled pci::00:1b.0 RP01S3*disabled pci::00:1c.0 RP02S3*disabled pci::00:1c.1 RP03S3*disabled pci::00:1c.2 ARPTS4*disabled pci::03:00.0 RP05S3*disabled pci::00:1c.4 RP06S3*disabled pci::00:1c.5 SPITS3*disabled XHC1S3*enabled pci::00:14.0 ADP1S3*disabled platform:ACPI0003:00 LID0S3*enabled ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 17:03:05 2014 InstallationDate: Installed on 2014-04-23 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1311724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386361] [NEW] network-manager-openvpn leaks while connecting
Public bug reported: Network-manager-openvpn leaks while connecting. Maybe that is intended behavior when activating a VPN-connection manually but it also leaks when "Automatically connect to VPN when using this connection" is checked. Verfied the following way: 1. Set up a VPN that connects via UDP (verify it). 2. Configure a Wifi network that blocks UDP, check "Automatically connect to VPN..." and preselect your special VPN. 3. Connect to that newly configured Wifi network. 4. Browse the internet. Another way: 1. Type "traceroute ubuntu.com" into a terminal but don't press enter. 2. Start the Wifi network that uses the "Automatically connect... VPN..." feature. 3. Go back to the terminal press enter. 4. After the VPN has connected repeat the command. 5. Compare the first hop of the traceroute results. I consider this a security bug since it endangers users relying on a working/leak-free VPN. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: leak vpn ** Information type changed from Private Security to Public ** Also affects: network-manager-openvpn (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/1386361 Title: network-manager-openvpn leaks while connecting Status in “network-manager” package in Ubuntu: New Status in “network-manager-openvpn” package in Ubuntu: New Bug description: Network-manager-openvpn leaks while connecting. Maybe that is intended behavior when activating a VPN-connection manually but it also leaks when "Automatically connect to VPN when using this connection" is checked. Verfied the following way: 1. Set up a VPN that connects via UDP (verify it). 2. Configure a Wifi network that blocks UDP, check "Automatically connect to VPN..." and preselect your special VPN. 3. Connect to that newly configured Wifi network. 4. Browse the internet. Another way: 1. Type "traceroute ubuntu.com" into a terminal but don't press enter. 2. Start the Wifi network that uses the "Automatically connect... VPN..." feature. 3. Go back to the terminal press enter. 4. After the VPN has connected repeat the command. 5. Compare the first hop of the traceroute results. I consider this a security bug since it endangers users relying on a working/leak-free VPN. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1386361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386354] Re: package click 0.4.21.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1386354 Title: package click 0.4.21.1 failed to install/upgrade: subprocess new pre- removal script returned error exit status 1 Status in “click” package in Ubuntu: New Bug description: While upgrading to 14.10 this continually triggers warnings I only partially understand. Now all menu-bars and side-bars are missing, though icons remain. I have booted using several kernel via GRUB menu in an attempt to avoid the problem. Also tried to install via 'sudo apt-get click --upgrade' Error message is "cannot import name 'commands'" NVIDIA proprietary driver install happened in here somewhere... 343.22 and 340.?? were tried. This restored desktop without menu bars or side-bar - the current situation. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: click 0.4.21.1 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Mon Oct 27 12:49:59 2014 DuplicateSignature: package:click:0.4.21.1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-03-31 (209 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: click Title: package click 0.4.21.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1386354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
Sticking it the parser.conf also counts as overriding because the set of flags used during compile are currently not stored (basically anything different than the default binary behavior is treated as different). The proper long term fix is to store this information off so that the parser can detect compile option changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1385947 Title: specifying -O to parser causes the parser to not consider cache files Status in AppArmor Linux application security framework: Confirmed Status in “apparmor” package in Ubuntu: Confirmed Status in “apparmor” package in Ubuntu RTM: Confirmed Bug description: If the cache files are up to date and I specify: /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -- profile1 profile2 ... then the cache files in /var/cache/apparmor are used (good). However, if the cache files are up to date and I specify: /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -O no-expr-simplify -- profile1 profile2 ... then the cache files in /var/cache/apparmor are all regenerated (not good). This needs to be fixed in order to use '-O no-expr-simplify' to fix bug #1383858. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1385947/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386359] [NEW] [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all
Public bug reported: When I select a music file or a video file, no sound comes from the speakers, although when I checked the speakers, it worked fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vientozur 1794 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 27 14:48:38 2014 InstallationDate: Installed on 2014-01-16 (283 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Audio Interno - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vientozur 1794 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-10-23 (3 days ago) dmi.bios.date: 03/26/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd03/26/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXV2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1386359 Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: When I select a music file or a video file, no sound comes from the speakers, although when I checked the speakers, it worked fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vientozur 1794 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 27 14:48:38 2014 InstallationDate: Installed on 2014-01-16 (283 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Audio Interno - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vientozur 1794 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-10-23 (3 days ago) dmi.bios.date: 03/26/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd03/26/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXV2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1386359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386354] [NEW] package click 0.4.21.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: While upgrading to 14.10 this continually triggers warnings I only partially understand. Now all menu-bars and side-bars are missing, though icons remain. I have booted using several kernel via GRUB menu in an attempt to avoid the problem. Also tried to install via 'sudo apt-get click --upgrade' Error message is "cannot import name 'commands'" NVIDIA proprietary driver install happened in here somewhere... 343.22 and 340.?? were tried. This restored desktop without menu bars or side- bar - the current situation. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: click 0.4.21.1 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Mon Oct 27 12:49:59 2014 DuplicateSignature: package:click:0.4.21.1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-03-31 (209 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: click Title: package click 0.4.21.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1386354 Title: package click 0.4.21.1 failed to install/upgrade: subprocess new pre- removal script returned error exit status 1 Status in “click” package in Ubuntu: New Bug description: While upgrading to 14.10 this continually triggers warnings I only partially understand. Now all menu-bars and side-bars are missing, though icons remain. I have booted using several kernel via GRUB menu in an attempt to avoid the problem. Also tried to install via 'sudo apt-get click --upgrade' Error message is "cannot import name 'commands'" NVIDIA proprietary driver install happened in here somewhere... 343.22 and 340.?? were tried. This restored desktop without menu bars or side-bar - the current situation. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: click 0.4.21.1 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Mon Oct 27 12:49:59 2014 DuplicateSignature: package:click:0.4.21.1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-03-31 (209 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: click Title: package click 0.4.21.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1386354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385572] Re: gnome-session not shutting down cleanly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1385572 Title: gnome-session not shutting down cleanly Status in Ubuntu GNOME: New Status in “upstart” package in Ubuntu: Confirmed Bug description: We have had reports going back to 13.10 that gnome-shell extensions are disabled after restart (LP: #1236749), I've only just managed to reproduce this and have discovered that gnome-session is not shutting down cleanly. Basically, X gets shutdown, which causes gnome-shell to abort, following this gnome-session tries to respawn gnome-shell which fails and due to this failure disables all shell extensions. I don't know enough about upstart to really understand what is going on but it appears this also affects unity and it just hasnt been noticed since there are probably no such side-effects happening there. Filing this against upstart since this is not reproducible when using systemd init, though it may well be a bug in gnome-session, but related to upstart user sessions. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 25 14:05:24 2014 InstallationDate: Installed on 2012-09-23 (762 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1385572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386351] [NEW] спасибо
Public bug reported: спасибо ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-lowlatency 3.13.11.7 Uname: Linux 3.13.0-37-lowlatency x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 27 21:07:05 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.117, 3.13.0-24-lowlatency, x86_64: installed nvidia-304, 304.117, 3.13.0-37-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) Subsystem: LeadTek Research Inc. Device [107d:2089] InstallationDate: Installed on 2014-10-26 (1 days ago) InstallationMedia: Ubuntu-Studio 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.3) LightdmGreeterLog: ** (lightdm-gtk-greeter:1353): WARNING **: Failed to load user image: Не удалось открыть файл «/home/fabirge/.face»: Нет такого файла или каталога LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1520): WARNING **: Failed to load user image: Не удалось открыть файл «/home/fabirge/.face»: Нет такого файла или каталога MachineType: Hewlett-Packard p6633ru ProcEnviron: LANGUAGE=ru PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-lowlatency root=UUID=a9f82e81-1af8-486d-bbf7-ca0da5cd3f0b ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.12 dmi.board.name: 2A9C dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: CZC0402M06 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.12:bd07/12/2010:svnHewlett-Packard:pnp6633ru:pvrxxx0204GR0:rvnMSI:rn2A9C:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6633ru dmi.product.version: xxx0204GR0 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Oct 27 16:35:55 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- 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/1386351 Title: спасибо Status in “xorg” package in Ubuntu: New Bug description: спасибо ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-lowlatency 3.13.11.7 Uname: Linux 3.13.0-37-lowlatency x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 27 21:07:05 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.117, 3.13.0-24-lowlatency, x86_64: installed nvidia-304, 304.117, 3.13.0-37-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (
[Touch-packages] [Bug 305546] Re: Nautilus crashing/freezing when opening folder with svg file
This bug is back -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/305546 Title: Nautilus crashing/freezing when opening folder with svg file Status in libRSVG - SVG Rendering Library: Invalid Status in “librsvg” package in Ubuntu: Fix Released Status in Debian GNU/Linux: Invalid Bug description: Strange thing started happening a few days ago: When I access nautilus from the Places menu and open my home directory (named eric) nautilus always freezes. I can open subdirectories and other bookmarks such as Documents, Pictures, etc and browse files, but the second I browse to my main home directory, nautilus freezes. I can click any icons for sub- folders in my home folder, but nautilus will hang and, within a few seconds, turn grey and stay that way. The only way to get nautilus to close is by forcing a quit. I can access any of the files and folders by CLI, or by using emelFM2. After much searching, I found an old bug report at: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/30010 . . . which seemed to blame the crashiness on folders containing an svg image. Interestingly enough, I was messing around in Inkscape the other day trying to create a business card and saved my work into my home folder as an svg. As soon as I deleted or moved that file Nautilus no longer crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/305546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Sorry, one more thing... I think the correct matepackage is ubuntu- gnome-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Here's an article with screenshots of how to actually find the icon that lets you choose your "shell": http://www.howtogeek.com/112620/how-to-install-use-gnome-shell-on-ubuntu/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270245] Re: Backward frame jumps on mali (Nexus 10 & krillin)
I've was also able to reproduce the frame jump issue today, so my theories in comment #32 don't have a bearing on the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1270245 Title: Backward frame jumps on mali (Nexus 10 & krillin) Status in Mir: Confirmed Status in “mir” package in Ubuntu: Confirmed Bug description: Alexandros, Andreas, and I have noted at different points that we see frame skips on the nexus 10. The frames look like they move in a 1,3,2 pattern, particularly when unlocking the device. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1270245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381041] Re: Network indicator is sometimes blank
approved https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-1361642 in https://bugs.launchpad.net/dbus-cpp/+bug/1361642 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1381041 Title: Network indicator is sometimes blank Status in “indicator-network” package in Ubuntu: In Progress Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: This is on krillin r103, but it has been happening for a while. See attached photo. I am not certain what triggers it. but I think it may happen when wifi APs become in and out of range while walking around town (as if the list does not refresh reliably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1381041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I have a workaround for this, use Gnome instead of Unity. It took me a while to realize/figure out that it's pretty painless to just run a different window manager on Ubuntu. I did look at maybe switching to a different lock screen but there was no straightforward way to do that. It turns out you just use apt to install gnome-shell and then from the login screen you have the option to run Gnome instead of Unity (click the little icon on that line with your name when you're logging in to select the window manager you want). The bug makes Unity so inconvenient to use that I was considering switching to another Linux distribution. I don't see any downside to switching to Gnome so far, so this seems like a reasonable workaround until the problem is resolved. Or maybe forever, I don't care about Gnome vs. Unity and Gnome seems to work just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270245] Re: Backward frame jumps on mali (Nexus 10 & krillin)
See backwards frame jumps at 0:04 and 0:24 marks in the attached video. ** Attachment added: "IMG_1038.MOV" https://bugs.launchpad.net/mir/+bug/1270245/+attachment/4246372/+files/IMG_1038.MOV -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1270245 Title: Backward frame jumps on mali (Nexus 10 & krillin) Status in Mir: Confirmed Status in “mir” package in Ubuntu: Confirmed Bug description: Alexandros, Andreas, and I have noted at different points that we see frame skips on the nexus 10. The frames look like they move in a 1,3,2 pattern, particularly when unlocking the device. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1270245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Fix works for me too, but it obviously isn't the proper solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 Status in “openssh” package in Ubuntu: Confirmed Bug description: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386323] [NEW] is friend app not available in 14.10?
Public bug reported: is friend app not available in 14.10. I used to get notifications in the previous versions of ubuntu. Its not working in 14.10. I was using the friends app till ubuntu 14.04 as soon as I updated to ubuntu 14.10, the friends app is not working. I used to get notifications (notify osd) in the previous version. Neither the app is getting updated with the latest feeds from twitter and facebook nor I am getting any notifications. I tried uninstalling and reinstalling as well as remove the online accounts from the systems settings menu and added the accounts again. Neither way it doesnt seems to work. It was reallt a very good application. Please some one help me on this. Is the friends app still supported in the latest version of ubuntu? ** Affects: friends-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1386323 Title: is friend app not available in 14.10? Status in “friends-app” package in Ubuntu: New Bug description: is friend app not available in 14.10. I used to get notifications in the previous versions of ubuntu. Its not working in 14.10. I was using the friends app till ubuntu 14.04 as soon as I updated to ubuntu 14.10, the friends app is not working. I used to get notifications (notify osd) in the previous version. Neither the app is getting updated with the latest feeds from twitter and facebook nor I am getting any notifications. I tried uninstalling and reinstalling as well as remove the online accounts from the systems settings menu and added the accounts again. Neither way it doesnt seems to work. It was reallt a very good application. Please some one help me on this. Is the friends app still supported in the latest version of ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1386323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270245] Re: Backward frame jumps on mali (Nexus 10 & krillin)
In krillin you can still see "frame jumps" or out of order frames with: sudo stop lightdm sudo mir_demo_server_basic --disable-overlays=true --launch-client mir_demo_client_egltriangle -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1270245 Title: Backward frame jumps on mali (Nexus 10 & krillin) Status in Mir: Confirmed Status in “mir” package in Ubuntu: Confirmed Bug description: Alexandros, Andreas, and I have noted at different points that we see frame skips on the nexus 10. The frames look like they move in a 1,3,2 pattern, particularly when unlocking the device. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1270245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351939] Re: Sending USSD message does not work
** Changed in: modem-manager-gui (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351939 Title: Sending USSD message does not work Status in Modem Manager Gui: Invalid Status in ModemManager (with NetworkManager support): New Status in “modem-manager-gui” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: New Bug description: The error message says: "Error sending USSD" "GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.ModemManager1.Modem.Modem3gpp.Ussd' on object at path /org/freedesktop/ModemManager1/Modem/5" This is reported upstream here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374721] Re: ibus-daemon uses 100% CPU when using gnome-calculator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1374721 Title: ibus-daemon uses 100% CPU when using gnome-calculator Status in “ibus” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open gnome-calculator 2. Enter 3*7 3. Notice that ibus-daemon and ibus-x11 are using 100+% CPU ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 27 20:32:05 2014 InstallationDate: Installed on 2014-09-03 (24 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1374721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278193] Re: logrotate skip the rotation of many files under /var/log due to bad group ownership
I've went through this problem just now. The changes described in #5 solved the problem for me as well. The fix released in LP: #1258202 (logrotate version 3.8.6-1ubuntu2) adds those lines to the default logrotate.conf file, but I got some custom configs in mine and so I had to manually change it. Of course it only works when it reads logrotate.conf, which I guess is not the case when you run this way: logrotate -df /etc/logrotate.d/rsyslog Running either /etc/cron.daily/logrotate or "/usr/sbin/logrotate /etc/logrotate.conf" works fine. Maybe the config "su root syslog" should be the compile-time-default in Ubuntu so to avoid this situation. Don't know if it is possible. Also, from what I understand reading man logrotate.conf, the "su root syslog" line only changes the user/group that the process of rotation will run as, which does not (necessarily) affect the owner and group of the log files: that is defined by the "create" directive (see the logrotate.conf man for that directive). That's why you don't see any files with group syslog, Uwe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1278193 Title: logrotate skip the rotation of many files under /var/log due to bad group ownership Status in “logrotate” package in Ubuntu: Confirmed Bug description: With the latest update to logrotate (3.8.7-1ubuntu1), the group ownership of /var/log was changed to "syslog" causing this kind of problem: # logrotate -df /etc/logrotate.d/rsyslog reading config file /etc/logrotate.d/rsyslog Handling 2 logs rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. ... # ls -la /var/ | grep log drwxrwxr-x 17 root syslog 4096 Feb 9 10:58 log $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ apt-cache policy logrotate logrotate: Installed: 3.8.7-1ubuntu1 Candidate: 3.8.7-1ubuntu1 Version table: *** 3.8.7-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: logrotate 3.8.7-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 17:19:41 2014 InstallationDate: Installed on 2014-01-26 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: logrotate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1278193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384393] Re: Photos in scope not visible until all loaded
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Albert Astals Cid (aacid) ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu RTM) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1384393 Title: Photos in scope not visible until all loaded Status in The Savilerow project: Confirmed Status in “unity-api” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: I think this is a generic unity8 issue that is exposed in the My Photos scope. This scope displays photos from the photo roll through mediascanner. Problem: When there are many photos, the scope does not display thumbnails for quite a while. (It may even be that no photo thumbnails display until all are loaded into memory.) This is an awkward user experience because the scope looks like nothing is happening for significant periods of time. Expectation: Photo thumbnails would display as they arrive. (Perhaps there would be some kind of window around what is currently visible in the scope so that as soon as photos in the current scroll area, before it by some amount, and after it by some amount are in memory, they could display and the user could scroll somewhat, with the window moving appropriately.) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1384393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon
I take that back. Setting managed=true breaks the networking. Even though I get the proper icon and all the network connection information appears to be correct (both as displayed by ifconfig and through the NM u/i), I cannot ping or connect to any service outside my LAN. Gateway and DNS services, IPv4 address and netmask all *look* right, but nothing gets outside the LAN. Setting it back to managed=false fixes this but of course volcano-izes the icon. I'll take functional networking over cosmetics. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/751939 Title: Wired-only machine has empty volcano icon Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/751939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381930] Re: 7digital previews do not play in the scope
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: New Status in “unity8” package in Ubuntu RTM: New Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378827] Re: [notification] incoming call snap decision should prevent edge interaction on greeter
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Mirco Müller (macslow) ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu RTM) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378827 Title: [notification] incoming call snap decision should prevent edge interaction on greeter Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: rtm build 88 on krillin Steps to reproduce: - unlock the phone - call the phone - when the incoming call snap decision is displayed, all access to the edges is blocked and the dialog is modal, as it should be - now lock the phone - call the phone Expected results: - all access to the edges is blocked and the snap-decision is modal, as is the case when the phone is unlocked Actual results: - the launcher can be swiped and the top panel can be interacted with. the edges are not blocked as they should be This is related to #1358343 [notifications] [design] too easy to answer a call by accident. We need this to be fixed so users don't inadavertently interact with the indicators or launcher when the phone is there pocket and an incoming call arrives. This fix, coupled with the fix to the snap decision to have a swipe to answer would prevent most of the problems that can occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378462] Re: cannot reply to second notification
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Status: New => In Progress ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Nick Dedekind (nick-dedekind) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1378462 Title: cannot reply to second notification Status in “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: build 88, rtm on krillin - unlock the phone - make sure messaging-app is not running - send two sms messages to the phone - once they appear, open the messaging-menu - reply to the first message by clicking the message which makes it expand to reveal the send field - this works - attempt to reply to the second message by clicking the message to make it expand Expected results: the item should expand and allow you to send a message Actual results: the item cannot be expanded and you can't reply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385630] Re: New systemd (215) does not boot very well
I downgraded systemd to the version 208 in official Vivid repos. Now booting works perfectly and fast. It may be worthwhile to tell that I have purged systemd-shim, cgmanager and libcgmanager0 from my setup. So this really is a pure systemd booting setup now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1385630 Title: New systemd (215) does not boot very well Status in “systemd” package in Ubuntu: New Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358343] Re: [TOPBLOCKER] too easy to answer a call by accident
** Also affects: unity-notifications (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity-notifications (Ubuntu RTM) Assignee: (unassigned) => Mirco Müller (macslow) ** Changed in: unity-notifications (Ubuntu RTM) Status: New => In Progress ** Changed in: unity-notifications (Ubuntu RTM) Importance: Undecided => Critical ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Mirco Müller (macslow) ** Changed in: unity8 (Ubuntu RTM) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1358343 Title: [TOPBLOCKER] too easy to answer a call by accident Status in Telephony Service: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: Confirmed Status in “telephony-service” package in Ubuntu: New Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: If you put the phone in your pocket with locked screen and you receive a call is too easy to answer or reject that by mistake. Or pressing the screen while trying to get the phone or the call can be answered without you noticed by your pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1358343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355173] Re: Switching windows with a Trusted Prompt Session active loses the trusted prompt session
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Nick Dedekind (nick-dedekind) ** Changed in: unity8 (Ubuntu RTM) Status: New => In Progress ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu RTM) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1355173 Title: Switching windows with a Trusted Prompt Session active loses the trusted prompt session Status in Qt integration with the Mir display server: In Progress Status in Online Accounts setup for Ubuntu Touch: Confirmed Status in “pay-service” package in Ubuntu: New Status in “trust-store” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: When we create a trusted prompt session over an application, let's say a small dialog, and then switch applications, when we switch back to the original application the dialog is not overlayed on top of the original application. The program providing the dialog seems happy, and is still running, but visually it is not there. We notice this when using the payments UI which overlays ontop of the dash. In some cases we need to show Online Accounts which runs as an independent application and causes a switching behavior. When returning back to the dash the Payment UI is not visible. It also happens if the Payment UI is visible and you switch applications using the right swipe. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1355173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376044] Re: [scopes] Ubuntu button on launcher is hardcoded to click scope
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Michael Zanetti (mzanetti) ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu RTM) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1376044 Title: [scopes] Ubuntu button on launcher is hardcoded to click scope Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: The Ubuntu button should bring the user to their first favorite scope, rather than always the click scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 (not installed) ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 19:11:58 2014 InstallationDate: Installed on 2013-04-26 (522 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1376044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon
** Changed in: network-manager (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/751939 Title: Wired-only machine has empty volcano icon Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/751939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383702] Re: Welcome Wizard: Passphrase has no obvious way to continue
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Status: New => In Progress ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Michael Terry (mterry) ** Also affects: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: New => In Progress ** Changed in: ubuntu-system-settings (Ubuntu RTM) Assignee: (unassigned) => Michael Terry (mterry) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383702 Title: Welcome Wizard: Passphrase has no obvious way to continue Status in Ubuntu Touch System Settings: New Status in “ubuntu-system-settings” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: STEPS: 1. Flash a fresh image 2. Select a language 3. Select passphrase 4. Add a passphrase EXPECTED: Every other page has a back and continue/skip buttons, I expect to see a continue button on the page ACTUAL: You have no obvious way to continue, there is no text saying to hit enter after the passphrase is completed nor is there a continue button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1383702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336715] Re: switch-items in indicators sometimes get out of sync with system-settings
** Also affects: ubuntu-system-settings (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu RTM) Status: New => In Progress ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Nick Dedekind (nick-dedekind) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1336715 Title: switch-items in indicators sometimes get out of sync with system- settings Status in Display Indicator: Invalid Status in Indicator Location: Invalid Status in Network Menu: Invalid Status in Sound Menu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu RTM: New Status in “unity8” package in Ubuntu RTM: In Progress Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333187] Re: [Dash] [design] Preview images display as black thumbnails
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu RTM) Status: New => In Progress ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Andrea Cimitan (cimi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1333187 Title: [Dash] [design] Preview images display as black thumbnails Status in The Savilerow project: New Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: If the image is large, the Ubuntu shape rounded corners become very little, hardly noticable. REQUESTED UX SOLUTION Updated spec so images only zoomable once full screen. For all other instances of ubuntu shape, SDK documentation should be used (see link from Jouni in comments) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1333187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373985] Re: unity8-dash doesn't seem to get activated after we leave the lock screen
** Branch linked: lp:~michael-sheldon/ubuntu/utopic/maliit- framework/fix-1373985 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1373985 Title: unity8-dash doesn't seem to get activated after we leave the lock screen Status in “maliit-framework” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Bug description: Steps to reproduce the issue: 1 - lock the phone (reboot or have the display off and then turn it back on) 2 - type you password [you're brought to unity8-dash] 3 - tap on the looking glass icon in the top right [search bar text entry shows up with "Search apps" written on it] Expected outcome: A blinking cursor caret is displayed on the app search text entry and the VKB comes up. Actual outcome: Nothing happens. Causing unity-8 dash to be refocused, such as bringing the indicators panel down and then back up solves it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1373985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
Note for everyone who wants to test and for the SRU team. The SRU works only by updating all three packages, especially the binary package system-config-printer-udev needs the new cups-filters-ippusbxd package now. ** Changed in: cups (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: cups-filters (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: system-config-printer (Ubuntu Trusty) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no "Generic IPP Everywhere Printer"). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
Uploaded fixed versions of the cups-filters, system-config-printer, and cups packages to trusty-proposed now. As soon as they get approved they get available for installation and instructions for installing them get posted here. Please update all the packages and test the IPP Everywhere support. Report your results here as this is required for the update getting into the official updates or Trusty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no "Generic IPP Everywhere Printer"). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
Daniel, I am very grateful if you could test the IPP-over-USB support with these updates on a Trusty system and with your IPP-over-USB printer. You can already start testing before SRU -proposed approval by applying the three debdiffs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no "Generic IPP Everywhere Printer"). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
For the SRU team: debdiff for cups ** Patch added: "cups_1.7.2-0ubuntu1.2_1.7.2-0ubuntu1.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+attachment/4246320/+files/cups_1.7.2-0ubuntu1.2_1.7.2-0ubuntu1.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no "Generic IPP Everywhere Printer"). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
For the SRU team: debdiff for cups-filters ** Patch added: "cups-filters_1.0.52-0ubuntu1.2_1.0.52-0ubuntu1.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+attachment/4246318/+files/cups-filters_1.0.52-0ubuntu1.2_1.0.52-0ubuntu1.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no "Generic IPP Everywhere Printer"). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
For the SRU team: debdiff for system-config-printer ** Patch added: "system-config-printer_1.4.3+20140219-0ubuntu2.2_1.4.3+20140219-0ubuntu2.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+attachment/4246319/+files/system-config-printer_1.4.3%2B20140219-0ubuntu2.2_1.4.3%2B20140219-0ubuntu2.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: In Progress Status in “cups-filters” source package in Trusty: In Progress Status in “system-config-printer” source package in Trusty: In Progress Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no "Generic IPP Everywhere Printer"). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-typical features. 3. Share a local print queue on your box and try to access this queue with a mobile device which supports printing on IPP Everywhere printers. The printer will not be found or be found based on older mobile printing protocols. After installing this SRU (all three packages) all this will work. [Regression Potential] Most changes are addition of new code files and new conversion rules, there are only a few simple changes in existing code files so the risk of regressions is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1386241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon
This has only been a cosmetic bug for me for a long time. However, I took the ping as an opportunity to try a few of the things in comment #6. Changing managed=false to managed=true was the only change necessary to fix the icon in Utopic. I consider this bug fixed. ** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/751939 Title: Wired-only machine has empty volcano icon Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/751939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386268] [NEW] Edge tutorial's redesign: new look
Public bug reported: This is a breakout from bug 1383297 (which now just covers new gestures). This bug is just about implementing the new look and feel as well as dropping the first greeter screen, which is no longer in the tutorial designs. I'm making a separate bug because they will likely be given different priorities and implemented at different times. You can see the new visuals in this folder: https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg And the flow in general here: https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Description changed: - This is a breakout from bug 1383297 (which now just covers the edge - tutorial's redesigned additional gestures -- things like right edge - swipe). + This is a breakout from bug 1383297 (which now just covers new + gestures). This bug is just about implementing the new look and feel as well as dropping the first greeter screen, which is no longer in the tutorial designs. I'm making a separate bug because they will likely be given different priorities and implemented at different times. You can see the new visuals in this folder: https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg And the flow in general here: https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw -- 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/1386268 Title: Edge tutorial's redesign: new look Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: This is a breakout from bug 1383297 (which now just covers new gestures). This bug is just about implementing the new look and feel as well as dropping the first greeter screen, which is no longer in the tutorial designs. I'm making a separate bug because they will likely be given different priorities and implemented at different times. You can see the new visuals in this folder: https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg And the flow in general here: https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1386268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378872] Re: [emergency call] active call panel not displayed when phone locked
** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu RTM) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378872 Title: [emergency call] active call panel not displayed when phone locked Status in Dialer app for Ubuntu Touch: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: rtm build 88 on krillin Steps to reproduce: 1) lock phone (with passcode enabled) 2) call phone 3) answer call 4) dialer is displayed (in limited mode as phone is locked) 5) press back button in dialer header so that phone can be unlocked while on the call 6) greeter is displayed 7) now try to get back to active call Expected results: - the active call panel should be displayed on the greeter screen to allow user to go directly back to the call without having to unlock the phone Actual results: - the active call panel is not displayed. The only way to get back to the active call is to unlock the phone (or press the emergency call button), neither which is obvious To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1378872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383297] Re: Edge tutorial's redesign: new gestures
** Description changed: - A while ago, Design gave me new visuals for the edge demo [1], but it - kept getting put off for other work. + The first-boot edge tutorial should cover a wider range of gestures than + it currently does. Things like right edge swipe, bottom edge swipe, and + long vs short swipes. - I'm filing a bug here to help it not get forgotten and so it can be - assigned a priority. - - [1] https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- + Visual designs (not entirely finished yet): + https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383297 Title: Edge tutorial's redesign: new gestures Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: The first-boot edge tutorial should cover a wider range of gestures than it currently does. Things like right edge swipe, bottom edge swipe, and long vs short swipes. Visual designs (not entirely finished yet): https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383297] Re: Edge tutorial's redesign: new gestures
I've split this bug in two: - This bug, which is about adding new gestures to the tutorial (right edge swipe, bottom edge swipe, long vs short swipes). - And bug 1386268, which is just about the new look and feel (and dropping the greeter swipe page). This way, we can schedule the two changes separately. ** Summary changed: - Edge intro/demo redesign + Edge tutorial's redesign: new gestures -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383297 Title: Edge tutorial's redesign: new gestures Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: The first-boot edge tutorial should cover a wider range of gestures than it currently does. Things like right edge swipe, bottom edge swipe, and long vs short swipes. Visual designs (not entirely finished yet): https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1335761] Re: [Dash] Activating a preview with a scope URI for the current scope doesn't send you back to the results view
** Tags removed: touch-2014-10-09 ** Tags added: touch-2014-11-13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1335761 Title: [Dash] Activating a preview with a scope URI for the current scope doesn't send you back to the results view Status in “unity-scopes-shell” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: You'll have to compile (prototype) the Youtube scope from source (https://launchpad.net/unity-scope-youtube/), as it's not in distro yet. Basically the workflow is: 1) Search for something that has a result with a scope URI for the current scope. In the case of Youtube, search for "queenofficial" to get Queen's music channel. 2) Preview the first item (the channel itself), and click the search button. 3) This runs a new query for the current scope, but doesn't switch away from the preview view). 4) You will see a preview of the first video in the new results list. Like when searching other scopes, the view should be returned to the results list, instead of saying in the preview "view". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1335761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379788] Re: Oxide processes don't get OOM adjusted
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1379788 Title: Oxide processes don't get OOM adjusted Status in Qt integration with the Mir display server: In Progress Status in “qtmir” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “qtmir” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: OOM adjustment is important to the lifecycle because it makes it so that the focused application actually gets the full usage of the device. By not OOM adjusting the Oxide renders, some of the largest processes in the system aren't killed appropriately by the OOM killer. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1379788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379786] Re: Processes out of pgroup don't get stopped
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1379786 Title: Processes out of pgroup don't get stopped Status in Qt integration with the Mir display server: In Progress Status in “qtmir” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “qtmir” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: If an application has processes that are not in the process group of the primary process the application lifecycle will not stop or resume them, effectively leaving them unmanaged. The most obvious cause of this is any web app or the browser which has processes started by the sandbox. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1379786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381930] Re: 7digital previews do not play in the scope
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1381930 Title: 7digital previews do not play in the scope Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: New Bug description: Steps to reproduce: 1. Navigate to the music scope 2. In the section 'New albums from 7digital' click on any album 3. Press the play button on one of the track previews Expected result: The preview plays Actual result: No preview plays ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity-scope-mediascanner2 0.2+14.10.20141009-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 16 08:11:12 2014 InstallationDate: Installed on 2014-10-16 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141016-010328) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1381930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378872] Re: [emergency call] active call panel not displayed when phone locked
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378872 Title: [emergency call] active call panel not displayed when phone locked Status in Dialer app for Ubuntu Touch: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: New Bug description: rtm build 88 on krillin Steps to reproduce: 1) lock phone (with passcode enabled) 2) call phone 3) answer call 4) dialer is displayed (in limited mode as phone is locked) 5) press back button in dialer header so that phone can be unlocked while on the call 6) greeter is displayed 7) now try to get back to active call Expected results: - the active call panel should be displayed on the greeter screen to allow user to go directly back to the call without having to unlock the phone Actual results: - the active call panel is not displayed. The only way to get back to the active call is to unlock the phone (or press the emergency call button), neither which is obvious To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1378872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378462] Re: cannot reply to second notification
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1378462 Title: cannot reply to second notification Status in “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: In Progress Bug description: build 88, rtm on krillin - unlock the phone - make sure messaging-app is not running - send two sms messages to the phone - once they appear, open the messaging-menu - reply to the first message by clicking the message which makes it expand to reveal the send field - this works - attempt to reply to the second message by clicking the message to make it expand Expected results: the item should expand and allow you to send a message Actual results: the item cannot be expanded and you can't reply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333187] Re: [Dash] [design] Preview images display as black thumbnails
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1333187 Title: [Dash] [design] Preview images display as black thumbnails Status in The Savilerow project: New Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Bug description: If the image is large, the Ubuntu shape rounded corners become very little, hardly noticable. REQUESTED UX SOLUTION Updated spec so images only zoomable once full screen. For all other instances of ubuntu shape, SDK documentation should be used (see link from Jouni in comments) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1333187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376044] Re: [scopes] Ubuntu button on launcher is hardcoded to click scope
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1376044 Title: [scopes] Ubuntu button on launcher is hardcoded to click scope Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: In Progress Bug description: The Ubuntu button should bring the user to their first favorite scope, rather than always the click scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 (not installed) ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 30 19:11:58 2014 InstallationDate: Installed on 2013-04-26 (522 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1376044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376707] Re: Launcher needs to dynamically respond to reset
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1376707 Title: Launcher needs to dynamically respond to reset Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: Currently the reset launcher action initiated from the system settings app requires the user to reboot the device. The intended design is for the launcher to dynamically reset to the initial state and briefly reveal itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1376707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336715] Re: switch-items in indicators sometimes get out of sync with system-settings
** Tags removed: touch-2014-10-23 ** Tags added: touch-2014-10-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1336715 Title: switch-items in indicators sometimes get out of sync with system- settings Status in Display Indicator: Invalid Status in Indicator Location: Invalid Status in Network Menu: Invalid Status in Sound Menu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386241] Re: Add the full IPP Everywhere support from Utopic to Trusty
** Also affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Also affects: cups (Ubuntu) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Importance: Undecided => High ** Changed in: system-config-printer (Ubuntu) Importance: Undecided => High ** Also affects: system-config-printer (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cups-filters (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: cups (Ubuntu Trusty) Importance: Undecided => High ** Changed in: cups-filters (Ubuntu Trusty) Importance: Undecided => High ** Changed in: system-config-printer (Ubuntu Trusty) Importance: Undecided => High ** Changed in: cups (Ubuntu) Status: New => Fix Released ** Changed in: cups-filters (Ubuntu) Status: New => Fix Released ** Changed in: system-config-printer (Ubuntu) Status: New => Fix Released ** Changed in: cups-filters (Ubuntu Trusty) Milestone: None => trusty-updates ** Changed in: cups-filters (Ubuntu) Milestone: trusty-updates => None ** Changed in: cups (Ubuntu Trusty) Milestone: None => trusty-updates ** Changed in: system-config-printer (Ubuntu Trusty) Milestone: None => trusty-updates ** Changed in: cups (Ubuntu Trusty) Status: New => Triaged ** Changed in: cups-filters (Ubuntu Trusty) Status: New => Triaged ** Changed in: system-config-printer (Ubuntu Trusty) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1386241 Title: Add the full IPP Everywhere support from Utopic to Trusty Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “system-config-printer” package in Ubuntu: Fix Released Status in “cups” source package in Trusty: Triaged Status in “cups-filters” source package in Trusty: Triaged Status in “system-config-printer” source package in Trusty: Triaged Bug description: This is a hardware enablement SRU for Ubuntu 14.04 LTS (Trusty). From 14.10 (Utopic) on Ubuntu has full support for IPP Everywhere printing: 1. Printing on IPP Everywhere printers 2. Printing on IPP-over-USB printers 3. When sharing a printer to the network the shared print queue emulates an IPP Everywhere printer 4. PPD-less printing on IPP network printers (IPP Everywhere, PDF, PostScript, PCL) without need of a printer setup tool 14.04 *Trusty), the current LTS, supports only (4). An OEM asked whether we could backport the full IPP Everywhere support to Trusty. This bug report is about the backport of IPP Everywhere support into Trusty as an SRU. Affected are the source packages cups-filters, cups, and system- config-printer: cups-filters: - Add ippusbxd (Support for IPP-over-USB printers), generating the new binary package cups-filters-ippusbxd. Its installation in Trusty will be assured by a dependency on it in system-config-printer-udev - Add rastertopdf filter. This filter allows PWG Raster as input format for a CUPS queue. This is needed to make shared CUPS printers fully emulating IPP Everywhere printers (all other requirements are fulfilled by CUPS itself). - Add conversion rule for rastertopdf filter to the MIME conversion rules. - Add PPD file for a generic IPP Everywhere printer (on-the-fly auto-generation by cupsfilters.drv). - Support for PWG-Raster output activation via a keyword in the PPD file. - pdftoraster filter: Support for output in the color spaces 18 (sGray), 19 (sRGB), and 20 (Adobe RGB). No color management appropriate to these color spaces is added yet. system-config-printer: - Add auto-setup for UDEV-discovered IPP-over-USB printers using ippusbxd. cups: - Fix priority setting of PWG Raster MIME type, so that PWG Raster input is actually recognized. [Impact] Trusty has a total support life of 5 years, ending in April 2019, but it does not support the new PWG standard IPP Everywhere for driverless printing. So in the near future many new printer models which can get easily supported under Linux as they are fulfilling an open standard are not supported by Trusty. This is especially very bad for Trusty being used as pre-installed OS on new PC/notebook/server hardware and on mobile devices. [Test Case] 1. Connect an IPP Everywhere printer to the network and try to set it up. There is no suitable selection in the Make/Model lists (no "Generic IPP Everywhere Printer"). 2. Connect an IPP-over-USB printer to the USB. It gets set up automatically but with the conventional USB interface, not giving access to the printer's configuration web interface and other network-printer-t
[Touch-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
** Description changed: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags Related Bugs: - * bug 1382632: horizon insecure key file permissions - * bug 1386237: tar strange behavior with --acl - * bug 1313550: ping broken (xattrs lost in tar extraction) + * bug 1382632: horizon insecure key file permissions + * bug 1386237: tar strange behavior with --acl and xattr + * bug 1313550: ping broken (xattrs lost in tar extraction) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Won't Fix Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl and xattr * bug 1313550: ping broken (xattrs lost in tar extraction) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386237] Re: tar acl support has strange behavior when used with --xattr
Just to demonstrate a particularly odd behavior: #!/bin/bash set -e; set -o pipefail tmpd=$(mktemp -d) trap "rm -Rf "$tmpd"" EXIT cd $tmpd; mkdir defaults ex setfacl --default --modify u::rwx --modify g::r-x --modify other::r-x defaults setfacl --remove-default ex xattr_args="--xattrs --xattrs-include=*" ( set -x; tar $xattr_args --no-acl -cpf - defaults | tar -C ex $xattr_args --no-acl -xpf - ) for d in defaults ex/defaults; do echo === $d === echo " == getfacl $d =="; getfacl $d | sed 's,^, ,' echo " == ls -l $d ==" ; ls -l "$d" | sed 's,^, ,' echo " == ls -ld $d ==" ; ls -ld "$d" | sed 's,^, ,' echo done ## end script / begin output ## + tar --xattrs '--xattrs-include=*' --no-acl -cpf - defaults + tar -C ex --xattrs '--xattrs-include=*' --no-acl -xpf - === defaults === == getfacl defaults == # file: defaults # owner: smoser # group: smoser user::rwx group::rwx other::r-x default:user::rwx default:group::r-x default:other::r-x == ls -l defaults == total 0 == ls -ld defaults == drwxrwxr-x+ 2 smoser smoser 4096 Oct 27 11:18 defaults === ex/defaults === == getfacl ex/defaults == # file: ex/defaults # owner: smoser # group: smoser user::rwx group::rwx other::r-x default:user::rwx default:group::r-x default:other::r-x == ls -l ex/defaults == total 0 == ls -ld ex/defaults == drwxrwxr-x+ 2 smoser smoser 4096 Oct 27 11:18 ex/defaults ** Summary changed: - tar acl support has strange behaviors + tar acl support has strange behavior when used with --xattr -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1386237 Title: tar acl support has strange behavior when used with --xattr Status in “tar” package in Ubuntu: New Bug description: as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl has unexpected behaviors. The one that caught us there was that extracting a tar file with '--acl' that was created without '--acl' results in default acl being set on the top level extracted directory. One would expect that if the source tar file had no acl information that the extracted directory would have no 'default' acl. I'll attach a script here that shows behavior of multiple combinations of: tar -c [--acl / -no-acl / default] tar -x [--acl / --no-acl / default ] and source directories with acl, without acl and with default "default" acl. Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl * bug 1313550: ping broken (xattrs lost in tar extraction) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: tar 1.27.1-2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 09:42:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1104 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: tar UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1386237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383297] Re: Edge intro/demo redesign
Olga, another aspect of this redesign that Saviq brought to my attention: translations for the "fake apps" during the right-edge swipe tutorial. Currently, they show English wording. If we're going to use screenshots that look like fake apps, we'd need to include translated screenshots. Which sounds like a pain. Maybe we could change the fake apps to not have visible text or temperatures or anything that needs localization? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383297 Title: Edge intro/demo redesign Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: A while ago, Design gave me new visuals for the edge demo [1], but it kept getting put off for other work. I'm filing a bug here to help it not get forgotten and so it can be assigned a priority. [1] https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358310] Re: using umount with bash wildcard ends in "device is busy" for mount of parent directory
I'm not able to reproduce it here. Did you get any error messages from umount? ** Changed in: util-linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1358310 Title: using umount with bash wildcard ends in "device is busy" for mount of parent directory Status in “util-linux” package in Ubuntu: Incomplete Bug description: hi, i've run into a problem on ubuntu 14.04 while mounting an ganeti instance for doing some chroot stuff. but the problem itself not related to ganeti or any other virtualization. its just a problem while mounting/unmounting some devices. so heres an example how to reproduce the problem: lvcreate -L 1G -n test system lvcreate -L 1G -n test2 system mkfs.ext4 /dev/system/test mkfs.ext4 /dev/system/test2 mount /dev/system/test /mnt/ mkdir /mnt/test2 mount /dev/system/test2 /mnt/test2/ ln -sf /etc/issue /mnt/ umount /mnt/* umount /mnt/ lvremove -f /dev/system/test2 lvremove -f /dev/system/test if i run this commands /mnt/ is still mounted and it is only possible to umount it using "-l" switch. but after this it is still not possible to remove the logical volume because it says "Logical volume system/test contains a filesystem in use." if i run the same commands but without the "ln -sf /etc/issue /mnt/" everything is okay. also if i replace "umount /mnt/*" with "umount /mnt/boot" everything works. so it seems like umount ist opening /etc/issue for some reason if a bash wildcard is used and not releasing it. checking with lsof or fuser does not show any open files under /mnt/ nor for /etc/issue. the problem does not exist with ubuntu 12.04. a solution for this problem would be great because if you often do some chroot stuff it is easier to use "umount /mnt/*" to umount all bind mounts like /proc/ or /sys/ than running a umount command for each mount. also i havent found a way, other than reboot, to remove an open logical volume if it was hit by this problem. lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 regards the2nd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1358310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386237] Re: tar acl support has strange behaviors
heres output of a run of 'tmp-acl-bavior': ** Attachment added: "example output of running" https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1386237/+attachment/4246269/+files/out ** Description changed: as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl has unexpected behaviors. The one that caught us there was that extracting a tar file with '--acl' that was created without '--acl' results in default acl being set on the top level extracted directory. One would expect that if the source tar file had no acl information that the extracted directory would have no 'default' acl. I'll attach a script here that shows behavior of multiple combinations of: - tar -c [--acl / -no-acl / default] - tar -x [--acl / --no-acl / default ] + tar -c [--acl / -no-acl / default] + tar -x [--acl / --no-acl / default ] and source directories with acl, without acl and with default "default" acl. + + Related Bugs: + * bug 1382632: horizon insecure key file permissions + * bug 1386237: tar strange behavior with --acl + * bug 1313550: ping broken (xattrs lost in tar extraction) + ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: tar 1.27.1-2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 09:42:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1104 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: tar UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1386237 Title: tar acl support has strange behaviors Status in “tar” package in Ubuntu: New Bug description: as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl has unexpected behaviors. The one that caught us there was that extracting a tar file with '--acl' that was created without '--acl' results in default acl being set on the top level extracted directory. One would expect that if the source tar file had no acl information that the extracted directory would have no 'default' acl. I'll attach a script here that shows behavior of multiple combinations of: tar -c [--acl / -no-acl / default] tar -x [--acl / --no-acl / default ] and source directories with acl, without acl and with default "default" acl. Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl * bug 1313550: ping broken (xattrs lost in tar extraction) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: tar 1.27.1-2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 09:42:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1104 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: tar UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1386237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367696] Re: spinning Ubuntu logo on update & boot feels frantic and not very classy
Actually, those don't cover all the issues. One issue is the consistency (or intentional inconsistency) of the activity notification. The other issue is the use of a spinning logo at all (regardless of size and speed). I believe the spinning logo is overly simplistic, not very classy and doesn't live up to the standard of design elsewhere in the product. I think we can do better than that (and have done so in the desktop start up/shut down images as an example). Un-duped, and original description edited to reflect the design question rather than the implementation of size/speed. ** Description changed: - There is a large spinning Ubuntu logo during updates and a small spinning Ubuntu logo during the boot process. I think there are two problems with this: - - whatever the progress indicator is should be consistent (not one large and one small), - - more importantly, this progress indicator feels frantic, cheap and off brand to me. The desktop has the word Ubuntu with dots which change colour to indicate progress. That feels classier to me. Is there a specific reason we have diverged from an existing (and excellent) solution? Isn't this unnecessary divergence for the phone? + There is a large spinning Ubuntu logo during updates and a small + spinning Ubuntu logo during the boot process. There are several bugs + already filed regarding the inconsistency in size and speed (see bug + 1355093 1335789 1350348) + + Regardless of the size/speed of the spinner, I this progress indicator + feels frantic, cheap and off brand to me. It is an obvious and + simplistic device, and one which we have tried to avoid as a core part + of the user experience. We have always been able to develop classier + options. E.g., the desktop has the word Ubuntu with dots which change + colour to indicate progress. Is there a specific reason we have + diverged from an existing (and excellent) solution? Isn't this + unnecessary divergence for the phone? And if there is a good reason for + a new solution (i.e, different than the desktop), then I think it needs + more work to reach the standard of beautiful design elsewhere in the + product. ** This bug is no longer a duplicate of bug 1355093 Inconsistent spinning-logo screens for startup and system image update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1367696 Title: spinning Ubuntu logo on update & boot feels frantic and not very classy Status in Ubuntu UX bugs: Triaged Status in “unity-system-compositor” package in Ubuntu: New Bug description: There is a large spinning Ubuntu logo during updates and a small spinning Ubuntu logo during the boot process. There are several bugs already filed regarding the inconsistency in size and speed (see bug 1355093 1335789 1350348) Regardless of the size/speed of the spinner, I this progress indicator feels frantic, cheap and off brand to me. It is an obvious and simplistic device, and one which we have tried to avoid as a core part of the user experience. We have always been able to develop classier options. E.g., the desktop has the word Ubuntu with dots which change colour to indicate progress. Is there a specific reason we have diverged from an existing (and excellent) solution? Isn't this unnecessary divergence for the phone? And if there is a good reason for a new solution (i.e, different than the desktop), then I think it needs more work to reach the standard of beautiful design elsewhere in the product. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1367696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
** Description changed: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags - SRU curtin - == - - [Impact] - - As the original bug report description mentions, curtin's extraction - needs to use xattr/acl flags. - - [Test Case] - - To reproduce this bug, use curtin extraction without the extended file - attributes. - - [Regression Potential] - - Since the patch for this bug fix *looks* to see if there are extended - file attributes, it should work in the event that they are there or are - not there or are. More specifically, if tar cmd supports xattrs, curtin - will return the required flags to extract them. This lowers the - probability of introducing a regression. + Related Bugs: + * bug 1382632: horizon insecure key file permissions + * bug 1386237: tar strange behavior with --acl + * bug 1313550: ping broken (xattrs lost in tar extraction) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Won't Fix Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl * bug 1313550: ping broken (xattrs lost in tar extraction) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386237] [NEW] tar acl support has strange behaviors
Public bug reported: as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl has unexpected behaviors. The one that caught us there was that extracting a tar file with '--acl' that was created without '--acl' results in default acl being set on the top level extracted directory. One would expect that if the source tar file had no acl information that the extracted directory would have no 'default' acl. I'll attach a script here that shows behavior of multiple combinations of: tar -c [--acl / -no-acl / default] tar -x [--acl / --no-acl / default ] and source directories with acl, without acl and with default "default" acl. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: tar 1.27.1-2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 09:42:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1104 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: tar UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago) ** Affects: tar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: "tar-acl-behavior: show tars' behavior with different combinations" https://bugs.launchpad.net/bugs/1386237/+attachment/4246255/+files/tar-acl-beavior -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1386237 Title: tar acl support has strange behaviors Status in “tar” package in Ubuntu: New Bug description: as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl has unexpected behaviors. The one that caught us there was that extracting a tar file with '--acl' that was created without '--acl' results in default acl being set on the top level extracted directory. One would expect that if the source tar file had no acl information that the extracted directory would have no 'default' acl. I'll attach a script here that shows behavior of multiple combinations of: tar -c [--acl / -no-acl / default] tar -x [--acl / --no-acl / default ] and source directories with acl, without acl and with default "default" acl. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: tar 1.27.1-2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 09:42:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (1104 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: tar UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1386237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385537] Re: logrotate does not rotate logs (rsyslog)
Could this be a duplicate of bug 1385464?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in “logrotate” package in Ubuntu:
New
Bug description:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly"
according to /etd/..., actually: no rotation even after weeks; and
manual forcing may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about
1000 entries a day, resulting in many GB load for the USB drive per
day. I learnt about logrotate and rsyslog and modified
/etc/logrotate.conf and /etc/logrotate.d/rsyslog. Yet none had any
effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22
where I had not changed /etc/logrotate.conf, neither
/etc/logrotate.d/rsyslog ("daily", "weekly"), and the three files
still have the entries from 2014-08-31, although three "weeks" had
passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of
memory" finally) in some installations in summer 2013; in later installations
the same year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
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
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Sat Oct 25 01:02:40 2014
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385537/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383279] Re: power button events queued, should probably be dropped
** Changed in: unity-system-compositor Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1383279 Title: power button events queued, should probably be dropped Status in Unity System Compositor: In Progress Status in “unity-system-compositor” package in Ubuntu: Confirmed Bug description: Lock phone Repeatedly and rapidly press the power button. Wait Observe the screen blink on and off for some seconds after you finish pressing the power button. The presses after the first few should probably be dropped? To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1383279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
