[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available
** Also affects: lightdm (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1481561 Title: Connect to XDMCP clients on address requests come from if available Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: New Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Committed Bug description: [Impact] Currently LightDM connects to an XDMCP enabled X server using the first suitable address in the XDMCP Request packet. However, some clients may put a number of addresses in this message and potentially they are not all routable. If the address the request message came from is in the list we should use that first as that is more likely to be a routable address. This also matches the behaviour of GDM which ignores the contents of the Request packet anyway. [Test Case] 1. Start LightDM with XDMCP enabled 2. Connect with a client that puts a number of addresses in the Request packet Expected result: LightDM prefers the address the Request came from over the other addresses. Observed result: LightDM always picks the first address. [Regression Potential] There is a possibility of a behaviour change in existing clients that had two valid addresses, though the particular address shouldn't matter (unless complex firewalling / routing rules are being used). There is a risk that XDMCP behaviour could have been broken by the change (tested with regression tests). To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1481561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1503693] Re: Dim timeout gsetting key not set anymore
** Changed in: ubuntu-system-settings (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-qt in Ubuntu. https://bugs.launchpad.net/bugs/1503693 Title: Dim timeout gsetting key not set anymore Status in Canonical System Image: Fix Released Status in gsettings-qt package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: The dim-timeout gsettings key is not set anymore when the activity- timeout key changes, so a default value of 45sec is used for dim- timeout regardless of the activity timeout selected by the user in the batter plugin. The logic to set the dim timeout value is there in battery/SleepValues.xml in the GSettings onChanged handler, but it seems that the onChanged handler is not called when the activity- timeout value changes. Not sure if this is a problem in the way ubuntu-system-settings uses the GSettings QML item, or if the item implementation itself is broken somehow. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1503693/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1515561] Re: Windows flash black briefly before being drawn
This bug was fixed in the package gtk+3.0 - 3.18.5-1ubuntu1 --- gtk+3.0 (3.18.5-1ubuntu1) xenial; urgency=medium [ Iain Lane ] * Merge with Debian. Remaining changes: + Install the settings.ini file to set our themes. + Enable parallel builds + Ubuntu specific patches: - 073_treeview_almost_fixed.patch - 074_eventbox_scroll_mask.patch - bzg_gtkcellrenderer_grabbing_modifier.patch - ubuntu_gtk_custom_menu_items.patch - print-dialog-show-options-of-remote-dnssd-printers.patch - uimanager-guard-against-nested-node-updates.patch - x-canonical-accel.patch - message-dialog-restore-traditional-look-on-unity.patch - 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch - restore_filechooser_typeaheadfind - 0001-calendar-always-emit-day-selected-once.patch - git_icon_fallback.patch + Add Breaks on gnome-shell << 3.16 - this needs to be updated at the same time. + Add Breaks on old overlay-scrollbar versions which still provided the gtk3 module - we don't want to use this any more with GTK 3.16. [ Lars Uebernickel ] * Add debian/patches/0001-gtkwindow-continue-calling-gtk_style_context_set_bac.patch: - fixes black flickering when new windows are created (LP: #1515561) gtk+3.0 (3.18.5-1) unstable; urgency=medium * New upstream stable release 3.18.5 + GtkFileChooser: - Make sure external drives show up either in the sidebar or the places view - Ignore double-click events + Avoid some crashes in CSS parsing error handling -- Iain Lane Tue, 17 Nov 2015 14:21:50 + ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1515561 Title: Windows flash black briefly before being drawn Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Since 3.18, windows flash black for a split second before they are drawn. It's visually disruptive. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1515561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
We already figured out how this was introduced and how to fix it. We just need someone to actually create the fix. The ibus package changed the default setting of desktop.ibus.general .use-system-keyboard-layout from true to false. Ever since this dconf setting was introduced, we had this error. For existing installations you need to change this manually either with dconf-editor or ibus-setup. For fresh installs we need to patch the package to revert this setting back to its old default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Confirmed Status in ibus source package in Trusty: Triaged Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518079] Re: scrollbars gone in 15.10
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: vinagre (Ubuntu) Importance: Undecided => High ** Changed in: vinagre (Ubuntu) Status: New => Confirmed ** Tags added: rls-x-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1518079 Title: scrollbars gone in 15.10 Status in vinagre package in Ubuntu: Confirmed Bug description: When I use vinagre to connect to a remote display that is larger than my local display, there are no scrollbars on the vinagre window to allow me to scroll the remove display up/down or left/right. There were scrollbars in 15.04. They have disappeared in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: vinagre 3.16.1-1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 19 16:02:12 2015 SourcePackage: vinagre UpgradeStatus: Upgraded to wily on 2015-11-17 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1518079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1507033] Re: lightdm.conf boolean values false if have trailing whitespace
** Also affects: lightdm (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1507033 Title: lightdm.conf boolean values false if have trailing whitespace Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: New Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. [Test Case] 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) 2. Run LightDM Expected result: The configured value is interpreted as true. Observed result: The configured value is interpreted as false. [Regression potential] Low. We just strip trailing whitespace when checking for the value "true". To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1507033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1516831] Re: XDMCP Request packet with no addresses crashes LightDM
The way I found this was by testing the SRU in vivid - for some reason the X server was sending Request packets with a addresses field empty. Other Ubuntu releases are not doing this. I haven't yet investigated if why it was doing this. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Status: New => Fix Committed ** Changed in: lightdm (Ubuntu Wily) Status: New => Fix Committed ** Changed in: lightdm (Ubuntu) Importance: Undecided => Critical ** Changed in: lightdm (Ubuntu Wily) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1516831 Title: XDMCP Request packet with no addresses crashes LightDM Status in Light Display Manager: Fix Released Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Wily: Fix Committed Bug description: [Impact] If LightDM receives an XDMCP Request packet with no addresses then it will attempt to access a negative index into an array and crash. This only occurs if the XDMCP server is enabled. [Test Case] 1. Enable XDMCP in lightdm.conf: [XDMCPServer] enabled=true 2. Start LightDM 3. Send an XDMCP Request without an empty addresses field (valid XDMCP servers do not send this). Expected result: The request is ignored. Observed result: LightDM crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1516831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black
** No longer affects: hwe-next -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1381625 Title: Adjust brightness to lowest value caused screen whole black Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in Unity Settings Daemon: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Trusty: In Progress Bug description: [Impact] When adjusting screen brightness to lowest value, it turns screen backlight off. [Test Case] 1. Install Image 2. Press System's brightness hotkey to adjust the brightness level to the lowest or 3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level to the lowest 4. Check if the screen display still has backlight Expected results: There is still screen backlight Actual results: Sceen backlight is turned off [Regression Potential] None [Other Info] Ubuntu 14.04 has HWE stack lts-vivid 3.19 and it also has this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1381625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1431128] Re: screen remains blank after waking up from suspend
The attachment "adarshbug.txt" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1431128 Title: screen remains blank after waking up from suspend Status in lightdm package in Ubuntu: Confirmed Status in lightdm source package in Trusty: Confirmed Bug description: Steps: 1. Suspend the computer by pressing the Sleep key(Fn+F2 on the keyboard here) 2. Press any key on the keyboard or the Power button to wake the device up Expected results: 1. The system suspends and the Power button LED blinks 2. The system wakes up and user can log in. Actual results: 1. The system suspends and the Power button LED blinks (OK) 2. The login screen appears and the screen is immediately turned off (NOK). User needs to move the mouse or enter a key to turn the screen on. Additional information: - In a few additional occasions, after performing this action several times (pressing the Sleep key to suspend the system, then wake it up), the system freezes at log in screen just before going to suspend mode. It has to be force-stopped and restarted. - Please note that this problem does NOT happen when suspending from the User Menu or using the Power button and selecting Suspend. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Thu Mar 12 11:19:32 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2 InstallationDate: Installed on 2015-02-10 (29 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150205-07:08 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin #autologin-user=u SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1509139] Re: Shows "Chromium isn't your default browser" since 15.10.
Dear Alex, Can you please describe briefly how you reset the unity settings? Thankfully, ~ Robert -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1509139 Title: Shows "Chromium isn't your default browser" since 15.10. Status in chromium-browser package in Ubuntu: Confirmed Status in xdg-utils package in Ubuntu: Confirmed Bug description: Since the 15.10. upgrade Chromium shows on every launch "Chromium isn't your default browser", even when i select "Set as default" or "Don't ask again". Chromium is set as default application for "Web" at System Settings -> Details -> Default Applications. Version 45.0.2454.101 Ubuntu 15.10 (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1509139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1511545] Re: Implement XDMCP ForwardQuery
** Changed in: lightdm (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: lightdm (Ubuntu Trusty) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: lightdm (Ubuntu Wily) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1511545 Title: Implement XDMCP ForwardQuery Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: New Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] LightDM ignores the XDMCP ForwardQuery request. [Test Case] 1. Set up XDMCP so queries are forwarded through a server 2. Connect to LightDM Observed result: Connection fails Expected result: Connection succeeds. [Regression Potential] Some risk of existing XDMCP queries being broken by the change. Checked with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1511259] Re: Session child does not inherit all LC_* variables
** Also affects: lightdm (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Wily) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: lightdm (Ubuntu Trusty) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: lightdm (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1511259 Title: Session child does not inherit all LC_* variables Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Not all system locale variables are passed to sessions. [Test Case] 1. Edit /etc/locale.conf and set LC_PAPER to a particular value 2. Start LightDM 3. Log into a session Expected result: LC_PAPER is set to the value in /etc/locale.conf Observed result: LC_PAPER is not set. [Regression potential] Low. We just added to an existing list of LC_* variables that are passed through to sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518211] [NEW] fglrx-core 2:15.201-0ubuntu2~15.10.2: fglrx-core kernel module failed to build
Public bug reported: lsb_release -rd Description:Ubuntu 15.10 Release:15.10 apt-cache policy fglrx-core fglrx-core: Installed: 2:15.201-0ubuntu2~15.10.2 Candidate: 2:15.201-0ubuntu2~15.10.2 Version table: *** 2:15.201-0ubuntu2~15.10.2 0 500 http://nl.archive.ubuntu.com/ubuntu/ wily-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 2:15.201-0ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ wily/restricted amd64 Packages Installation comes with error Preparing to unpack fglrx-dev_15.201-0ubuntu1_amd64.deb ... Unpacking fglrx-dev (2:15.201-0ubuntu1) ... Setting up fglrx-core (2:15.201-0ubuntu1) ... Loading new fglrx-core-15.201 DKMS files... Building only for 4.2.0-18-generic Building for architecture x86_64 Building initial module for 4.2.0-18-generic Error! Bad return status for module build on kernel: 4.2.0-18-generic (x86_64) Consult /var/lib/dkms/fglrx-core/15.201/build/make.log for more information. update-initramfs: deferring update (trigger activated) Setting up fglrx-dev (2:15.201-0ubuntu1) ... Setting up fglrx (2:15.201-0ubuntu1) ... update-alternatives: warning: forcing reinstallation of alternative /usr/lib/fglrx/ld.so.conf because link group x86_64-linux-gnu_gl_conf is broken update-alternatives: warning: forcing reinstallation of alternative /usr/lib/fglrx/ld.so.conf because link group x86_64-linux-gnu_gl_conf is broken initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'gdm' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `gdm' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `gdm' Processing triggers for bamfdaemon (0.5.2~bzr0+15.10.20150627.1-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.22-1ubuntu3) ... Setting up fglrx-amdcccle (2:15.201-0ubuntu1) ... Processing triggers for systemd (225-1ubuntu9) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for gnome-menus (3.13.3-6ubuntu1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for initramfs-tools (0.120ubuntu6) ... update-initramfs: Generating /boot/initrd.img-4.2.0-18-generic ProblemType: Package DistroRelease: Ubuntu 15.10 Package: fglrx-core 2:15.201-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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 DKMSKernelVersion: 4.2.0-18-generic Date: Fri Nov 20 09:18:24 2015 DistUpgraded: 2015-11-19 11:50:41,962 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201: added virtualbox, 5.0.4, 3.19.0-33-generic, x86_64: installed virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] [1002:675d] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:2b22] InstallationDate: Installed on 2012-11-27 (1087 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Dell Inc. Vostro 470 PackageVersion: 2:15.201-0ubuntu2~15.10.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=0bda98b0-546b-4f94-98bc-8612282906f0 ro noquiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: fglrx-installer Title: fglrx-core 2:15.201-0ubuntu2~15.10.2: fglrx-core kernel module failed to build UpgradeStatus: Upgraded to wily on 2015-11-19 (0 days ago) dmi.bios.date: 09/05/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0YJPT1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/05/2012:svnDellInc.:pnVostro470:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-vi
[Desktop-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
Good point - this will be SRU'd to 14.04 LTS. ** Also affects: lightdm (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1449282 Title: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: New Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] xserver-allow-tcp=true option no longer works with X.org 1.17. [Test Case] 1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] xserver-allow-tcp=true 2. Start LightDM 3. Attempt to connect to the X server using TCP Expected result: Able to connect Observed result: Unable to connect [Regression potential] Low. X.org changed their default behaviour from listen by default to listen if "-listen tcp" is passed as a command line flag. This is just the equivalent change in LightDM. Since this is a new flag to X.org if a user was to use another X server there is a risk it would not understand that flag. However it seems unlikely since X.org is the only actively developed X server. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1449282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518035] Re: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1
Marc, do you plan to merge libjpeg-turbo with Debian? They current version includes the Conflicts required between those packages, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757860 we should at least do the same to our current version (would be nice to update as well though) ** Also affects: libjpeg-turbo (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #757860 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757860 ** Changed in: libjpeg-turbo (Ubuntu) Importance: Undecided => High ** Changed in: libjpeg-turbo (Ubuntu) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1518035 Title: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 Status in libjpeg-turbo package in Ubuntu: New Status in libjpeg9 package in Ubuntu: New Status in libjpeg9 package in Debian: Unknown Bug description: just upgrading ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 1:9a-2ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 Date: Mon Nov 16 15:38:22 2015 Dependencies: gcc-5-base 5.2.1-23ubuntu1 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-23ubuntu1 libjpeg9 1:9a-2ubuntu1 multiarch-support 2.21-0ubuntu4 DuplicateSignature: Unpacking libjpeg-progs (1:9a-2ubuntu1) over (8c-2ubuntu8) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ErrorMessage: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2014-02-24 (633 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.3ubuntu1 apt 1.0.10.2ubuntu1 SourcePackage: libjpeg9 Title: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1518035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1517991] Re: Arithmetical errors
** Changed in: gnome-calculator (Ubuntu) Importance: Undecided => High ** Changed in: gnome-calculator (Ubuntu) Status: New => Triaged ** Bug watch added: GNOME Bug Tracker #756960 https://bugzilla.gnome.org/show_bug.cgi?id=756960 ** Also affects: gnome-calculator via https://bugzilla.gnome.org/show_bug.cgi?id=756960 Importance: Unknown Status: Unknown ** Tags added: rls-x-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1517991 Title: Arithmetical errors Status in GNOME Calculator: Unknown Status in gnome-calculator package in Ubuntu: Triaged Bug description: Ubuntu release: 15.10 Package version: 1:3.16.2-1ubuntu1 Enter: 1^(−0.5) Result: 1.071508607×10³⁰¹ Expected result: 1 Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=756960 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1517991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1508718] Re: NetworkManager - error initialzing editor
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: network-manager-applet (Ubuntu) Importance: Undecided => High ** Changed in: network-manager-applet (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1508718 Title: NetworkManager - error initialzing editor Status in network-manager-applet package in Ubuntu: Incomplete Bug description: Error initializing editor settings/nm-settings-connection.c.995 - Connection didn't have requested setting 'ppp' Error occurs when attempting to edit existing mobile broadband connection. Editing existing Ethernet connections succeeds without error. This broke between 1.0.4-0ubuntu3 and 1.0.4-0ubuntu5 The connection still functions correctly but its properties can no longer be edited with gui. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager-gnome 0.9.10.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 21 23:14:57 2015 ExecutablePath: /usr/bin/nm-connection-editor IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (21 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IpRoute: default via 10.109.83.190 dev wwan0 proto static metric 750 10.109.83.188/30 dev wwan0 proto kernel scope link src 10.109.83.189 metric 750 169.254.0.0/16 dev wwan0 scope link metric 1000 IwConfig: wwan0 no wireless extensions. eno1 no wireless extensions. lono wireless extensions. JournalErrors: No journal files were found. -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH cdc-wdm0 gsm connected /org/freedesktop/NetworkManager/Devices/2 att_stick d13a7207-c11a-47ad-8876-ee62c3ccb5b2 /org/freedesktop/NetworkManager/ActiveConnection/7 eno1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/0 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1508718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1517983] Re: Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet
Thank you for your bug report. The commit message states it's needed for glib > 2.41 or trusty has glib 2.40, are you sure your issue is the same one? ** Changed in: gtk+2.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1517983 Title: Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet Status in gtk+2.0 package in Ubuntu: New Bug description: In trusty, gtk+2.0 is currently on version 2.24.23-0ubuntu. The commit specified here[1] fixes a bug where using libgtk+2.0 in an unidiomatic manner leads to a SIGABRT when starting the app. I know that unidiomatic behaviour is not supported per-se, but there are a whole bunch of "legacy" apps that are hard to update. Examples include IntelliJ IDEA, OpenXenManager, and numerous others. Is there a chance of getting libgtk+2 updated to a version that in includes [1], or getting that commit backported to trusty? The fix seems to have landed in upstream[2] and utopic[3], but not in trusty. Thanks, Claus Strasburger [1]: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=fbf38d16bcc26630f0f721d266509f5bc292f606 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758619 [3]: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1376530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1517983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330634] Re: gvfsd-smb breaks (hangs?) on resume
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1330634 Title: gvfsd-smb breaks (hangs?) on resume Status in gvfs package in Ubuntu: Confirmed Bug description: When the system returns from suspend to RAM, gvfsd-smb stops working entirely. It does not recover even after the system returns to the same network where the remote server is still available and sharing. This will sometimes cause Nautilus to hang too, but not always; not clear on the circumstances that cause that, may be time related. killing gvfsd-smb and remounting brings things back to normal operation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs-backends 1.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 16 15:03:22 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-15 (151 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140102) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1330634/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518208] [NEW] Canon LBP7200Cdn installed but won't print
You have been subscribed to a public bug: ubuntu@ubuntu:~$ ping 192.168.1.180 PING 192.168.1.180 (192.168.1.180) 56(84) bytes of data. 64 bytes from 192.168.1.180: icmp_seq=1 ttl=255 time=0.498 ms 64 bytes from 192.168.1.180: icmp_seq=2 ttl=255 time=0.396 ms 64 bytes from 192.168.1.180: icmp_seq=3 ttl=255 time=0.352 ms 64 bytes from 192.168.1.180: icmp_seq=4 ttl=255 time=0.495 ms ^C --- 192.168.1.180 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3000ms rtt min/avg/max/mdev = 0.352/0.435/0.498/0.064 ms ubuntu@ubuntu:~$ nmap 192.168.1.180 Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-20 18:06 AEST Nmap scan report for 192.168.1.180 Host is up (0.0032s latency). Not shown: 997 closed ports PORT STATE SERVICE 80/tcp open http 427/tcp open svrloc 9100/tcp open jetdirect Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds ubuntu@ubuntu:~$ /usr/lib/cups/backend/snmp network socket://192.168.1.180 "Canon LBP7200C" "Canon LBP7200C 1.02" "MFG:Canon;MDL:LBP7200C;CMD:CAPT;VER:3.0;CLS:PRINTER;DES:Canon LBP7200C" "" ubuntu@ubuntu:~$ sudo /usr/lib/cups/backenddnsd [sudo] password for ubuntu: sudo: /usr/lib/cups/backenddnsd: command not found ubuntu@ubuntu:~$ sudo /usr/lib/cups/backend/dnssd DEBUG: sent=0, count=0 DEBUG: sent=0, count=0 ubuntu@ubuntu:~$ /usr/lib/cups/backend/snmp 192.168.1.180 network socket://192.168.1.180 "Canon LBP7200C" "Canon LBP7200C 1.02" "MFG:Canon;MDL:LBP7200C;CMD:CAPT;VER:3.0;CLS:PRINTER;DES:Canon LBP7200C" "" ubuntu@ubuntu:~$ lpinfo -v network ipp14 direct ccp network lpd network socket network http network ipps network ipp network https direct hp network smb direct hpfax network socket://192.168.1.180 ubuntu@ubuntu:~$ avahi-browse -a -v -t -r Server version: avahi 0.6.31; Host name: ubuntu.local E Ifce Prot Name Type Domain + eth0 IPv6 ubuntu [08:00:27:25:b9:12]Workstation local + eth0 IPv4 ubuntu [08:00:27:25:b9:12]Workstation local = eth0 IPv6 ubuntu [08:00:27:25:b9:12]Workstation local hostname = [ubuntu.local] address = [fe80::a00:27ff:fe25:b912] port = [9] txt = [] = eth0 IPv4 ubuntu [08:00:27:25:b9:12]Workstation local hostname = [ubuntu.local] address = [192.168.1.185] port = [9] txt = [] : Cache exhausted + eth0 IPv6 linuxmint [50:e5:49:e3:00:76] Workstation local + eth0 IPv4 linuxmint [50:e5:49:e3:00:76] Workstation local = eth0 IPv6 linuxmint [50:e5:49:e3:00:76] Workstation local hostname = [linuxmint.local] address = [fe80::52e5:49ff:fee3:76] port = [9] txt = [] = eth0 IPv4 linuxmint [50:e5:49:e3:00:76] Workstation local hostname = [linuxmint.local] address = [192.168.1.110] port = [9] txt = [] + eth0 IPv4 ipcamera(id:00EA216238CE) Web Site local = eth0 IPv4 ipcamera(id:00EA216238CE) Web Site local hostname = [ipcamera_00EA216238CE.local] address = [192.168.1.210] port = [88] txt = [] + eth0 IPv6 linuxmint's remote desktop on linuxmint VNC Remote Access local + eth0 IPv6 linuxmint's remote desktop on linuxmint Web Site local + eth0 IPv6 linuxmint Remote Disk Management local + eth0 IPv4 linuxmint's remote desktop on linuxmint VNC Remote Access local + eth0 IPv4 linuxmint's remote desktop on linuxmint Web Site local + eth0 IPv4 linuxmint Remote Disk Management local = eth0 IPv6 linuxmint's remote desktop on linuxmint VNC Remote Access local hostname = [linuxmint.local] address = [fe80::52e5:49ff:fee3:76] port = [5900] txt = [] = eth0 IPv6 linuxmint's remote desktop on linuxmint Web Site local hostname = [linuxmint.local] address = [fe80::52e5:49ff:fee3:76] port = [5800] txt = [] = eth0 IPv6 linuxmint Remote Disk Management local hostname = [linuxmint.local] address = [fe80::52e5:49ff:fee3:76] port = [22] txt = [] = eth0 IPv4 linuxmint's remote desktop on linuxmint VNC Remote Access local hostname = [linuxmint.local] address = [192.168.1.110] port = [5900] txt = [] = eth0 IPv4 linuxmint's remote desktop on linuxmint Web Site local hostname = [linuxmint.local] address = [192.168.1.110] port = [5800] txt = [] = eth0 IPv4 linuxmint Remote Disk Management local hostname = [linuxmint.local] address = [192.168.1.110] port = [22] txt = [] + eth0 IPv6 Mac mini VNC Remote Access local + eth0 IPv4 Mac mini
[Desktop-packages] [Bug 1518208] Re: Canon LBP7200Cdn installed but won't print
** Package changed: compiz (Ubuntu) => cups (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1518208 Title: Canon LBP7200Cdn installed but won't print Status in cups package in Ubuntu: New Bug description: ubuntu@ubuntu:~$ ping 192.168.1.180 PING 192.168.1.180 (192.168.1.180) 56(84) bytes of data. 64 bytes from 192.168.1.180: icmp_seq=1 ttl=255 time=0.498 ms 64 bytes from 192.168.1.180: icmp_seq=2 ttl=255 time=0.396 ms 64 bytes from 192.168.1.180: icmp_seq=3 ttl=255 time=0.352 ms 64 bytes from 192.168.1.180: icmp_seq=4 ttl=255 time=0.495 ms ^C --- 192.168.1.180 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3000ms rtt min/avg/max/mdev = 0.352/0.435/0.498/0.064 ms ubuntu@ubuntu:~$ nmap 192.168.1.180 Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-20 18:06 AEST Nmap scan report for 192.168.1.180 Host is up (0.0032s latency). Not shown: 997 closed ports PORT STATE SERVICE 80/tcp open http 427/tcp open svrloc 9100/tcp open jetdirect Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds ubuntu@ubuntu:~$ /usr/lib/cups/backend/snmp network socket://192.168.1.180 "Canon LBP7200C" "Canon LBP7200C 1.02" "MFG:Canon;MDL:LBP7200C;CMD:CAPT;VER:3.0;CLS:PRINTER;DES:Canon LBP7200C" "" ubuntu@ubuntu:~$ sudo /usr/lib/cups/backenddnsd [sudo] password for ubuntu: sudo: /usr/lib/cups/backenddnsd: command not found ubuntu@ubuntu:~$ sudo /usr/lib/cups/backend/dnssd DEBUG: sent=0, count=0 DEBUG: sent=0, count=0 ubuntu@ubuntu:~$ /usr/lib/cups/backend/snmp 192.168.1.180 network socket://192.168.1.180 "Canon LBP7200C" "Canon LBP7200C 1.02" "MFG:Canon;MDL:LBP7200C;CMD:CAPT;VER:3.0;CLS:PRINTER;DES:Canon LBP7200C" "" ubuntu@ubuntu:~$ lpinfo -v network ipp14 direct ccp network lpd network socket network http network ipps network ipp network https direct hp network smb direct hpfax network socket://192.168.1.180 ubuntu@ubuntu:~$ avahi-browse -a -v -t -r Server version: avahi 0.6.31; Host name: ubuntu.local E Ifce Prot Name Type Domain + eth0 IPv6 ubuntu [08:00:27:25:b9:12]Workstation local + eth0 IPv4 ubuntu [08:00:27:25:b9:12]Workstation local = eth0 IPv6 ubuntu [08:00:27:25:b9:12]Workstation local hostname = [ubuntu.local] address = [fe80::a00:27ff:fe25:b912] port = [9] txt = [] = eth0 IPv4 ubuntu [08:00:27:25:b9:12]Workstation local hostname = [ubuntu.local] address = [192.168.1.185] port = [9] txt = [] : Cache exhausted + eth0 IPv6 linuxmint [50:e5:49:e3:00:76] Workstation local + eth0 IPv4 linuxmint [50:e5:49:e3:00:76] Workstation local = eth0 IPv6 linuxmint [50:e5:49:e3:00:76] Workstation local hostname = [linuxmint.local] address = [fe80::52e5:49ff:fee3:76] port = [9] txt = [] = eth0 IPv4 linuxmint [50:e5:49:e3:00:76] Workstation local hostname = [linuxmint.local] address = [192.168.1.110] port = [9] txt = [] + eth0 IPv4 ipcamera(id:00EA216238CE) Web Site local = eth0 IPv4 ipcamera(id:00EA216238CE) Web Site local hostname = [ipcamera_00EA216238CE.local] address = [192.168.1.210] port = [88] txt = [] + eth0 IPv6 linuxmint's remote desktop on linuxmint VNC Remote Access local + eth0 IPv6 linuxmint's remote desktop on linuxmint Web Site local + eth0 IPv6 linuxmint Remote Disk Management local + eth0 IPv4 linuxmint's remote desktop on linuxmint VNC Remote Access local + eth0 IPv4 linuxmint's remote desktop on linuxmint Web Site local + eth0 IPv4 linuxmint Remote Disk Management local = eth0 IPv6 linuxmint's remote desktop on linuxmint VNC Remote Access local hostname = [linuxmint.local] address = [fe80::52e5:49ff:fee3:76] port = [5900] txt = [] = eth0 IPv6 linuxmint's remote desktop on linuxmint Web Site local hostname = [linuxmint.local] address = [fe80::52e5:49ff:fee3:76] port = [5800] txt = [] = eth0 IPv6 linuxmint Remote Disk Management local hostname = [linuxmint.local] address = [fe80::52e5:49ff:fee3:76] port = [22] txt = [] = eth0 IPv4 linuxmint's remote desktop on linuxmint VNC Remote Access local hostname = [linuxmint.local] address = [192.168.1.110] port = [5900]
[Desktop-packages] [Bug 1515371] Re: Using search from omnibar causes Xorg to restart or crash
I turned off 'Override software rendering list' in Chrome, and the problem disappeared. Should I test it anyway? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1515371 Title: Using search from omnibar causes Xorg to restart or crash Status in xorg package in Ubuntu: Incomplete Bug description: I just happened, nothing special. Using chrome, typing into the omnibar to search on Google, and Xorg crashes. No crash on normal domain input. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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: Wed Nov 11 20:07:33 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05fe] InstallationDate: Installed on 2015-07-04 (129 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 15 9530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=904a0ffb-8477-46ae-bbb8-775512ba4e95 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Nov 11 20:03:17 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5169 vendor SHP xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1515371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510781] Re: The network manager icon is missing from the top task bar
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => smita (smitaprabhu95) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1510781 Title: The network manager icon is missing from the top task bar Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: I have recently updated from 15.04 to 15.10 , now the network manager icon is missing from the top task bar and i am not able to chose wifi networks . i tried ti open the network settings and is shows an message ' The system network services are not compatible with this version'. I am able to access internet sometimes but don't know which wi-fi I am currently connected to. I have referred online and tried to downgrade the network manager but event that didn't fixed the problem so I upgraded it back to the latest. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 09:37:16 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-13 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.48 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-27 (0 days ago) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 1: (process:4223): nmcli-CRITICAL **: Error: Could not create NMClient object: Timeout was reached. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 1: (process:4219): nmcli-CRITICAL **: Error: Could not create NMClient object: Timeout was reached. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1510781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518235] [NEW] youtube-dl is outdated
Public bug reported: 15.10 wily youtube-dl has stopped working. at the moment, there are many ExtractorErrors. This affects other packages (like mpv) that use youtube-dl to play youtube links directly, too. ** Affects: flashplugin-nonfree (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1518235 Title: youtube-dl is outdated Status in flashplugin-nonfree package in Ubuntu: New Bug description: 15.10 wily youtube-dl has stopped working. at the moment, there are many ExtractorErrors. This affects other packages (like mpv) that use youtube-dl to play youtube links directly, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1518235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
I'm using Xubuntu, yes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" Status in policykit-1-gnome package in Ubuntu: Confirmed Bug description: Every few days a dialog pops up saying "Authentication is required to change your own user data" with an entry field for a password. If I type my user's password the dialog will reappear with an empty entry field. If I click on the cross to close the window many times it will be gone, but reappear a few days later. I don't know what this window is for and it makes no difference whether I close it or leave it. I don't use the gnome keyring. This started with Ubuntu 15.04 or maybe with an earlier release, and is still there in Ubuntu 15.10, also on machines I did a fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1512002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1509139] Re: Shows "Chromium isn't your default browser" since 15.10.
i should be more precise, i reset my gnome settings like this: cd ~ rm -rf .gnome .gnome2 .gconf .gconfd .metacity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1509139 Title: Shows "Chromium isn't your default browser" since 15.10. Status in chromium-browser package in Ubuntu: Confirmed Status in xdg-utils package in Ubuntu: Confirmed Bug description: Since the 15.10. upgrade Chromium shows on every launch "Chromium isn't your default browser", even when i select "Set as default" or "Don't ask again". Chromium is set as default application for "Web" at System Settings -> Details -> Default Applications. Version 45.0.2454.101 Ubuntu 15.10 (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1509139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518242] [NEW] package fglrx 2:15.200-0ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: The computer sends me information about crashes and errors often and I seem to not be able to renew packages correctly . It seems to be a follow up error from previous package install failure ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx 2:15.200-0ubuntu0.6 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 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 Date: Fri Nov 20 10:14:08 2015 DistUpgraded: 2015-02-08 22:15:37,520 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.13.0-45-generic, x86_64: installed fglrx-core, 15.200, 3.13.0-70-generic, x86_64: installed DuplicateSignature: package:fglrx:2:15.200-0ubuntu0.6:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c600] InstallationDate: Installed on 2012-09-27 (1148 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=0bb6cfec-e01a-4799-a1e6-57d915e94293 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: fglrx-installer Title: package fglrx 2:15.200-0ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to trusty on 2015-02-08 (284 days ago) dmi.bios.date: 09/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 03PS.M505.20110929.LEO dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305U1A/305U1A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 03PS dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 305U1A dmi.product.version: 03PS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Nov 19 11:19:05 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] Synaptics Inc. Composite TouchPad / TrackPoint: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.6 xserver.video_driver: fglrx ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 need-duplicate-check package-from-proposed trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1518242 Title: package fglrx 2:15.200-0ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in fglrx-installer package in Ubuntu: New Bug description: The computer sends me information about crashes and errors often and I seem to not be able t
[Desktop-packages] [Bug 1387134] Re: when enabled nvidia graphics card, desktop freezes
** Changed in: xorg (Ubuntu) Assignee: Veereshwari S.K (kumbiveereshwari) => Meghana vk (vkmegha57) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1387134 Title: when enabled nvidia graphics card, desktop freezes Status in X.Org X server: New Status in xorg package in Ubuntu: Incomplete Bug description: Screen freezes occasionally while simply browsing the web, can be recovered by ctrl+alt+f1 and ctrl+alt+f7 This has been the case in 14.04, and it's still the case in 14.10 (64 bit) Asus UX32V 331.89-0ubuntu5 *** 331.89-0ubuntu5 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ez egy könyvtár: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: .tmp.unity.support.test.1: 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: Wed Oct 29 12:40:01 2014 DistUpgraded: 2014-10-28 11:18:50,177 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed bbswitch, 0.7, 3.16.0-24-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1507] Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507] InstallationDate: Installed on 2014-05-31 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=690e7454-2b46-48e2-9b5e-57228f67864a ro quiet splash processor.ignore_ppc=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-10-28 (1 days ago) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Oct 29 12:00:13 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4931 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1387134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1514241] Re: Update to 1.26
Laney said he would have a look to this one ** Changed in: gvfs (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1514241 Title: Update to 1.26 Status in gvfs package in Ubuntu: Triaged Bug description: Update to 1.26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1514241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1509139] Re: Shows "Chromium isn't your default browser" since 15.10.
Dear Alex, Thanks for sharing! I thought there was a GUI setting somewhere that I had missed. :) ~ Robert -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1509139 Title: Shows "Chromium isn't your default browser" since 15.10. Status in chromium-browser package in Ubuntu: Confirmed Status in xdg-utils package in Ubuntu: Confirmed Bug description: Since the 15.10. upgrade Chromium shows on every launch "Chromium isn't your default browser", even when i select "Set as default" or "Don't ask again". Chromium is set as default application for "Web" at System Settings -> Details -> Default Applications. Version 45.0.2454.101 Ubuntu 15.10 (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1509139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1509139] Re: Shows "Chromium isn't your default browser" since 15.10.
But beware, the above command will delete configuration files and you might have to reconfigure a lot of settings! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1509139 Title: Shows "Chromium isn't your default browser" since 15.10. Status in chromium-browser package in Ubuntu: Confirmed Status in xdg-utils package in Ubuntu: Confirmed Bug description: Since the 15.10. upgrade Chromium shows on every launch "Chromium isn't your default browser", even when i select "Set as default" or "Don't ask again". Chromium is set as default application for "Web" at System Settings -> Details -> Default Applications. Version 45.0.2454.101 Ubuntu 15.10 (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1509139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518269] [NEW] fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build
Public bug reported: Ubuntu 15.04 x64 When install the kernel 4.0 take this error ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.8 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 DKMSKernelVersion: 4.0.0-04rc1-generic Date: Fri Nov 20 12:12:29 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-33-generic, x86_64: installed DuplicateSignature: dkms:fglrx-core:2:15.200-0ubuntu4.2:include/generated/utsrelease.h:2:32: error: invalid suffix "rc1" on integer constant GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0464] NVIDIA Corporation GT200 [GeForce GTX 260] [10de:05e2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1257] InstallationDate: Installed on 2015-11-19 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageVersion: 2:15.200-0ubuntu4.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed root=UUID=a6dd7c57-e3fd-40b4-bf78-31055cccf027 ro quiet splash amd_iommu=on ivrs_ioapic[9]=00:14.0 vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: fglrx-installer Title: fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Card 0" Driver "fglrx" BusID "PCI:1@0:0:0" EndSection dmi.bios.date: 04/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/10/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 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.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Nov 20 12:03:15 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: fglrx(0): XMM failed to initialize AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1 xserver.video_driver: fglrx ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 need-duplicate-check ubuntu vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1518269 Title: fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build Status in fglrx-installer package in Ubuntu: New Bug description: Ubuntu 15.04 x64 When install the kernel 4.0 take this error ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-c
[Desktop-packages] [Bug 1518269] Re: fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build
Test astuce : sudo apt-get install fglrx-updates gcc-4.9 g++-4.9 sudo rm -f /usr/bin/gcc sudo rm -f /usr/bin/g++ sudo ln -s /usr/bin/gcc-4.9 /usr/bin/gcc sudo ln -s /usr/bin/g++-4.9 /usr/bin/g++ sudo apt-get --reinstall install fglrx-updates-core sudo aticonfig --initial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1518269 Title: fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build Status in fglrx-installer package in Ubuntu: New Bug description: Ubuntu 15.04 x64 When install the kernel 4.0 take this error ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.8 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 DKMSKernelVersion: 4.0.0-04rc1-generic Date: Fri Nov 20 12:12:29 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-33-generic, x86_64: installed DuplicateSignature: dkms:fglrx-core:2:15.200-0ubuntu4.2:include/generated/utsrelease.h:2:32: error: invalid suffix "rc1" on integer constant GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0464] NVIDIA Corporation GT200 [GeForce GTX 260] [10de:05e2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1257] InstallationDate: Installed on 2015-11-19 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageVersion: 2:15.200-0ubuntu4.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed root=UUID=a6dd7c57-e3fd-40b4-bf78-31055cccf027 ro quiet splash amd_iommu=on ivrs_ioapic[9]=00:14.0 vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: fglrx-installer Title: fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to build UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Card 0" Driver "fglrx" BusID "PCI:1@0:0:0" EndSection dmi.bios.date: 04/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99X EVO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/10/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 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.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Nov 20 12:03:15 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: fglrx(0): XMM failed to initialize AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file
[Desktop-packages] [Bug 1518192] Re: unity-control-center
Well i think Ubuntu snappy in 16.04 should avoid these issues. i hope. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1518192 Title: unity-control-center Status in unity-control-center package in Ubuntu: Invalid Bug description: I had a mic issue in Ubuntu 15.10 and i issued few commands to remove and reinstall pulse audio, that cause few packages to be removed and in its place gnome-center control panel got installed. so i searched ask ubuntu and found the solution by reinstalling unity control centre, which restored the control panel of ubuntu. What my take is that such things should not happen, that all operating system packages should be isolated from other system, so that any removing and installing of packages should affect this issue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-control-center 15.04.0+15.10.20150923-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 20 10:31:51 2015 InstallationDate: Installed on 2015-11-07 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1518192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1377847] Re: unity screen saver no longer blanks nor locks automatically
** Changed in: gnome-desktop3 (Ubuntu) Assignee: (unassigned) => Chintana Prabhu (chintanarp98) ** Changed in: gnome-desktop3 (Ubuntu Utopic) Assignee: (unassigned) => Chintana Prabhu (chintanarp98) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1377847 Title: unity screen saver no longer blanks nor locks automatically Status in gnome-desktop3 package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Utopic: Triaged Status in unity-settings-daemon source package in Utopic: Fix Released Bug description: After updating over the weekend the screen saver is no longer blanking or locking. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:44:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (472 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-11-10 (329 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1377847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518289] [NEW] front headphone jack recognised by alsa but ignored by pulseaudio
Public bug reported: Summary: PC has Card: HD-Audio Generic Chip: Realtek ALC887-VD Ubuntu 15.10 64-bit pulseaudio 1:6.0-0ubuntu13 - working rear audio jack connected to speakers - volume controlled from Settings>Sound>Sound Output tab. - nonworking front headphone jack - no corresponding output device in Settings>Sound>Sound Output tab. (not affected by whether or not headphones are connected at boot time) However front headphone jack is visible (muted) in alsamixer, and volume can be unmuted and raised in current session - returns to muted on reboot. Detail: This desktop PC was previously running trusty with front headphone jack working normally - if audio on rear jack there was audio in headphones. I do not remember now whether the audio volume was separately controlled as a second output device, either would have worked fine for me. Fresh install of wily on a new disk resulted in working rear audio jack, but non-working front headphone jack. The ubuntu Settings>Sound Output tab shows only one device for sound output: "Line Out - Built-in Audio". My expectation is that the volume level of the headphone jack should initially be set to a non-zero level. After exploring various options, I discovered that the front headphone jack is visible in alsamixer but displayed as level 0 and muted. It can be made to work in the current session by unmuting and setting to a non- zero level. Adjusting volume and balance in the ubuntu Settings>Sound Output tab affects the audio output levels to the headphone jack in the way one might expect, but when the settings are changed while alsamixer is open (eg left right balance), the vertical bars for the headphone level do not move as they do for all other output jacks. But when the surround sound profile is changed in the Settings>Sound Output tab, both actual headphone volume and headphone volume bars in alsamixer drop to 0 with muting. In any event, on reboot the jack is muted again and needs to be reset in alsamixer. Following online advice, I unsuccessfully tried various ways to make the unmuted settings survive a reboot - eg running alsamixer under sudo, alsactl store. Eventually I looked at the contents of the /var/lib/alsa/asound.state file and realised that the unmuted state was properly set in the file and was unchanged on reboot. The muting was being caused by pulseaudio. I was able to verify this by unmuting in alsamixer and restarting pulseaudio without rebooting - the output was muted again. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jane 1189 F pulseaudio jane 1491 F alsamixer /dev/snd/controlC0: jane 1189 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 20 20:26:26 2015 InstallationDate: Installed on 2015-11-17 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FM2-A75MA-E35 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd09/24/2012:svnMSI:pnMS-7721:pvr1.0:rvnMSI:rnFM2-A75MA-E35(MS-7721):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7721 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1518289 Title: front headphone jack recognised by alsa but ignored by pulseaudio Status in pulseaudio package in Ubuntu: New Bug description: Summary: PC has Card: HD-Audio Generic Chip: Realtek ALC887-VD Ubuntu 15.10 64-bit pulseaudio 1:6.0-0ubuntu13 - working rear audio jack connected to speakers - volume controlled from Settings>Sound>Sound Output tab. - nonworking front headphone jack - no corresponding output device in Settings>Sound>Sound Output tab. (not affected by whether or not headphones are connected at boot time) However front headphone jack is visible (muted) in alsamixer, and volume can be unmuted and raised in current session - returns to muted on reboot. Detail: This desktop PC was previously running trusty with front headphone jack working normally - if audio on rear jack ther
[Desktop-packages] [Bug 882040] Re: should let users enable or disable suspend and hibernate
** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Chintana Prabhu (chintanarp98) ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/882040 Title: should let users enable or disable suspend and hibernate Status in Ayatana Design: Fix Committed Status in gnome-control-center package in Ubuntu: In Progress Status in Baltix: Confirmed Bug description: We should have an ui in the power capplet for that: https://wiki.ubuntu.com/Power#Power_settings The corresponding task for other desktop environments that do not use the GNOME control center: Kubuntu/Lubuntu bug #976654 Xubuntu bug #1271169 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/882040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1438755] Re: Screenshot application not working 15.04 beta 2
** Changed in: gnome-screenshot (Ubuntu) Assignee: (unassigned) => zakir husain (mohammedzakirhusain) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1438755 Title: Screenshot application not working 15.04 beta 2 Status in gnome-screenshot package in Ubuntu: New Bug description: None of the following methods of taking screenshots seem to work on 15.04 default installation. 1. Grab the whole screen 2. Grab the current window 3. Select area to grab Using the PrintScreen button, which defaults to option 1 produces same result. Screenshot is taken but seems to only take screenshot of lock screen wallpaper and not anything that is actually on the screen. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-screenshot 3.14.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 31 17:27:54 2015 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2015-03-31 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1438755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1505904] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1505904 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Confirmed Bug description: Just started my Gnome Ubuntu box. After logging in, this error surfaced. In the 'report a problem' interface, it showed me the Xorg error. However I think this might has to do with Compiz. I noticed the following message in the error summary display: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'. Then I searched the problem on the internet. Found a post which I thought was a good starting point for the investigation: http://askubuntu.com/questions/74313/list-and-enable-disable-compiz-plugins-on-command-line Turns out compiz is not even installed, i checked this with aptitude. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: xserver-xorg-core 2:1.17.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 CurrentDesktop: GNOME Date: Tue Oct 13 17:13:16 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2ade] InstallationDate: Installed on 2015-09-18 (25 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150915) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Compaq Pro 4300 SFF PC ProcCmdline: /usr/bin/X vt7 -displayfd 3 -auth /run/user/120/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=018176c1-88ee-46b1-be76-dfc1466d72c4 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () FatalError () ?? () xf86CloseConsole () ddxGiveUp () Title: Xorg crashed with SIGABRT in OsAbort() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/23/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.10 dmi.board.asset.tag: CZC3211FPH dmi.board.name: 2ADE dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.0 dmi.chassis.asset.tag: CZC3211FPH dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.10:bd01/23/2013:svnHewlett-Packard:pnHPCompaqPro4300SFFPC:pvr:rvnHewlett-Packard:rn2ADE:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP Compaq Pro 4300 SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Oct 14 06:50:54 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputMicrosoft Microsoft 3-Button Mouse with IntelliEye(TM) MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1505904/+s
[Desktop-packages] [Bug 1518310] [NEW] no sound through headphones after boot
Public bug reported: After Ubuntu boots, randomly (say with 25% probability) the Headphone alsamixer setting will be muted and set to 0 on my notebook. The notebook will not play any sounds on headphones, only through the notebook speakers when headphones are disconnected. I then have to manually run alsamixer, unmute the Headphone setting and max it out to 100. This started to happen after upgrade to Ubuntu 15.10 - Ubuntu 15.04 worked fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vyzivus2444 F pulseaudio /dev/snd/pcmC0D0p: vyzivus2444 F...m pulseaudio /dev/snd/controlC0: vyzivus2444 F pulseaudio vyzivus6270 F alsamixer CurrentDesktop: Unity Date: Fri Nov 20 13:45:18 2015 InstallationDate: Installed on 2014-03-07 (622 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to wily on 2015-10-08 (43 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 029M77 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.name: XPS L521X dmi.product.version: A16 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1518310 Title: no sound through headphones after boot Status in alsa-driver package in Ubuntu: New Bug description: After Ubuntu boots, randomly (say with 25% probability) the Headphone alsamixer setting will be muted and set to 0 on my notebook. The notebook will not play any sounds on headphones, only through the notebook speakers when headphones are disconnected. I then have to manually run alsamixer, unmute the Headphone setting and max it out to 100. This started to happen after upgrade to Ubuntu 15.10 - Ubuntu 15.04 worked fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vyzivus2444 F pulseaudio /dev/snd/pcmC0D0p: vyzivus2444 F...m pulseaudio /dev/snd/controlC0: vyzivus2444 F pulseaudio vyzivus6270 F alsamixer CurrentDesktop: Unity Date: Fri Nov 20 13:45:18 2015 InstallationDate: Installed on 2014-03-07 (622 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to wily on 2015-10-08 (43 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 029M77 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.name: XPS L521X dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1518310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518310] Re: no sound through headphones after boot
** Attachment added: "Screenshot of the alsamixer with the Headphones setting initially muted and set to 0." https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1518310/+attachment/4522596/+files/Screenshot%20from%202015-11-20%2013-44-34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1518310 Title: no sound through headphones after boot Status in alsa-driver package in Ubuntu: New Bug description: After Ubuntu boots, randomly (say with 25% probability) the Headphone alsamixer setting will be muted and set to 0 on my notebook. The notebook will not play any sounds on headphones, only through the notebook speakers when headphones are disconnected. I then have to manually run alsamixer, unmute the Headphone setting and max it out to 100. This started to happen after upgrade to Ubuntu 15.10 - Ubuntu 15.04 worked fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vyzivus2444 F pulseaudio /dev/snd/pcmC0D0p: vyzivus2444 F...m pulseaudio /dev/snd/controlC0: vyzivus2444 F pulseaudio vyzivus6270 F alsamixer CurrentDesktop: Unity Date: Fri Nov 20 13:45:18 2015 InstallationDate: Installed on 2014-03-07 (622 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to wily on 2015-10-08 (43 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 029M77 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.name: XPS L521X dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1518310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510676] Re: package sane-utils 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 8
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1510676 Title: package sane-utils 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 8 Status in sane-backends package in Ubuntu: Confirmed Bug description: Encountered during upgrade from Vivid to Wily (15.04 to 15.10) ProblemType: Package DistroRelease: Ubuntu 15.10 Package: sane-utils 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Thu Oct 22 22:07:26 2015 DuplicateSignature: package:sane-utils:1.0.25+git20150528-1ubuntu2:subprocess installed post-installation script returned error exit status 8 ErrorMessage: subprocess installed post-installation script returned error exit status 8 InstallationDate: Installed on 2013-03-02 (964 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: sane-backends Title: package sane-utils 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 8 UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago) mtime.conffile..etc.default.saned: 2015-04-28T00:00:59.104233 mtime.conffile..etc.sane.d.saned.conf: 2013-09-09T00:21:31.828295 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1510676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 673370] Re: Power manager status icon
** Changed in: gnome-power-manager (Ubuntu) Assignee: (unassigned) => Sushmita (sush-patil-mita) ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/673370 Title: Power manager status icon Status in gnome-power-manager package in Ubuntu: Fix Committed Bug description: Binary package hint: gedit Power manager status icon in the Notification Applet does not switch from AC power to Battery when unplugged, although the screen dims. Since it still shows as AC power, it does not show an estimate of battery time left. If it is unplugged at login, it will switch to AC power status when plugged in, but not back if unplugged again. A work around for this is to add the add the following line in /etc/rc.local before the exit 0 line /etc/init.d/laptop-mode start service laptop-mode status I folow those steps but the system does not let me apply the changes because I dont have administrtion rights. ProblemType: Bug Architecture: i386 CheckboxSubmission: 06358a083ff377d68ab3757deb91576b CheckboxSystem: 5a0b5a7a81cebbedee8b5ecfa0917a78 Date: Wed Nov 10 08:26:16 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/gedit Package: gedit 2.28.0-0ubuntu2 ProcEnviron: LANG=el_GR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-22.68-generic SourcePackage: gedit Tags: ubuntu-unr Uname: Linux 2.6.31-22-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/673370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1168746] Re: power indicator icon mismatch with battery level when charging
** Description changed: - Since Ubuntu 12.10 there are more than one power indicator icon for battery to show "battery level" during charging process while connected to AC adapter. This battery level never works correctly. - When charging, this icon is expected to change to show how full the battery is, ranging for 20, 40, 60, 80, and 100. But it always shows 20 until is fully charged then it shows 100. + Since Ubuntu 14.04 LTS there are more than one power indicator icon for battery to show "battery level" during charging process while connected to AC adapter. This battery level never works correctly. + When charging, this icon is expected to change to show how full the battery is, ranging for 20, 40, 60, 80, and 100. But it always shows 20 The battery level should change during charging, but it is still on 20%. ** Description changed: - Since Ubuntu 14.04 LTS there are more than one power indicator icon for battery to show "battery level" during charging process while connected to AC adapter. This battery level never works correctly. + In Ubuntu 14.04 LTS, the battery level never works correctly. When charging, this icon is expected to change to show how full the battery is, ranging for 20, 40, 60, 80, and 100. But it always shows 20 The battery level should change during charging, but it is still on 20%. ** Changed in: gnome-power-manager (Ubuntu) Assignee: (unassigned) => Sushmita (sush-patil-mita) ** Summary changed: - power indicator icon mismatch with battery level when charging + Battery icon not working in Ubuntu 14.04 LTS ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1168746 Title: Battery icon not working in Ubuntu 14.04 LTS Status in gnome-power: New Status in gnome-power-manager package in Ubuntu: Fix Committed Bug description: In Ubuntu 14.04 LTS, the battery level never works correctly. When charging, this icon is expected to change to show how full the battery is, ranging for 20, 40, 60, 80, and 100. But it always shows 20 The battery level should change during charging, but it is still on 20%. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1168746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510676] Re: package sane-utils 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 8
Is this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774941 ? Sounds very much like it except that that bug was fixed in 1.0.24-9. Quite possibly the fix is incomplete when updating from a broken version. ** Bug watch added: Debian Bug tracker #774941 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774941 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1510676 Title: package sane-utils 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 8 Status in sane-backends package in Ubuntu: Confirmed Bug description: Encountered during upgrade from Vivid to Wily (15.04 to 15.10) ProblemType: Package DistroRelease: Ubuntu 15.10 Package: sane-utils 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Thu Oct 22 22:07:26 2015 DuplicateSignature: package:sane-utils:1.0.25+git20150528-1ubuntu2:subprocess installed post-installation script returned error exit status 8 ErrorMessage: subprocess installed post-installation script returned error exit status 8 InstallationDate: Installed on 2013-03-02 (964 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: sane-backends Title: package sane-utils 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 8 UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago) mtime.conffile..etc.default.saned: 2015-04-28T00:00:59.104233 mtime.conffile..etc.sane.d.saned.conf: 2013-09-09T00:21:31.828295 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1510676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1326954] Re: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate
It gives an overview about whats happening and why this solution works. (the dell device is an em7305) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Confirmed Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwan0 (net)' - Numbers | own
[Desktop-packages] [Bug 1510824]
Perfect. Committed, thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1510824 Title: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas) Status in PolicyKit: Fix Released Status in policykit-1 package in Ubuntu: New Status in policykit-1 source package in Trusty: New Status in policykit-1 source package in Vivid: New Status in policykit-1 source package in Wily: New Bug description: There is an error observed when Ubuntu is configured to perform authentication via pam_vas (Vintela Authentication Services by Dell) in a disconnected mode (using cached authentication). Steps to reproduce: 1. Configure pam_vas client authenticating to a remote server. 2. Perform authentication to cache the credentials. 3. Disconnect from the network where the server is reachable (to force using cached information). 4. Perform an action requiring polkit authentication. Expected result: Authentication succeeds accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Actual result: Authentication fails accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Probable cause: The PolkitAgentSession part of polkit is designed to interpret only 1-line output, while interaction with pam_vas in the above scenario triggers helper to produce the following 2-line output: PAM_TEXT_INFO You have logged in using cached account information. Some network services will be unavailable. The 'will be unavailable.' part is interpreted as an unknown message and causes failed authorization. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 09:01:37 2015 InstallationDate: Installed on 2015-04-13 (197 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1510824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510824]
Created attachment 119702 Refactoring to use send_to_helper -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1510824 Title: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas) Status in PolicyKit: Fix Released Status in policykit-1 package in Ubuntu: New Status in policykit-1 source package in Trusty: New Status in policykit-1 source package in Vivid: New Status in policykit-1 source package in Wily: New Bug description: There is an error observed when Ubuntu is configured to perform authentication via pam_vas (Vintela Authentication Services by Dell) in a disconnected mode (using cached authentication). Steps to reproduce: 1. Configure pam_vas client authenticating to a remote server. 2. Perform authentication to cache the credentials. 3. Disconnect from the network where the server is reachable (to force using cached information). 4. Perform an action requiring polkit authentication. Expected result: Authentication succeeds accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Actual result: Authentication fails accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Probable cause: The PolkitAgentSession part of polkit is designed to interpret only 1-line output, while interaction with pam_vas in the above scenario triggers helper to produce the following 2-line output: PAM_TEXT_INFO You have logged in using cached account information. Some network services will be unavailable. The 'will be unavailable.' part is interpreted as an unknown message and causes failed authorization. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 09:01:37 2015 InstallationDate: Installed on 2015-04-13 (197 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1510824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)
** Changed in: policykit-1 Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1510824 Title: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas) Status in PolicyKit: Fix Released Status in policykit-1 package in Ubuntu: New Status in policykit-1 source package in Trusty: New Status in policykit-1 source package in Vivid: New Status in policykit-1 source package in Wily: New Bug description: There is an error observed when Ubuntu is configured to perform authentication via pam_vas (Vintela Authentication Services by Dell) in a disconnected mode (using cached authentication). Steps to reproduce: 1. Configure pam_vas client authenticating to a remote server. 2. Perform authentication to cache the credentials. 3. Disconnect from the network where the server is reachable (to force using cached information). 4. Perform an action requiring polkit authentication. Expected result: Authentication succeeds accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Actual result: Authentication fails accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Probable cause: The PolkitAgentSession part of polkit is designed to interpret only 1-line output, while interaction with pam_vas in the above scenario triggers helper to produce the following 2-line output: PAM_TEXT_INFO You have logged in using cached account information. Some network services will be unavailable. The 'will be unavailable.' part is interpreted as an unknown message and causes failed authorization. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 09:01:37 2015 InstallationDate: Installed on 2015-04-13 (197 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1510824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1517015] Re: Please sync jansson 2.7-3 from Debian testing
This bug was fixed in the package jansson - 2.7-3 Sponsored for Łukasz Zemczak (sil2100) --- jansson (2.7-3) unstable; urgency=medium * Always build the documentation (Closes: #789675) -- Alessandro Ghedini Tue, 23 Jun 2015 13:11:09 +0200 jansson (2.7-2) unstable; urgency=medium * Use dh_sphinxdoc before installing documentation (Closes: #769327) * Bump Standards-Version to 3.9.6 (no changes needed) -- Alessandro Ghedini Mon, 22 Jun 2015 14:42:51 +0200 ** Changed in: jansson (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1517015 Title: Please sync jansson 2.7-3 from Debian testing Status in jansson package in Ubuntu: Fix Released Bug description: The ubuntu changes are no longer required, the backbone dependency is no longer present. The package builds fine on current Ubuntu (xenial): https://launchpad.net/~sil2100/+archive/ubuntu/testing/+build/8309054 The Ubuntu changes can be safely overwritten. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1517015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start or freezes with systemd + lightdm
Meanwhile, I've upgraded to 15.10. Now the system _mostly_ works, but let's say about every 5th boot the system freezes with black screen if systemd is used. Upstart always work. Interestingly in most cases systemd works as well, but not always. I cannot find any reason about this always changing behaviour if I try to boot multiple times. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start or freezes with systemd + lightdm Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 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 CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 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.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1517058] Re: network manager does not connect to AP anymore
downgrading the respective firmware to an older release helped. the system was loading iwlwifi-7260-15.ucode which seemed to be the source of trouble. Removing any firmware but iwlwifi-7260-10.ucode allows me to reliably connect to my network again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1517058 Title: network manager does not connect to AP anymore Status in network-manager package in Ubuntu: New Bug description: network manager does not connect to my AP anymore, tries to authenticate and then asks for a password (of a previously connected wifi network). Upon entering the right password manually and/or verifying the stored password is correct the connection still fails. I have not been able to get a concise list of actions that get me connected, but a wild mix of: rmmod iwlmvm iwlwifi modprobe iwlmvm iwlwifi killall wpa_supplicant iwlist scanning (dis-/enabling networking in NWmgr) (dis-/enabling wifi in NWmgr) gets me back online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1517058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 750497] Re: Workspace switcher has no quicklist
** Changed in: unity Status: Invalid => In Progress ** Changed in: unity (Ubuntu) Status: Invalid => In Progress ** Changed in: unity Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity Milestone: None => 7.4.0 ** Changed in: unity (Ubuntu) Milestone: None => ubuntu-16.04 ** Tags added: rls-x-incoming ** Branch linked: lp:~3v1n0/unity/expo-icon-quicklist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/750497 Title: Workspace switcher has no quicklist Status in Ayatana Design: Invalid Status in Unity: In Progress Status in unity-2d: Invalid Status in unity package in Ubuntu: In Progress Status in unity-2d package in Ubuntu: Invalid Bug description: Binary package hint: unity This is the only Unity launcher item with no right-click quicklist. To me it seems important to have consistency. Though of course we know that we shouldn't just add things for the sake of it. I don't know if added "Switch to Workspace X" options is considered a good idea? ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,regex,vpswitch,move,animation,imgpng,mousepoll,grid,unitymtgrabhandles,gnomecompat,place,workarounds,wall,wobbly,expo,ezoom,staticswitcher,session,fade,scale,unityshell] Date: Mon Apr 4 18:06:36 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110127) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to natty on 2011-03-09 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/750497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) => Tony Espy (awe) ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => High ** Changed in: qtbase-opensource-src (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices Status in Canonical System Image: Confirmed Status in Unity 8: New Status in dbus-cpp package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: In Progress Status in buteo-syncfw package in Ubuntu RTM: New Status in location-service package in Ubuntu RTM: In Progress Status in maliit-framework package in Ubuntu RTM: New Status in network-manager package in Ubuntu RTM: Incomplete Status in sync-monitor package in Ubuntu RTM: New Bug description: Krillin, rc-proposed, r83 DESCRIPTION: I've been trying to track down the cause of the occasional UI freezes on my Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor Here's a log of what's shown in dbus-monitor: http://pastebin.ubuntu.com/11992322/ I'd guess the problem is in the code that actually catches the signals and acts accordingly. HOW TO REPRODUCE: 1) Move to a place where many wifi hotspots are available 2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor" 3) Use the device while keeping an eye on dbus-monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)
Added SRU proposal for wily. ** Patch added: "wily_policykit-1_0.105-11ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+attachment/4522624/+files/wily_policykit-1_0.105-11ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1510824 Title: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas) Status in PolicyKit: Fix Released Status in policykit-1 package in Ubuntu: New Status in policykit-1 source package in Trusty: New Status in policykit-1 source package in Vivid: New Status in policykit-1 source package in Wily: New Bug description: [Impact] * Some PAM modules produce output of more than 1 line (e.g. PAM_TEXT_INFO may contain newlines in the message content). Polkit authentication agent is prepared to receive only single-line messages so it treats each line as a separate message. It fails to recognize the type of message for all of them except the first - hence failed authorization even if it was successful on the PAM-level. * The PAM specification does not require the modules to send only single-line messages. Thus, polkit needs to be fixed. * The helper component should escape (g_strescape) all messages before sending it up to the authentication agent. This way everything will be read as a single line and then unescaped to restore it's formatting with no changes required in PAM modules. [Test Case] * Use a pam module that returns a multi-line PAM_TEXT_INFO message on successful authentication (may require to artificially modify a pam module). * Perform a polkit authorization with e.g. pkexec ls * Correct authorization should end with a failure with an unrecognized PAM message [Regression Potential] * Fix makes advantage of the fact that polkit authentication agent already un-escapess (g_strcompress) all input from the helper component. * Fix is a backport of an upstream change. [Other Info] * Original bug description: There is an error observed when Ubuntu is configured to perform authentication via pam_vas (Vintela Authentication Services by Dell) in a disconnected mode (using cached authentication). Steps to reproduce: 1. Configure pam_vas client authenticating to a remote server. 2. Perform authentication to cache the credentials. 3. Disconnect from the network where the server is reachable (to force using cached information). 4. Perform an action requiring polkit authentication. Expected result: Authentication succeeds accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Actual result: Authentication fails accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Probable cause: The PolkitAgentSession part of polkit is designed to interpret only 1-line output, while interaction with pam_vas in the above scenario triggers helper to produce the following 2-line output: PAM_TEXT_INFO You have logged in using cached account information. Some network services will be unavailable. The 'will be unavailable.' part is interpreted as an unknown message and causes failed authorization. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 09:01:37 2015 InstallationDate: Installed on 2015-04-13 (197 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1510824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)
Added SRU proposal for Xenial. ** Description changed: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + + * Use a pam module that returns a multi-line PAM_TEXT_INFO message on + successful authentication (may require to artificially modify a pam + module). + + * Perform a polkit authorization with e.g. pkexec ls + + * Correct authorization should end with a failure with an unrecognized + PAM message + + [Regression Potential] + + * Fix makes advantage of the fact that polkit authentication agent + already un-escapess (g_strcompress) all input from the helper component. + + * Fix is a backport of an upstream change. + + [Other Info] + + * Original bug description: + There is an error observed when Ubuntu is configured to perform authentication via pam_vas (Vintela Authentication Services by Dell) in a disconnected mode (using cached authentication). Steps to reproduce: 1. Configure pam_vas client authenticating to a remote server. 2. Perform authentication to cache the credentials. 3. Disconnect from the network where the server is reachable (to force using cached information). 4. Perform an action requiring polkit authentication. Expected result: Authentication succeeds accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Actual result: Authentication fails accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Probable cause: The PolkitAgentSession part of polkit is designed to interpret only 1-line output, while interaction with pam_vas in the above scenario triggers helper to produce the following 2-line output: PAM_TEXT_INFO You have logged in using cached account information. Some network services will be unavailable. The 'will be unavailable.' part is interpreted as an unknown message and causes failed authorization. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 09:01:37 2015 InstallationDate: Installed on 2015-04-13 (197 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Impact] - * An explanation of the effects of the bug on users and + * Some PAM modules produce output of more than 1 line (e.g. + PAM_TEXT_INFO may contain newlines in the message content). Polkit + authentication agent is prepared to receive only single-line messages so + it treats each line as a separate message. It fails to recognize the + type of message for all of them except the first - hence failed + authorization even if it was successful on the PAM-level. - * justification for backporting the fix to the stable release. + * The PAM specification does not require the modules to send only + single-line messages. Thus, polkit needs to be fixed. - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + * The helper component should escape (g_strescape) all messages before + sending it up to the authentication agent. This way everything will be + read as a single line and then unescaped to restore it's formatting with + no changes required in PAM modules. [Test Case] - * Use a pam module that returns a multi-line PAM_TEXT_INFO message on + * Use a pam module that returns a multi-line PAM_TEXT_INFO message on successful authentication (may require to artificially modify a pam module). - * Perform a polkit authorization with e.g. pkexec ls + * Perform a polkit authorization with e.g. pkexec ls - * Correct authorization should end with a failure with an unrecognized + * Correct authorization should end with a failure with an unrecognized PAM message [Regression Potential] - * Fix makes advantage of the fact that polkit authentication agent + * Fix makes advantage of the fact that polkit authentication agent already un-escapess (g_strcompress) all input from the helper component. * Fix is a backport of an upstream change. [Other Info] - - * Original bug description: + + * Original bug description: There is an error observed when Ubuntu is configured to perform authentication via pam_vas (Vintela Authentication Services by Dell) in a disconnected mode
[Desktop-packages] [Bug 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)
Added SRU proposal for trusty. ** Patch added: "trusty_policykit-1_0.105-4ubuntu3.14.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+attachment/4522626/+files/trusty_policykit-1_0.105-4ubuntu3.14.04.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1510824 Title: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas) Status in PolicyKit: Fix Released Status in policykit-1 package in Ubuntu: New Status in policykit-1 source package in Trusty: New Status in policykit-1 source package in Vivid: New Status in policykit-1 source package in Wily: New Bug description: [Impact] * Some PAM modules produce output of more than 1 line (e.g. PAM_TEXT_INFO may contain newlines in the message content). Polkit authentication agent is prepared to receive only single-line messages so it treats each line as a separate message. It fails to recognize the type of message for all of them except the first - hence failed authorization even if it was successful on the PAM-level. * The PAM specification does not require the modules to send only single-line messages. Thus, polkit needs to be fixed. * The helper component should escape (g_strescape) all messages before sending it up to the authentication agent. This way everything will be read as a single line and then unescaped to restore it's formatting with no changes required in PAM modules. [Test Case] * Use a pam module that returns a multi-line PAM_TEXT_INFO message on successful authentication (may require to artificially modify a pam module). * Perform a polkit authorization with e.g. pkexec ls * Correct authorization should end with a failure with an unrecognized PAM message [Regression Potential] * Fix makes advantage of the fact that polkit authentication agent already un-escapess (g_strcompress) all input from the helper component. * Fix is a backport of an upstream change. [Other Info] * Original bug description: There is an error observed when Ubuntu is configured to perform authentication via pam_vas (Vintela Authentication Services by Dell) in a disconnected mode (using cached authentication). Steps to reproduce: 1. Configure pam_vas client authenticating to a remote server. 2. Perform authentication to cache the credentials. 3. Disconnect from the network where the server is reachable (to force using cached information). 4. Perform an action requiring polkit authentication. Expected result: Authentication succeeds accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Actual result: Authentication fails accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Probable cause: The PolkitAgentSession part of polkit is designed to interpret only 1-line output, while interaction with pam_vas in the above scenario triggers helper to produce the following 2-line output: PAM_TEXT_INFO You have logged in using cached account information. Some network services will be unavailable. The 'will be unavailable.' part is interpreted as an unknown message and causes failed authorization. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 09:01:37 2015 InstallationDate: Installed on 2015-04-13 (197 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1510824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)
Added SRU proposal for vivid. ** Patch added: "vivid_policykit-1_0.105-8ubuntu5.debdiff" https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+attachment/4522625/+files/vivid_policykit-1_0.105-8ubuntu5.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1510824 Title: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas) Status in PolicyKit: Fix Released Status in policykit-1 package in Ubuntu: New Status in policykit-1 source package in Trusty: New Status in policykit-1 source package in Vivid: New Status in policykit-1 source package in Wily: New Bug description: [Impact] * Some PAM modules produce output of more than 1 line (e.g. PAM_TEXT_INFO may contain newlines in the message content). Polkit authentication agent is prepared to receive only single-line messages so it treats each line as a separate message. It fails to recognize the type of message for all of them except the first - hence failed authorization even if it was successful on the PAM-level. * The PAM specification does not require the modules to send only single-line messages. Thus, polkit needs to be fixed. * The helper component should escape (g_strescape) all messages before sending it up to the authentication agent. This way everything will be read as a single line and then unescaped to restore it's formatting with no changes required in PAM modules. [Test Case] * Use a pam module that returns a multi-line PAM_TEXT_INFO message on successful authentication (may require to artificially modify a pam module). * Perform a polkit authorization with e.g. pkexec ls * Correct authorization should end with a failure with an unrecognized PAM message [Regression Potential] * Fix makes advantage of the fact that polkit authentication agent already un-escapess (g_strcompress) all input from the helper component. * Fix is a backport of an upstream change. [Other Info] * Original bug description: There is an error observed when Ubuntu is configured to perform authentication via pam_vas (Vintela Authentication Services by Dell) in a disconnected mode (using cached authentication). Steps to reproduce: 1. Configure pam_vas client authenticating to a remote server. 2. Perform authentication to cache the credentials. 3. Disconnect from the network where the server is reachable (to force using cached information). 4. Perform an action requiring polkit authentication. Expected result: Authentication succeeds accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Actual result: Authentication fails accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Probable cause: The PolkitAgentSession part of polkit is designed to interpret only 1-line output, while interaction with pam_vas in the above scenario triggers helper to produce the following 2-line output: PAM_TEXT_INFO You have logged in using cached account information. Some network services will be unavailable. The 'will be unavailable.' part is interpreted as an unknown message and causes failed authorization. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 09:01:37 2015 InstallationDate: Installed on 2015-04-13 (197 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1510824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1482616] Re: yoga 3 screen rotation does not work
Hi, it can be; the system reports it by itself until its solved, probably. thanks! On cs, nov 19, 2015 at 3:59 , Kai Petzke wrote: > Is this a duplicate of Bug #1484039 ? > > -- > You received this bug notification because you are subscribed to the > bug > report. > https://bugs.launchpad.net/bugs/1482616 > > Title: > yoga 3 screen rotation does not work > > Status in xorg package in Ubuntu: > New > > Bug description: > Dear Developers, > > I bought a lenovo yoga 3 and installed u15.04. The screen rotation > of > the touch screen does not work. I can flip the monitor back, touch > screen sensitivity works, but it does not switch screens from > vertical > to horizontal. > > please help, > many thanks > > ProblemType: Bug > DistroRelease: Ubuntu 15.04 > Package: xorg 1:7.7+7ubuntu4 > ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 > Uname: Linux 3.19.0-25-generic x86_64 > NonfreeKernelModules: wl > .tmp.unity.support.test.0: > > ApportVersion: 2.17.2-0ubuntu1.1 > 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 > Date: Fri Aug 7 13:30:46 2015 > DistUpgraded: Fresh install > DistroCodename: vivid > DistroVariant: ubuntu > DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-25-generic, x86_64: > installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev > 09) (prog-if 00 [VGA controller]) > Subsystem: Lenovo Device [17aa:3906] > InstallationDate: Installed on 2015-07-27 (10 days ago) > InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 > (20150422) > MachineType: LENOVO 80HE > ProcKernelCmdLine: > BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed > root=UUID=4fff414d-6c5a-4304-bdda-4c1932e1cafd ro quiet splash > vt.handoff=7 > SourcePackage: xorg > UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/29/2015 > dmi.bios.vendor: LENOVO > dmi.bios.version: A6CN50WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: VIUU4 > dmi.board.vendor: LENOVO > dmi.board.version: 31900058 WIN > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Lenovo YOGA 3 Pro-1370 > dmi.modalias: > dmi:bvnLENOVO:bvrA6CN50WW:bd04/29/2015:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370: > dmi.product.name: 80HE > dmi.product.version: Lenovo YOGA 3 Pro-1370 > dmi.sys.vendor: LENOVO > version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.60-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental > N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 > 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.5.0-1ubuntu2 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917-1~exp1ubuntu2.2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.11-1ubuntu2build1 > xserver.bootTime: Fri Aug 7 10:28:02 2015 > xserver.configfile: default > xserver.errors: [dix] ATML1000:00 03EB:8A10: unable to find touch > point 0 > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: >product id 17226 >vendor SDC > xserver.version: 2:1.17.1-0ubuntu3 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482616/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1482616 Title: yoga 3 screen rotation does not work Status in xorg package in Ubuntu: New Bug description: Dear Developers, I bought a lenovo yoga 3 and installed u15.04. The screen rotation of the touch screen does not work. I can flip the monitor back, touch screen sensitivity works, but it does not switch screens from vertical to horizontal. please help, many thanks ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/
[Desktop-packages] [Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration
** Changed in: vino (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/984093 Title: vino http server binds to external interfaces despite local_only configuration Status in vino: Fix Released Status in vino package in Ubuntu: Fix Committed Bug description: Environment: Debian Wheezy Vino 3.2.2-1+b1 Vino is configured for local access only via: gconftool-2 --set /desktop/gnome/remote_access/local_only --type bool true Vino's vnc server is only listening on localhost:5900 and no other interfaces - as expected. Vino's http server, though, is listening on all interfaces, despite the local_only configuration. The expected behaviour would be for all vino services, including the http server, to only bind to the localhost interface when configured accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/984093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1462183] Re: Nautilus "Enter Location" Stops Working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1462183 Title: Nautilus "Enter Location" Stops Working Status in nautilus package in Ubuntu: Confirmed Bug description: Earlier, I had been able to use CTRL-L for "Enter Location" and it worked. At some point I had pressed ESC to revert back to the button- based paths. Later on, with that same window open, I came back and tried CTRL-L and the path didn't switch back to the textbox. Even going to "Go"->"Enter Location" did nothing. While writing this up, I did a test by closing that window, then opening a new "Files" window and CTRL-L worked right off the bat. This wasn't my first experience with that "bug", but enough times for me to finally submit it when it happened. Hopefully the data submitted will provide the information needed to find the cause. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-20.20+test-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 23:41:00 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'mime_type']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-06-04 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1462183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)
** Changed in: policykit-1 (Ubuntu) Status: New => Triaged ** Changed in: policykit-1 (Ubuntu) Importance: Undecided => Medium ** Changed in: policykit-1 (Ubuntu Trusty) Status: New => Triaged ** Changed in: policykit-1 (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: policykit-1 (Ubuntu Vivid) Status: New => Triaged ** Changed in: policykit-1 (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: policykit-1 (Ubuntu Wily) Status: New => Triaged ** Changed in: policykit-1 (Ubuntu Wily) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1510824 Title: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas) Status in PolicyKit: Fix Released Status in policykit-1 package in Ubuntu: Triaged Status in policykit-1 source package in Trusty: Triaged Status in policykit-1 source package in Vivid: Triaged Status in policykit-1 source package in Wily: Triaged Bug description: [Impact] * Some PAM modules produce output of more than 1 line (e.g. PAM_TEXT_INFO may contain newlines in the message content). Polkit authentication agent is prepared to receive only single-line messages so it treats each line as a separate message. It fails to recognize the type of message for all of them except the first - hence failed authorization even if it was successful on the PAM-level. * The PAM specification does not require the modules to send only single-line messages. Thus, polkit needs to be fixed. * The helper component should escape (g_strescape) all messages before sending it up to the authentication agent. This way everything will be read as a single line and then unescaped to restore it's formatting with no changes required in PAM modules. [Test Case] * Use a pam module that returns a multi-line PAM_TEXT_INFO message on successful authentication (may require to artificially modify a pam module). * Perform a polkit authorization with e.g. pkexec ls * Correct authorization should end with a failure with an unrecognized PAM message [Regression Potential] * Fix makes advantage of the fact that polkit authentication agent already un-escapess (g_strcompress) all input from the helper component. * Fix is a backport of an upstream change. [Other Info] * Original bug description: There is an error observed when Ubuntu is configured to perform authentication via pam_vas (Vintela Authentication Services by Dell) in a disconnected mode (using cached authentication). Steps to reproduce: 1. Configure pam_vas client authenticating to a remote server. 2. Perform authentication to cache the credentials. 3. Disconnect from the network where the server is reachable (to force using cached information). 4. Perform an action requiring polkit authentication. Expected result: Authentication succeeds accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Actual result: Authentication fails accompanied by the following message "You have logged in using cached account information. Some network services will be unavailable". Probable cause: The PolkitAgentSession part of polkit is designed to interpret only 1-line output, while interaction with pam_vas in the above scenario triggers helper to produce the following 2-line output: PAM_TEXT_INFO You have logged in using cached account information. Some network services will be unavailable. The 'will be unavailable.' part is interpreted as an unknown message and causes failed authorization. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 28 09:01:37 2015 InstallationDate: Installed on 2015-04-13 (197 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1510824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518310] Re: no sound through headphones after boot
10.765719] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3260:
line_outs=1 (0x15/0x0/0x0/0x0/0x0) type:line
[ 10.765722] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=1
(0x14/0x0/0x0/0x0/0x0)
[ 10.765724] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1
(0x1a/0x0/0x0/0x0/0x0)
[ 10.765725] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 10.765726] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 10.765728] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18
[ 10.765729] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
ode 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
Control: name="Line Out Playback Switch", index=0, device=0 ControlAmp: chs=3,
dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x00]
Pincap 0x0001001c: OUT HP EAPD Detect
EAPD 0x2: EAPD
Pin Default 0x02211020: [Jack] HP Out at Ext Front Conn = 1/8, Color = Black
DefAssociation = 0x2, Sequence = 0x0
Pin-ctls: 0x00: Unsolicited: tag=01, enabled=1
Power states: D0 D1 D2 D3 EPSS
Power: setting=D3, actual=D3 Connection: 2 0x0c* 0x0d
seem two HP pin complex
Control.17 { iface CARD name 'Front Headphone Jack' value false comment
{ access read type BOOLEAN count 1 } }
control.18 { iface CARD name 'Front Headphone Jack' index 1 value true
comment { access read type BOOLEAN count 1 } }
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
** Summary changed:
- no sound through headphones after boot
+ [Dell L521X, ALC3260]No sound through headphones after boot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1518310
Title:
[Dell L521X, ALC3260]No sound through headphones after boot
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
After Ubuntu boots, randomly (say with 25% probability) the Headphone
alsamixer setting will be muted and set to 0 on my notebook. The
notebook will not play any sounds on headphones, only through the
notebook speakers when headphones are disconnected. I then have to
manually run alsamixer, unmute the Headphone setting and max it out to
100. This started to happen after upgrade to Ubuntu 15.10 - Ubuntu
15.04 worked fine.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vyzivus2444 F pulseaudio
/dev/snd/pcmC0D0p: vyzivus2444 F...m pulseaudio
/dev/snd/controlC0: vyzivus2444 F pulseaudio
vyzivus6270 F alsamixer
CurrentDesktop: Unity
Date: Fri Nov 20 13:45:18 2015
InstallationDate: Installed on 2014-03-07 (622 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64
(20130423.1)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to wily on 2015-10-08 (43 days ago)
dmi.bios.date: 12/17/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 029M77
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A16
dmi.modalias:
dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA16:
dmi.product.name: XPS L521X
dmi.product.version: A16
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1518310/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518310] Re: [Dell L521X, ALC3260]No sound through headphones after boot
Node 0x1a [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out Control: name="Headphone Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x00 0x00] Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x373c: IN OUT HP Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x0221101f: [Jack] HP Out at Ext Front Conn = 1/8, Color = Black DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0xc0: OUT HP VREF_HIZ Unsolicited: tag=02, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 2 0x0c 0x0d* Seem driver put your HP jack node 0x15 to line out but create Front Headphone jack index=1 Try hdajacksensetest to find out which node 0x15 or 0x1a are your HP jack -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1518310 Title: [Dell L521X, ALC3260]No sound through headphones after boot Status in alsa-driver package in Ubuntu: Incomplete Bug description: After Ubuntu boots, randomly (say with 25% probability) the Headphone alsamixer setting will be muted and set to 0 on my notebook. The notebook will not play any sounds on headphones, only through the notebook speakers when headphones are disconnected. I then have to manually run alsamixer, unmute the Headphone setting and max it out to 100. This started to happen after upgrade to Ubuntu 15.10 - Ubuntu 15.04 worked fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vyzivus2444 F pulseaudio /dev/snd/pcmC0D0p: vyzivus2444 F...m pulseaudio /dev/snd/controlC0: vyzivus2444 F pulseaudio vyzivus6270 F alsamixer CurrentDesktop: Unity Date: Fri Nov 20 13:45:18 2015 InstallationDate: Installed on 2014-03-07 (622 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to wily on 2015-10-08 (43 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 029M77 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.name: XPS L521X dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1518310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1517983] Re: Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet
I apologize. I am running elementary and was sure that glib 2.42 was coming from trusty, which of course it doesn't. ** Changed in: gtk+2.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1517983 Title: Attempt to unlock mutex that was not locked, Or: Do not release the GDK lock if it hasn't been acquired yet Status in gtk+2.0 package in Ubuntu: Invalid Bug description: In trusty, gtk+2.0 is currently on version 2.24.23-0ubuntu. The commit specified here[1] fixes a bug where using libgtk+2.0 in an unidiomatic manner leads to a SIGABRT when starting the app. I know that unidiomatic behaviour is not supported per-se, but there are a whole bunch of "legacy" apps that are hard to update. Examples include IntelliJ IDEA, OpenXenManager, and numerous others. Is there a chance of getting libgtk+2 updated to a version that in includes [1], or getting that commit backported to trusty? The fix seems to have landed in upstream[2] and utopic[3], but not in trusty. Thanks, Claus Strasburger [1]: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=fbf38d16bcc26630f0f721d266509f5bc292f606 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758619 [3]: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1376530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1517983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black
** Changed in: unity-settings-daemon (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1381625 Title: Adjust brightness to lowest value caused screen whole black Status in gnome-settings-daemon: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Trusty: In Progress Bug description: [Impact] When adjusting screen brightness to lowest value, it turns screen backlight off. [Test Case] 1. Install Image 2. Press System's brightness hotkey to adjust the brightness level to the lowest or 3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level to the lowest 4. Check if the screen display still has backlight Expected results: There is still screen backlight Actual results: Sceen backlight is turned off [Regression Potential] None [Other Info] Ubuntu 14.04 has HWE stack lts-vivid 3.19 and it also has this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1381625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1462183] Re: Nautilus "Enter Location" Stops Working
I have Ubuntu 14.04.3 LTS 64 bit and Nautilus 3.10.1. I experience the same problem repeatedly. All other shortcut keys work, Ctrl+h, Ctrl+f, etc. Just Ctrl+l stops working after a while. The Go -> Enter Location menu entry also stops working. Restarting Nautilus always solves the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1462183 Title: Nautilus "Enter Location" Stops Working Status in nautilus package in Ubuntu: Confirmed Bug description: Earlier, I had been able to use CTRL-L for "Enter Location" and it worked. At some point I had pressed ESC to revert back to the button- based paths. Later on, with that same window open, I came back and tried CTRL-L and the path didn't switch back to the textbox. Even going to "Go"->"Enter Location" did nothing. While writing this up, I did a test by closing that window, then opening a new "Files" window and CTRL-L worked right off the bat. This wasn't my first experience with that "bug", but enough times for me to finally submit it when it happened. Hopefully the data submitted will provide the information needed to find the cause. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-20.20+test-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 4 23:41:00 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'mime_type']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-06-04 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1462183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black
** Project changed: unity-settings-daemon => gnome-settings-daemon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1381625 Title: Adjust brightness to lowest value caused screen whole black Status in gnome-settings-daemon: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Trusty: In Progress Bug description: [Impact] When adjusting screen brightness to lowest value, it turns screen backlight off. [Test Case] 1. Install Image 2. Press System's brightness hotkey to adjust the brightness level to the lowest or 3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level to the lowest 4. Check if the screen display still has backlight Expected results: There is still screen backlight Actual results: Sceen backlight is turned off [Regression Potential] None [Other Info] Ubuntu 14.04 has HWE stack lts-vivid 3.19 and it also has this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1381625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1375637] Re: Premature end of data in tag file line 247651 with libxml2
Hi Sebastien, The problem is I've found no consistent trigger for the bug. I have 225 packages in my repository, built out for two different branches and two oses (so 225x4). createrepo just randomly corrupts when executing 'createrepo --update .' when adding a new source/binary rpm pair. It is trivially solvable (rm -rf repodata .repodata; createrepo .), but having to briefly have a 100% repo outage is the problem. I've not seen anything specific about the packages that would cause this to occur. It seems to be some type of race condition during the update process, because of it complaining about " I/O error : No such file or directory". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1375637 Title: Premature end of data in tag file line 247651 with libxml2 Status in libxml2 package in Ubuntu: Confirmed Bug description: Hello, I'm getting the following behaviour of createrepo on Ubuntu 14.04.1 LTS with libxml2=2.9.1+dfsg1-3ubuntu4.3(trusty-updates/main) and libxml2=2.9.1+dfsg1-3ubuntu4(trusty/main). createrepo -g /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/comps.xml \ -o /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ I/O error : No such file or directory (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag package line 246828 (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag filelists line 2 Spawning worker 0 with 54 pkgs Spawning worker 1 with 54 pkgs Spawning worker 2 with 54 pkgs Spawning worker 3 with 54 pkgs Spawning worker 4 with 54 pkgs Spawning worker 5 with 54 pkgs Spawning worker 6 with 54 pkgs Spawning worker 7 with 54 pkgs Spawning worker 8 with 54 pkgs Spawning worker 9 with 54 pkgs Spawning worker 10 with 53 pkgs Spawning worker 11 with 53 pkgs Spawning worker 12 with 53 pkgs Spawning worker 13 with 53 pkgs Spawning worker 14 with 53 pkgs Spawning worker 15 with 53 pkgs Spawning worker 16 with 53 pkgs Spawning worker 17 with 53 pkgs Spawning worker 18 with 53 pkgs Spawning worker 19 with 53 pkgs Spawning worker 20 with 53 pkgs Spawning worker 21 with 53 pkgs Spawning worker 22 with 53 pkgs Spawning worker 23 with 53 pkgs Workers Finished Saving Primary metadata Saving file lists metadata Saving other metadata Generating sqlite DBs Traceback (most recent call last): File "/usr/share/createrepo/genpkgmetadata.py", line 308, in main(sys.argv[1:]) File "/usr/share/createrepo/genpkgmetadata.py", line 280, in main mdgen.doRepoMetadata() File "/usr/lib/python2.7/dist-packages/createrepo/__init__.py", line 999, in doRepoMetadata rp.getFilelists(complete_path, csum) File "/usr/lib/python2.7/dist-packages/sqlitecachec.py", line 55, in getFilelists self.repoid)) TypeError: Parsing filelists.xml error: Premature end of data in tag file line 247651 Problem fixes by installing libxml2=2.9.1+dfsg1 from debian sid. Comparing patchsets in debian package sources between 2.9.1+dfsg1 and 2.9.1+dfsg1-3ubuntu4.3 I see in debian package much more patches, I suppose one of them helps in my problem: 2.9.1+dfsg1-3ubuntu4.3: 0001-modify-xml2-config-and-pkgconfig-behaviour.patch 0002-Fix-an-error-in-xmlCleanupParser.patch 0003-Fix-missing-break-on-last-function-for-attributes.patch 0004-xmllint-memory-should-fail-on-empty-files.patch 0005-properly-quote-the-namespace-uris-written-out-during.patch 0006-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch 0006-fix-python-multiarch-includes.patch 0007-Fix-XPath-optimization-with-predicates.patch CVE-2014-0191.patch lp1321869.patch xmllint_pretty.patch 2.9.1+dfsg1: 0001-modify-xml2-config-and-pkgconfig-behaviour.patch 0002-fix-python-multiarch-includes.patch 0003-Fix-an-error-in-xmlCleanupParser.patch 0004-Fix-missing-break-on-last-function-for-attributes.patch 0005-xmllint-memory-should-fail-on-empty-files.patch 0006-properly-quote-the-namespace-uris-written-out-during.patch 0007-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch 0008-missing-else-in-xlink.c.patch 0009-Catch-malloc-error-and-exit-accordingly.patch 0010-Fix-handling-of-mmap-errors.patch 0011-Avoid-crash-if-allocation-fails.patch 0012-Fix-a-possible-NU
Re: [Desktop-packages] [Ubuntu-webapps-bugs] [Bug 1517509] [NEW] Remove amazon as a webapp, move to simple sensible browser call
The main advantage is that you can switch back to the Amazon webapp window if one is already opened. This is a key advantage for certain webapps, like Gmail. But for more classic web sites, like Amazon or Ebay, the benefits are debatable. On Wed, Nov 18, 2015 at 4:11 PM, Bryan Quigley wrote: > Public bug reported: > > What advantages do we get from running Amazon as a webapp? > > Instead provide a desktop icon with Exec=sensible-browser > https://www.amazon.com/ > > and we save significant space on the image by using the already existing > browser. > > ** Affects: webapps-applications (Ubuntu) > Importance: Undecided > Status: New > > -- > You received this bug notification because you are a member of Ubuntu > WebApps bug tracking, which is subscribed to webapps-applications in > Ubuntu. > https://bugs.launchpad.net/bugs/1517509 > > Title: > Remove amazon as a webapp, move to simple sensible browser call > > Status in webapps-applications package in Ubuntu: > New > > Bug description: > What advantages do we get from running Amazon as a webapp? > > Instead provide a desktop icon with Exec=sensible-browser > https://www.amazon.com/ > > and we save significant space on the image by using the already > existing browser. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1517509/+subscriptions > > -- > Mailing list: https://launchpad.net/~ubuntu-webapps-bugs > Post to : ubuntu-webapps-b...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs > More help : https://help.launchpad.net/ListHelp > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webapps-applications in Ubuntu. https://bugs.launchpad.net/bugs/1517509 Title: Remove amazon as a webapp, move to simple sensible browser call Status in webapps-applications package in Ubuntu: New Bug description: What advantages do we get from running Amazon as a webapp? Instead provide a desktop icon with Exec=sensible-browser https://www.amazon.com/ and we save significant space on the image by using the already existing browser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1517509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518379] Re: Interrupt audio on bluetooth headset
And strange behavior! I ping: PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=128 time=107 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=128 time=321 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=128 time=291 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=128 time=282 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=128 time=498 ms 64 bytes from 192.168.1.2: icmp_seq=6 ttl=128 time=2664 ms 64 bytes from 192.168.1.2: icmp_seq=7 ttl=128 time=1663 ms 64 bytes from 192.168.1.2: icmp_seq=9 ttl=128 time=1415 ms 64 bytes from 192.168.1.2: icmp_seq=10 ttl=128 time=411 ms 64 bytes from 192.168.1.2: icmp_seq=11 ttl=128 time=91.2 ms 64 bytes from 192.168.1.2: icmp_seq=12 ttl=128 time=87.8 ms 64 bytes from 192.168.1.2: icmp_seq=13 ttl=128 time=300 ms 64 bytes from 192.168.1.2: icmp_seq=14 ttl=128 time=84.9 ms 64 bytes from 192.168.1.2: icmp_seq=15 ttl=128 time=184 ms 64 bytes from 192.168.1.2: icmp_seq=16 ttl=128 time=105 ms 64 bytes from 192.168.1.2: icmp_seq=17 ttl=128 time=1402 ms 64 bytes from 192.168.1.2: icmp_seq=18 ttl=128 time=398 ms 64 bytes from 192.168.1.2: icmp_seq=19 ttl=128 time=28.3 ms And when see high delay, sound is interrupting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1518379 Title: Interrupt audio on bluetooth headset Status in pulseaudio package in Ubuntu: New Bug description: In bluetooth headset i hear periodic pauses (interrupt). In syslog i see this message: ov 20 19:05:36 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 2851700 us (= 503036 bytes) in audio stream Nov 20 19:05:36 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 215199 us (= 37960 bytes) in audio stream Nov 20 19:05:39 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 2522676 us (= 445000 bytes) in audio stream Nov 20 19:05:39 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 275523 us (= 48600 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 30653 us (= 5404 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 11324 us (= 1996 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 64623 us (= 11396 bytes) in audio stream Nov 20 19:05:43 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 37157 us (= 6552 bytes) in audio stream Nov 20 19:05:54 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 1821597 us (= 321328 bytes) in audio stream ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry21 1468 F pulseaudio /dev/snd/controlC1: dmitry21 1468 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 20 19:05:18 2015 InstallationDate: Installed on 2015-11-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_HB dmi.board.vendor: Acer dmi.board.version: V1.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd03/23/2015:svnAcer:pnExtensa2510G:pvrV1.27:rvnAcer:rnBA50_HB:rvrV1.27:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Extensa 2510G dmi.product.version: V1.27 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1518379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518379] [NEW] Interrupt audio on bluetooth headset
Public bug reported: In bluetooth headset i hear periodic pauses (interrupt). In syslog i see this message: ov 20 19:05:36 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 2851700 us (= 503036 bytes) in audio stream Nov 20 19:05:36 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 215199 us (= 37960 bytes) in audio stream Nov 20 19:05:39 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 2522676 us (= 445000 bytes) in audio stream Nov 20 19:05:39 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 275523 us (= 48600 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 30653 us (= 5404 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 11324 us (= 1996 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 64623 us (= 11396 bytes) in audio stream Nov 20 19:05:43 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 37157 us (= 6552 bytes) in audio stream Nov 20 19:05:54 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 1821597 us (= 321328 bytes) in audio stream ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry21 1468 F pulseaudio /dev/snd/controlC1: dmitry21 1468 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 20 19:05:18 2015 InstallationDate: Installed on 2015-11-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_HB dmi.board.vendor: Acer dmi.board.version: V1.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd03/23/2015:svnAcer:pnExtensa2510G:pvrV1.27:rvnAcer:rnBA50_HB:rvrV1.27:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Extensa 2510G dmi.product.version: V1.27 dmi.sys.vendor: Acer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1518379 Title: Interrupt audio on bluetooth headset Status in pulseaudio package in Ubuntu: New Bug description: In bluetooth headset i hear periodic pauses (interrupt). In syslog i see this message: ov 20 19:05:36 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 2851700 us (= 503036 bytes) in audio stream Nov 20 19:05:36 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 215199 us (= 37960 bytes) in audio stream Nov 20 19:05:39 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 2522676 us (= 445000 bytes) in audio stream Nov 20 19:05:39 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 275523 us (= 48600 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 30653 us (= 5404 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 11324 us (= 1996 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 64623 us (= 11396 bytes) in audio stream Nov 20 19:05:43 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 37157 us (= 6552 bytes) in audio stream Nov 20 19:05:54 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 1821597 us (= 321328 bytes) in audio stream ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry21 1468 F pulseaudio /dev/snd/controlC1: dmitry21 1468 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 20 19:05:18 2015 InstallationDate: Installed on 2015-11-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: pulseaudio UpgradeStatus: No
[Desktop-packages] [Bug 1504049] Re: Chromium not working in guest session (need more AppArmor rules)
It doesn't look like any of the fixes will be in the chromium-browser package. Can I remove that task from the bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1504049 Title: Chromium not working in guest session (need more AppArmor rules) Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: Triaged Status in chromium-browser source package in Vivid: New Status in lightdm source package in Vivid: Fix Committed Status in chromium-browser source package in Wily: Confirmed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Unable to run Chromium from guest session. [Test Case] 1. Start Ubuntu 2. From greeter select guest session 3. Load Chromium Expected result: Chromium runs. Observed result: Chromium does not run. [Regression Potential] Low. The change is a few additional apparmor rules. There is a low risk that the new rules might allow a guest program to access a flaw. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1504049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1168746] Re: Battery icon not working in Ubuntu 14.04 LTS
** Changed in: gnome-power-manager (Ubuntu) Status: Fix Committed => Incomplete ** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1168746 Title: Battery icon not working in Ubuntu 14.04 LTS Status in gnome-power: New Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: In Ubuntu 14.04 LTS, the battery level never works correctly. When charging, this icon is expected to change to show how full the battery is, ranging for 20, 40, 60, 80, and 100. But it always shows 20 The battery level should change during charging, but it is still on 20%. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1168746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5
I'm still have the same problems - after performing apt-get update and upgrade, installing fglrx-updates, fglrx-updates-core, fglrx-amdcccle- updates, lightdm, xorg and ubuntu-desktop, and then running amdconfig, I am greeted by a black screen upon restart (several restarts do not fix the problem). Purging fglrx*, lightdm and xorg return me to a command line interface. Even if this problem is thus isolated to be separate to the problem in this thread, I am afraid I have hit a brick wall in troubleshooting this - does anyone have any advice on how I can track down the bug (and hopefully the solution!)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1493888 Title: FGLRX incompatible with gcc 5 Status in Release Notes for Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in fglrx-installer source package in Wily: Fix Released Status in fglrx-installer-updates source package in Wily: Fix Released Bug description: SRU Request: [Impact] The fglrx driver is not compatible with gcc 5.x. This causes the kernel module to crash on initialisation. As a result, users will boot into a black screen, as X will fail (except on Intel+AMD hybrid systems, where intel is used). [Test Case] 1. Either install (or upgrade to) Ubuntu 15.10 and fglrx 2. Reboot 3. Check the display, and the output of the "dmesg | grep fglrx" command (to see the actual crash) Expected results: the system should be able to start X correctly. Actual results: The kernel module fails and X doesn't start. [Regression Potential] Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be replaced with the proper fix once AMD makes it available. __ With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am able to SSH into the machine. I booted the older kernel (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and using xserver-xorg-video-radeon I am able to get the graphics working, but even it has issues with my display port (The DVI ports are working correctly). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Wed Sep 9 09:29:54 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2011-01-07 (1705 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fglrx-installer UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1469313] Re: After installing hplip 3.15.6 printer is sometimes not recognized after reboot
With hplip 3.15.11 I still have the same problem. Every time I have to boot the computer I need to uninstall and reinstall hplip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1469313 Title: After installing hplip 3.15.6 printer is sometimes not recognized after reboot Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: HPLIP was automatically updated on 11 June 2015. During the upgrade instructions were carefully followed however at the end the printer was not recognized. The upgrade was attempted again and it was then noted that it was required to turn off then on the printer for it be be recognized at the end of the install. Today, 26 June 2015 after a reboot caused by a video freeze the printer was not recognized (firmware was not downloaded during boot as usual) and running hp- setup shows printer not recognized even after turning the printer off then on several times and also unplugging and replugging it in to the usb port. I have not yet gone through these steps: => Run the command "hp-uninstall" to cleanly uninstall HPLIP. Remove plug-ins too when prompted. => Install the latest (or already downloaded 3.15.2 run file) => Remove all the existing queues by running the command "hp-setup -r" => Re-configure the queue by running the command "hp-setup". This step will also prompt for installing the plugin. Follow the prompts to install the plugins. => Try printing to the queue named HP_LaserJet_1020 After going through all the steps above the printer is again functional. Note: during the step to install the hp driver besides unplugging and replugging in the usb cable I have to additionally turn the printer off and on. Once this is done the driver installs correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hplip (not installed) Uname: Linux 4.0.0-997-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jun 26 15:12:48 2015 InstallationDate: Installed on 2014-10-24 (245 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1469313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518386] [NEW] RDC can't restore to previous session
Public bug reported: I followed the proposal from https://bugs.launchpad.net/gnome- session/+bug/1251281 and updated my Ubuntu 14.04 installation with workarounds for accessing Ubuntu desktop using Windows 7 RDC. Also, I use xrdp on Ubuntu. I expect that when I just close Windows 7 RDC, my Ubuntu session is continue running and if I wish I may connect to it later. However, it does not happen. When I re-launch RDC, a new gnome-session is started and I lose access to all previously launched applications. I believe it shall be fixed. -- lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty apt-cache policy gnome-session gnome-session: Installed: (none) Candidate: 3.9.90-0ubuntu12.1 Version table: 3.9.90-0ubuntu12.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3.9.90-0ubuntu12 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages apt-cache policy gnome-session-fallback gnome-session-fallback: Installed: 1:3.8.0-1ubuntu12.2 Candidate: 1:3.8.0-1ubuntu12.2 Version table: *** 1:3.8.0-1ubuntu12.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 100 /var/lib/dpkg/status 1:3.8.0-1ubuntu11 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages cat .xsession gnome-session --session=gnome-flashback --disable-acceleration-check ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1518386 Title: RDC can't restore to previous session Status in gnome-session package in Ubuntu: New Bug description: I followed the proposal from https://bugs.launchpad.net/gnome- session/+bug/1251281 and updated my Ubuntu 14.04 installation with workarounds for accessing Ubuntu desktop using Windows 7 RDC. Also, I use xrdp on Ubuntu. I expect that when I just close Windows 7 RDC, my Ubuntu session is continue running and if I wish I may connect to it later. However, it does not happen. When I re-launch RDC, a new gnome-session is started and I lose access to all previously launched applications. I believe it shall be fixed. -- lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty apt-cache policy gnome-session gnome-session: Installed: (none) Candidate: 3.9.90-0ubuntu12.1 Version table: 3.9.90-0ubuntu12.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3.9.90-0ubuntu12 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages apt-cache policy gnome-session-fallback gnome-session-fallback: Installed: 1:3.8.0-1ubuntu12.2 Candidate: 1:3.8.0-1ubuntu12.2 Version table: *** 1:3.8.0-1ubuntu12.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 100 /var/lib/dpkg/status 1:3.8.0-1ubuntu11 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages cat .xsession gnome-session --session=gnome-flashback --disable-acceleration-check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1518386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518383] [NEW] Monitor sleeps without regard to brightness & lock settings
Public bug reported: Setting the monitor to never sleep has no effect, X will force it to sleep after 10 minutes of inactivity regardless of what you set. There is a very simple workaround of disabling that feature in X, but there is no GUI to do this, and it's particularly troublesome for a multimedia PC, where it can be in active use despite no one having touched any input devices for over an hour (e.g. while watching a movie). Again, there is a simple workaround, but the fact that a workaround exists doesn't make it less of a bug, especially when the workaround requires things that an average user would shy away from (terminal/X settings). I know for a fact that it does this on both Nvidia and AMD proprietary drivers (installed through the additional drivers dialogue), and I haven't specifically tested it, but find it highly likely that it would do this with the open source variants as well. Maybe related to https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/273484 But I didn't find any other reports of monitors sleeping too much. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 20 11:17:16 2015 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2015-11-16 (3 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1518383 Title: Monitor sleeps without regard to brightness & lock settings Status in unity-control-center package in Ubuntu: New Bug description: Setting the monitor to never sleep has no effect, X will force it to sleep after 10 minutes of inactivity regardless of what you set. There is a very simple workaround of disabling that feature in X, but there is no GUI to do this, and it's particularly troublesome for a multimedia PC, where it can be in active use despite no one having touched any input devices for over an hour (e.g. while watching a movie). Again, there is a simple workaround, but the fact that a workaround exists doesn't make it less of a bug, especially when the workaround requires things that an average user would shy away from (terminal/X settings). I know for a fact that it does this on both Nvidia and AMD proprietary drivers (installed through the additional drivers dialogue), and I haven't specifically tested it, but find it highly likely that it would do this with the open source variants as well. Maybe related to https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/273484 But I didn't find any other reports of monitors sleeping too much. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 20 11:17:16 2015 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2015-11-16 (3 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1518383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1449059] Re: [mako] Music stays 'ducked' for 15s after selecting dialpad buttons with dialpad tones
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu RTM) Importance: Undecided Status: New ** No longer affects: media-hub -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1449059 Title: [mako] Music stays 'ducked' for 15s after selecting dialpad buttons with dialpad tones Status in pulseaudio package in Ubuntu: New Status in pulseaudio package in Ubuntu RTM: New Bug description: Steps: 1) Start playing music in the music-app 2) Ensure that 'Dialpad tones' are enabled in the sound settings 3) Open the dialer-app 4) Press one of the numbers on the dialer 5) Notice that the audio 'ducks' to allow for the dialpad tone, but then the audio takes ~15s to then be restored to its original value It was expected that the audio would be restored as soon as the dialpad tone ended. $ system-image-cli -i current build number: 181 device name: mako channel: ubuntu-touch/devel-proposed-customized-here alias: ubuntu-touch/vivid-proposed-customized-here last update: 2015-04-26 17:27:16 version version: 181 version ubuntu: 20150424.1 version device: 20150210 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1449059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot
Any news on fixing the bug? Yesterday a new version of network-manager 0.9.8.8-0ubuntu7.2 got pushed out, replacing the version from cschieli's ppa 0.9.8.8-0ubuntu7.1+athome1, causing the bridges to break once again -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1273201 Title: bridge_ignore_without_connections.patch breaks NM created bridge at boot Status in network-manager package in Ubuntu: Fix Released Bug description: I've created a bridge with network-manager-gnome, the bridge slave physical device is eth0. After a reboot the bridge is brought up, but eth0 isn't attached. First test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0 and remove all other connections. After a reboot the bridge is brought up, but eth0 isn't attached. When I open /etc/NetworkManager/NetworkManager.conf and save it without any modification, eth0 is instantly added to my bridge. Strange! Second test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0. Disable the "autoconnect" of the default wired network. After a reboot the bridge is brought up, but eth0 isn't attached. Instead eth0 is brought up and full configured. After compiling and testing different upstream versions, i could track the problem down to bridge_ignore_without_connections.patch. A network-manager package without this specific patch, brings my bridge up at boot and adds eth0 to the bridge in both test-cases. I've checked the behaviour on my ubuntu 13.10 box with network-manager (0.9.8.0-0ubuntu22) and the trusty version network-manager (0.9.8.8-0ubuntu1) . Till now i couldn't encounter any sideeffects of removing this patch with the bridge created by libvirt. Regards Mathias Kresin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518394] [NEW] [Skylake Platform, Realtek ALC269VB, Speaker, Internal] No sound at all
Public bug reported: We try to certify the TopStar u931 laptop which includes Skylake audio. When going to sound preferences , speaker is never shown, only headphones, even if they are not connected When running pavucontrol, headphones are shown plugged in and speakers are shown "unavailable" this might be a bios problem or hardware. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2296 F pulseaudio oem7591 F alsamixer CurrentDesktop: Unity Date: Fri Nov 20 18:00:31 2015 InstallationDate: Installed on 2015-11-14 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2296 F pulseaudio oem7591 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Skylake Platform, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd09/10/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-11-15T21:52:13.199491 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1518394 Title: [Skylake Platform, Realtek ALC269VB, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: We try to certify the TopStar u931 laptop which includes Skylake audio. When going to sound preferences , speaker is never shown, only headphones, even if they are not connected When running pavucontrol, headphones are shown plugged in and speakers are shown "unavailable" this might be a bios problem or hardware. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2296 F pulseaudio oem7591 F alsamixer CurrentDesktop: Unity Date: Fri Nov 20 18:00:31 2015 InstallationDate: Installed on 2015-11-14 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2296 F pulseaudio oem7591 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Skylake Platform, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd09/10/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-11-15T21:52:13.199491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1518394/+subscriptions --
[Desktop-packages] [Bug 1518079] Re: scrollbars gone in 15.10
** Bug watch added: GNOME Bug Tracker #758411 https://bugzilla.gnome.org/show_bug.cgi?id=758411 ** Also affects: vinagre via https://bugzilla.gnome.org/show_bug.cgi?id=758411 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1518079 Title: scrollbars gone in 15.10 Status in Vinagre: VNC client for GNOME: Unknown Status in vinagre package in Ubuntu: Confirmed Bug description: When I use vinagre to connect to a remote display that is larger than my local display, there are no scrollbars on the vinagre window to allow me to scroll the remove display up/down or left/right. There were scrollbars in 15.04. They have disappeared in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: vinagre 3.16.1-1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 19 16:02:12 2015 SourcePackage: vinagre UpgradeStatus: Upgraded to wily on 2015-11-17 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vinagre/+bug/1518079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445527] Re: Speaker remains on after podcast finishes
** Also affects: media-hub (Ubuntu) Importance: Undecided Status: New ** Also affects: media-hub (Ubuntu RTM) Importance: Undecided Status: New ** No longer affects: media-hub ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu RTM) Importance: Undecided Status: New ** No longer affects: pulseaudio ** Changed in: media-hub (Ubuntu) Importance: Undecided => Medium ** Changed in: media-hub (Ubuntu RTM) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu RTM) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1445527 Title: Speaker remains on after podcast finishes Status in podbird: New Status in media-hub package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in media-hub package in Ubuntu RTM: New Status in pulseaudio package in Ubuntu RTM: New Bug description: This might be a Media Hub bug - I'm not sure. Steps to reproduce: 1. Start playing a podcast. 2. Switch to a different app. 3. Lock the screen. 4. Wait for the Podcast to finish. 5. Wait a bit longer. Expected results: No noise from speaker. Actual results: Soft white noise from speaker. It seems that some part of the audio subsystem is still switched on. I am concerned that this could be draining battery. Workaround: After the Podcast finishes, unlock the phone and switch back to the Podbird app. This causes the noise to stop. Comments: I noticed the same soft white noise continues a second or two after the phone plays any sound from any app, but then turns off. I presume there is some time out turning off some part of the audio subsystem. Presumably if there is a reason, it should happen even when the app causing the sound to play is not active. To manage notifications about this bug go to: https://bugs.launchpad.net/podbird/+bug/1445527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518379] Re: Interrupt audio on bluetooth headset
Please, move to right section. When i turn off wifi networking, problem is gonem but after turn on already here! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1518379 Title: Interrupt audio on bluetooth headset Status in pulseaudio package in Ubuntu: New Bug description: In bluetooth headset i hear periodic pauses (interrupt). In syslog i see this message: ov 20 19:05:36 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 2851700 us (= 503036 bytes) in audio stream Nov 20 19:05:36 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 215199 us (= 37960 bytes) in audio stream Nov 20 19:05:39 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 2522676 us (= 445000 bytes) in audio stream Nov 20 19:05:39 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 275523 us (= 48600 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 30653 us (= 5404 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 11324 us (= 1996 bytes) in audio stream Nov 20 19:05:40 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 64623 us (= 11396 bytes) in audio stream Nov 20 19:05:43 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 37157 us (= 6552 bytes) in audio stream Nov 20 19:05:54 Photonix-Laptop pulseaudio[1468]: [bluetooth] module-bluez5-device.c: Skipping 1821597 us (= 321328 bytes) in audio stream ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry21 1468 F pulseaudio /dev/snd/controlC1: dmitry21 1468 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 20 19:05:18 2015 InstallationDate: Installed on 2015-11-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA50_HB dmi.board.vendor: Acer dmi.board.version: V1.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd03/23/2015:svnAcer:pnExtensa2510G:pvrV1.27:rvnAcer:rnBA50_HB:rvrV1.27:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Extensa 2510G dmi.product.version: V1.27 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1518379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration
This bug was fixed in the package vino - 3.8.1-0ubuntu7 --- vino (3.8.1-0ubuntu7) xenial; urgency=medium * debian/patches/git_struct_init.patch: - "Be more careful with memory allocation", should fix some of the segfault issues reports (lp: #987287) * debian/patches/git_small_bugfixes.patch: - backport some easy bugfixes * debian/patches/git_no_http_server.patch: - remove http server, it's not used and listen on interfaces for no reason (lp: #984093) -- Sebastien Bacher Fri, 20 Nov 2015 16:51:19 +0100 ** Changed in: vino (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/984093 Title: vino http server binds to external interfaces despite local_only configuration Status in vino: Fix Released Status in vino package in Ubuntu: Fix Released Bug description: Environment: Debian Wheezy Vino 3.2.2-1+b1 Vino is configured for local access only via: gconftool-2 --set /desktop/gnome/remote_access/local_only --type bool true Vino's vnc server is only listening on localhost:5900 and no other interfaces - as expected. Vino's http server, though, is listening on all interfaces, despite the local_only configuration. The expected behaviour would be for all vino services, including the http server, to only bind to the localhost interface when configured accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/984093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 987287] Re: vino-server crashed with SIGABRT in __libc_message()
This bug was fixed in the package vino - 3.8.1-0ubuntu7 --- vino (3.8.1-0ubuntu7) xenial; urgency=medium * debian/patches/git_struct_init.patch: - "Be more careful with memory allocation", should fix some of the segfault issues reports (lp: #987287) * debian/patches/git_small_bugfixes.patch: - backport some easy bugfixes * debian/patches/git_no_http_server.patch: - remove http server, it's not used and listen on interfaces for no reason (lp: #984093) -- Sebastien Bacher Fri, 20 Nov 2015 16:51:19 +0100 ** Changed in: vino (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/987287 Title: vino-server crashed with SIGABRT in __libc_message() Status in vino: Fix Released Status in vino package in Ubuntu: Fix Released Status in vino source package in Trusty: Triaged Bug description: dont know ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: vino 3.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Mon Apr 23 16:13:57 2012 ExecutablePath: /usr/lib/vino/vino-server InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcCmdline: /usr/lib/vino/vino-server --sm-disable ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: vino StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 FreeUPNPUrls () from /usr/lib/libminiupnpc.so.8 Title: vino-server crashed with SIGABRT in raise() UpgradeStatus: Upgraded to precise on 2012-04-02 (21 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/987287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518310] Re: [Dell L521X, ALC3260]No sound through headphones after boot
Thank you very much for your reply. I can't say that I really understand all that stuff ;) I tried to disable 0x1a first, but then the line out stopped working entirely. I have therefore enabled 0x1a and disabled 0x15, things are working so far. Please see screenshot for details. ** Attachment added: "Screenshot from 2015-11-20 18-35-47.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1518310/+attachment/4522704/+files/Screenshot%20from%202015-11-20%2018-35-47.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1518310 Title: [Dell L521X, ALC3260]No sound through headphones after boot Status in alsa-driver package in Ubuntu: Incomplete Bug description: After Ubuntu boots, randomly (say with 25% probability) the Headphone alsamixer setting will be muted and set to 0 on my notebook. The notebook will not play any sounds on headphones, only through the notebook speakers when headphones are disconnected. I then have to manually run alsamixer, unmute the Headphone setting and max it out to 100. This started to happen after upgrade to Ubuntu 15.10 - Ubuntu 15.04 worked fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vyzivus2444 F pulseaudio /dev/snd/pcmC0D0p: vyzivus2444 F...m pulseaudio /dev/snd/controlC0: vyzivus2444 F pulseaudio vyzivus6270 F alsamixer CurrentDesktop: Unity Date: Fri Nov 20 13:45:18 2015 InstallationDate: Installed on 2014-03-07 (622 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to wily on 2015-10-08 (43 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 029M77 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.name: XPS L521X dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1518310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1326954]
With the aforementioned udev rules file, the situation got much better. However, it is not perfect. In some occasions (about 20~30% of resumes), the modem is still unusable, and when this happens, only a reboot can help to get it usable again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Confirmed Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | prima
[Desktop-packages] [Bug 1504049] Re: Chromium not working in guest session (need more AppArmor rules)
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Invalid ** Changed in: chromium-browser (Ubuntu Wily) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1504049 Title: Chromium not working in guest session (need more AppArmor rules) Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in chromium-browser package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: Triaged Status in chromium-browser source package in Vivid: New Status in lightdm source package in Vivid: Fix Committed Status in chromium-browser source package in Wily: Invalid Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Unable to run Chromium from guest session. [Test Case] 1. Start Ubuntu 2. From greeter select guest session 3. Load Chromium Expected result: Chromium runs. Observed result: Chromium does not run. [Regression Potential] Low. The change is a few additional apparmor rules. There is a low risk that the new rules might allow a guest program to access a flaw. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1504049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518411] [NEW] "Maximum number of clients reached", new in Ubuntu 15.10
Public bug reported: In my newly upgraded (from 15.04) Ubuntu 15.10 system, after I've been logged in for a while I can no longer open new windows and instead get a "Maximum number of clients reached" error. This did not happen in 15.04. I ran "lsof" on the X server and did not see an excessive number of open file descriptors. I ran it again on a newly restarted X server and the number of open file descriptors looked about the same. I also ran "xlsclients" when the X server was reporting "Maximum number of clients reached" and the list of clients looked correct and reasonable (and there were less than 30 of them). I am happy to collect any additional logs or debugging information to help track this down. I don't know where to look further. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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: Fri Nov 20 13:00:09 2015 DistUpgraded: 2015-11-17 11:59:09,835 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.4, 3.19.0-33-generic, x86_64: installed virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:7410] MachineType: System76, Inc. Galago UltraPro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=821f94aa-97e2-4384-8494-9f510a75877b ro i915.disable_power_well=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-11-17 (3 days ago) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Nov 20 12:51:23 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1518411 Title: "Maximum number of clients reached", new in Ubuntu 15.10 Status in xorg package in Ubuntu: New Bug description: In my newly upgraded (from 15.04) Ubuntu 15.10 system, after I've been logged in for a while I can no longer open new windows and instead get a "Maximum number of clients reached" error. This did not happen in 15.04. I ran "lsof" on the X server and did not see an excessive number of open file descriptors. I ran it again on a newly restarted X server and the number of open file descriptors looked about the same. I also ran "xlsclients" when the X server was reporting "Maximum number of clients reached" and the list of clients looked correct and reasonable (and there were less than 30 of them). I am happy to collect any additional logs or debugging information to help track this down. I don't know where to look further. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/op
[Desktop-packages] [Bug 1168746] Re: Battery icon not working in Ubuntu 14.04 LTS
** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1168746 Title: Battery icon not working in Ubuntu 14.04 LTS Status in gnome-power: New Status in gnome-power-manager package in Ubuntu: Fix Committed Bug description: In Ubuntu 14.04 LTS, the battery level never works correctly. When charging, this icon is expected to change to show how full the battery is, ranging for 20, 40, 60, 80, and 100. But it always shows 20 The battery level should change during charging, but it is still on 20%. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1168746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
** Changed in: canonical-pocket-desktop Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android Status in canonical-pocket-desktop: Fix Committed Status in Mir: Fix Committed Status in xorg-server package in Ubuntu: Invalid Bug description: I'm seeing severe graphical corruption running mir_demo_client_flicker on mako. Start a few instances of the client (or just one flicker and some other clients) and you'll see the mir_demo_client_flicker window contains significant corruption. I don't think it's an overlays issue. The problem occurs even without overlays. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1515711] Re: lightdm hangs, windows freeze, lightdm restart helps most of the times.
I have upgraded to Ubuntu 15.10, bug is still there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1515711 Title: lightdm hangs, windows freeze, lightdm restart helps most of the times. Status in lightdm package in Ubuntu: New Bug description: Since a few days, when I use Android Studio, my screens freeze. Nothing works. With alt-crtrl-F2 I log in to a shell window, restart lightdm, then it works. Except on the last freeze, now I had to restart the computer. When restarting lightdm, a popup said "system in low graphics res, cannot detect your settings". I have reported the but to Android Studio developers. But a program, even a big one like an IDE, should not be able to crash my computer. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 12 18:22:33 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-02 (41 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1515711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
No, I have plain Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" Status in policykit-1-gnome package in Ubuntu: Confirmed Bug description: Every few days a dialog pops up saying "Authentication is required to change your own user data" with an entry field for a password. If I type my user's password the dialog will reappear with an empty entry field. If I click on the cross to close the window many times it will be gone, but reappear a few days later. I don't know what this window is for and it makes no difference whether I close it or leave it. I don't use the gnome keyring. This started with Ubuntu 15.04 or maybe with an earlier release, and is still there in Ubuntu 15.10, also on machines I did a fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1512002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot
+1 Updated version currently rebuilding in my PPA: https://launchpad.net/~cschieli/+archive/ubuntu/bug1273201 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1273201 Title: bridge_ignore_without_connections.patch breaks NM created bridge at boot Status in network-manager package in Ubuntu: Fix Released Bug description: I've created a bridge with network-manager-gnome, the bridge slave physical device is eth0. After a reboot the bridge is brought up, but eth0 isn't attached. First test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0 and remove all other connections. After a reboot the bridge is brought up, but eth0 isn't attached. When I open /etc/NetworkManager/NetworkManager.conf and save it without any modification, eth0 is instantly added to my bridge. Strange! Second test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0. Disable the "autoconnect" of the default wired network. After a reboot the bridge is brought up, but eth0 isn't attached. Instead eth0 is brought up and full configured. After compiling and testing different upstream versions, i could track the problem down to bridge_ignore_without_connections.patch. A network-manager package without this specific patch, brings my bridge up at boot and adds eth0 to the bridge in both test-cases. I've checked the behaviour on my ubuntu 13.10 box with network-manager (0.9.8.0-0ubuntu22) and the trusty version network-manager (0.9.8.8-0ubuntu1) . Till now i couldn't encounter any sideeffects of removing this patch with the bridge created by libvirt. Regards Mathias Kresin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 828316] Re: [GTK3] Navigation bar menubuttons don't look pressed when clicked
** Attachment added: "README.txt" https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/828316/+attachment/4522749/+files/README.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/828316 Title: [GTK3] Navigation bar menubuttons don't look pressed when clicked Status in software-center package in Ubuntu: Triaged Bug description: software-center-gtk3 trunk 2114, Ubuntu Ocelot 1. Click the menubuttons next to "All Software" or "Installed". What happens: * The triangle changes color a little. * The triangle sometimes wobbles. What should happen: * The whole menubutton goes dark, just like the button for the current section. * The triangle does not change color, except in the same way as the whole menubutton does. * The triangle doesn't wobble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/828316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1303438] Re: Reveal after enabling Auto-hide Launcher does not work.
** Changed in: unity-control-center (Ubuntu) Assignee: (unassigned) => Chintana Prabhu (chintanarp98) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1303438 Title: Reveal after enabling Auto-hide Launcher does not work. Status in unity-control-center package in Ubuntu: Confirmed Bug description: I enable Auto-hide Launcher. Launcher auto-hides. Moving the mouse to the top left corner does not reveal the launcher, even with reveal sensitivity slid to maximum. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 Uname: Linux 3.14.0-031400-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 14:39:25 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140403) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1303438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518421] [NEW] package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal
Public bug reported: don't know details only know that problem exists with installation of this :( ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Nov 19 11:50:04 2015 DuplicateSignature: package:gir1.2-gst-plugins-base-1.0:1.2.4-1~ubuntu2:Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2015-09-27 (54 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: gst-plugins-base1.0 Title: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-from-proposed trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1518421 Title: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: don't know details only know that problem exists with installation of this :( ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Nov 19 11:50:04 2015 DuplicateSignature: package:gir1.2-gst-plugins-base-1.0:1.2.4-1~ubuntu2:Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2015-09-27 (54 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: gst-plugins-base1.0 Title: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1518421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 828316] Re: [GTK3] Navigation bar menubuttons don't look pressed when clicked
** Attachment added: "README.txt" https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/828316/+attachment/4522757/+files/README.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/828316 Title: [GTK3] Navigation bar menubuttons don't look pressed when clicked Status in software-center package in Ubuntu: Triaged Bug description: software-center-gtk3 trunk 2114, Ubuntu Ocelot 1. Click the menubuttons next to "All Software" or "Installed". What happens: * The triangle changes color a little. * The triangle sometimes wobbles. What should happen: * The whole menubutton goes dark, just like the button for the current section. * The triangle does not change color, except in the same way as the whole menubutton does. * The triangle doesn't wobble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/828316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518035] Re: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libjpeg-turbo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1518035 Title: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg9 package in Ubuntu: Confirmed Status in libjpeg9 package in Debian: Unknown Bug description: just upgrading ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 1:9a-2ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 Date: Mon Nov 16 15:38:22 2015 Dependencies: gcc-5-base 5.2.1-23ubuntu1 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-23ubuntu1 libjpeg9 1:9a-2ubuntu1 multiarch-support 2.21-0ubuntu4 DuplicateSignature: Unpacking libjpeg-progs (1:9a-2ubuntu1) over (8c-2ubuntu8) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ErrorMessage: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2014-02-24 (633 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.3ubuntu1 apt 1.0.10.2ubuntu1 SourcePackage: libjpeg9 Title: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1518035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
