[Desktop-packages] [Bug 1133477] Re: cut-n-paste move files got stuck forever
I'm constantly getting this problem in Ubuntu 16.04. Moving 608 jpg files to a sub-folder of the current folder has just taken ages (15 minutes? - certainly long enough for me to find this thread and compose this comment while I was waiting for the move to complete). The "Preparing to move n files" message very slowly decreases the value of n indicating that there is some progress being made but it should never take this long. It's getting to the point where I'll always boot into Windows rather than Ubuntu just in case I need to move some files. -- 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/1133477 Title: cut-n-paste move files got stuck forever Status in nautilus package in Ubuntu: Confirmed Status in pcmanfm package in Ubuntu: Confirmed Bug description: With Nautilus, I navigated to a folder that contained about 2,000 gif files. I selected all of them I cut with Ctrl+X I navigated to another folder I pasted with Ctrl+V => A popup window appeared saying "Preparing to move N files", and it got stuck there forever. Nautilus stopped responding. I waited half an hour, then I had to kill it. Actually some of the files were moved. Which is the worst thing that could happen. I tried again with the remaining files and it happened again!! It's systematic!! I suspect it has to do with displaying the previews of a big number of files. Nautilus becomes completely unmanageable whenever you open folders with lots of files. Maximum priority should be given to the UI and actual operations; displaying of the previews should be done in the background and should never, ever slow down user operations the slightest bit. Seems pretty obvious. Also note that 2000 is not even that much. Actually it's very few files. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Tue Feb 26 18:23:52 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'180' b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true' InstallationDate: Installed on 2010-06-23 (979 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1133477/+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 1648649] Re: Ubufox is broken in Firefox Nightly, due to using no-longer-supported "for each" syntax. Error console now shows "SyntaxError: missing ( after for UpdateNotifier.j
[CC'ing Alexander, Arzhel/xionox, & Chris, who are all listed as "Contributors" at the top of UpdateNotifier.js, one of the affected JS files. Hoping one of them can address this or might know who can.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1648649 Title: Ubufox is broken in Firefox Nightly, due to using no-longer-supported "for each" syntax. Error console now shows "SyntaxError: missing ( after for UpdateNotifier.js:217:8" Status in ubufox package in Ubuntu: New Bug description: Firefox Nightly (53) no longer supports the non-standard "for each" looping construct, as of https://bugzilla.mozilla.org/show_bug.cgi?id=1293305 Unfortunately, ubufox uses this construct, which causes problems as shown in the error console at startup: > SyntaxError: missing ( after for UpdateNotifier.js:217:8 > SyntaxError: missing ( after for utils.jsm:217:8 Fortunately, it's easy to fix! Just replace code like this... > for each (let k in [...]) ...with code like this: > for (let k of [...]) Note: I also filed this in Mozilla's bug-tracker (under Tech Evangelism | Add-ons) here: https://bugzilla.mozilla.org/show_bug.cgi?id=1322551 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1648649/+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 1639926] Re: Update evolution-data-server to 3.22.3
** Changed in: evolution-data-server (Ubuntu Yakkety) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1639926 Title: Update evolution-data-server to 3.22.3 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Yakkety: In Progress Bug description: Impact == This is the second evolution SRU for yakkety. This update includes the new bugfix releases 3.22.2 and 3.22.3. Updating e-d-s is required to update evolution to 3.22.3 (LP: #1639942) https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22 Test Case = After installing the update, restart your computer. (Is there a flag evolution-data-server should set to prompt the user to do this?) Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential Low. There are a fair amount of changes in this update, but they are all targeted towards fixing bugs. This is the same release that other GNOME 3.22 distros ship. This may be the last official 3.22 release for the Evolution stack. Other Info == Note that there is an issue with Google authentication affecting at least 3.20 and 3.22.0. It might still be present in this release. I was a bit confused trying to read the evolution mailing list and some of the bug reports. It's possible that other people using older versions of evolution are causing the Google to block the shared API key because of too many authentication errors. If that's so, we can hope distros and users update promptly. Or we could ship an Ubuntu- specific key. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+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 1639942] Re: Update evolution to 3.22.3
** Changed in: evolution (Ubuntu Yakkety) Status: Confirmed => In Progress ** Changed in: evolution (Ubuntu Yakkety) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1639942 Title: Update evolution to 3.22.3 Status in evolution package in Ubuntu: Fix Released Status in evolution source package in Yakkety: In Progress Bug description: Impact == This is the second SRU for Ubuntu 16.10 for evolution. It includes 3.22.2 and 3.22.3. https://git.gnome.org/browse/evolution/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution/log/?h=gnome-3-22 Test Case = After installing this update, please restart your computer. Verify that evolution still works as well as it did before. Optionally, you can even go through some of the fixed bugs to verify the bug and the fix but there are a lot of fixed bugs! Regression Potential Low to Moderate. This is a substantial update with 90 or so commits. On the other hand, these are focused on fixing bugs. This may be the last official 3.22 evolution release. This is the same version that is being shipped by other GNOME 3.22 distros. Other Info == This update depends on evolution-data-server 3.22.3. See the note on that SRU bug (LP: #/1639926) for information about the persistent Google authentication issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1639942/+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 1604352] Re: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: el subprocés s'ha instaŀlat el script post-removal retornà el codi d'eixida d'error 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1604352 Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: el subprocés s'ha instaŀlat el script post-removal retornà el codi d'eixida d'error 1 Status in lightdm package in Ubuntu: Confirmed Bug description: "login loop" after kernel update (probably nvidia drivers?) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 AptOrdering: ubuntu-desktop: Purge lightdm: Purge Architecture: amd64 Date: Tue Jul 19 10:43:37 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:el subprocés s'ha instaŀlat el script post-removal retornà el codi d'eixida d'error 1 ErrorMessage: el subprocés s'ha instaŀlat el script post-removal retornà el codi d'eixida d'error 1 InstallationDate: Installed on 2014-12-19 (577 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: lightdm Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: el subprocés s'ha instaŀlat el script post-removal retornà el codi d'eixida d'error 1 UpgradeStatus: Upgraded to trusty on 2015-01-08 (557 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1604352/+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 1639942] Re: Update evolution to 3.22.3
** Description changed: Impact == + This is the second SRU for Ubuntu 16.10 for evolution. It includes 3.22.2 and 3.22.3. https://git.gnome.org/browse/evolution/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution/log/?h=gnome-3-22 Test Case = + After installing this update, please restart your computer. + + Verify that evolution still works as well as it did before. + + Optionally, you can even go through some of the fixed bugs to verify the + bug and the fix but there are a lot of fixed bugs! Regression Potential + Low to Moderate. This is a substantial update with 90 or so commits. + On the other hand, these are focused on fixing bugs. This may be the last official 3.22 evolution release. This is the same version that is being shipped by other GNOME 3.22 distros. + + Other Info + == + This update depends on evolution-data-server 3.22.3. See the note on that SRU bug (LP: #/1639926) for information about the persistent Google authentication issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1639942 Title: Update evolution to 3.22.3 Status in evolution package in Ubuntu: Fix Released Status in evolution source package in Yakkety: Confirmed Bug description: Impact == This is the second SRU for Ubuntu 16.10 for evolution. It includes 3.22.2 and 3.22.3. https://git.gnome.org/browse/evolution/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution/log/?h=gnome-3-22 Test Case = After installing this update, please restart your computer. Verify that evolution still works as well as it did before. Optionally, you can even go through some of the fixed bugs to verify the bug and the fix but there are a lot of fixed bugs! Regression Potential Low to Moderate. This is a substantial update with 90 or so commits. On the other hand, these are focused on fixing bugs. This may be the last official 3.22 evolution release. This is the same version that is being shipped by other GNOME 3.22 distros. Other Info == This update depends on evolution-data-server 3.22.3. See the note on that SRU bug (LP: #/1639926) for information about the persistent Google authentication issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1639942/+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 1596826] Re: Gimp does not respond when using Cage Transform tool
no solution yet ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1596826 Title: Gimp does not respond when using Cage Transform tool Status in gimp package in Ubuntu: Confirmed Bug description: I'm running gimp on ubuntu 16.04 LTS. Everytime I try to use the Cage Transform tool gimp stops responding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1596826/+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 1639926] Re: Update to 3.22.2
** Description changed: Impact == + This is the second evolution SRU for yakkety. This update includes the new bugfix releases 3.22.2 and 3.22.3. Updating e-d-s is required to update evolution to 3.22.3 (LP: #1639942) https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22 Test Case = + After installing the update, restart your computer. (Is there a flag evolution-data-server should set to prompt the user to do this?) + + Run several eds-using apps like Evolution, GNOME Calendar and verify + that they continue to run at least as well as before this update. Regression Potential + Low. There are a fair amount of changes in this update, but they are all targeted towards fixing bugs. This is the same release that other GNOME 3.22 distros ship. This may be the last official 3.22 release for the Evolution stack. + + Other Info + == + Note that there is an issue with Google authentication affecting at least 3.20 and 3.22.0. It might still be present in this release. + + I was a bit confused trying to read the evolution mailing list and some + of the bug reports. It's possible that other people using older versions + of evolution are causing the Google to block the shared API key because + of too many authentication errors. If that's so, we can hope distros and + users update promptly. Or we could ship an Ubuntu-specific key. ** Changed in: evolution-data-server (Ubuntu Yakkety) Status: New => In Progress ** Summary changed: - Update to 3.22.2 + Update evolution-data-server to 3.22.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1639926 Title: Update evolution-data-server to 3.22.3 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Yakkety: In Progress Bug description: Impact == This is the second evolution SRU for yakkety. This update includes the new bugfix releases 3.22.2 and 3.22.3. Updating e-d-s is required to update evolution to 3.22.3 (LP: #1639942) https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22 Test Case = After installing the update, restart your computer. (Is there a flag evolution-data-server should set to prompt the user to do this?) Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential Low. There are a fair amount of changes in this update, but they are all targeted towards fixing bugs. This is the same release that other GNOME 3.22 distros ship. This may be the last official 3.22 release for the Evolution stack. Other Info == Note that there is an issue with Google authentication affecting at least 3.20 and 3.22.0. It might still be present in this release. I was a bit confused trying to read the evolution mailing list and some of the bug reports. It's possible that other people using older versions of evolution are causing the Google to block the shared API key because of too many authentication errors. If that's so, we can hope distros and users update promptly. Or we could ship an Ubuntu- specific key. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+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 1639942] Re: Update evolution to 3.22.3
** Summary changed: - Update evolution to 3.22.2 + Update evolution to 3.22.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1639942 Title: Update evolution to 3.22.3 Status in evolution package in Ubuntu: Fix Released Status in evolution source package in Yakkety: Confirmed Bug description: Impact == https://git.gnome.org/browse/evolution/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution/log/?h=gnome-3-22 Test Case = Regression Potential To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1639942/+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 805303] Re: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui
Experiencing this problem developing PyQt5 applications, in regards to QTextEdit items. Currently the only fix is to use a non-native style. See here: http://stackoverflow.com/questions/35351024/pyqt5-gtk- critical-ia-gtk-widget-style-get-assertion-gtk-is-widget-widg Any ideas of how related these issues are? -- 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/805303 Title: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui Status in Ubuntu: Fix Released Status in qt4-x11 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in The Oneiric Ocelot: Fix Released Status in qt4-x11 source package in Oneiric: Fix Released Status in xorg-server source package in Oneiric: Invalid Bug description: vlc will hang when trying to open anything additional - it also appears to crash unity-window-decorator among other things (have crash report on that) Ex.'s - the playlist, tools > preferences and so forth Switching the qt4 gui to anything but 'default' (gtk+) in qtconfig-qt4 and it works without incidence (tooltips are empty bit otherwise good). Will attach xsession.errors, reflects a login, opening vlc, opening xsession.errors, then attempting to open playlist window in vlc. (using nvidia-current) Note to Vlc users - I've found clearlooks to be best choice, should be good for other apps as well. Also do as mentioned in comment 13 Note to Anki users - please review comments 20, 22 for current workaround This happens with many Qt4 and PyQt4 applications. Some errors displayed (from comments 16 and 18): (python:2901): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed (python:2901): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed QWidget::setMinimumSize: (/MainWindow) The largest allowed size is (16777215,16777215) X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x0 X Error: BadAlloc (insufficient resources for operation) 11 Major opcode: 53 (X_CreatePixmap) Resource id: 0x15a X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension:152 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x42004f6 X Error: RenderBadPicture (invalid Picture parameter) 174 Extension:152 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x42004f6 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x42004f6 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: vlc 1.1.10-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-9.43lp760131v201106060906-generic 2.6.38.7 Uname: Linux 2.6.38-9-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun Jul 3 23:23:42 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to oneiric on 2011-07-03 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/805303/+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 1342175] Re: [upstream] Poor performance with find & replace with empty value on large data set
Hi Could someone help in pointing me in the right direction to upgrade our current version to the one that fixes the problem? I have tried this on Linux Mint 18.1 Beta which installs Libreoffice Calc 5.1.4.2, and the problem still exists. The real issue seems to be that the Find/Replace function is trying to populate thousands of records into a small window for display to the user and the system takes a very long time (> 15 min) to display this. In any case, the window is of not much use especially if more than 20-30 records are being replaced, as the user cannot do much with the information once the replacement has taken place. Alternatively, is there a patch that can be applied for only Calc which resolves this issue? Thanks for any help that I can get. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1342175 Title: [upstream] Poor performance with find & replace with empty value on large data set Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Trusty: Fix Released Bug description: [SRU justification] [Impact] Hang or Very slow performance after replaceall or searchall massive data Regression in Find and Replace with LO Calc 4.2 (last worked in 4.1). It now takes a long time to "Find and Replace" if the to be replaced is to nothing. See comment #5/#6 of upstream for reproducer. See commend #8 for bibisect. [Test Case] fill A column to 0 select A column Replace All 0 to " " ( null space ) [Regression Potential] restricted, relevant patches are currently: - upstream master - all upstream 4.4.0 alpha/beta builds - upstream 4-4 branch - backported (by me) to upstream 4-3 branch => thus also included in upstream 4.3.5~rc1 released on November, 27th => thus will also be released by upstream 4.3.5 on ~December, 18th - backported to 4.3.4/utopic package (downstream, Ubuntu only) - backported to 4.2.7/trusty package (downstream, Ubuntu only) - included in all current 4.3.x and 4.2.x backports in the LibreOffice PPAs - included in all the 4.4~beta1 builds on the LibreOffice prereleases PPA [Other Info] upstream patch http://cgit.freedesktop.org/libreoffice/core/commit/?id=1cf19ea84794ca065749667b480dfed2d27d47b7 http://cgit.freedesktop.org/libreoffice/core/commit/?id=1e721077b43de84edab2a3ed2f316ddcbec6e3ec http://cgit.freedesktop.org/libreoffice/core/commit/?id=91502a72c12c559442e8bf77c27a516b49c2a68d To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1342175/+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 1041336] Re: PCI/internal sound card not detected
this also happened on my PowerMac G5 -- 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/1041336 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 12.04 LTS Sound card work until update August, 24. After the update and restart the sound card is not working anymore. No sound card listed in System settings "Audio" (only dummy output) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 Uname: Linux 3.2.0-29-generic-pae i686 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Aug 24 19:54 seq crw-rw---T 1 root audio 116, 33 Aug 24 19:54 timer AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 ArecordDevices: arecord: device_list:252: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Aug 24 20:45:54 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7181 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 2.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/20/2006:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7181:pvr2.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7181:rvr2.0:cvn:ct3:cvr: dmi.product.name: MS-7181 dmi.product.version: 2.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1041336/+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 1649768] [NEW] FTBFS : Segmentation fault (core dumped) ./temacs --batch
Public bug reported: Ubuntu: 16.10 yakkety emacs24: Installed: 24.5+1-6ubuntu3 Candidate: 24.5+1-6ubuntu3 Version table: *** 24.5+1-6ubuntu3 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status gcc: Installed: 4:6.1.1-1ubuntu2 Candidate: 4:6.1.1-1ubuntu2 gcc-5: Installed: 5.4.1-2ubuntu2 Candidate: 5.4.1-2ubuntu2 Linux Hedy 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux cd debian; debuild -us -us -b ... gcc -Demacs -I. -I. -I../lib -I./../lib -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircommon -I/usr/include/mircookie -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/alsa -pthread -I/usr/include/librsvg-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/x86_64-linux-gnu/ImageMagick-6 -I/usr/include/ImageMagick-6 -I/usr/include/libxml2 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/freetype2 -I/usr/include/freetype2 -MMD -MF deps/.d -MP -I/usr/include/p11-kit-1 -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/home/themusicgod1/emacs-24/emacs24-24.5+1=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -no -pie -Wl,-znocombreloc -Wl,-Bsymbolic-functions -Wl,-z,relro -no-pie \ -o temacs vm-limit.o dispnew.o frame.o scroll.o xdisp.o menu.o xmenu.o window.o charset.o coding.o category.o ccl.o character.o chartab.o bidi.o cm.o term.o terminal.o xfaces.o xterm.o xfns.o xselect.o xrdb.o xsmfns.o xsettings.o gtkutil.o emacsgtkfixed.o dbusbind.o emacs.o keyboard.o macros.o keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o minibuf.o fileio.o dired.o cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o alloc.o data.o doc.o editfns.o callint.o eval.o floatfns.o fns.o font.o print.o lread.o syntax.o unexelf.o bytecode.o process.o gnutls.o callproc.o region-cache.o sound.o atimer.o doprnt.o intervals.o textprop.o composite.o xml.o gfilenotify.o profiler.o decompress.o xfont.o ftfont.o xftfont.o ftxfont.o fontset.o fringe.o image.o xgselect.o terminfo.o lastfile.o gmalloc.o ralloc.o ../lib/libgnu.a -ltiff -ljpeg -lpng16 -lz -lm -lgif -lXpm -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 - lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lX11 -lXrender -lXft -lasound -lrsvg-2 -lm -lgio-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lcairo -lMagickWand-6.Q16 -lMagickCore-6.Q16 -lacl-lrt -ldbus-1 -lXrandr -lXinerama -lxml2 -lgpm -ltinfo -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgconf-2 -lglib-2.0 -lgobject-2.0 -lglib-2.0 -lselinux -lfreetype -lfontconfig -lfreetype -lfreetype -lotf -lfreetype -lm17n-core -lm17n-flt -lm17n-core -lgnutls -lpthread -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lm -lz /bin/mkdir -p ../etc : test "no" = "yes" || \ test "X" = X || -r temacs test "no" = "yes" || test -z "setfattr" || \ setfattr -n user.pax.flags -v er temacs cd ../lisp; /usr/bin/make -w update-subdirs make[4]: Entering directory '/home/themusicgod1/emacs-24/emacs24-24.5+1/debian/build-x/lisp' for file in `find . -type d -print`; do case $file in .*/cedet* | .*/leim* ) ;; *) wins="$wins${wins:+ }$file" ;; esac; done; \ for file in $wins; do \ ./../build-aux/update-subdirs $file; \ done; make[4]: Leaving directory '/home/themusicgod1/emacs-24/emacs24-24.5+1/debian/build-x/lisp' if test "no" = "yes"; then \ rm -f bootstrap-emacs; \ ln temacs bootstrap-emacs; \ else \ ./temacs --batch --load loadup bootstrap || exit 1; \ test "X" = X || -zex emacs; \ mv -f emacs bootstrap-emacs; \ fi /bin/bash: line 7: 11934
Re: [Desktop-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Till- Still having a problem with this. The auto updates will not launch and I have several program updates that are on hold. Additionally, I have tried to install several pieces of software from the library and the authentication link does not launch. Steve Jones Sacramento, CA USA From: boun...@canonical.comon behalf of Till Kamppeter <1642...@bugs.launchpad.net> Sent: Friday, December 9, 2016 9:08:31 AM To: svjones4...@hotmail.com Subject: [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 xnox, can you have a look into this? -- You received this bug notification because you are subscribed to a duplicate bug report (1643257). https://bugs.launchpad.net/bugs/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Status in init-system-helpers package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: This is in xenial-proposed, please block release to -updates accordingly :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Status in init-system-helpers package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: This is in xenial-proposed, please block release to -updates accordingly :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package
[Desktop-packages] [Bug 1644021] Re: Firefox doesn't include EmojiOne font
** Description changed: Firefox has shipped with an emoji font since version 50.0, but Ubuntu doesn't include it in their Firefox packages. - When opening a page in Firefox containing emoji characters, the black - and white glyphs from DejaVu are displayed instead of the EmojiOne - glyphs. + Therefore, when opening a page in Firefox containing emoji characters, + the black and white glyphs from DejaVu are displayed instead of the + glyphs from the EmojiOneMozilla font. According to http://packages.ubuntu.com/xenial- updates/amd64/firefox/filelist, EmojiOneMozilla.ttf is not included in the firefox package in Ubuntu's repositories. Manual installing this font and verifying that it works: 1) Download Firefox tarball from Firefox website 2) Extract EmojiOneMozilla.ttf from /firefox/fonts/ 3) Copy EmojiOneMozilla.ttf to /usr/lib/firefox/fonts/ 4) Quit Ubuntu session and launch a new one 5) Launch Firefox and go to http://getemoji.com/ - 6) Open a page containing emoji characters + 6) Open a page containing emoji characters such as https://eosrei.github.io/emojione-color-font/full-demo.html + 7) Now, instead of using glyphs from DejaVu, the majority of emoji on this page are taken from EmojiOneMozilla.ttf ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 50.0+build2-0ubuntu0.12.04.2 ProcVersionSignature: Ubuntu 3.13.0-101.148~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-101-generic. ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gris 2087 F pulseaudio BuildID: 20161114145344 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf880 irq 42' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:10ec0272,15580771,0011 HDA:80862804,80860101,0010' Controls : 52 Simple ctrls : 16 Channel: Unavailable Date: Tue Nov 22 22:31:27 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.14 metric 2 Locales: extensions.sqlite corrupt or missing MarkForUpload: True MostRecentCrashID: bp-bc8d2df2-4862-40a6-987d-4234e2160922 Plugins: Windows Media Player Plug-in 10 (compatible; Totem) - /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla) VLC Multimedia Plugin (compatible Totem 3.0.1) - /usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla) DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so (totem-mozilla) QuickTime Plug-in 7.6.6 - /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) PrefErrors: 'utf8' codec can't decode byte 0xe9 in position 14394: invalid continuation byte Profiles: Profile0 (Default) - LastVersion=50.0/20161114145344 (In use) RelatedPackageVersions: totem-mozilla 3.0.1-0ubuntu21.1 rhythmbox-mozilla 2.96-0ubuntu4.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-bc8d2df2-4862-40a6-987d-4234e2160922 bp-8d5e91df-7bcf-4edb-8642-657f92160922 bp-fc7bab24-1a1a-4a80-9d5f-f86852160922 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: CALPELLACRB.86C..X.00 dmi.board.asset.tag: Tag 12345 dmi.board.name: W760C dmi.board.vendor: CLEVO Co. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrCALPELLACRB.86C..X.00:bd05/05/2010:svnCLEVOCo.:pnW76OC:pvrNotApplicable:rvnCLEVOCo.:rnW760C:rvrNotApplicable:cvnCLEVO:ct9:cvrN/A: dmi.product.name: W76OC dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO Co. ** Description changed: Firefox has shipped with an emoji font since version 50.0, but Ubuntu doesn't include it in
[Desktop-packages] [Bug 1225467] Re: Pashto keyboard bug
[Expired for xkeyboard-config (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xkeyboard-config (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1225467 Title: Pashto keyboard bug Status in xkeyboard-config package in Ubuntu: Expired Bug description: On Pashto keyboard ALTGR+U KEY should yield U+0659 ARABIC ZWARAKAY and ALTGR+Y KEY U+0653 ARABIC MADDAH ABOVE. Instead, they yield wacko Latin characters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1225467/+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 1632162] Re: Slow LibreOffice Calc file save operations
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1632162 Title: Slow LibreOffice Calc file save operations Status in libreoffice package in Ubuntu: Expired Bug description: When saving a large spread sheet (209k) with lots of comments, Calc (LibreOffice) take 50 minutes to save the file on the first attempt. The screen goes gray and we wait. Once completed, a second save with take about 12 seconds. Also screen movement from cell to cell is jerky. If a page up/down/left/right is executed, again the screen locks up as the program pans a few spaces at a time. Painfully slow. Make using the application impossible. This did not happen with with the same file in Ubuntu 14.04 LTS. It would take 10 seconds to complete the save. Cursor movement around the screen was crisp. 1- Ubuntu Release 16.04 LTS 2- Version: 5.2.2.2 Build ID: 1:5.2.2-0ubuntu1~xenial0 CPU Threads: 2; OS Version: Linux 4.4; UI Render: default; Locale: en-US (en_US.UTF-8); Calc: group regards, Russ Jansch mister_r...@yahoo.com ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.16 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Oct 10 20:20:20 2016 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to xenial on 2016-08-19 (52 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2016-09-01T11:40:06.042988 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1632162/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
The bug also affects me on 12.04. Often get the "libavcodec may be vulnerable or is not supported, and should be updated to play video" error. Will I have to upgrade to 14.04? Will the update for 12.04 eventually be available on the standard update package? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec Status in libav: Unknown Status in firefox package in Ubuntu: Confirmed Status in libav package in Ubuntu: Invalid Status in firefox source package in Precise: Confirmed Status in libav source package in Precise: Confirmed Status in firefox source package in Trusty: Fix Released Status in libav source package in Trusty: Fix Released Bug description: Whenever it tries to play a video, Firefox 50 displays this message at the top of every page: "libavcodec may be vulnerable or is not supported, and should be updated to play video" https://dxr.mozilla.org/mozilla-central/source/browser/locales/en- US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742 Firefox refuses any libavcodec version prior to 54.35.1 (unless media.libavcodec.allow-obsolete==true). https://dxr.mozilla.org/mozilla- central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60 Users should not be subjected to this warning, as it is vague (does not instruct them how to fix it). Ubuntu 14.04 LTS should ship with an updated version of libavcodec. DistroRelease: Ubuntu 14.04 Package: firefox 50.0+build2-0ubuntu0.14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/libav/+bug/1643467/+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 1644021] Re: Firefox doesn't include EmojiOne font
** Description changed: - Since Firefox 50 Emoji could be used inside a web page: https://www.mozilla.org/en-US/firefox/50.0/releasenotes/ - Firefox 50 release :" Added a built-in Emoji set for operating systems without native Emoji fonts (Windows 8.0 and lower and Linux) " + Firefox has shipped with an emoji font since version 50.0, but Ubuntu + doesn't include it in their Firefox packages. - Step to reproduce: - 1) Update Firefox to Firefox 50 - 2) Launch Firefox - 3) Go to http://getemoji.com/ + When opening a page in Firefox containing emoji characters, the black + and white glyphs from DejaVu are displayed instead of the EmojiOne + glyphs. - Actual result: a lot Emoji are not here + According to http://packages.ubuntu.com/xenial- + updates/amd64/firefox/filelist, EmojiOneMozilla.ttf is not included in + the firefox package in Ubuntu's repositories. - Expected Result: All Emoji sould be shown - - Workform: Manual install of the Emoji font: - 1) Download https://ftp.mozilla.org/pub/firefox/releases/50.0/linux-i686/en-US/firefox-50.0.tar.bz2 + Manual installing this font and verifying that it works: + 1) Download Firefox tarball from Firefox website 2) Extract EmojiOneMozilla.ttf from /firefox/fonts/ - 3) Copy EmojiOneMozilla.ttf in /usr/lib/firefox/fonts/ (badly it's no work in ~/.fonts/ ) - 4) Quit your Ubuntu's session and launch a new one + 3) Copy EmojiOneMozilla.ttf to /usr/lib/firefox/fonts/ + 4) Quit Ubuntu session and launch a new one 5) Launch Firefox and go to http://getemoji.com/ - 6) It's work! - - Mozilla decide that Firefox MUST read Emoji and install a font for that for Windows et Linux's users. Badly, Ubuntu remove it. - For a better interoperability, Ubuntu should add EmojiOneMozilla.ttf + 6) Open a page containing emoji characters ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 50.0+build2-0ubuntu0.12.04.2 ProcVersionSignature: Ubuntu 3.13.0-101.148~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-101-generic. ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gris 2087 F pulseaudio BuildID: 20161114145344 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf880 irq 42' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:10ec0272,15580771,0011 HDA:80862804,80860101,0010' Controls : 52 Simple ctrls : 16 Channel: Unavailable Date: Tue Nov 22 22:31:27 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.14 metric 2 Locales: extensions.sqlite corrupt or missing MarkForUpload: True MostRecentCrashID: bp-bc8d2df2-4862-40a6-987d-4234e2160922 Plugins: Windows Media Player Plug-in 10 (compatible; Totem) - /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla) VLC Multimedia Plugin (compatible Totem 3.0.1) - /usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla) DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so (totem-mozilla) QuickTime Plug-in 7.6.6 - /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) PrefErrors: 'utf8' codec can't decode byte 0xe9 in position 14394: invalid continuation byte Profiles: Profile0 (Default) - LastVersion=50.0/20161114145344 (In use) RelatedPackageVersions: totem-mozilla 3.0.1-0ubuntu21.1 rhythmbox-mozilla 2.96-0ubuntu4.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-bc8d2df2-4862-40a6-987d-4234e2160922 bp-8d5e91df-7bcf-4edb-8642-657f92160922 bp-fc7bab24-1a1a-4a80-9d5f-f86852160922 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: CALPELLACRB.86C..X.00 dmi.board.asset.tag: Tag 12345 dmi.board.name: W760C dmi.board.vendor: CLEVO Co.
[Desktop-packages] [Bug 1644021] Re: Firefox doesn't include EmojiOne font
** Summary changed: - Firefox 50 must support Emoji + Firefox doesn't include EmojiOne font -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1644021 Title: Firefox doesn't include EmojiOne font Status in firefox package in Ubuntu: Confirmed Bug description: Since Firefox 50 Emoji could be used inside a web page: https://www.mozilla.org/en-US/firefox/50.0/releasenotes/ Firefox 50 release :" Added a built-in Emoji set for operating systems without native Emoji fonts (Windows 8.0 and lower and Linux) " Step to reproduce: 1) Update Firefox to Firefox 50 2) Launch Firefox 3) Go to http://getemoji.com/ Actual result: a lot Emoji are not here Expected Result: All Emoji sould be shown Workform: Manual install of the Emoji font: 1) Download https://ftp.mozilla.org/pub/firefox/releases/50.0/linux-i686/en-US/firefox-50.0.tar.bz2 2) Extract EmojiOneMozilla.ttf from /firefox/fonts/ 3) Copy EmojiOneMozilla.ttf in /usr/lib/firefox/fonts/ (badly it's no work in ~/.fonts/ ) 4) Quit your Ubuntu's session and launch a new one 5) Launch Firefox and go to http://getemoji.com/ 6) It's work! Mozilla decide that Firefox MUST read Emoji and install a font for that for Windows et Linux's users. Badly, Ubuntu remove it. For a better interoperability, Ubuntu should add EmojiOneMozilla.ttf ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 50.0+build2-0ubuntu0.12.04.2 ProcVersionSignature: Ubuntu 3.13.0-101.148~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-101-generic. ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gris 2087 F pulseaudio BuildID: 20161114145344 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xf880 irq 42' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:10ec0272,15580771,0011 HDA:80862804,80860101,0010' Controls : 52 Simple ctrls : 16 Channel: Unavailable Date: Tue Nov 22 22:31:27 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.14 metric 2 Locales: extensions.sqlite corrupt or missing MarkForUpload: True MostRecentCrashID: bp-bc8d2df2-4862-40a6-987d-4234e2160922 Plugins: Windows Media Player Plug-in 10 (compatible; Totem) - /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla) VLC Multimedia Plugin (compatible Totem 3.0.1) - /usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla) DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so (totem-mozilla) QuickTime Plug-in 7.6.6 - /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) PrefErrors: 'utf8' codec can't decode byte 0xe9 in position 14394: invalid continuation byte Profiles: Profile0 (Default) - LastVersion=50.0/20161114145344 (In use) RelatedPackageVersions: totem-mozilla 3.0.1-0ubuntu21.1 rhythmbox-mozilla 2.96-0ubuntu4.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-bc8d2df2-4862-40a6-987d-4234e2160922 bp-8d5e91df-7bcf-4edb-8642-657f92160922 bp-fc7bab24-1a1a-4a80-9d5f-f86852160922 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: CALPELLACRB.86C..X.00 dmi.board.asset.tag: Tag 12345 dmi.board.name: W760C dmi.board.vendor: CLEVO Co. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrCALPELLACRB.86C..X.00:bd05/05/2010:svnCLEVOCo.:pnW76OC:pvrNotApplicable:rvnCLEVOCo.:rnW760C:rvrNotApplicable:cvnCLEVO:ct9:cvrN/A: dmi.product.name: W76OC
[Desktop-packages] [Bug 1648989] Re: Sometimes after resume there is a problem with text
I'm not sure what the text rendering stack is, but I do know it's not xorg. :) ** Package changed: xorg (Ubuntu) => ubuntu -- 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/1648989 Title: Sometimes after resume there is a problem with text Status in Ubuntu: New Bug description: Sometimes (not often) after resume from suspend and unlocking screen (blocked with lightlocker) there is the problem with text in GTK applications (you can see it on screenshot). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Dec 10 19:15:34 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-19 (21 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1648989/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name
The commits in this merge can fix this bug: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0d7bf7dee31175d3eeab2bd5a9eef8e7b6618016 -- 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/1647283 Title: WiFi being detected as ethernet when race condition on renaming for persistent name Status in HWE Next: New Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: New Bug description: Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613 Version: NetworkManager 1.4.2 This bug happens after power-on with probability about 1/50. That means we need to reboot about 50 times to get into the buggy situation. "nmcli d" shows the device type is ethernet: DEVICE TYPE STATECONNECTION wlp1s0 ethernet unavailable -- lo loopback unmanaged-- The bug starts from a race condition. But it is not the root cause. I've also attach 2 logs. One is in good situation. Another is in bad situation. This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff. In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is: * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared. * Inside the NM, it is still using "wlan0" in "_linktype_get_type()". * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type(). * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared. * And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0. Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet. But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet. I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%
I got the same machine and restored the system to factory image. After doing some check and write some intel reg value for testing, then I can't reproduce this issue any more, even do a cold boot or restore the image again. BTW, the patched kernel on #4 seems doesn't help. -- 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/1646537 Title: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in xorg source package in Vivid: Invalid Status in linux source package in Xenial: Fix Released Status in xorg source package in Xenial: Invalid Bug description: Back-light sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Issue is interment in occurrence. Will be reproducible with the command "sudo pm-suspend" & or close/reopen laptop lid for a period of time days or hours, then go a period of time, days or hours without being able to trigger it again. This is irrespective of running "apt-get update && apt-get upgrade -y" and has continued to be intermittent on last 3 versions of 3.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 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: Thu Dec 1 10:06:43 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06e5] InstallationDate: Installed on 2016-11-22 (8 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 0W7V82 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 1 09:14:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646537/+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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Ok, I do not see anything obvious from the log. Did you attempt to pair your headphones whilst pulseaudio was running? TO be sure, delete the pairing from bluetooth preferences if it exists, and start fresh. Load pulse as per instructions to get the log, attempt to pair the bluetooth headphones, wait till the pair fails/pulse seems to crash. If pulse is still running, terminate it and then submit the log to the bug. Thanks. -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Yakkety: Fix Released Bug description: Impact: A patch we carry for Ubuntu touch introduced a change that originally was required to make sure PulseAudio did not crash. This patch was ported to PulseAudio 8 in Xenial, but the patch author's bluetooth hardware that was to hand at the time worked so was assumed to be ok. However, the opposite is now happening, i.e PulseAudio is crashing with a subset of Bluetooth hardware. Regression potential: Very low to none. As can be read in this report, much debugging and testing has been done to find the problem, and the eventual fix. Moreover the change is the removal of a patch hunk that removed a line of code originally present in PulseAudio. Test case: NOTE that this test case applies to bluetooth hardware that is identified as not working in this bug report. 1. Install, or upgrade to Xenial or yakkety. 2. Pair your bluetooth device in the bluetooth settings in the relevant settings application for your desktop environment. 3. Once paired, you will notice that sound stops working, as pulseaudio has thrown an assertion error. 4. You do not have to remove your audio device from the paired device list, but it may be easier to do so for the next part of the testing. 5. Update to the version of PulseAudio in xenial-proposed which is 1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1. 6. Re-pair your device. Audio should continue to work, and you should be able to switch to your bluetooth device and use it. Original bug report: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1583088] Re: Randomly corrupt characters in Unity8
This is still happening in zesty (seen today in the Unity8 indicator menu and logout dialog). It looks like the text renderer might have mistaken buffer width for buffer stride in some cases...? ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt characters in Unity8 Status in Canonical System Image: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Corrupted characters in text rendering, mainly in Unity8 window titlebars. I think this is a new issue. It only started happening (on xenial desktop) in the past month or two. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1649662] Re: resizing a gtk+3/mir app makes it unusable
Invalid for GTK -- the toolkit can never cause such stretching. Invalid for Mir -- Mir still works well elsewhere. If your pixels are stretched then that's definitely a server/compositor bug. So QtMir or Unity8. I can't reproduce the bug in regular 17.04 so assume it's just a problem in proposed... ** Changed in: ubuntu Status: New => Invalid ** Changed in: mir (Ubuntu) Status: New => Invalid ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Summary changed: - resizing a gtk+3/mir app makes it unusable + resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working ** Changed in: qtmir (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Tags added: unity8-desktop ** Changed in: canonical-devices-system-image Importance: Undecided => High -- 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/1649662 Title: resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: ubuntu 17.04 unity8 + proposed mir 0.25 miral 0.25 unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 [installed,automatic] steps: 1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for ex). if you are not sure how to launch a gtk3 app run "ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch " 2) resize the window (the context gets stretched in a weird way and input doesn't work anymore) see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649662/+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 1649662] [NEW] resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working
You have been subscribed to a public bug: ubuntu 17.04 unity8 + proposed mir 0.25 miral 0.25 unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 [installed,automatic] steps: 1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for ex). if you are not sure how to launch a gtk3 app run "ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch " 2) resize the window (the context gets stretched in a weird way and input doesn't work anymore) see attached screenshot ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: mir (Ubuntu) Importance: Undecided Status: Invalid ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working https://bugs.launchpad.net/bugs/1649662 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. -- 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 1649751] [NEW] [20BXCTO1WW, Intel Broadwell HDMI, Digital Out, HDMI] fails after suspend/resume
Public bug reported: HDMI sound works initially (actually I'm using DisplayPort), but after suspend/resume it no longer works. Based on what I read out there, I tried `pulseaudio --kill; sudo alsa force-reload; pulseaudio --start`, but to no avail. Happy to debug if there are things I should try. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: james 19076 F...m pulseaudio /dev/snd/controlC1: james 19076 F pulseaudio /dev/snd/controlC0: james 19076 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 13 21:10:09 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-10 (156 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Sound works for a while, then breaks Title: [20BXCTO1WW, Intel Broadwell HDMI, Digital Out, HDMI] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: JBET56WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1649751 Title: [20BXCTO1WW, Intel Broadwell HDMI, Digital Out, HDMI] fails after suspend/resume Status in alsa-driver package in Ubuntu: New Bug description: HDMI sound works initially (actually I'm using DisplayPort), but after suspend/resume it no longer works. Based on what I read out there, I tried `pulseaudio --kill; sudo alsa force-reload; pulseaudio --start`, but to no avail. Happy to debug if there are things I should try. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: james 19076 F...m pulseaudio /dev/snd/controlC1: james 19076 F pulseaudio /dev/snd/controlC0: james 19076 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 13 21:10:09 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-10 (156 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Sound works for a while, then breaks Title: [20BXCTO1WW, Intel Broadwell HDMI, Digital Out, HDMI] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: JBET56WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1649751/+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 738724] Re: please enable popsquares screensaver
This has been fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/738724 Title: please enable popsquares screensaver Status in xscreensaver package in Ubuntu: Fix Released Bug description: It was disabled because of the name clash with the one in gnome- screensaver. It has now been removed in Ubuntu gnome-screensaver, so it can be put back in xscreensaver again (only the .desktop file is missing). This will not happen in Debian yet, since the gnome-screensaver there (and upstream) still ships its own popsquares. PREVIOUSLY LINKED QUESTION: https://answers.launchpad.net/ubuntu/+source/xscreensaver/+question/149793 ORIGINAL REPORT: Binary package hint: xscreensaver On a new install of Lucid, I can't find the popsquares screensaver, which was previously part of xscreensaver. The changelog for the gnome-screensaver package shows that it was recently removed from there because the developers thought it was part of the xscreensaver-extra package (see https://launchpad.net/ubuntu/lucid/+source/gnome- screensaver/+changelog for gnome-screensaver 2.28.0-1ubuntu1). However, the popsquares screensaver is not currently listed as part of the xscreensaver-extra package. This particular screensaver was a favorite of my son. Any chance it can be restored? If not, any suggestions on how to add it manually? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/738724/+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 1648920] Re: Option does not work greeter-show-remote-login
** Package changed: lightdm (Ubuntu) => lightdm-gtk-greeter (Ubuntu) ** Changed in: lightdm-gtk-greeter (Ubuntu) Status: Incomplete => 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/1648920 Title: Option does not work greeter-show-remote-login Status in lightdm-gtk-greeter package in Ubuntu: New Bug description: I set the value of this option greeter-show-remote-login=true. When you restart the computer, i did not see an offer remote login! My version: lightdm 1.10.3 I make every possible logs, and I hope for your speedy assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1648920/+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 738724] Re: please enable popsquares screensaver
** Changed in: xscreensaver (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/738724 Title: please enable popsquares screensaver Status in xscreensaver package in Ubuntu: Fix Released Bug description: It was disabled because of the name clash with the one in gnome- screensaver. It has now been removed in Ubuntu gnome-screensaver, so it can be put back in xscreensaver again (only the .desktop file is missing). This will not happen in Debian yet, since the gnome-screensaver there (and upstream) still ships its own popsquares. PREVIOUSLY LINKED QUESTION: https://answers.launchpad.net/ubuntu/+source/xscreensaver/+question/149793 ORIGINAL REPORT: Binary package hint: xscreensaver On a new install of Lucid, I can't find the popsquares screensaver, which was previously part of xscreensaver. The changelog for the gnome-screensaver package shows that it was recently removed from there because the developers thought it was part of the xscreensaver-extra package (see https://launchpad.net/ubuntu/lucid/+source/gnome- screensaver/+changelog for gnome-screensaver 2.28.0-1ubuntu1). However, the popsquares screensaver is not currently listed as part of the xscreensaver-extra package. This particular screensaver was a favorite of my son. Any chance it can be restored? If not, any suggestions on how to add it manually? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/738724/+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 1649668] Re: PCI/internal sound card not detected Acer Aspire E5-575 Intel Corporation Device 9d71
I filed a similar bug: 1649727 -- 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/1649668 Title: PCI/internal sound card not detected Acer Aspire E5-575 Intel Corporation Device 9d71 Status in alsa-driver package in Ubuntu: New Bug description: I am running Ubuntu 16.04 LTS on my Acer Aspire E5-575 with kernel 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linuxmy. my system has no sound (built in speakers and headphone jack)and only shows a dummy output. I have follow many forms for answers with no luck. Playing around on my own I have found that the the issue seems to be with the kernel. The problem seems to go away when reverting back to kernel 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux. when I switch to this kernel all audio functions appear to function properly. I do not know if anyone else is experiencing this or similar issue, or if this has already been solved but for now using the 4.4.0-31 kernel seems to be the only workaround for me at the moment. Please let me know if their is any more information I can provide to help solve this issue. Hear is some information about my system: $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 Running the following commands on kernel 4.4.0-31 $ sudo lspci -v 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) Subsystem: Acer Incorporated [ALI] Device 1094 Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at b132 (64-bit, non-prefetchable) [size=16K] Memory at b131 (64-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 3 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel $ sudo aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC255 Analog [ALC255 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.4.0-31-generic/kernel/sound/isa/sb/snd-sb-common.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-podhd.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-toneport.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-pod.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-line6.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-variax.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/6fire/snd-usb-6fire.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/misc/snd-ua101.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/bcd2000/snd-bcd2000.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/hiface/snd-usb-hiface.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/snd-usbmidi-lib.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/snd-usb-audio.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/caiaq/snd-usb-caiaq.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/usx2y/snd-usb-us122l.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/usx2y/snd-usb-usx2y.ko /lib/modules/4.4.0-31-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.4.0-31-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/xtensa/snd-soc-xtfpga-i2s.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-ssi.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-esai.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-imx-audmux.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-asrc.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-sai.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-spdif.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/snd-soc-core.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/generic/snd-soc-simple-card.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-spdif-tx.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-ssm2602-spi.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-tfa9879.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-cs42l56.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-tlv320aic23.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-cs35l32.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-max98090.ko
[Desktop-packages] [Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup
Hello there! The bug reported here is not only valid for Ubuntu 16.04 I'm using Ubuntu 14.04 in an old desktop PC (32 bits). Everything worked fine until the latest update. Now I cannot start Firefox, not even with "-safe-mode". What I get is: - OLDEST-ubuntu:~> firefox -safe-mode (firefox:2609): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed (firefox:2609): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed (firefox:2609): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed (firefox:2609): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed ExceptionHandler::GenerateDump cloned child 2644 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... OLDEST-ubuntu:~> - Do you know when would appear a patch for this issue??? Thanks in advance, -- 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/1582496 Title: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup Status in gnome-session package in Ubuntu: Confirmed Bug description: I submitted this question a week but did not receive an answer or advice to solving them. https://answers.launchpad.net/ubuntu/+source /gnome-session/+question/293479 These failures are still plaguing my syslog every time I activate Nautilus. Appreciate help to resolve these failures. Earlier question After a recent updating, I notice these failures in the systemlogs. May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:35:01 Eliot org.gnome.zeitgeist.Engine[1400]: (zeitgeist-daemon:2197): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed May 9 16:42:54 Eliot gnome-session[1576]: (nautilus:2606): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 16:59:53 Eliot gnome-session[1576]: (nautilus:2842): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 17:00:19 Eliot gnome-session[1576]: (nautilus:2857): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed The last three failures appears whenever I activate nautilus. Nautilus will appear and work as usual. How can I resolve these failure notices? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1582496/+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 1649723] Re: Preview of pages sometimes empty
This is the test PDF with text ** Attachment added: "This is the test PDF with text" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1649723/+attachment/4791355/+files/test.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1649723 Title: Preview of pages sometimes empty Status in evince package in Ubuntu: New Bug description: With an PDF file like testpics.pdf, which contains a image on every page, scrolling in the preview area results in that area being empty. Scrolling again shows the previews again after some tries. This does also happen with PDF files like test.pdf, which only contains text. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 13 23:59:36 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: evince UpgradeStatus: Upgraded to yakkety on 2016-10-26 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1649723/+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 1649723] [NEW] Preview of pages sometimes empty
Public bug reported: With an PDF file like testpics.pdf, which contains a image on every page, scrolling in the preview area results in that area being empty. Scrolling again shows the previews again after some tries. This does also happen with PDF files like test.pdf, which only contains text. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 13 23:59:36 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: evince UpgradeStatus: Upgraded to yakkety on 2016-10-26 (48 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1649723 Title: Preview of pages sometimes empty Status in evince package in Ubuntu: New Bug description: With an PDF file like testpics.pdf, which contains a image on every page, scrolling in the preview area results in that area being empty. Scrolling again shows the previews again after some tries. This does also happen with PDF files like test.pdf, which only contains text. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 13 23:59:36 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: evince UpgradeStatus: Upgraded to yakkety on 2016-10-26 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1649723/+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 1649723] Re: Preview of pages sometimes empty
This is how it should look like ** Attachment added: "This is how it should look like" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1649723/+attachment/4791352/+files/ok.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1649723 Title: Preview of pages sometimes empty Status in evince package in Ubuntu: New Bug description: With an PDF file like testpics.pdf, which contains a image on every page, scrolling in the preview area results in that area being empty. Scrolling again shows the previews again after some tries. This does also happen with PDF files like test.pdf, which only contains text. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 13 23:59:36 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: evince UpgradeStatus: Upgraded to yakkety on 2016-10-26 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1649723/+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 1649723] Re: Preview of pages sometimes empty
This is the test PDF with images ** Attachment added: "This is the test PDF with images" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1649723/+attachment/4791354/+files/testpics.pdf ** Description changed: With an PDF file like testpics.pdf, which contains a image on every page, scrolling in the preview area results in that area being empty. Scrolling again shows the previews again after some tries. - This does not happen with PDF files like test.pdf, which only contains + This does also happen with PDF files like test.pdf, which only contains text. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 13 23:59:36 2016 JournalErrors: - Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. -Users in the 'systemd-journal' group can see all messages. Pass -q to -turn off this notice. - No journal files were opened due to insufficient permissions. + Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. + Users in the 'systemd-journal' group can see all messages. Pass -q to + turn off this notice. + No journal files were opened due to insufficient permissions. SourcePackage: evince UpgradeStatus: Upgraded to yakkety on 2016-10-26 (48 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1649723 Title: Preview of pages sometimes empty Status in evince package in Ubuntu: New Bug description: With an PDF file like testpics.pdf, which contains a image on every page, scrolling in the preview area results in that area being empty. Scrolling again shows the previews again after some tries. This does also happen with PDF files like test.pdf, which only contains text. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 13 23:59:36 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: evince UpgradeStatus: Upgraded to yakkety on 2016-10-26 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1649723/+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 1649723] Re: Preview of pages sometimes empty
This is how it looks after some scrolling down ** Attachment added: "This is how it looks after some scrolling down" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1649723/+attachment/4791353/+files/empty.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1649723 Title: Preview of pages sometimes empty Status in evince package in Ubuntu: New Bug description: With an PDF file like testpics.pdf, which contains a image on every page, scrolling in the preview area results in that area being empty. Scrolling again shows the previews again after some tries. This does also happen with PDF files like test.pdf, which only contains text. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 13 23:59:36 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: evince UpgradeStatus: Upgraded to yakkety on 2016-10-26 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1649723/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
The new Zesty Chromium 55 packages are much more stable than 54 for me. Haven't noticed any issues yet! They also install cleanly on 16.10. https://launchpad.net/~canonical-chromium- builds/+archive/ubuntu/stage/+packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium browser in xenial no longer trusts Symantec issued certificates. See [1]. 1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177 Ubuntu release: 16.04 chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 606624] Re: Nibbles - Invisible wall and Unexpected Death upon rebirth (gnibbles)
Hi, I believe this bug has been resolved in the recent re-write of Nibbles 3.22.0 ** Changed in: gnome-games (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-games in Ubuntu. https://bugs.launchpad.net/bugs/606624 Title: Nibbles - Invisible wall and Unexpected Death upon rebirth (gnibbles) Status in gnome-games package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-games As reported by others in the following thread: https://bugs.launchpad.net/gnome-games/+bug/574212 The following 2 behaviours can be observed: 1) Death upon rebirth 2) Unexplained death during play (not associated with reversal) I will assume that the same cause underlies both. Investigation has shown me that in the case of (2) the program believes you are colliding with another worm (often number 6) when the display shows that the other worm is in a completely different area of the board. Therefore there is a discrepancy between the internal board representation (board->walls) and the screen representation (clutter actor). In the case of (1) I imagine that there is an 'invisible segment' of worm close to the point at which you are reborn with which you collide. Therefore you die immediately after rebirth, whereas if you manage to change direction immediately you can avoid death. I have not yet made any progress in finding or fixing the underlying bug. :-( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/606624/+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 1624699] Re: Release Remmina 1.2 on Ubuntu 16.10
** Tags added: upgrade-software-version ** Changed in: remmina (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1624699 Title: Release Remmina 1.2 on Ubuntu 16.10 Status in remmina package in Ubuntu: Confirmed Bug description: Remmina 1.1 series it's old dated and the new series is 1.2, so this version should be released for Ubuntu 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1624699/+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 1647174] Re: opening menu for certain types of GtkComboBox causes Gdk-CRITICAL assertion 'GDK_IS_WINDOW (window)' failed
This bug was fixed in the package gtk+3.0 - 3.22.5-1ubuntu1 --- gtk+3.0 (3.22.5-1ubuntu1) zesty; urgency=medium * Merge with Debian (LP: #1647174). Remaining changes: + Install the settings.ini file to set our themes + Install a gsettings override to start filechoosers in the cwd + Enable Mir backend + debian/control.in: - Build-depend on adwaita-icon-theme-full for icon name check test + debian/rules: Mark additional known test failures: - box-shadow-changes-modify-clip.ui - label-text-shadow-changes-modify-clip.ui + 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 - 0001-gtkwindow-set-transparent-background-color.patch - ubuntu_fileselector_behaviour.patch - unity-border-radius.patch - unity-headerbar-maximized-mode.patch * Drop 'Use dh_strip --dbgsym-migration for proper upgrades' added in 3.22.4-1ubuntu1 since there is no file conflict here. Anyone with obsolete -dbg packages installed will need to manually remove the old -dbg packages, enable the ddebs repository, and install the appropriate -dbgsym packages. gtk+3.0 (3.22.5-1) unstable; urgency=medium * New upstream release. -- Jeremy BichaSat, 10 Dec 2016 13:52:57 -0500 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => 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/1647174 Title: opening menu for certain types of GtkComboBox causes Gdk-CRITICAL assertion 'GDK_IS_WINDOW (window)' failed Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 package in Debian: Fix Released Bug description: It happens when try to open any ComboBox or a CellRendererCombo: Gdk-CRITICAL **: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1647174/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
The Build on #68 does prevent the error but in/shortly after the loading of the page it crashes the tab. Display: Aw, Snap! without any hint why Tested with codingame.com (Crashes only after login) and amazon.(com|de) Tested with incognito modus, no active plugins. When will chromium 55 be available? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium browser in xenial no longer trusts Symantec issued certificates. See [1]. 1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177 Ubuntu release: 16.04 chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1649670] Re: unity-settings-daemon crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1567240 *** https://bugs.launchpad.net/bugs/1567240 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1567240, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1649670/+attachment/4791243/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1649670/+attachment/4791245/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1649670/+attachment/4791247/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1649670/+attachment/4791248/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1649670/+attachment/4791249/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1649670/+attachment/4791250/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1649670/+attachment/4791251/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1567240 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1649670 Title: unity-settings-daemon crashed with SIGSEGV in ffi_call_unix64() Status in unity-settings-daemon package in Ubuntu: New Bug description: None. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-settings-daemon 15.04.1+16.10.20161003-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-31.33-generic 4.8.11 Uname: Linux 4.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Dec 13 11:32:54 2016 ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon InstallationDate: Installed on 2015-07-19 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fb757b4e4d2:mov0x10(%rax),%rdi PC (0x7fb757b4e4d2) ok source "0x10(%rax)" (0x0010) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-settings-daemon StacktraceTop: ?? () from /usr/lib/unity-settings-daemon-1.0/libremote-display.so ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-settings-daemon crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1649670/+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 1573959] Re: On-screen text disappears after suspend
So it could be possible to identify the patch/commit on 4.8 that fixes the bug ? If it is, maybe a fixed kernel for 16.04 LTS could be released in main repository ? This should be a proper solution than to switch on kernel-ppa which will never be upgraded by APT (too new) and leaves the user without any security fixes ! Does anyone known how to reproduce the bug at every suspend ? I could test different kernel, if I could be sure on how to get the bug. Le 13 déc. 2016 14:32, "PeterPall" <1573...@bugs.launchpad.net> a écrit : Tested the final 4.9 kernel. If "sync to vblank" is active in ccsm it freezes the system at high cpu loads. ...but for all other settings 4.9 seems to be fine, too. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-intel/+bug/1573959/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: After resuming from a suspend, almost all text on screen is not visible. This includes menu items, text in all three boxes (list of folders, list of e-mails, e-mail body) in Thunderbird (with the curious exception of "ffl" in the File menu), top menu in Chromium (but not the menu obtained by pressing the hamburger button), and the menus produced by clicking items in the system tray. Also, the apport dialog had no text except for a few capital letters. ADDITIONAL INFORMATION: * initctl restart unity-panel-service restarts the panel, but the text is still missing * suspend and resume does not fix the issue * Logging out fixes the issue * Other affected applications: ** Chromium file select dialog ** Terminal (entire window) ** ttys 1-6 (Ctrl+Alt+F1, etc.) ** Document viewer (menus) ** Software Updater ** Rhythmbox ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc ** ubuntu-bug ** Nautilus ** LibreOffice Calc (spreadsheet text contents) ** Firefox * Unity dash is not affected. * Skype is not affected. * Mousing over a button in a dialog correctly shows the text. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 23 12:04:57 2016 DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics Controller [14c0:0075] InstallationDate: Installed on 2015-01-21 (457 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Compal VAW70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.01T01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Compal dmi.board.version: V1.01T01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: VAW70 dmi.product.version: V1.01T01 dmi.sys.vendor: Compal upstart.unity-panel-service-lockscreen.log: (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs:
[Desktop-packages] [Bug 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out
Confirmed this has been my most annoying bug. lshw *-network description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:06:00.0 logical name: wlp6s0 version: 6b serial: e8:2a:ea:b3:75:72 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-53-generic firmware=17.352738.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn resources: irq:35 memory:f790-f7901fff lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial uname -a Linux hostname 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- 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/1542733 Title: Connect to Hidden Wi-Fi Network, "Connect" grayed out Status in network-manager package in Ubuntu: Confirmed Bug description: Reproduce: 1. Create a static, connection to hidden Wi-Fi connection using nm-connection-editor 2. click nm-applet icon click "Connect to Hidden Wi-Fi Network" click pre-existing connection "Connect" is grayed out Work around is using terminal. nmcli c up id ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 6 15:58:22 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.55 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7c22db8e-2026-413b-86cd-0c796f177dd5 802-3-ethernet 1454790964 Sat 06 Feb 2016 02:36:04 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab 802-11-wireless 1454795858 Sat 06 Feb 2016 03:57:38 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab /org/freedesktop/NetworkManager/ActiveConnection/4 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code
[Desktop-packages] [Bug 1649668] [NEW] PCI/internal sound card not detected Acer Aspire E5-575 Intel Corporation Device 9d71
Public bug reported: I am running Ubuntu 16.04 LTS on my Acer Aspire E5-575 with kernel 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linuxmy. my system has no sound (built in speakers and headphone jack)and only shows a dummy output. I have follow many forms for answers with no luck. Playing around on my own I have found that the the issue seems to be with the kernel. The problem seems to go away when reverting back to kernel 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux. when I switch to this kernel all audio functions appear to function properly. I do not know if anyone else is experiencing this or similar issue, or if this has already been solved but for now using the 4.4.0-31 kernel seems to be the only workaround for me at the moment. Please let me know if their is any more information I can provide to help solve this issue. Hear is some information about my system: $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 Running the following commands on kernel 4.4.0-31 $ sudo lspci -v 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) Subsystem: Acer Incorporated [ALI] Device 1094 Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at b132 (64-bit, non-prefetchable) [size=16K] Memory at b131 (64-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 3 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel $ sudo aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC255 Analog [ALC255 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.4.0-31-generic/kernel/sound/isa/sb/snd-sb-common.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-podhd.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-toneport.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-pod.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-line6.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/line6/snd-usb-variax.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/6fire/snd-usb-6fire.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/misc/snd-ua101.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/bcd2000/snd-bcd2000.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/hiface/snd-usb-hiface.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/snd-usbmidi-lib.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/snd-usb-audio.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/caiaq/snd-usb-caiaq.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/usx2y/snd-usb-us122l.ko /lib/modules/4.4.0-31-generic/kernel/sound/usb/usx2y/snd-usb-usx2y.ko /lib/modules/4.4.0-31-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.4.0-31-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/xtensa/snd-soc-xtfpga-i2s.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-ssi.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-esai.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-imx-audmux.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-asrc.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-sai.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/fsl/snd-soc-fsl-spdif.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/snd-soc-core.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/generic/snd-soc-simple-card.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-spdif-tx.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-ssm2602-spi.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-tfa9879.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-cs42l56.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-tlv320aic23.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-cs35l32.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-max98090.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-wm8804-i2c.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-rt286.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-gtm601.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-wm8731.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-pcm512x.ko /lib/modules/4.4.0-31-generic/kernel/sound/soc/codecs/snd-soc-ak4613.ko
[Desktop-packages] [Bug 1464848] Re: Missing german translation
** No longer affects: flashplugin-nonfree (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1464848 Title: Missing german translation Status in console-setup package in Ubuntu: New Status in eog package in Ubuntu: Invalid Status in libpaper package in Ubuntu: New Status in nano package in Ubuntu: Invalid Status in pam package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: I'm using Ubuntu 15.10 dev with nano 2.4.1-1 and initially I have reported this issue here: http://savannah.gnu.org/bugs/?45287 . But it seems that this issue is specific to Ubuntu so I'm forwarding it to here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1464848/+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 1649662] [NEW] resizing a gtk+3/mir app makes it unusable
Public bug reported: ubuntu 17.04 unity8 + proposed mir 0.25 miral 0.25 unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 [installed,automatic] steps: 1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for ex). if you are not sure how to launch a gtk3 app run "ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch " 2) resize the window (the context gets stretched in a weird way and input doesn't work anymore) see attached screenshot ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: mir (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161213_202640214.png" https://bugs.launchpad.net/bugs/1649662/+attachment/4791233/+files/screenshot20161213_202640214.png ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- 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/1649662 Title: resizing a gtk+3/mir app makes it unusable Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: ubuntu 17.04 unity8 + proposed mir 0.25 miral 0.25 unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 [installed,automatic] steps: 1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for ex). if you are not sure how to launch a gtk3 app run "ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch " 2) resize the window (the context gets stretched in a weird way and input doesn't work anymore) see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649662/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
This bug was fixed in the package indicator-keyboard - 0.0.0+17.04.20161212-0ubuntu1 --- indicator-keyboard (0.0.0+17.04.20161212-0ubuntu1) zesty; urgency=medium [ Michael Terry ] * Work inside a snap by prefixing hard coded paths with $SNAP. (LP: #1629009) -- Rodney DawesMon, 12 Dec 2016 16:10:39 + ** Changed in: indicator-keyboard (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: Fix Released Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-location package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-network package in Ubuntu: Fix Released Status in indicator-power package in Ubuntu: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-transfer package in Ubuntu: Fix Released Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+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 1649360] Re: identifying a partitition in fstab by PARTLABEL creates a second entry for the partition, for it's file system label
@Phillip Susi (psusi) Indeed you misunderstood. I apologize for my bug report being much too long to read carefully, but it is my first bug report, and I wanted to be as complete as my understanding allows. This is wat I did say concerning the part that you misunderstood: ... When a partition has both a partition label and a filesystem label, and is identified in /etc/fstab by PARTLABEL= ... and ... I choose PARTLABEL= instead of LABEL= ... The shortcuts that I talk about that are based on the filesystem label, are generated by the system, although I do not know what part of it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1649360 Title: identifying a partitition in fstab by PARTLABEL creates a second shortcut for the partition, for it's file system label Status in udisks2 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 Short story: When a partition has both a partition label and a filesystem label, and is identified in /etc/fstab by PARTLABEL= , both file manager's side pane (thunar on Xubuntu) and the desktop (with the setting 'icons/default icons/Removable Devices/Disk and Drives') show two shortcuts for the partition: one for the /etc/fstab entry, named as the last pathname component of the mount point in /etc/fstab, and a self-generated second shortcut, named after the filesystem label. By some seemingly random process either of both shortcuts is mounted at some point, preventing the other one to be mounted, EVEN when that one is marked as automount in /etc/fstab. If the mounted shortcut is /etc/fstab's PARTLABEL= entry, it is mounted to the provided /etc/fstab mount point. If the mounted shortcut is that for the filesystem label, it is mounted to a temporary directory under /media/myusername/. In either case, the other shortcut can't be mounted then. This behaviour makes it unpredictable through which path a partition can be reached. The problem is not present for partitions without a filesystem label, even if they are identified in /etc/fstab by PARTLABEL= . As a workaround I reverted back to identifying the partitions in /etc/fstab by UUID=, which if I am right, is a filesystem feature. Identified as such, the destop and the file manager side bar show one shortcut only, named after the file system label, and mounting it to the /etc/fstab mount point. I read somewhere that the option to identify partitions by PARTLABEL= and PARTUUID= is a more recent addition to fstab-syntax, so my first guess is that the auto-mounting system isn't yet aware of these; it seems to collect and identify partitions by the uuid or label of the filesystem on each partition, and when comparing that to the /etc/fstab entries, it does not recognize them as being the same partition that is identified in /etc/fstab by it's uuid or label from the partition table. Long story: After using and learning linux (Xubuntu) for half a year, I decided to do the right thing and stop identifying partitions to be mounted by block special device node (/dev/sda1 to /dev/sdb4 for my setup), but by a persistent name. So I set out to change /etc/fstab to identify the partitions to mount by UUID=, and that went well and I felt safe. Only problem was that a week later, I had no clue which UUID is which partition, which made me uncomfortably uncertain. So I used 'parted' to name all my partitions with a meaningfull partition label, similar but not identical to the filesystem label that I had named them to with 'e2label', 'fatlabel' and 'ntfslabel'. I also changed /etc/fstab to reflect that, now identifying my partitions using the PARTLABEL= . I choose PARTLABEL= instead of LABEL=, because it requires more skill and privileges to change a partition label than to change a filesystem label, so it is 'more persistent'. From then on, the automatic mounting behaviour became erratic. The desktop and the side pane of the file manager now showed 2 shortcuts for each partition: one named like the filesystem label, another named like the last path component of the mount point in /etc/fstab. When mounting the partition is triggered,by clicking one of both shortcuts in on desktop or in filemanager, or by some other process, and even with automount in /etc/fstab, one of the shortcuts is used for mounting the partition, preventing the other one to be mounted as well later. By this behaviour the same partition could be accessed at either but not both mount points. Either the mount point provided in /etc/fstab/, which is accessible in file manager under an entry named after the last path component of that mount point, which is linked to the full mount path. Either a temporary mount point which 'the system' creates in my user's /media/myusername/ directory,
[Desktop-packages] [Bug 1649360] Re: identifying a partitition in fstab by PARTLABEL creates a second shortcut for the partition, for it's file system label
@Phillip Susi (psusi) Indeed you misunderstood. I apologize for my bug report being much too long to read carefully, but it is my first bug report, and I wanted to be as complete as my understanding allows. This is wat I did say concerning the part that you misunderstood: ... When a partition has both a partition label and a filesystem label, and is identified in /etc/fstab by PARTLABEL= ... and ... I choose PARTLABEL= instead of LABEL= ... But the title may be misleading. I made the distinction between entry in fstab and shortcut on desktop and in filemanager late into writing the report, and did not reflect that in the title. I will do that now. The shortcuts that I talk about that are based on the filesystem label, are generated by the system, although I do not know what part of it. ** Summary changed: - identifying a partitition in fstab by PARTLABEL creates a second entry for the partition, for it's file system label + identifying a partitition in fstab by PARTLABEL creates a second shortcut for the partition, for it's file system label -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1649360 Title: identifying a partitition in fstab by PARTLABEL creates a second shortcut for the partition, for it's file system label Status in udisks2 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 Short story: When a partition has both a partition label and a filesystem label, and is identified in /etc/fstab by PARTLABEL= , both file manager's side pane (thunar on Xubuntu) and the desktop (with the setting 'icons/default icons/Removable Devices/Disk and Drives') show two shortcuts for the partition: one for the /etc/fstab entry, named as the last pathname component of the mount point in /etc/fstab, and a self-generated second shortcut, named after the filesystem label. By some seemingly random process either of both shortcuts is mounted at some point, preventing the other one to be mounted, EVEN when that one is marked as automount in /etc/fstab. If the mounted shortcut is /etc/fstab's PARTLABEL= entry, it is mounted to the provided /etc/fstab mount point. If the mounted shortcut is that for the filesystem label, it is mounted to a temporary directory under /media/myusername/. In either case, the other shortcut can't be mounted then. This behaviour makes it unpredictable through which path a partition can be reached. The problem is not present for partitions without a filesystem label, even if they are identified in /etc/fstab by PARTLABEL= . As a workaround I reverted back to identifying the partitions in /etc/fstab by UUID=, which if I am right, is a filesystem feature. Identified as such, the destop and the file manager side bar show one shortcut only, named after the file system label, and mounting it to the /etc/fstab mount point. I read somewhere that the option to identify partitions by PARTLABEL= and PARTUUID= is a more recent addition to fstab-syntax, so my first guess is that the auto-mounting system isn't yet aware of these; it seems to collect and identify partitions by the uuid or label of the filesystem on each partition, and when comparing that to the /etc/fstab entries, it does not recognize them as being the same partition that is identified in /etc/fstab by it's uuid or label from the partition table. Long story: After using and learning linux (Xubuntu) for half a year, I decided to do the right thing and stop identifying partitions to be mounted by block special device node (/dev/sda1 to /dev/sdb4 for my setup), but by a persistent name. So I set out to change /etc/fstab to identify the partitions to mount by UUID=, and that went well and I felt safe. Only problem was that a week later, I had no clue which UUID is which partition, which made me uncomfortably uncertain. So I used 'parted' to name all my partitions with a meaningfull partition label, similar but not identical to the filesystem label that I had named them to with 'e2label', 'fatlabel' and 'ntfslabel'. I also changed /etc/fstab to reflect that, now identifying my partitions using the PARTLABEL= . I choose PARTLABEL= instead of LABEL=, because it requires more skill and privileges to change a partition label than to change a filesystem label, so it is 'more persistent'. From then on, the automatic mounting behaviour became erratic. The desktop and the side pane of the file manager now showed 2 shortcuts for each partition: one named like the filesystem label, another named like the last path component of the mount point in /etc/fstab. When mounting the partition is triggered,by clicking one of both shortcuts in on desktop or in filemanager, or by some other process, and even with automount in /etc/fstab, one of the shortcuts is used for
[Desktop-packages] [Bug 1639937] Re: Cannot set Emacs key bindings
I'm moving this bug from gnome-desktop to unity because ubuntu-gnome- desktop does not seem to exhibit the same problem. It might still be a chromium issue though so keeping that. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-desktop (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1639937 Title: Cannot set Emacs key bindings Status in chromium-browser package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: Fully up-to-date, freshly installed Zesty desktop. chromium-browser no longer seems to honor Gnome keybindings, e.g. % gconftool-2 --get /desktop/gnome/interface/gtk_key_theme Emacs % gsettings get org.gnome.desktop.interface gtk-key-theme 'Emacs' Also confirmed Emacs is the keyboard theme via gnome-tweak-tool However, chromium-browser on Zesty does not honor these keybindings either in the url bar, or in text entry windows such as this one. This is a regression from Yakkety. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: chromium-browser 53.0.2785.143-0ubuntu1.1307 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1639937/+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 1639965] Re: Alt doesn't always get forwarded to the application
Actually, I believe this is a unity7 bug since ubuntu-gnome-desktop does the right thing. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-desktop (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1639965 Title: Alt doesn't always get forwarded to the application Status in unity package in Ubuntu: New Bug description: I've begun to notice this problem on a fresh Zesty install. I've seen it with gnome-terminal, the standard switcher, and emacs25 but I suspect other applications may have a similar problem. Hitting an Alt+ combination seems fairly racy. Sometimes it will do what I expect but other times the key just gets eaten, with (almost) nothing apparent happening. For example, sometimes when I hit Alt-Tab, I get to the switcher and can happily switch away. Other times, the switcher does not come up until I release Alt+Tab and hit it again. Note that sometimes I might hit and hold Alt just a slight fraction before I hit the Tab key. The amount of time between hitting Alt and Tab is very small but unpredictable. When I say almost nothing happens when Alt+Tab isn't forwarded to the application, this isn't entirely true. When you're using an application like chromium-browser or emacs25 that's what I see. However, with gnome-terminal, as soon as I hit Alt (but before hitting TAB), I see the application's menus show up in the menu bar. But sometimes, no application menus show up and all you see is "Terminal". I haven't completely correlated this with whether Alt is passed to the application or not but it seems related. I.e. there's weird race condition here somewhere. I will try to A/B this behavior against a Yakkety desktop, but it does seem like a regression and it makes the desktop difficult to use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1639965/+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 1639937] Re: Cannot set Emacs key bindings
@cmiller: ping; any progress on this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1639937 Title: Cannot set Emacs key bindings Status in chromium-browser package in Ubuntu: New Status in gnome-desktop package in Ubuntu: New Bug description: Fully up-to-date, freshly installed Zesty desktop. chromium-browser no longer seems to honor Gnome keybindings, e.g. % gconftool-2 --get /desktop/gnome/interface/gtk_key_theme Emacs % gsettings get org.gnome.desktop.interface gtk-key-theme 'Emacs' Also confirmed Emacs is the keyboard theme via gnome-tweak-tool However, chromium-browser on Zesty does not honor these keybindings either in the url bar, or in text entry windows such as this one. This is a regression from Yakkety. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: chromium-browser 53.0.2785.143-0ubuntu1.1307 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1639937/+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 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
I'm getting the following error, yet I don't understand what I need to do about it. Help please. Thanks in advance. ** (appstreamcli:11741): DEBUG: Refreshing AppStream cache ** (appstreamcli:11741): DEBUG: Reading: /usr/share/app-info/xmls/org.freedesktop.fwupd.xml ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial_main_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial_restricted_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial_universe_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial_multiverse_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_main_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_restricted_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_universe_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_multiverse_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-security_main_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-security_restricted_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-security_universe_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-security_multiverse_dep11_Components-amd64.yml.gz ** (appstreamcli:11741): DEBUG: Reading: /var/cache/app-info/xmls/fwupd.xml ** (appstreamcli:11741): DEBUG: Detected colliding ids: plan.desktop was already added with the same priority. ** (appstreamcli:11741): DEBUG: Detected colliding ids: flcheckers.desktop was already added with the same priority. ** (appstreamcli:11741): DEBUG: Detected colliding ids: flblocks.desktop was already added with the same priority. ** (appstreamcli:11741): DEBUG: Detected colliding ids: flsudoku.desktop was already added with the same priority. ** (appstreamcli:11741): DEBUG: Replaced 'libreoffice-writer.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'eog.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'update-manager.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'gnome-session-properties.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'upstart-monitor.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'fcitx-configtool.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'fcitx.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'org.gnome.FileRoller.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'gnome-sudoku.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'libreoffice-math.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'xdiagnose.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'gnome-system-monitor.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'gnome-system-monitor-kde.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'software-properties-gnome.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'software-properties-gtk.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'software-properties-drivers.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'vino-preferences.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'vim.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'unity-wacom-panel.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'unity-keyboard-panel.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'unity-sound-panel.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'unity-bluetooth-panel.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'unity-user-accounts-panel.desktop' with data of higher priority. ** (appstreamcli:11741): DEBUG: Replaced 'unity-color-panel.desktop' with data of higher priority. **
[Desktop-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
a2dp.py does not work for me. the bluetooth headset doesn't even show up in the sound control. nothing i do makes it come back. restarting pulseaudio, reloading alsa, reloading module-bluetooth-discover. the only solution is to reboot. -- 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/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. 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 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader 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 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1649360] Re: identifying a partitition in fstab by PARTLABEL creates a second entry for the partition, for it's file system label
Maybe I misunderstood, but did you say that you edited /etc/fstab and put in two entries for the same partition? One using PARTLABEL and one using LABEL? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1649360 Title: identifying a partitition in fstab by PARTLABEL creates a second entry for the partition, for it's file system label Status in udisks2 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 Short story: When a partition has both a partition label and a filesystem label, and is identified in /etc/fstab by PARTLABEL= , both file manager's side pane (thunar on Xubuntu) and the desktop (with the setting 'icons/default icons/Removable Devices/Disk and Drives') show two shortcuts for the partition: one for the /etc/fstab entry, named as the last pathname component of the mount point in /etc/fstab, and a self-generated second shortcut, named after the filesystem label. By some seemingly random process either of both shortcuts is mounted at some point, preventing the other one to be mounted, EVEN when that one is marked as automount in /etc/fstab. If the mounted shortcut is /etc/fstab's PARTLABEL= entry, it is mounted to the provided /etc/fstab mount point. If the mounted shortcut is that for the filesystem label, it is mounted to a temporary directory under /media/myusername/. In either case, the other shortcut can't be mounted then. This behaviour makes it unpredictable through which path a partition can be reached. The problem is not present for partitions without a filesystem label, even if they are identified in /etc/fstab by PARTLABEL= . As a workaround I reverted back to identifying the partitions in /etc/fstab by UUID=, which if I am right, is a filesystem feature. Identified as such, the destop and the file manager side bar show one shortcut only, named after the file system label, and mounting it to the /etc/fstab mount point. I read somewhere that the option to identify partitions by PARTLABEL= and PARTUUID= is a more recent addition to fstab-syntax, so my first guess is that the auto-mounting system isn't yet aware of these; it seems to collect and identify partitions by the uuid or label of the filesystem on each partition, and when comparing that to the /etc/fstab entries, it does not recognize them as being the same partition that is identified in /etc/fstab by it's uuid or label from the partition table. Long story: After using and learning linux (Xubuntu) for half a year, I decided to do the right thing and stop identifying partitions to be mounted by block special device node (/dev/sda1 to /dev/sdb4 for my setup), but by a persistent name. So I set out to change /etc/fstab to identify the partitions to mount by UUID=, and that went well and I felt safe. Only problem was that a week later, I had no clue which UUID is which partition, which made me uncomfortably uncertain. So I used 'parted' to name all my partitions with a meaningfull partition label, similar but not identical to the filesystem label that I had named them to with 'e2label', 'fatlabel' and 'ntfslabel'. I also changed /etc/fstab to reflect that, now identifying my partitions using the PARTLABEL= . I choose PARTLABEL= instead of LABEL=, because it requires more skill and privileges to change a partition label than to change a filesystem label, so it is 'more persistent'. From then on, the automatic mounting behaviour became erratic. The desktop and the side pane of the file manager now showed 2 shortcuts for each partition: one named like the filesystem label, another named like the last path component of the mount point in /etc/fstab. When mounting the partition is triggered,by clicking one of both shortcuts in on desktop or in filemanager, or by some other process, and even with automount in /etc/fstab, one of the shortcuts is used for mounting the partition, preventing the other one to be mounted as well later. By this behaviour the same partition could be accessed at either but not both mount points. Either the mount point provided in /etc/fstab/, which is accessible in file manager under an entry named after the last path component of that mount point, which is linked to the full mount path. Either a temporary mount point which 'the system' creates in my user's /media/myusername/ directory, which is accessible in file manager under the name of the filesystem label, which again is linked to the full mount path. Because I find it a bit creepy to edit /etc/fstab, I did not go on to try identifying the partitions by LABEL= or by PARTUUID= . My guess is that PARTUUID= would exhibit the same problem, and LABEL= not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 2.1.7-1ubuntu1
[Desktop-packages] [Bug 1573959] Re: On-screen text disappears after suspend
Tested the final 4.9 kernel. If "sync to vblank" is active in ccsm it freezes the system at high cpu loads. ...but for all other settings 4.9 seems to be fine, too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: After resuming from a suspend, almost all text on screen is not visible. This includes menu items, text in all three boxes (list of folders, list of e-mails, e-mail body) in Thunderbird (with the curious exception of "ffl" in the File menu), top menu in Chromium (but not the menu obtained by pressing the hamburger button), and the menus produced by clicking items in the system tray. Also, the apport dialog had no text except for a few capital letters. ADDITIONAL INFORMATION: * initctl restart unity-panel-service restarts the panel, but the text is still missing * suspend and resume does not fix the issue * Logging out fixes the issue * Other affected applications: ** Chromium file select dialog ** Terminal (entire window) ** ttys 1-6 (Ctrl+Alt+F1, etc.) ** Document viewer (menus) ** Software Updater ** Rhythmbox ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc ** ubuntu-bug ** Nautilus ** LibreOffice Calc (spreadsheet text contents) ** Firefox * Unity dash is not affected. * Skype is not affected. * Mousing over a button in a dialog correctly shows the text. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 23 12:04:57 2016 DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics Controller [14c0:0075] InstallationDate: Installed on 2015-01-21 (457 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Compal VAW70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.01T01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Compal dmi.board.version: V1.01T01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: VAW70 dmi.product.version: V1.01T01 dmi.sys.vendor: Compal upstart.unity-panel-service-lockscreen.log: (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Apr 22 09:26:06 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1479 vendor
[Desktop-packages] [Bug 797485] Re: SRU: Status Bar Covers File Name at Bottom
** Branch linked: lp:~ubuntu-desktop/nautilus/ubuntu-xenial -- 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/797485 Title: SRU: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: In Progress Bug description: [Impact] If using Nautilus without a status bar the selected item title 'floats' at the bottom of the file listing. If you choose the last file item in a list this 'floating' title prevents you seeing the actual title making editing difficult/impossible. This issue is also present in icon view if you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. [Test Case] Using Ubuntu 16.04.1 open the file manager, click "Home", enable list view and resize the file manager window so that the contents of the home directory just fit vertically and horizontally. Select the last item in the file listing and then move the mouse slowly from left to right and back again several time. You will see the floating status bar will jump from left to right, obscuring details of the selected item. After the patched nautilus package is installed, performing the same test will result on the floating status bar being hidden when the mouse hovers over it. [Regression Potential] None. This patch has been adapted from the following upstream commit: * https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca Packages have been built in a PPA and tested for regressions. [ Other Info ] Binary package hint: nautilus The following possible solutions were considered: * Give the file list a bottom margin of the height of the status bar. * Move status bar to the left side when working with files in that corner. * Do not show status bar while renaming. * Hide the floating bars when hovering over part of the selection. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+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 797485] Re: SRU: Status Bar Covers File Name at Bottom
I just uploaded the proposed update, thanks. You should get a call for testing soon when it's available. -- 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/797485 Title: SRU: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: In Progress Bug description: [Impact] If using Nautilus without a status bar the selected item title 'floats' at the bottom of the file listing. If you choose the last file item in a list this 'floating' title prevents you seeing the actual title making editing difficult/impossible. This issue is also present in icon view if you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. [Test Case] Using Ubuntu 16.04.1 open the file manager, click "Home", enable list view and resize the file manager window so that the contents of the home directory just fit vertically and horizontally. Select the last item in the file listing and then move the mouse slowly from left to right and back again several time. You will see the floating status bar will jump from left to right, obscuring details of the selected item. After the patched nautilus package is installed, performing the same test will result on the floating status bar being hidden when the mouse hovers over it. [Regression Potential] None. This patch has been adapted from the following upstream commit: * https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca Packages have been built in a PPA and tested for regressions. [ Other Info ] Binary package hint: nautilus The following possible solutions were considered: * Give the file list a bottom margin of the height of the status bar. * Move status bar to the left side when working with files in that corner. * Do not show status bar while renaming. * Hide the floating bars when hovering over part of the selection. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+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 223133] Re: wrong volume interactions
On re-reading the original post (which is not very clear), I'm wondering if it's same problem. My problem is not on VLC-specific volume in pulseaudio (or any other app), rather on the master volume (hardware-specific). So, perhaps it's not the same problem. Anyway, many things have probably changed since Karmic and this bug report. -- 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/223133 Title: wrong volume interactions Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Binary package hint: pulseaudio I have the front slider at maximum volume. I have the PCM slider at 72% volume. I have the VLC internal slider at maximum volume. In PulseAudio Volume Control when I put a volume for VLC to 27% it's to loud, than I put a volume at 26% an I don't have any sound !! The volume will be probably added instance of multiply. And it will be grate to have volumes in dB ;-) For example we can have a fader from -80 dB to 0 dB with a linear part for to first "8.68588963806504 dB" to don't have any angle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/223133/+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 223133] Re: wrong volume interactions
On a USB audio adapter 0d8c:000c "C-Media Electronics, Inc. Audio Adapter", I experience same problem as original report and comment #2. Links at comment #3 no longer exist. I can't correlate with comment #4 and #5. To me, original report and comment #2 only mention an annoyance on a specific volume slider, nothing related to unifying volume or whatever. What can we do? -- 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/223133 Title: wrong volume interactions Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Binary package hint: pulseaudio I have the front slider at maximum volume. I have the PCM slider at 72% volume. I have the VLC internal slider at maximum volume. In PulseAudio Volume Control when I put a volume for VLC to 27% it's to loud, than I put a volume at 26% an I don't have any sound !! The volume will be probably added instance of multiply. And it will be grate to have volumes in dB ;-) For example we can have a fader from -80 dB to 0 dB with a linear part for to first "8.68588963806504 dB" to don't have any angle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/223133/+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 1643997] Re: nvidia driver causes blank screen
I did another test: 1. I installed Linux Mint 18.0 (Sarah) which is based on Xenial (vanilla installation) 2. I updated the system (recommended updates) 3. Installed Nvidia driver 367.57 - system not broken ! everything works 4. installed Intel proprietary driver (it was in the additional drivers - intel-microcode (3.20151106.1) - Then the system broke again. 5. At this point I tended to believe that the problem was in the combination of intel-microdcode package and nvidia-367 package 6. I remember that Ubuntu 16.04 comes automatically installed with intel-microcode package, so I decided to expand my test. I reinstalled Ubuntu 16.04.1 fresh. 7. I updated the system (software update). 8. I removed intel-microcode usage (using the "additional drivers" option to disable that device) 9. reboot. 10. install nvidia-367 driver (from additional drivers) - reboot. 11. system is still broken (blank screen, can't reach login at all, no TTY, can't even ssh, even though openssh was installed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1643997 Title: nvidia driver causes blank screen Status in nvidia-graphics-drivers-367 package in Ubuntu: New Bug description: I just installed ubuntu 16.04.1 64 bit (complete vanilla) 1. apt-get upgrade 2. apt-get dist-upgrade 3. install nvidia proprietary driver from "System settings -> Software & updates -> Additional Drivers" (current driver is 367.57- marked "proprietary, tested"). 4. reboot 5. blank screen as described above. I've modified grub with "nomodeset" - did not work. Removed "quiet, splash" - did not work add "set gfxpayload=text" - got some output to the screen, but not can't tell what it does and I have no idea where the data is stored - and then blank screen. disabled vesa frame buffer (vesafb.nonsense=1) - did not work My graphic HW: GTX 960 For now, I purged nvidia driver and the system is running well. I am sure the card is working properly because up until 3 days ago it had ubuntu 14.04 installed on it with nvidia driver active. Then there was an update which caused the same blank screen on 14.04. I decided to install 16.04 fresh (over the 14.04). I hoped the blank screen issue will disappear with 16.04, but it turns out it doesn't. If you need me to run some tests, I'll be more then happy to do so. I installed openssh-server on my machine, so I think I might be able to ssh into it from another machine while its in blank screen (did not test this). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: 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: Tue Nov 22 21:51:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-11-22 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 04/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd04/25/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
Debian just updated to Chromium 55 https://packages.debian.org/stable/web/chromium So this should come soon to Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium browser in xenial no longer trusts Symantec issued certificates. See [1]. 1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177 Ubuntu release: 16.04 chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
This bug was fixed in the package ubuntu-touch-session - 0.108+17.04.20161206-0ubuntu1 --- ubuntu-touch-session (0.108+17.04.20161206-0ubuntu1) zesty; urgency=medium * Support running inside a snap (without breaking non-snap runs). (LP: #1629009, #1645797, #1645833) -- Michael TerryTue, 06 Dec 2016 13:46:42 + ** Changed in: ubuntu-touch-session (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: Fix Released Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: In Progress Status in indicator-location package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-network package in Ubuntu: Fix Released Status in indicator-power package in Ubuntu: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-transfer package in Ubuntu: Fix Released Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+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 1641889] Re: The network indicator shows the wrong status
It's being merged into master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0d7bf7dee31175d3eeab2bd5a9eef8e7b6618016 -- 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/1641889 Title: The network indicator shows the wrong status Status in Network Manager Applet: Unknown Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Triaged Bug description: [Summary] The network indicator shows the wrong status [Reproduce Steps] 1.Boot into Ubuntu OS , remove wireless connection Note : the issue can't be reproduced with wifi connection 2.Enable/disable wifi function by hotkey the check wifi manager status [Results] Expected: "Enable Wi-Fi" option should be OFF Actual:"Enable Wi-Fi" option is ON [Additional Information] Product Name:Inspiron-7460 BIOS Version:1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
I think that the proposed 'fix' of just importing the Symantec certs isn't a very smart move, chrome requires transparency for a reason (you can read about it following the links in the original ticket). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium browser in xenial no longer trusts Symantec issued certificates. See [1]. 1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177 Ubuntu release: 16.04 chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
Also this one: === Common Name (CN)GeoTrust EV SSL CA - G4 Organization (O)GeoTrust Inc. === -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium browser in xenial no longer trusts Symantec issued certificates. See [1]. 1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177 Ubuntu release: 16.04 chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
I am affected, too. Manually importing the certificate as suggested in #82 has helped in sites like Amazon.com, but does not solve the problem. I am experiencing issues with this certificate: === Common Name (CN)RapidSSL SHA256 CA Organization (O)GeoTrust Inc. === Although before Chromium update it had worked normally and also it is working right now in Firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium browser in xenial no longer trusts Symantec issued certificates. See [1]. 1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177 Ubuntu release: 16.04 chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name
** Changed in: network-manager Status: Confirmed => Fix Released -- 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/1647283 Title: WiFi being detected as ethernet when race condition on renaming for persistent name Status in HWE Next: New Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: New Bug description: Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613 Version: NetworkManager 1.4.2 This bug happens after power-on with probability about 1/50. That means we need to reboot about 50 times to get into the buggy situation. "nmcli d" shows the device type is ethernet: DEVICE TYPE STATECONNECTION wlp1s0 ethernet unavailable -- lo loopback unmanaged-- The bug starts from a race condition. But it is not the root cause. I've also attach 2 logs. One is in good situation. Another is in bad situation. This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff. In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is: * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared. * Inside the NM, it is still using "wlan0" in "_linktype_get_type()". * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type(). * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared. * And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0. Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet. But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet. I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 441502] Re: Front Audio Jacks Not Working
I did not load the upstream yet.. but I installed the latest bios and it did not seem to work. I also tried a program called hdajackretask. This did not work according to the youtube.com video I watched to make the microphone work. So I am left with a problem. It should mute the speakers and internal mic and allow me to use plugged in headset. The internal mic is still active and the plugged in mic (of the headset) does not work. -- 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/441502 Title: Front Audio Jacks Not Working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Description: Ubuntu karmic (development branch) Release: 9.10 alsa-base: Installed: 1.0.20+dfsg-1ubuntu4 What is expected? I should plug in my headset (microphone included) and be able to hear and talk through any software, or at least restart such software if it does not automagically detect and adjust immediately so it may use the new configuration. What happened instead? The front jacks do not seem to be working. They did in ubuntu 9.04 (and only the ubuntu flavour, they did not in kubuntu 9.04) but not there's no output. Microphone works with configuration! * The microphone is still configured in the same manner. I open `alsamixer`. * In the [Playback] View which opens by default I adjust certain settings to: "Digital Input Source" (NOT "Digital Input Source 1") TO "Analog I". "Front Mic Jack Mode" TO "Mic In" * In the [Capture] View: "Front Mic Mixer" is ENABLED and volume adjusted (Maxed out for testing) "Capture" is ENABLED and volume adjusted (Maxed out for testing) Any other option is discardable in the front microphone jack configuration. This makes the microphone work when it is plugged in the front jack. I have not tested the back panel. Headphone I have not been able to configure the headphones yet, I'm not an alsa or pulse-audio expert ;[ LSPCI important output: 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller Notes: No alsa global configuration was tampered with. Only alsamixer for microphone configuration. ProblemType: Bug Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: exodus 1440 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd322 irq 22' Mixer name : 'IDT 92HD73E1X5' Components : 'HDA:111d7676,80865002,00100202' Controls : 47 Simple ctrls : 29 CheckboxCommand: alsa_record_playback CheckboxTest: alsa_record_playback_alternates Date: Sat Oct 3 11:23:19 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: alsa-base 1.0.20+dfsg-1ubuntu4 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-11.38-generic SourcePackage: alsa-driver Tags: checkbox-bug Uname: Linux 2.6.31-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/441502/+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 1649566] [NEW] xserver-xorg-video-nouveau: X freeze
Public bug reported: Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version in each case). From 14.04 on, I was unable to graphically log in. A few seconds after the login (varying between 1 and 10 s), the screen changed to a pattern with dense white stripes on the violet/red background, and X froze (no reaction to mouse or keyboard). The latest messages in "/var/log/syslog" each time showed varying "nouveau E" problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values and addresses varying). An internet search revealed that the problem is well known. It affects many NVidia graphic cards with the "nouveau" driver. Usually, the freeze happens when e.g. "firefox" is started (which happens in my context automatically after a graphical login). Most reports recommend to switch from "nouveau" to the proprietary NVidia driver. However, there seem to be problems with that driver for recent Ubuntu versions. I my case, the NVidia driver could not be started (I did not investigate why). One report suggested the boot parameter "nouveau.config=NvMSI=0" which in my case made the graphical login successful again. Today, I wanted to report the bug with "ubuntu-bug". However, during the collection of the system information, the error happened again (despite the "nouveau.config" boot parameter). Syslog gives: ... Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:59 localhost dbus[795]: [system] Activating service name='com.ubuntu.SoftwareProperties' (using servicehelper) Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp) Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020 Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Dec 13 11:39:01 localhost CRON[5723]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Dec 13 11:39:01 localhost CRON[5722]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. At this point, I had to reset the computer. Detailed system information: lsdm: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 xserver-xorg-video-nouveau 1:1.0.12-1build2 root@lsdm:~# lspci 00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1) 00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2) 00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2) 00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2) 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3) 00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3) 00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1) 00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2) 00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2) 00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2) 00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2) 00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2) 00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced
[Desktop-packages] [Bug 441502] Re: Front Audio Jacks Not Working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/441502 Title: Front Audio Jacks Not Working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Description: Ubuntu karmic (development branch) Release: 9.10 alsa-base: Installed: 1.0.20+dfsg-1ubuntu4 What is expected? I should plug in my headset (microphone included) and be able to hear and talk through any software, or at least restart such software if it does not automagically detect and adjust immediately so it may use the new configuration. What happened instead? The front jacks do not seem to be working. They did in ubuntu 9.04 (and only the ubuntu flavour, they did not in kubuntu 9.04) but not there's no output. Microphone works with configuration! * The microphone is still configured in the same manner. I open `alsamixer`. * In the [Playback] View which opens by default I adjust certain settings to: "Digital Input Source" (NOT "Digital Input Source 1") TO "Analog I". "Front Mic Jack Mode" TO "Mic In" * In the [Capture] View: "Front Mic Mixer" is ENABLED and volume adjusted (Maxed out for testing) "Capture" is ENABLED and volume adjusted (Maxed out for testing) Any other option is discardable in the front microphone jack configuration. This makes the microphone work when it is plugged in the front jack. I have not tested the back panel. Headphone I have not been able to configure the headphones yet, I'm not an alsa or pulse-audio expert ;[ LSPCI important output: 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller Notes: No alsa global configuration was tampered with. Only alsamixer for microphone configuration. ProblemType: Bug Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: exodus 1440 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd322 irq 22' Mixer name : 'IDT 92HD73E1X5' Components : 'HDA:111d7676,80865002,00100202' Controls : 47 Simple ctrls : 29 CheckboxCommand: alsa_record_playback CheckboxTest: alsa_record_playback_alternates Date: Sat Oct 3 11:23:19 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: alsa-base 1.0.20+dfsg-1ubuntu4 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-11.38-generic SourcePackage: alsa-driver Tags: checkbox-bug Uname: Linux 2.6.31-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/441502/+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 1649566] [NEW] xserver-xorg-video-nouveau: X freeze
You have been subscribed to a public bug: Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version in each case). From 14.04 on, I was unable to graphically log in. A few seconds after the login (varying between 1 and 10 s), the screen changed to a pattern with dense white stripes on the violet/red background, and X froze (no reaction to mouse or keyboard). The latest messages in "/var/log/syslog" each time showed varying "nouveau E" problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values and addresses varying). An internet search revealed that the problem is well known. It affects many NVidia graphic cards with the "nouveau" driver. Usually, the freeze happens when e.g. "firefox" is started (which happens in my context automatically after a graphical login). Most reports recommend to switch from "nouveau" to the proprietary NVidia driver. However, there seem to be problems with that driver for recent Ubuntu versions. I my case, the NVidia driver could not be started (I did not investigate why). One report suggested the boot parameter "nouveau.config=NvMSI=0" which in my case made the graphical login successful again. Today, I wanted to report the bug with "ubuntu-bug". However, during the collection of the system information, the error happened again (despite the "nouveau.config" boot parameter). Syslog gives: ... Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:59 localhost dbus[795]: [system] Activating service name='com.ubuntu.SoftwareProperties' (using servicehelper) Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp) Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020 Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Dec 13 11:39:01 localhost CRON[5723]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Dec 13 11:39:01 localhost CRON[5722]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. At this point, I had to reset the computer. Detailed system information: lsdm: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 xserver-xorg-video-nouveau 1:1.0.12-1build2 root@lsdm:~# lspci 00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1) 00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2) 00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2) 00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2) 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3) 00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3) 00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1) 00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2) 00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2) 00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2) 00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2) 00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2) 00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2
[Desktop-packages] [Bug 1633824] Re: nautilus ignores trash on external drives
Installed glib2.0 from proposed repository. Now all deleted items are visible in Trash. Upgrading these packages fixed the issue : libglib2.0-0 version 2.50.2-2ubuntu1 libglib2.0-bin version 2.50.2-2ubuntu1 libglib2.0-data version to 2.50.2-2ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1633824/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1649360] Re: identifying a partitition in fstab by PARTLABEL creates a second entry for the partition, for it's file system label
** Description changed: $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 Short story: When a partition has both a partition label and a filesystem label, and is identified in /etc/fstab by PARTLABEL= , both file manager's side pane (thunar on Xubuntu) and the desktop (with the setting 'icons/default icons/Removable Devices/Disk and Drives') show two shortcuts for the partition: one for the /etc/fstab entry, named as the last pathname component of the mount point in /etc/fstab, and a self-generated second shortcut, named after the filesystem label. By some seemingly random process either of both shortcuts is mounted at some point, preventing the other one to be mounted, EVEN when that one is marked as automount in /etc/fstab. If the mounted shortcut is /etc/fstab's PARTLABEL= entry, it is mounted to the provided /etc/fstab mount point. If the mounted shortcut is that for the filesystem label, it is mounted to a temporary directory under /media/myusername/. In either case, the other shortcut can't be mounted then. This behaviour makes it unpredictable through which path a partition can be reached. The problem is not present for partitions without a filesystem label, even if they are identified in /etc/fstab by PARTLABEL= . As a workaround I reverted back to identifying the partitions in /etc/fstab by UUID=, which if I am right, is a filesystem feature. Identified as such, the destop and the file manager side bar show one shortcut only, named after the file system label, and mounting it to the /etc/fstab mount point. I read somewhere that the option to identify partitions by PARTLABEL= and PARTUUID= is a more recent addition to fstab-syntax, so my first guess is that the auto-mounting system isn't yet aware of these; it - seems to collect and identify partitions by features (uuid or label) of - the filesystems on them, and when comparing that to the /etc/fstab - entries, it does not recognize them as being the same partition - identified in /etc/fstab by it's features from the partition table. + seems to collect and identify partitions by the uuid or label of the + filesystem on each partition, and when comparing that to the /etc/fstab + entries, it does not recognize them as being the same partition that is + identified in /etc/fstab by it's uuid or label from the partition table. Long story: After using and learning linux (Xubuntu) for half a year, I decided to do the right thing and stop identifying partitions to be mounted by block special device node (/dev/sda1 to /dev/sdb4 for my setup), but by a persistent name. So I set out to change /etc/fstab to identify the partitions to mount by UUID=, and that went well and I felt safe. Only problem was that a week later, I had no clue which UUID is which partition, which made me uncomfortably uncertain. So I used 'parted' to name all my partitions with a meaningfull - partition label (similar but not identical to the filesystem label that - I had named them to with 'e2label', 'fatlabel' and 'ntfslabel'). I also + partition label, similar but not identical to the filesystem label that + I had named them to with 'e2label', 'fatlabel' and 'ntfslabel'. I also changed /etc/fstab to reflect that, now identifying my partitions using the PARTLABEL= . I choose PARTLABEL= instead of LABEL=, because it requires more skill and privileges to change a partition label than to - change a filesystem label. + change a filesystem label, so it is 'more persistent'. From then on, the automatic mounting behaviour became erratic. The desktop and the side pane of the file manager now showed 2 shortcuts for each partition: one named like the filesystem label, another named like the last path component of the mount point in /etc/fstab. When mounting the partition is triggered,by clicking one of both shortcuts in on desktop or in filemanager, or by some other process, and even with automount in /etc/fstab, one of the shortcuts is used for mounting the partition, preventing the other one to be mounted as well later. By this behaviour the same partition could be accessed at either but not both mount points. Either the mount point provided in /etc/fstab/, which is accessible in file manager under an entry named after the last path component of that mount point, which is linked to the full mount path. Either a temporary mount point which 'the system' creates in my user's /media/myusername/ directory, which is accessible in file manager under the name of the filesystem label, which again is linked to the full mount path. Because I find it a bit creepy to edit /etc/fstab, I did not go on to try identifying the partitions by LABEL= or by PARTUUID= . My guess is that PARTUUID= would exhibit the same problem, and LABEL= not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 2.1.7-1ubuntu1 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1636473] Re: random cursor jumps when clicking on dell xps 13
This bug is very similar to this: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/365943 I managed to reproduce as described in bug 365943, however it takes 20-30 tries. Original i thought it was due to clicking but not,it's just multi touch bug/regression New steps to reproduce: 1. Touch the pad in the upper right and hold 2. Touch with another finger lower left and hold 3. Release the finger in the upper right 4. Repeat faster/slower until mouse jumps to lower left edge of the screen. -- 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/1636473 Title: random cursor jumps when clicking on dell xps 13 Status in xorg package in Ubuntu: Incomplete Bug description: 1 out of 20-40 clicks on the touch pad results in a pointer jump and a "random" click. Hard to reproduce, but mostly happens when I use my middle finger to move the cursor and click with index finger. Sometimes the double touch of middle/index finger is interpreted as mouse move, the jump is more or less the same distance as if i had moved the index to the middle finger position. Cheers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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 CurrentDesktop: Unity Date: Tue Oct 25 22:04:10 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:0704] InstallationDate: Installed on 2016-09-08 (46 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=fe8099eb-a258-42d6-8f67-69496f1e0fcf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Oct 22 20:20:44 2016 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5193 vendor SHP xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1636473/+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 1649538] [NEW] Dual monitor not working with i915
Public bug reported: Dual monitor works in live usb with ubuntu 14.04, but not in mate 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 BootLog: /dev/sda2: clean, 1133481/14106624 files, 9743255/56405760 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Dec 13 13:10:28 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:8694] InstallationDate: Installed on 2016-12-09 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed root=UUID=767271cd-b0c9-4191-930c-171a4e152a8a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1802 dmi.board.asset.tag: Default string dmi.board.name: H110M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1802:bd05/20/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Dec 13 13:02:22 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 49361 vendor PHL xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1649538 Title: Dual monitor not working with i915 Status in xorg package in Ubuntu: New Bug description: Dual monitor works in live usb with ubuntu 14.04, but not in mate 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 BootLog: /dev/sda2: clean, 1133481/14106624 files, 9743255/56405760 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Dec 13 13:10:28 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:8694] InstallationDate: Installed on 2016-12-09 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n Bus
[Desktop-packages] [Bug 1633824] Re: nautilus ignores trash on external drives
I can confirm that this is fixed for my external drive now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1633824/+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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
Thanks a million ! :-) I selected libglib2.0-0 to be upgraded to the new yakkety-proposed version 2.50.2-2ubuntu1. It automatically required also upgrading the existing libglib2.0-bin and libglib2.0-dev, and everything went OK. Now I can trash files in the root of other symlinked partitions as well! The only issue perhaps is that upgrading libglib2.0-0 to the new yakkety-proposed version 2.50.2-2ubuntu1 did not require upgrading libglib2.0-data as well. Perhaps I didn't experience any problems only because I've already got it upgraded to a compatible version created by Iain (ppa) for testing purposes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: New Status in glib2.0 source package in Yakkety: Fix Committed Bug description: [ Description ] Can't trash files if the directory they are in is a symlink to another device [ QA ] Steps: 1. Install system and partition disk into root and data partitions 2. create ~/Data folder, and mount data partition on it 3. create symlinks for ~/whatever/ to ~/Data/something/ 4. delete files directly inside ~/whatever/ What happen: Then Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". What should happen: The files moved into Trash. [ Regression potential ] The proposed fix uses g_stat instead of g_stat to follow symlinks, so we know where to place the trash (you can't rename() across filesystems). If that is wrong, then it could regress trashing other kinds of files. [ Original ] I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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 1649523] [NEW] libunity-protocol-private.so cannot be found
Public bug reported: If your snap links (directly or indirectly, for instance via the Ubuntu.UnityWebApps QML module) to the libunity.so library, running it will fail with the following error: "file:///snap/amazon-webapp/x1/share/webbrowser-app/webcontainer /webapp-container.qml:21 plugin cannot be loaded for module \"Ubuntu.UnityWebApps\": Cannot load library /snap/amazon-webapp/x1 /ubuntu-app-platform/usr/lib/x86_64-linux- gnu/qt5/qml/Ubuntu/UnityWebApps/libUnityWebApps.so: (libunity-protocol- private.so.0: cannot open shared object file: No such file or directory)\n" libunity-protocol-private.so *is* present in the ubuntu-app-platform snap, but it's in a subdirectory which is not in the library path: /usr/lib/x86_64-linux-gnu/libunity/libunity-protocol-private.so.0 (not the "libunity" subdirectory). It looks like (info obtained with "objdump -a -x") libunity.so has this RPATH: RPATH/usr/lib/x86_64-linux-gnu/libunity I'll try to see if using $ORIGIN in libunity helps; if not, we might have to play with LD_LIBRARY_PATH in the ubuntu-app-platform snap. ** Affects: ubuntu-app-platform Importance: Undecided Status: New ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Also affects: libunity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1649523 Title: libunity-protocol-private.so cannot be found Status in Ubuntu App Platform: New Status in libunity package in Ubuntu: New Bug description: If your snap links (directly or indirectly, for instance via the Ubuntu.UnityWebApps QML module) to the libunity.so library, running it will fail with the following error: "file:///snap/amazon-webapp/x1/share/webbrowser-app/webcontainer /webapp-container.qml:21 plugin cannot be loaded for module \"Ubuntu.UnityWebApps\": Cannot load library /snap/amazon-webapp/x1 /ubuntu-app-platform/usr/lib/x86_64-linux- gnu/qt5/qml/Ubuntu/UnityWebApps/libUnityWebApps.so: (libunity- protocol-private.so.0: cannot open shared object file: No such file or directory)\n" libunity-protocol-private.so *is* present in the ubuntu-app-platform snap, but it's in a subdirectory which is not in the library path: /usr/lib/x86_64-linux-gnu/libunity/libunity-protocol-private.so.0 (not the "libunity" subdirectory). It looks like (info obtained with "objdump -a -x") libunity.so has this RPATH: RPATH/usr/lib/x86_64-linux-gnu/libunity I'll try to see if using $ORIGIN in libunity helps; if not, we might have to play with LD_LIBRARY_PATH in the ubuntu-app-platform snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-platform/+bug/1649523/+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 1633824] Re: nautilus ignores trash on external drives
@cl-netbox : Did the update fix your variant of the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1633824/+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 1633824] Re: nautilus ignores trash on external drives
After updating, then logging out then back in; I confirm that this fixes the issue for USB drives making their trash folder be treated like that of internal drives. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1633824/+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 1633824] Re: nautilus ignores trash on external drives
Update-Manager just offered the update to me (I use proposed). I will test and report back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Yakkety: Fix Committed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1633824/+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