[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Same issue with Nvidia Geforce GTX 1060 6 GB - wouldn't work with 390, 396, 410, or 415 drivers. Only Nouveau under Ubuntu 18.10 (upgraded from beta and previously 18.04 as original install) Resolved by switching to lightdm and booting into Cinnamon Desktop instead of Gnome. Mate works as well. Also uncommented "WaylandEnable=false" for future possible use of gdm3 and gnome desktop. Can someone either mark this as "not fixed" or "won't fix" since it's clearly not resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 626321] Re: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate
** Changed in: xorg-server Status: Confirmed => Unknown -- 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/626321 Title: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate Status in Wine: Won't Fix Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Bug description: Applications like games change desktop resolution (graphics mode) for their needs. Unfortunately when such applications crash then X.org server doesn't revert the resolution back to its initial mode. To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/626321/+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 626321]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/249. -- 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/626321 Title: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate Status in Wine: Won't Fix Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Bug description: Applications like games change desktop resolution (graphics mode) for their needs. Unfortunately when such applications crash then X.org server doesn't revert the resolution back to its initial mode. To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/626321/+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 1650828] Re: package libgs9-common 9.18~dfsg~0-0ubuntu2 failed to install/upgrade: package libgs9-common is not ready for configuration cannot configure (current status 'half-i
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ghostscript (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1650828 Title: package libgs9-common 9.18~dfsg~0-0ubuntu2 failed to install/upgrade: package libgs9-common is not ready for configuration cannot configure (current status 'half-installed') Status in ghostscript package in Ubuntu: Confirmed Bug description: Detected at Raspberry PI3 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgs9-common 9.18~dfsg~0-0ubuntu2 Uname: Linux 4.1.19-v7+ armv7l ApportVersion: 2.20.1-0ubuntu2.4 Architecture: armhf CupsErrorLog: Date: Sun Dec 18 01:06:01 2016 Dependencies: DuplicateSignature: package:libgs9-common:9.18~dfsg~0-0ubuntu2 Processing triggers for libc-bin (2.23-0ubuntu4) ... dpkg: error processing package libgs9-common (--configure): package libgs9-common is not ready for configuration ErrorMessage: package libgs9-common is not ready for configuration cannot configure (current status 'half-installed') Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 004: ID 1ea7:0066 Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PackageArchitecture: all Papersize: letter ProcKernelCmdLine: 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1200 bcm2709.boardrev=0xa02082 bcm2709.serial=0xf3b07947 smsc95xx.macaddr=B8:27:EB:B0:79:47 bcm2708_fb.fbdepth=32 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: ghostscript Title: package libgs9-common 9.18~dfsg~0-0ubuntu2 failed to install/upgrade: package libgs9-common is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1650828/+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 66566]
(In reply to gpy98671 from comment #148) gpy98671 until the team changes it's opinion on this, which doesn't look likely, there would need to be an extension to get your desired functionality back. However AFAIK webextensions do not have this capability right now. You can join the conversation here to follow the progress and/or help/get help: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
(In reply to uhr80386 from comment #146) > What happened so shift+enter and ctrl+shift+enter? > Up to know shift+enter did .net and ctrl+shift+enter did .org.. now it does > open a new window or simply use .com. They were removed to enable support for opening URLs in a new window. No other browser implements these, and with the current set of available TLDs being rather different from those of the late 90s, there didn't seem a good reason to keep this behaviour. There isn't a pref to revert that change. -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
(In reply to :Gijs (he/him) from comment #147) > No other browser implements these That's my point! It's extremely usefull for fast navigation, at least for me or my colls at work. Of course you can type in .net or .org, use favorites, or something else. But I don't the point in linking opening URLs in a new window with that - even if its old - feature. It might be a relic and not know to many users, but I would like at least have the chance to decide if I want the new or the old feature. Now I'm pretty upset about the latest Firefox, there were already a lot things I missed during the latest versions, but that one is a real issue. -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
(In reply to Marco Bonardo [::mak] from comment #141) > (In reply to Anthony Ramine [:nox] from comment #140) > > The keyboard shortcut cmd-enter opens links in new *background* tabs in > > Chrome and Safari, Firefox is now opening them in new *foreground* tabs. Is > > there any way to change this behaviour? > > Please file a new bug, if the behavior is inconsistent with Chrome and > Safari we'll look into it. I think it's also inconsistent with Firefox itself. "browser.tabs.loadDivertedInBackground;true" should apply for this too at least. -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
(In reply to alexander.kern from comment #139) > :Gijs, I don't know how to tag people here so I hope posting here again is > ok to contact you. Could you show me the lines where you changed this code > so I can have a look at it? Because on the issue I created I commented on bug 1506203. -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
It's kinda the topic of this bug, though, see its title: > for Windows/Linux users where it interferes with opening URLs in (background) tabs -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
What happened so shift+enter and ctrl+shift+enter? Up to know shift+enter did .net and ctrl+shift+enter did .org.. now it does open a new window or simply use .com. That's not how it should be. How can I change it back? -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
(In reply to Anthony Ramine [:nox] from comment #140) > The keyboard shortcut cmd-enter opens links in new *background* tabs in > Chrome and Safari, Firefox is now opening them in new *foreground* tabs. Is > there any way to change this behaviour? Please file a new bug, if the behavior is inconsistent with Chrome and Safari we'll look into it. -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
The keyboard shortcut cmd-enter opens links in new *background* tabs in Chrome and Safari, Firefox is now opening them in new *foreground* tabs. Is there any way to change this behaviour? -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
(In reply to Jesse Peden from comment #138) > I suppose it is, but it seems to be counter-productive to get users used to > having it be CMD-Enter for all of these years and then change it out of the > middle of nowhere. They could have at least added an option to allow people > to opt out of it. We must evolve, and on certain things that means also reaching consensus and coherence with the other browsers, so that users can easily find themselves comfortable moving across them (even if just for development, testing, web-compat issues). Unfortunately in some cases this means changing behaviors that have been with us from a long time (I'm here from 11 years, I know well). If we'd add a pref for each change, in a few years the code would become totally unmanageable. Surely adding one pref here looks like a no-brainer, but if you multiple that by the hundreds of times I heard someone asking for a pref, you can easily see it's not sustainable long term. Breaking habits and muscle memory is bad, we don't do that often and we try to avoid it, but when an habit hurts a part of our users and it's inconsistent with the rest of the browsers world, we may actually look into it. This was one case, there have been others, there will be others. -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 66566]
Jesse, you can follow the progress of the issue/bug for better keyboard shortcut control here https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 When it's done there can be extensions that change this behavior. It is a bit unfortunate the change to webextensions was rushed and now we are missing some features. :Gijs, I don't know how to tag people here so I hope posting here again is ok to contact you. Could you show me the lines where you changed this code so I can have a look at it? Because on the issue I created it was said that it might be too much development effort to fix the issue (resolving the inconsistency of pressing multiple modifiers and enter in the navbar). Thank you! -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 1036168] Re: Superfluous option "print-color-mode" cannot be removed
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1036168 Title: Superfluous option "print-color-mode" cannot be removed Status in hplip package in Ubuntu: Expired Bug description: Drivers: hp-color_laserjet_cp1515n-pcl3.ppd hp-color_laserjet_cp1515n-hpijs-pcl3.ppd Both drivers display an advanced option called "print-color-mode" in the "Job Options" panel, which is superfluous, since color mode is selected on the "Printer Options" panel. Moreover, trying to remove this option pressing the "remove" button does not work. The option seems to disappear, but reappears when the dialog is displayed next time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: hplip 3.12.2-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 CurrentDmesg: [ 63.368304] init: plymouth-stop pre-start process (1700) terminated with status 1 Date: Mon Aug 13 14:47:01 2012 Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824 MachineType: exone D156200 Papersize: letter PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago) dmi.bios.date: 04/23/2004 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 4.06 Rev. 1.09.1562 dmi.board.name: D1562 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D1562 dmi.chassis.type: 6 dmi.chassis.vendor: exone dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr: dmi.product.name: D156200 dmi.sys.vendor: exone --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CupsErrorLog: W [15/Oct/2018:17:43:09 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Farblaser-Gray..\' already exists W [15/Oct/2018:17:43:09 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Farblaser-CMYK..\' already exists W [15/Oct/2018:17:43:16 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Farblaser-Gray..\' already exists W [15/Oct/2018:17:43:16 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Farblaser-CMYK..\' already exists CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-13 (1037 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: device for Farblaser: socket://192.168.1.8 MachineType: LENOVO 34382AG Package: hplip 3.17.10+repack0-5 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=/dev/mapper/vg-lv--root ro noprompt quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GCETB1WW (2.71 ) dmi.board.asset.tag: Not Available dmi.board.name: 34382AG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETB1WW(2.71):bd06/19/2018:svnLENOVO:pn34382AG:pvrThinkPadX230Tablet:rvnLENOVO:rn34382AG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 34382AG dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1036168/+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 1797784] Re: fail to syn/connect google callander with loal calander
[Expired for gnome-calendar (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-calendar (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1797784 Title: fail to syn/connect google callander with loal calander Status in gnome-calendar package in Ubuntu: Expired Bug description: although google authentication done but fail to syn ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 CurrentDesktop: Budgie:GNOME Date: Sun Oct 14 20:47:51 2018 InstallationDate: Installed on 2018-05-13 (154 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release i386 (20180426) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1797784/+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 1797983] Re: My session restarted
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797983 Title: My session restarted Status in gnome-shell package in Ubuntu: Expired Bug description: Hello, I do not know what happened, but I was voted out of my session. I immediately went to check '/var/crash' and there was no .crash file of this day. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 19:02:01 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-13 (367 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797983/+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 1797834] Re: Ubuntu dash-to-dock "Show on" bug
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1797834 Title: Ubuntu dash-to-dock "Show on" bug Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: Dear developers, How are you? I've noticed a bug/typo on the Settings->Dock->`Show on` settings on dual monitors: the Ubuntu Dock show on to the opposite of the display. In my case: I set "HP 23es" as my primary monitor while built-in screen as my secondary monitor, I then switch the "Show on" from "HP 23es" to "Built-in" display, then back again to "HP 23es", now the Ubuntu dock show on the "Built-in" monitor instead of the "HP 23es". And if I switch to "Built-in" display, the dock display on "HP 23es", which is doing opposite operation. What I guess is that the Ubuntu dock shows the typo information since I've tried dash-to-dock extension without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1797834/+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 1797578] Re: unable to open Ubuntu Software
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1797578 Title: unable to open Ubuntu Software Status in gnome-software package in Ubuntu: Expired Bug description: when i try to open Ubuntu Software it flashes on the launcher then the icon looks like it didn't open. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 12 16:41:02 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3616] InstallationDate: Installed on 2018-01-21 (264 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO Lenovo H420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=510425b4-02db-49c7-91bd-587ef9d2671d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2011 dmi.bios.vendor: LENOVO dmi.bios.version: DPKT22A dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrDPKT22A:bd11/08/2011:svnLENOVO:pnLenovoH420:pvrLenovo:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Lenovo H420 dmi.product.version: Lenovo dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 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: Fri Oct 12 15:05:52 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB Keyboard KEYBOARD, id 8 input USB Keyboard KEYBOARD, id 9 inputKYE SYSTEMS CORP. Wired Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1797578/+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 1808611] [NEW] chamelon
Public bug reported: export PATH=$PATH:/data/user/0/burrows.apps.busybox/app_busybox; export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/data/user/0/burrows.apps.busybox/app_busybox ** Affects: iputils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1808611 Title: chamelon Status in iputils package in Ubuntu: New Bug description: export PATH=$PATH:/data/user/0/burrows.apps.busybox/app_busybox; export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/data/user/0/burrows.apps.busybox/app_busybox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1808611/+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 1808610] [NEW] chamelon
Public bug reported: Search or scan a URL, IP address, domain, or file hash Sign in 1 / 61 One engine detected this file SHA-25676e27c4b09f9c1cbbf0b414719b741d3087fc744f6de9431a282fbd976bd445a File namemssoJ77AHDuALWGu6G File size11.78 MB Last analysis2018-03-28 08:17:09 UTC Detection Details Relations Behavior Community VirusTotal Droidy Detailed report Network Communication HTTP Requests http://api.exc.mob.com:80/errconf http://api.share.mob.com:80/conn http://api.share.mob.com:80/snsconf https://static.yuanbaopu.com/hotcode/fidewd/ http://api.share.mob.com:80/conf4 http://api.share.mob.com:80/data2 http://api.share.mob.com:80/date http://loc.map.baidu.com/offline_loc http://loc.map.baidu.com/sdk.php http://loc.map.baidu.com/statloc DNS Resolutions loc.map.baidu.com 180.97.104.187 cdn.polyfill.io 151.101.122.109 dualstack.f3.shared.global.fastly.net 151.101.122.109 api.share.mob.com newloc.map.n.shifen.com api.exc.mob.com static.yuanbaopu.com IP Traffic 61.174.10.208:80 (TCP) 120.132.176.173:80 (TCP) 151.101.122.109:443 (TCP) 182.254.154.23:443 (TCP) 180.97.104.187:80 (TCP) File System Actions Files Opened /data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml /data/misc/keychain/pins /storage/emulated/0/ShareSDK/com.yuanbaopu.ybpmark/cache/com.yuanbaopu.ybpmark/.lock /storage/emulated/0/baidu/.cuid /proc/net/if_inet6 /sys/class/net/ip6tnl0/ifindex /sys/class/net/lo/ifindex /sys/class/net/sit0/ifindex /sys/class/net/eth0/ifindex /storage/emulated/0/ShareSDK/.dk Files Written /storage/emulated/0/baidu/tempdata/ls.db /data/data/com.yuanbaopu.ybpmark/files/ofld/ofl_location.db /data/data/com.yuanbaopu.ybpmark/files/ofld/ofl_statistics.db /storage/emulated/0/test.0 /data/data/com.yuanbaopu.ybpmark/files/ofld/ofl.config /storage/emulated/0/baidu/tempdata/ller.dat /storage/emulated/0/baidu/tempdata/conlts.dat /storage/emulated/0/baidu/tempdata/grtcf.dat Files Deleted /data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml.bak /data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml /data/data/com.yuanbaopu.ybpmark/shared_prefs/share_sdk_1.xml.bak /data/data/com.yuanbaopu.ybpmark/shared_prefs/share_sdk_1.xml /storage/emulated/0/test.0 Files Copied /data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml /data/data/com.yuanbaopu.ybpmark/shared_prefs/share_sdk_1.xml Files Dropped 36ac59e578357746f7ab39a543f47e84260ca584534b3bbf3371bc1f4b407fd9 Process And Service Actions Permissions Checked android.permission.READ_PHONE_STATE android.permission.ACCESS_WIFI_STATE android.permission.CHANGE_WIFI_STATE android.permission.GET_TASKS Shell Commands su Services Opened com.google.android.gms.games.service.GamesIntentService (com.google.android.gms) com.google.android.gms.people.service.bg.PeopleBackgroundTasks (com.google.android.gms) Activities Started com.yuanbaopu.ybpmark.MainActivity (com.yuanbaopu.ybpmark) Synchronization Mechanisms & Signals Signals Hooked android.intent.action.PROXY_CHANGE android.intent.action.CONFIGURATION_CHANGED android.intent.action.PHONE_STATE android.intent.action.PACKAGE_ADDED android.intent.action.PACKAGE_REMOVED android.net.wifi.SCAN_RESULTS Modules Loaded Runtime Modules neh locSDK6a Invoked Methods android.os.SystemProperties.addChangeCallback android.os.SystemProperties.getLong com.fasterxml.jackson.databind.MapperFeature.values com.fasterxml.jackson.databind.DeserializationFeature.values com.fasterxml.jackson.databind.SerializationFeature.values com.android.org.conscrypt.OpenSSLCipher$Padding.values com.android.org.conscrypt.OpenSSLCipher$Mode.values android.net.wifi.SupplicantState.values android.net.wifi.WifiSsid.createFromAsciiEncoded com.nordnetab.chcp.main.model.ChcpError.values Highlighted Actions Calls Highlighted android.net.wifi.WifiInfo.getBSSID android.net.wifi.WifiInfo.getMacAddress android.net.wifi.WifiInfo.getSSID android.os.Debug.isDebuggerConnected android.telephony.TelephonyManager.getCellLocation android.telephony.TelephonyManager.getDeviceId android.telephony.TelephonyManager.getNetworkCountryIso android.telephony.TelephonyManager.getSimOperator android.telephony.TelephonyManager.getSubscriberId android.util.Base64.encode Cryptographical Algorithms Observed AES Cryptographical Keys Observed 30212102dicudiab sdk.sharesdk.sdk 14f0c07c317771a2 Encoding Algorithms Observed base64 Dataset Actions System Property Lookups debug.force_rtl debug.second-display.pkg debug.atrace.tags.enableflags sys.settings_system_version persist.sys.timezone persist.sys.ui.hw debug.layout sys.settings_secure_version viewroot.profile_rendering config.disable_media Shared Preferences Sets config_json config_json device_time device_data device_ext_data service_time lastInsertRunEventTime insertRunEventCount Content Model Observers NOT CACHED Content Model Sets exception_time exception_msg exception_level exception_md5 exception_time exception_msg exception_md5 exception_time exception_msg exception_md5
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
i have those lines already. this guide is terrible. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1807265] Re: Screen locking issue
I discovered that the issue seems to not actually be the lock screen. Last night the screen timed out but did not lock as the lock is set to happen at 30 minutes but the blank screen at 10 min. The screen blanked and the issue occurred. I came back to the laptop some time later and found that the login prompt was there, and it let me enter my password and login. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1807265 Title: Screen locking issue Status in gnome-screensaver package in Ubuntu: New Bug description: Upgraded to Cosmic Cuttlefish a little over a week ago, Now every time that the computer locks the screen, the screen is mostly blank and shows only the launchpad with favorites at the left, and the status icons at the top right. Clicking on the apps shows the app for a moment before being hidden again. The system drop down menu shows the usual information except the system tools / lock / power icons with a pause button displayed in their place but all is disabled except the pause button which suspends the computer. Upon waking again the computer is still locked. Have not discovered a key sequence that does anything when in this state. Cannot even switch virtual terminals or desktops. My only solution has been to power off the machine and do a hard reboot. I expected the lock screen to blank out the screen as it did in the previous release and show a login My computer is a Lenovo Thinkpad T-410 with 6Gb RAM. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 03:01:50 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-22 (624 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to cosmic on 2018-11-26 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1807265/+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 1354213] Re: With 'dwell-click' enabled there is no scrolling with mousewheel in gtk3 windows
A possible workaround is explained here: https://forums.linuxmint.com/viewtopic.php?t=242806 Adding this: GDK_CORE_DEVICE_EVENTS=1 at the end of ~/.profile solves this issue. GTK3 uses the X Input Device Extension Library by default. It seems that for some reason this extension is the source of the problem. Setting that environment variable, GKT3 only reacts to core X input events. It doesn't use that extension library. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mousetweaks in Ubuntu. https://bugs.launchpad.net/bugs/1354213 Title: With 'dwell-click' enabled there is no scrolling with mousewheel in gtk3 windows Status in mousetweaks package in Ubuntu: Confirmed Bug description: Test Case: enable dwell-click in System Settings > Universal access > Pointing & Clicking > Hover click or gsettings set org.gnome.desktop.a11y.mouse dwell-click-enabled true Try to scroll in a scroll-able gtk3 window with mouse wheel, nothing happens Scrolling is possible in gtk2 windows like Firefox ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mousetweaks 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 7 19:33:45 2014 InstallationDate: Installed on 2014-07-31 (7 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140729) SourcePackage: mousetweaks UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mousetweaks/+bug/1354213/+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 1688592] Re: Missing VA-API hardware decoding support drains battery
Launchpad has imported 23 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1210727. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-10-02T10:01:00+00:00 Jyavenard-9 wrote: This would do decoding only ; not rendering (yet) Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/0 On 2015-10-02T10:33:11+00:00 RussianNeuroMancer wrote: Hardware decoding on Intel Ironlake should be used only for 720p and lower. Hardware 1080p decoding on Intel Ironlake is slower than software decoding on CPU: https://bugs.freedesktop.org/show_bug.cgi?id=47858 GPU model from about:support Intel Open Source Technology Center -- Mesa DRI Intel(R) Ironlake Mobile I need to fill separate issue about VA-API on Ironlake or drop this info here is fine? Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/1 On 2015-10-02T12:42:52+00:00 Jyavenard-9 wrote: (In reply to russianneuromancer from comment #1) > Hardware decoding on Intel Ironlake should be used only for 720p and lower. > Hardware 1080p decoding on Intel Ironlake is slower than software decoding > on CPU: https://bugs.freedesktop.org/show_bug.cgi?id=47858 > > GPU model from about:support > Intel Open Source Technology Center -- Mesa DRI Intel(R) Ironlake Mobile > > I need to fill separate issue about VA-API on Ironlake or drop this info > here is fine? We have a generic preference to disable hardware acceleration, I'll hook it up to vaapi, but I have no intention at this stage to make specific cases for particular chipset. Would have to be in a separate bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/2 On 2016-07-06T04:29:09+00:00 Ajones-m wrote: Mass change P2 -> P3 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/3 On 2016-07-06T09:06:19+00:00 sheepdestro...@gmail.com wrote: Is there a reason the priority would go from P2 to P3? Lack of hardware acceleration is the worse offender on Linux right now. Some youtube videos can not even play at a decent framerate because of that, especially the 4K / 360 ones. And that's without speaking of the heat generated by those poor CPUs... I do not get why it would not even go the other way, right to P1 ? Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/4 On 2016-07-11T06:18:47+00:00 Ajones-m wrote: See bug 1210726. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/5 On 2016-08-11T18:00:44+00:00 agm97 wrote: linux had have the firefox browser by default in all distros I think much users of firefox are from linux and the only thing we get from mozilla a long waiting for a feature that is very needed.. between google with chromium and the denied featured requests and firefox not to working on features for firefox, linux in browser category is very late and the battery for laptops is damaged with linux and video viewing with browsers, I feel really annoying Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/6 On 2016-09-23T23:46:01+00:00 Melroy van den Berg wrote: I fully agree, video acceleration is a must have feature now a days. Please solve it! Don't force me to move to Chrome Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/7 On 2016-11-14T12:45:36+00:00 Waz wrote: I still have hope too to see full VDPAU/VAAVI support in order to have hardware video acceleration. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/8 On 2016-11-18T21:41:36+00:00 Ehumphries wrote: Gentle reminder: * Our guidelines ask you don't argue about priority setting on bugs. Triage leads and Mozillians working on the bug set the priority. See: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html * "Me too" or "Fix this or I'm moving to Chrome/Lynx/Gopher/Edge/Webkit" comments are off topic and just add noise. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1688592/comments/9
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Don't forget to 'sudo apt update' after making those changes. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Just uncomment the deb-src lines in /etc/apt/sources.list. For example, replace: # deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main restricted With: deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main restricted -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1808605] [NEW] the screen graphics card and input device settings could not be detected correctly and in lightdm.log file it says fail to start a greeter, i hard shutdown my la
Public bug reported: the screen graphics card and input device settings could not be detected correctly and in lightdm.log file it says fail to start a greeter, i hard shutdown my laptop many times also, I also made another user without giving them a home directory does that help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Dec 14 20:17:50 2018 InstallationDate: Installed on 2017-12-25 (354 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- 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/1808605 Title: the screen graphics card and input device settings could not be detected correctly and in lightdm.log file it says fail to start a greeter, i hard shutdown my laptop many times also, I also made another user without giving them a home directory does that help Status in lightdm package in Ubuntu: New Bug description: the screen graphics card and input device settings could not be detected correctly and in lightdm.log file it says fail to start a greeter, i hard shutdown my laptop many times also, I also made another user without giving them a home directory does that help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Dec 14 20:17:50 2018 InstallationDate: Installed on 2017-12-25 (354 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1808605/+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 159678] Re: Totem can't read this multilingual subtitle.
** Changed in: totem Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/159678 Title: Totem can't read this multilingual subtitle. Status in Totem: Expired Status in totem package in Ubuntu: Triaged Bug description: Binary package hint: totem I found Korean-English multilingual smi subtitle file in internet. When I read this subtitle in Totem, totem can read only Korean parts. I tried this in some other Linux based movie player such as VLC, but it also has same problem, it couldn't read English part. So I use Windows based movie player "The KMPlayer" and "GOM palyer" to use English subtitle. I upload this subtitle, and I copied part of this subtitle below. Netshow 3.0 - Close Captioning Sample 난 얘기할게 없다니까. 그는 그냥 나랑 같이 일 하는 사람이야 There's nothing to tell! He's just some guy I work with! To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/159678/+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 834575] Re: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
** Changed in: gconf Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/834575 Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value() Status in gconf: Won't Fix Status in gconf package in Ubuntu: Triaged Bug description: I don't know ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gconf2 3.1.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 Architecture: i386 CrashCounter: 1 Date: Fri Aug 26 17:54:26 2011 ExecutablePath: /usr/bin/gsettings-data-convert InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: gsettings-data-convert ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gconf StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 g_settings_set_value () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 g_settings_set () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value() UpgradeStatus: Upgraded to oneiric on 2011-08-25 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/gconf/+bug/834575/+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 1796607]
*** Bug 1659662 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1796607 Title: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_display_open Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell package in Fedora: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/a7a2ba87e4d962b215ce37aaf80089f085e1db97 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796607/+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 1796607]
I've also reported the issue to GNOME - https://gitlab.gnome.org/GNOME /gnome-shell/issues/853 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1796607 Title: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_display_open Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell package in Fedora: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/a7a2ba87e4d962b215ce37aaf80089f085e1db97 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796607/+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 1623666] Re: iOS device contents not displayed in Ubuntu
Yes, but this does not grant transparent access to the Documents folders of installed applications. Pairing and libimobiledevice are still needed for that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Fix Released Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+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 1759462] Re: Keyboard shortcuts not operational on 18.04
This (keyboard shortcuts not working) happened to me, specifically CTRL+ALT+T not giving me the terminal. I experimented and found that the ALT key was at fault - it wasn't registering. I then found a reference on line (sorry don't have the URL) to this being a keyboard Language issue. I then tried: Settings, Language and Region, then set Language to English (United States) - I had it on English (Australia). My ALT key is now working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1759462 Title: Keyboard shortcuts not operational on 18.04 Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: After installing 18.04, I noticed that certain keyboard shortcuts no longer function. It appears to be related to the shortcuts that gnome-settings-daemon control as my shortcuts that are provided by my desktop (Budgie) still function. Some examples are: * Media keys for volume up/down/mute * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same behaviour. I double checked, and it looks like the needed daemon is still running, ``` dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-power dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sound dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-color dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-printer dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep --color=auto gnome-settings-daemon ``` Reboot does not seem to help. However, occasionally the shortcuts do seem to work - but only very occasionally. Any other info needed? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 27 21:12:18 2018 InstallationDate: Installed on 2018-03-05 (22 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+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 1796607] Re: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_dis
Reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/853 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1796607 Title: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_display_open Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell package in Fedora: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/a7a2ba87e4d962b215ce37aaf80089f085e1db97 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796607/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
ettinger@sunny:~ $ sudo apt-get build-dep linux-image-$(uname -r) [sudo] password for ettinger: Sorry, try again. [sudo] password for ettinger: Reading package lists... Done E: You must put some 'source' URIs in your sources.list ettinger@sunny:~ $ apt-get source linux-image-$(uname -r) Reading package lists... Done E: You must put some 'source' URIs in your sources.list ettinger@sunny:~ $ sudo apt-get source linux-image-$(uname -r) Reading package lists... Done E: You must put some 'source' URIs in your sources.list -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1808599] [NEW] /usr/sbin/unity-greeter:6:_dbus_abort:_dbus_warn_check_failed:_dbus_warn_return_if_fail:dbus_connection_get_data:atspi_dbus_connection_setup_with_g_main
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-greeter. This problem was most recently seen with package version 18.04.0+18.10.20180926-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1a42397fb849118d157316682163444d581ca97e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1808599 Title: /usr/sbin/unity- greeter:6:_dbus_abort:_dbus_warn_check_failed:_dbus_warn_return_if_fail:dbus_connection_get_data:atspi_dbus_connection_setup_with_g_main Status in unity-greeter package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-greeter. This problem was most recently seen with package version 18.04.0+18.10.20180926-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1a42397fb849118d157316682163444d581ca97e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1808599/+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 1808576] Re: gnome-control-center segfaults when unit bolt.service is masked
Launchpad has imported 13 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1644488. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-10-31T01:54:53+00:00 dantepaoloni wrote: Description of problem: Hi! i open the Control Center after upgrading to F29. All options worked perfect, but as soon i clicked in thunderbolt. CC Crash. Running from console gives: Result -> CC Crash. Expected -> CC Stating that ther is no Thunderbolt device in laptop (As F28 Said before). Running from console: pewpew ~ gnome-control-center (gnome-control-center:16183): thunderbolt-cc-panel-WARNING **: 22:47:43.173: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) pewpew ~ gnome-control-center background (gnome-control-center:16348): thunderbolt-cc-panel-WARNING **: 22:47:47.154: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Selecting Wifi (maybe another one works too?) allow me to enter the CC (after two times) pewpew ~ gnome-control-center (gnome-control-center:17228): thunderbolt-cc-panel-WARNING **: 22:48:45.103: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Result -> CC Crash pewpew ~ gnome-control-center wifi (gnome-control-center:17389): thunderbolt-cc-panel-WARNING **: 22:48:50.103: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Result -> CC Crash pewpew ~ gnome-control-center wifi Result -> CC opens. Laptop UX410UAR with not thunderbolt device. Version-Release number of selected component: gnome-control-center-3.30.1-3.fc29 Additional info: reporter: libreport-2.9.6 backtrace_rating: 4 cmdline:gnome-control-center crash_function: g_object_notify_queue_thaw executable: /usr/bin/gnome-control-center journald_cursor: s=6f6ac97f9aca4e62a1e5f2446ea2204a;i=62e6c;b=fa084d2d635045558cc44b10485dd4fe;m=250d5fff;t=5797c5e5404d6;x=2fcc1bc094d469a7 kernel: 4.18.16-300.fc29.x86_64 rootdir:/ runlevel: N 5 type: CCpp uid:1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_object_notify_queue_thaw at gobject.c:289 #1 g_object_new_internal at gobject.c:1862 #2 g_object_new_valist at gobject.c:2128 #4 gdk_pixbuf_new_from_data at ../gdk-pixbuf/gdk-pixbuf-data.c:70 #5 symbolic_cache_get_proxy at gtkicontheme.c:4303 #6 gtk_icon_info_load_symbolic_internal at gtkicontheme.c:4625 #7 gtk_icon_info_load_symbolic at gtkicontheme.c:4726 #8 ensure_surface_for_gicon at gtkiconhelper.c:466 #9 gtk_icon_helper_load_surface at gtkiconhelper.c:566 #10 gtk_icon_helper_ensure_surface at gtkiconhelper.c:603 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1808576/comments/0 On 2018-10-31T01:55:06+00:00 dantepaoloni wrote: Created attachment 1499179 File: backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1808576/comments/1 On 2018-10-31T01:55:08+00:00 dantepaoloni wrote: Created attachment 1499180 File: cgroup Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1808576/comments/2 On 2018-10-31T01:55:12+00:00 dantepaoloni wrote: Created attachment 1499181 File: core_backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1808576/comments/3 On 2018-10-31T01:55:14+00:00 dantepaoloni wrote: Created attachment 1499182 File: cpuinfo Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1808576/comments/4 On 2018-10-31T01:55:18+00:00 dantepaoloni wrote: Created attachment 1499183 File: dso_list Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1808576/comments/5 On 2018-10-31T01:55:20+00:00 dantepaoloni wrote: Created attachment 1499184 File: environ
[Desktop-packages] [Bug 694910] Re: Regression: patch to bug 539477 breaks Super+P keybindings
** Changed in: gnome-settings-daemon Status: Unknown => Confirmed ** Changed in: gnome-settings-daemon Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/694910 Title: Regression: patch to bug 539477 breaks Super+P keybindings Status in GNOME Settings Daemon: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-settings-daemon The current patch to bug 539477 breaks the super+p keybinding for all user applications when running gnone-settings-daemon. This behavior is hard-coded, not discoverable, and not configurable. The "workaround" is to disable parts of xrandr such that screen switching is no longer possible. The patch has been checked in and released as a bugfix to Ubuntu 10.10, causing regressions in several applications. For more details, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/ particularly https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/comments/68 and immediately above. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/694910/+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 1808147] Re: autopkgtests fail on s390x
Right, I had overlooked that unit tests are intentionally disabled on s390x and all other big endian architectures, and thus libcppunit-dev is excluded from the build dependencies on s390x. It is unclear to me whether the smoke tests could eventually be made to run and pass on s390x, but for the moment it seems reasonable to just skip the failing autopkgtest on that architecture, which I've done with https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=7c69bd0dccbfc377fe644042e0dad75f142c04f8. 1:6.1.3-0ubuntu9 is now building in disco-proposed. -- 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/1808147 Title: autopkgtests fail on s390x Status in libreoffice package in Ubuntu: In Progress Bug description: libreoffice autopkgtests on s390x started failing reliably on 2018-12-11. This corresponds to when a new version of autopkgtest was deployed to the production infrastructure: https://lists.ubuntu.com/archives /ubuntu-devel/2018-December/040564.html The failing test is "smoketest". It has the "skippable" restriction, which was previously unknown, and as a result the test was skipped altogether. "skippable" is now a valid and understood restriction, so the test is being run, but it fails: […] mkdir -p /tmp/autopkgtest.A1jy64/build.urp/src/workdir/CustomTarget/i18npool/textconversion/ S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libcollator_data.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libdict_ja.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libdict_zh.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libindex_data.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/liblocaledata_en.so /tmp/autopkgtest.A1jy64/build.urp/src/solenv/gbuild/Package.mk:82: *** Something depends on package test_unittest which does not exist.. Stop. make[1]: *** Waiting for unfinished jobs S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libtextconv_dict.so [build PKG] test_unittest make[1]: Leaving directory '/tmp/autopkgtest.A1jy64/build.urp/src' make: *** [Makefile:112: i18npool.all] Error 2 autopkgtest [13:27:33]: test smoketest: ---] autopkgtest [13:27:34]: test smoketest: - - - - - - - - - - results - - - - - - - - - - smoketestFAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1808147/+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 1790360] Re: [wayland] Fullscreen games offset after switching back to them from an app in the same workspace
*** This bug is a duplicate of bug 1732245 *** https://bugs.launchpad.net/bugs/1732245 ** This bug has been marked a duplicate of bug 1732245 [wayland] Fullscreen games offset after returning from alt-tab -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1790360 Title: [wayland] Fullscreen games offset after switching back to them from an app in the same workspace Status in mutter package in Ubuntu: New Bug description: Impact == Using Alt-Tab to leave a fullscreen game and then return breaks the game by offsetting the game down by the size of the GNOME Shell top bar and to the right by the size of the Ubuntu Dock. Test Case = 1. Run a game full screen. I installed Steam and used Team Fortress 2 because it's free (but a very large download) 2. Press Alt-Tab or click a dock icon to switch to another window in the same workspace and then press Alt-Tab or click the dock icon to switch back to the game. The game should display and function normally. Workaround == Switch apps again using any method. Other Info == This is a duplicate of #1732245 which has been reported on Ubuntu 17.10 which reached it's end-of-life on July 19, 2018. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 2 14:36:29 2018 InstallationDate: Installed on 2018-07-10 (53 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790360/+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 1804008] Re: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated .... from ubuntu-d...@ubuntu.com/theming.js:416]
By disabling autohide, the error message in log does not go away, but desktop will recover and does not end up with black screen after wake up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1804008 Title: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated from ubuntu-d...@ubuntu.com/theming.js:416] Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: All my gnome-shell extensions randomly (apparently) crash. This behavior began when i upgraded to cosmic. Here's a excerpt of my logs: Nov 19 12:57:28 falcon gnome-shell[1640]: Object Meta.WindowActor (0x55669ffd87a0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #1 5566ae293bb8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7fc9f03d7820 @ 20) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #3 5566ae293b00 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 (7fc9f03d7790 @ 172) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #5 5566ae293a80 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 (7fc9f03d78b0 @ 17) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #7 5566ae293a00 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 (7fc9f03d2f70 @ 42) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #9 5566ae293978 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 (7fc9f03c2dc0 @ 82) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #11 5566ae2938e0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 (7fc9f03cf1f0 @ 116) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #13 5566ae293860 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 (7fc9f03cf5e0 @ 37) Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #15 5566ae2937e0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 (7fc9f03c2550 @ 12) Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618328' Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618329' Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #1 5566b0c47bf0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7fc9f03d7820 @ 20) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #3 5566b0c47b38 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 (7fc9f03d7790 @ 172) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #5 5566b0c47ab8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 (7fc9f03d78b0 @ 17) Nov 19 12:57:31 falcon gnome-shell[1640]: Object Meta.WindowActor (0x55669ffd87a0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #7 5566b0c47a38 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 (7fc9f03d2f70 @ 42) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #9 5566b0c479b0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 (7fc9f03c2dc0 @ 82) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #11 5566b0c47918 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 (7fc9f03cf1f0 @ 116) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #13 5566b0c47898 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 (7fc9f03cf5e0 @ 37) Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #15 5566b0c47818 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 (7fc9f03c2550 @ 12) Nov 19 13:50:35 falcon dbus-daemon[815]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.16238' (uid=1000 pid=1640 comm="/usr/bin/gnome-shell " label="unconfined") Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618328' Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: instance '0x55669ee22c00' has no handler with id '618329' Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #1 5566a7f84270 i
[Desktop-packages] [Bug 185928] Re: Pressing Space key should toggle play/pause (pause when playing; play when paused)
This is a standard for music players. Follow the standard!!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/185928 Title: Pressing Space key should toggle play/pause (pause when playing; play when paused) Status in One Hundred Papercuts: Invalid Status in Rhythmbox: Invalid Status in Totem: Invalid Status in rhythmbox package in Ubuntu: Won't Fix Bug description: Binary package hint: rhythmbox 1. Linux tavla 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION="Ubuntu 7.10" 2. rhythmbox 0.11.2-0ubuntu4 3. Pressing Space, Rhythmbox starts playing the current track from the beginning. That is, it restarts playing the track. By normal convension Space should act as a play/pause button. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/185928/+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 1793124]
I checked all the pages, but developing for Mac is so badly documentated. I gave up, because it was too frustrating. Couldn't find out how to create the Xcode-project. -- 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/1793124 Title: Scrolling on Calc leaves content invisible if cell is higher than screen Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I sometimes receive Calc documents where the content of an individual cell is split on so many lines that it fills up the whole screen and more. I can easily see the top part of these cells but scrolling to the bottom does not seem to work. Whether I try dragging the scrollbar or moving the screen with my laptop’s touchpad, Calc seems to skip the bottom part of the cell and jump directly to the following cell. See the attached screenshots of a document which has numbers 1 to 50 so that numbers 4 to 40 occupy one single cell (A4). In the first screenshot I see the top part of that cell (4 to 23) and in the next I have scrolled down the screen as little as possible, and now I see cell A5 (number 41) on the top. Everything in between is visually inaccessible whatever I try. Description: Ubuntu 18.04.1 LTS Release: 18.04 Installed: 1:6.0.3-0ubuntu1 Candidate: 1:6.0.3-0ubuntu1 Version table: *** 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 18 11:16:17 2018 InstallationDate: Installed on 2017-02-13 (582 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+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 583797]
I can confirm, that setting browser.sessionstore.warnOnQuit = true fixes this for me. The browser won't close down without a warning when hitting Ctrl+Q! Thanks for finally fixing it. -- 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/583797 Title: "Warn on closing with multiple tabs open" not honored Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Invalid Bug description: Binary package hint: firefox 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy firefox firefox: Installed: 11.0+build1-0ubuntu0.11.10.1 Candidate: 11.0+build1-0ubuntu0.11.10.1 Version table: *** 11.0+build1-0ubuntu0.11.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ oneiric-security/main i386 Packages 100 /var/lib/dpkg/status 7.0.1+build1+nobinonly-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in Firefox, with Edit -> Preferences -> Tabs -> "Warn on closing with multiple tabs open" checkbox checked, is when one click the X, File -> Quit, Ctrl+Q , or Alt+Space -> C, one get's the confirmation box: Confirm close You are about to close x tabs. Are you sure you want to continue? 4) What happens instead is one is not warned and the window closes. PARTIAL WORKAROUND: about:config -> browser.tabs.maxOpenBeforeWarn -> change from 15 to 2. This will pop up the confirmation box clicking the X and Alt+Space -> C only. WORKAROUND: Disable Ctrl+Q quiting the browser by installing keyconfig add-on: http://mozilla.dorando.at/keyconfig.xpi Then Tools -> Add-Ons -> Extensions -> keyconfig Preferences -> highlight Quit -> Disable Original Reporter Comments: I found a "workaround" that says to set "open to a blank page" somewhere else, and I set this, but it still doesn't warn me. I work from home and frequently spend an hour or so putting in data, all on one screen. If I accidentally hit the stupid little x (which is now in the left hand corner just where you don't need it, it is too easy to hit it by accident, but i can't change this, it comes with the distro), i lose all that work. Please tell me how to fix this terrible bug. Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3 GTB7.1 THIS BUG AFFECTS MY SECURITY (INCOME) but i guess would not be classifed as a security bug per se ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Fri May 21 14:07:40 2010 FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/583797/+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 1804952] Re: Please upgrade to 60.3.1 in Ubuntu LTS 18.04
** Tags added: bionic upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1804952 Title: Please upgrade to 60.3.1 in Ubuntu LTS 18.04 Status in thunderbird package in Ubuntu: New Bug description: Please upgrade to 60.3.1 in Ubuntu LTS 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1804952/+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 1808576] Re: gnome-control-center segfaults when unit bolt.service is masked
** Bug watch added: Red Hat Bugzilla #1644488 https://bugzilla.redhat.com/show_bug.cgi?id=1644488 ** Also affects: gnome-control-center (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1644488 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1808576 Title: gnome-control-center segfaults when unit bolt.service is masked Status in gnome-control-center package in Ubuntu: New Status in gnome-control-center package in Fedora: Unknown Bug description: I don't have any Thunderbolt devices so I masked the unused the bolt.service. This causes problem with gnome-control-center. Steps to reproduce: 1) launch gnome-control-center $ gnome-control-center 2) navigate to Thunderbolt section go to Devices, then Thunderbolt and close gnome-control-center 3) mask bold.service $ sudo systemctl stop bolt.service $ sudo systemctl mask bolt.service 4) re-launch gnome-control-center $ gnome-control-center (gnome-control-center:21859): thunderbolt-cc-panel-WARNING **: 14:04:53.423: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Expected result: no segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy gnome-control-center bolt gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.2 Candidate: 1:3.28.2-0ubuntu0.18.04.2 Version table: *** 1:3.28.2-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages bolt: Installed: 0.5-0ubuntu0.18.04.1 Candidate: 0.5-0ubuntu0.18.04.1 Version table: *** 0.5-0ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 14:05:26 2018 InstallationDate: Installed on 2018-07-15 (152 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: LANG=en_CA.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1808576/+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 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C
Thank you Kieran Clancy, thank you ThOR27. Model Samsung SNP900X5T- X01US. Can confirm that keyboard backlight now works with ambient light sensor. Elementary OS Juno (Built on Ubuntu 18.04 LTS) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1203592 Title: Keyboard backlight does not work in Samsung Series 9 NP900X4C Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: In Ubuntu 13.04, the keyboard backlight does not work in Samsung Series 9 NP900X4C. Adding the FN key mappings as described in https://help.ubuntu.com/community/SamsungSeries9 does show information in the notification area when pressing the keyboard backlight's + and - buttons, but: 1) The notification always identifies the backlight as "full max" 2) It has no effect on the backlight - it's always off When I first installed Ubuntu on this machine (12.10), even though the fn keys never worked I did have intermitent backlight functionality - the light sensor would sometimes work and I'd see light in the keyboard. I dual boot in Windows 8 and backlighting works there, so this is not a hardware issue. More discussion can be found here: http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight- fn-buttons-work-in-samsung-series-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+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 1808583] [NEW] Update policykit dependency
Public bug reported: screen-resolution-extra depends on policykit-1-gnome | polkit-1-auth-agent . I recommend changing that to: gnome-shell | policykit-1-gnome | polkit-1-auth-agent policykit-1-gnome's package description --- PolicyKit-gnome provides a D-Bus session bus service that is used to bring up authentication dialogs used for obtaining privileges. . This implementation was originally designed for GNOME 2, but most GNOME-based desktop environments, including GNOME 3, GNOME Flashback, and MATE, have their own built-in PolicyKit agents and no longer use this one. The remaining users of this implementation are Cinnamon, XFCE and Unity. Explanation --- Since policykit-1-gnome is no longer required by the default Ubuntu desktop and is not really maintained upstream any more, I think it should be demoted to universe. gnome-shell Provides polkit-1-auth-agent so the current dependency should have been good enough. Based on my experience with working on demoting xterm to universe, I found that germinate doesn't handle alternate dependencies and virtual packages very well. I had to have packages like xinit recommend gnome- terminal ahead of xterm in the alternate dependency list. So I think we'll have to act similarly here to specify the exact dependency we want in main first in the dependency list. ** Affects: screen-resolution-extra (Ubuntu) Importance: Low Status: New ** Tags: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1808583 Title: Update policykit dependency Status in screen-resolution-extra package in Ubuntu: New Bug description: screen-resolution-extra depends on policykit-1-gnome | polkit-1-auth-agent . I recommend changing that to: gnome-shell | policykit-1-gnome | polkit-1-auth-agent policykit-1-gnome's package description --- PolicyKit-gnome provides a D-Bus session bus service that is used to bring up authentication dialogs used for obtaining privileges. . This implementation was originally designed for GNOME 2, but most GNOME-based desktop environments, including GNOME 3, GNOME Flashback, and MATE, have their own built-in PolicyKit agents and no longer use this one. The remaining users of this implementation are Cinnamon, XFCE and Unity. Explanation --- Since policykit-1-gnome is no longer required by the default Ubuntu desktop and is not really maintained upstream any more, I think it should be demoted to universe. gnome-shell Provides polkit-1-auth-agent so the current dependency should have been good enough. Based on my experience with working on demoting xterm to universe, I found that germinate doesn't handle alternate dependencies and virtual packages very well. I had to have packages like xinit recommend gnome- terminal ahead of xterm in the alternate dependency list. So I think we'll have to act similarly here to specify the exact dependency we want in main first in the dependency list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1808583/+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 1808582] [NEW] VCS is out of date
Public bug reported: The Vcs fields in screen-resolution-extra point to https://github.com/tseliot/screen-resolution-extra but that repository is several versions out of date. ** Affects: screen-resolution-extra (Ubuntu) Importance: Low Status: New ** Changed in: screen-resolution-extra (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1808582 Title: VCS is out of date Status in screen-resolution-extra package in Ubuntu: New Bug description: The Vcs fields in screen-resolution-extra point to https://github.com/tseliot/screen-resolution-extra but that repository is several versions out of date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1808582/+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 1808581] [NEW] cannot print to Canon MX860 after upgrade to Ubuntu 18.04
Public bug reported: After upgrading to Ubuntu 18.04, I can no longer print to my Canon MX860. It is connected to my WiFi network. - I can successfully ping the printer. - I can connect to the printer via the printer web server. - When I try to print, it just hangs: no error messages, no printing. Additional information was submitted with 'ubuntu-bug cups' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 13:30:40 2018 InstallationDate: Installed on 2015-01-10 (1434 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) KernLog: Lpstat: device for MX860: cnijnet:/00:1E:8F:74:5A:78 MachineType: MSI MS-7865 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MX860.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MX860.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=c7580c78-9be5-43e5-8256-d02dd697238b ro plymouth:debug drm.debug=0xe SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-08-16 (120 days ago) dmi.bios.date: 02/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1I (MS-7865) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.0:bd02/21/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7865 dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1808581 Title: cannot print to Canon MX860 after upgrade to Ubuntu 18.04 Status in cups package in Ubuntu: New Bug description: After upgrading to Ubuntu 18.04, I can no longer print to my Canon MX860. It is connected to my WiFi network. - I can successfully ping the printer. - I can connect to the printer via the printer web server. - When I try to print, it just hangs: no error messages, no printing. Additional information was submitted with 'ubuntu-bug cups' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 13:30:40 2018 InstallationDate: Installed on 2015-01-10 (1434 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) KernLog: Lpstat: device for MX860: cnijnet:/00:1E:8F:74:5A:78 MachineType: MSI MS-7865 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MX860.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MX860.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=c7580c78-9be5-43e5-8256-d02dd697238b ro plymouth:debug drm.debug=0xe SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-08-16 (120 days ago) dmi.bios.date: 02/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1I (MS-7865) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.0:bd02/21/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7865 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1808581/+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 1247668]
Guys, the problem still happens on various linux distros in 2016. Is there anybody looking into this? It's so annoying for anybody using more than one keyboard layout. -- 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/1247668 Title: NumLock turned off on layout switch Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: Extracting from bug 1218322, confirmed there by multiple users: When switching the keyboard layout using a shortcut (such as Alt+Shift), NumLock functionality is (mostly) turned off. More precisely: it goes into an inconsistent state where pressing numpad 5 inserts the digit 5, but the other numpad keys move the cursor. Pressing the NumLock key turns it off completely (pressing numpad 5 no longer does anything), and pressing once again turns it on. This means that if someone prefers to have the NumLock functionality switched on all the time, they have to press the NumLock key twice after each layout change. I find this a huge usability problem. (I don't have a LED, so I cannot tell how that one is lit.) The bug is not present when changing the layout via the indicator applet. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 3 21:54:37 2013 InstallationDate: Installed on 2012-05-30 (522 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to saucy on 2013-10-12 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1247668/+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 1247668] Re: NumLock turned off on layout switch
** Changed in: xorg-server Status: Confirmed => Unknown -- 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/1247668 Title: NumLock turned off on layout switch Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: Extracting from bug 1218322, confirmed there by multiple users: When switching the keyboard layout using a shortcut (such as Alt+Shift), NumLock functionality is (mostly) turned off. More precisely: it goes into an inconsistent state where pressing numpad 5 inserts the digit 5, but the other numpad keys move the cursor. Pressing the NumLock key turns it off completely (pressing numpad 5 no longer does anything), and pressing once again turns it on. This means that if someone prefers to have the NumLock functionality switched on all the time, they have to press the NumLock key twice after each layout change. I find this a huge usability problem. (I don't have a LED, so I cannot tell how that one is lit.) The bug is not present when changing the layout via the indicator applet. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 3 21:54:37 2013 InstallationDate: Installed on 2012-05-30 (522 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to saucy on 2013-10-12 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1247668/+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 135738] Re: DisplaySize setting not honored
** Changed in: xorg-server Status: Confirmed => Unknown -- 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/135738 Title: DisplaySize setting not honored Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Bug description: Binary package hint: xorg I have this in my xorg.conf: Section "Monitor" Identifier "VG2230wm" Option "DPMS" DisplaySize 444 277 HorizSync 24-82 VertRefresh 50-85 EndSection However, xdpyinfo reports that it's not using it: screen #0: dimensions:1680x1050 pixels (474x303 millimeters) This was working in 7.04, but broke when I upgraded to gusty somewhere around tribe 5. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/135738/+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 135738]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/246. -- 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/135738 Title: DisplaySize setting not honored Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Bug description: Binary package hint: xorg I have this in my xorg.conf: Section "Monitor" Identifier "VG2230wm" Option "DPMS" DisplaySize 444 277 HorizSync 24-82 VertRefresh 50-85 EndSection However, xdpyinfo reports that it's not using it: screen #0: dimensions:1680x1050 pixels (474x303 millimeters) This was working in 7.04, but broke when I upgraded to gusty somewhere around tribe 5. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/135738/+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 1247668]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/261. -- 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/1247668 Title: NumLock turned off on layout switch Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: Extracting from bug 1218322, confirmed there by multiple users: When switching the keyboard layout using a shortcut (such as Alt+Shift), NumLock functionality is (mostly) turned off. More precisely: it goes into an inconsistent state where pressing numpad 5 inserts the digit 5, but the other numpad keys move the cursor. Pressing the NumLock key turns it off completely (pressing numpad 5 no longer does anything), and pressing once again turns it on. This means that if someone prefers to have the NumLock functionality switched on all the time, they have to press the NumLock key twice after each layout change. I find this a huge usability problem. (I don't have a LED, so I cannot tell how that one is lit.) The bug is not present when changing the layout via the indicator applet. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 3 21:54:37 2013 InstallationDate: Installed on 2012-05-30 (522 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to saucy on 2013-10-12 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1247668/+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 201491] Re: Screen DPI detected incorrectly by xdpyinfo
** Changed in: xorg-server Status: Confirmed => Unknown -- 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/201491 Title: Screen DPI detected incorrectly by xdpyinfo Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Invalid Bug description: Binary package hint: xorg It seems tools like xdpyinfo are reporting screen sizes as 300x230 mm in a lot of cases when they are not. On my own Iiyama ProLite E431S with an ATI Radeon 9800 Pro connected over DVI using the "ati" driver, I get this from xdpyinfo: screen #0: dimensions:1280x1024 pixels (300x230 millimeters) resolution:108x113 dots per inch ddcprobe correctly detects the screen physical dimensions: screensize: 34 27 In another report, https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-video-intel/+bug/201032 the reporter shows that xdpyinfo quotes: screen #0: dimensions:1280x800 pixels (300x230 millimeters) resolution:108x88 dots per inch and ddcprobe reports: screensize: 33 21 Notice that the screens are actually different dimensions, both in physical terms and pixel terms, yet xdpyinfo thinks they are 300x230 mm. Also, the other reporter is using the intel driver. This did indeed used to work correctly in the early Hardy alphas, and previous releases of Ubuntu. ProblemType: Bug Architecture: i386 Date: Wed Mar 12 17:34:11 2008 DistroRelease: Ubuntu 8.04 Package: xorg 1:7.3+10ubuntu6 PackageArchitecture: i386 SourcePackage: xorg Uname: Linux 2.6.24-11-386 i686 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/201491/+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 1754401] Re: mounting /proc with hidepid causes: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)
** Changed in: xorg-server Status: Incomplete => Unknown -- 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/1754401 Title: mounting /proc with hidepid causes: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Bug description: I don't what changed but today, my Artful laptop refuses to start a graphical session. The last update seems entirely unrelated: # /var/log/apt/history.log Start-Date: 2018-03-06 15:50:35 Commandline: apt-get dist-upgrade Requested-By: simon (1000) Upgrade: libpq5:amd64 (9.6.7-0ubuntu0.17.10, 9.6.8-0ubuntu0.17.10) End-Date: 2018-03-06 15:50:39 I tried linux-image-4.13.0-32-generic and linux- image-4.13.0-36-generic to no avail. I removed the "quiet splash" args from /etc/default/grub but it didn't help. Using "nomodeset" makes the graphical session almost work but the brightness of the screen is so low that I cannot use it and can't make it brighter either. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Thu Mar 8 11:08:35 2018 InstallationDate: Installed on 2017-10-21 (137 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1754401/+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 201491]
xdpyinfo on XRandR 1.2+ screen really reports wrong DPI information. Last version of patch for xdpyinfo which fixes this problem is there: https://lists.x.org/archives/xorg-devel/2017-May/053743.html Also this patch (v2) fixes reporing of negative values in resolution information. -- 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/201491 Title: Screen DPI detected incorrectly by xdpyinfo Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Invalid Bug description: Binary package hint: xorg It seems tools like xdpyinfo are reporting screen sizes as 300x230 mm in a lot of cases when they are not. On my own Iiyama ProLite E431S with an ATI Radeon 9800 Pro connected over DVI using the "ati" driver, I get this from xdpyinfo: screen #0: dimensions:1280x1024 pixels (300x230 millimeters) resolution:108x113 dots per inch ddcprobe correctly detects the screen physical dimensions: screensize: 34 27 In another report, https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-video-intel/+bug/201032 the reporter shows that xdpyinfo quotes: screen #0: dimensions:1280x800 pixels (300x230 millimeters) resolution:108x88 dots per inch and ddcprobe reports: screensize: 33 21 Notice that the screens are actually different dimensions, both in physical terms and pixel terms, yet xdpyinfo thinks they are 300x230 mm. Also, the other reporter is using the intel driver. This did indeed used to work correctly in the early Hardy alphas, and previous releases of Ubuntu. ProblemType: Bug Architecture: i386 Date: Wed Mar 12 17:34:11 2008 DistroRelease: Ubuntu 8.04 Package: xorg 1:7.3+10ubuntu6 PackageArchitecture: i386 SourcePackage: xorg Uname: Linux 2.6.24-11-386 i686 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/201491/+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 201491]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/366. -- 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/201491 Title: Screen DPI detected incorrectly by xdpyinfo Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Invalid Bug description: Binary package hint: xorg It seems tools like xdpyinfo are reporting screen sizes as 300x230 mm in a lot of cases when they are not. On my own Iiyama ProLite E431S with an ATI Radeon 9800 Pro connected over DVI using the "ati" driver, I get this from xdpyinfo: screen #0: dimensions:1280x1024 pixels (300x230 millimeters) resolution:108x113 dots per inch ddcprobe correctly detects the screen physical dimensions: screensize: 34 27 In another report, https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-video-intel/+bug/201032 the reporter shows that xdpyinfo quotes: screen #0: dimensions:1280x800 pixels (300x230 millimeters) resolution:108x88 dots per inch and ddcprobe reports: screensize: 33 21 Notice that the screens are actually different dimensions, both in physical terms and pixel terms, yet xdpyinfo thinks they are 300x230 mm. Also, the other reporter is using the intel driver. This did indeed used to work correctly in the early Hardy alphas, and previous releases of Ubuntu. ProblemType: Bug Architecture: i386 Date: Wed Mar 12 17:34:11 2008 DistroRelease: Ubuntu 8.04 Package: xorg 1:7.3+10ubuntu6 PackageArchitecture: i386 SourcePackage: xorg Uname: Linux 2.6.24-11-386 i686 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/201491/+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 201491]
I have something maybe related to this problem. Incorrect resolution detected: screen #0: dimensions:5120x1024 pixels (1354x270 millimeters) resolution:-2147483648x-2147483648 dots per inch More on https://bugs.launchpad.net/xorg-server/+bug/1650192 -- 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/201491 Title: Screen DPI detected incorrectly by xdpyinfo Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Invalid Bug description: Binary package hint: xorg It seems tools like xdpyinfo are reporting screen sizes as 300x230 mm in a lot of cases when they are not. On my own Iiyama ProLite E431S with an ATI Radeon 9800 Pro connected over DVI using the "ati" driver, I get this from xdpyinfo: screen #0: dimensions:1280x1024 pixels (300x230 millimeters) resolution:108x113 dots per inch ddcprobe correctly detects the screen physical dimensions: screensize: 34 27 In another report, https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-video-intel/+bug/201032 the reporter shows that xdpyinfo quotes: screen #0: dimensions:1280x800 pixels (300x230 millimeters) resolution:108x88 dots per inch and ddcprobe reports: screensize: 33 21 Notice that the screens are actually different dimensions, both in physical terms and pixel terms, yet xdpyinfo thinks they are 300x230 mm. Also, the other reporter is using the intel driver. This did indeed used to work correctly in the early Hardy alphas, and previous releases of Ubuntu. ProblemType: Bug Architecture: i386 Date: Wed Mar 12 17:34:11 2008 DistroRelease: Ubuntu 8.04 Package: xorg 1:7.3+10ubuntu6 PackageArchitecture: i386 SourcePackage: xorg Uname: Linux 2.6.24-11-386 i686 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/201491/+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 201491]
This bug is still present. xdpyinfo reports always 96x96 dpi resulting in wrong screen dimensions and incorrect scaling. $ xdpyinfo | grep -B2 resolution screen #0: dimensions:3840x2160 pixels (1016x571 millimeters) resolution:96x96 dots per inch however, xrandr is right; $ xrandr | grep DP1 DP1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm -- 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/201491 Title: Screen DPI detected incorrectly by xdpyinfo Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Invalid Bug description: Binary package hint: xorg It seems tools like xdpyinfo are reporting screen sizes as 300x230 mm in a lot of cases when they are not. On my own Iiyama ProLite E431S with an ATI Radeon 9800 Pro connected over DVI using the "ati" driver, I get this from xdpyinfo: screen #0: dimensions:1280x1024 pixels (300x230 millimeters) resolution:108x113 dots per inch ddcprobe correctly detects the screen physical dimensions: screensize: 34 27 In another report, https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-video-intel/+bug/201032 the reporter shows that xdpyinfo quotes: screen #0: dimensions:1280x800 pixels (300x230 millimeters) resolution:108x88 dots per inch and ddcprobe reports: screensize: 33 21 Notice that the screens are actually different dimensions, both in physical terms and pixel terms, yet xdpyinfo thinks they are 300x230 mm. Also, the other reporter is using the intel driver. This did indeed used to work correctly in the early Hardy alphas, and previous releases of Ubuntu. ProblemType: Bug Architecture: i386 Date: Wed Mar 12 17:34:11 2008 DistroRelease: Ubuntu 8.04 Package: xorg 1:7.3+10ubuntu6 PackageArchitecture: i386 SourcePackage: xorg Uname: Linux 2.6.24-11-386 i686 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/201491/+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 1754401]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/243. -- 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/1754401 Title: mounting /proc with hidepid causes: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Bug description: I don't what changed but today, my Artful laptop refuses to start a graphical session. The last update seems entirely unrelated: # /var/log/apt/history.log Start-Date: 2018-03-06 15:50:35 Commandline: apt-get dist-upgrade Requested-By: simon (1000) Upgrade: libpq5:amd64 (9.6.7-0ubuntu0.17.10, 9.6.8-0ubuntu0.17.10) End-Date: 2018-03-06 15:50:39 I tried linux-image-4.13.0-32-generic and linux- image-4.13.0-36-generic to no avail. I removed the "quiet splash" args from /etc/default/grub but it didn't help. Using "nomodeset" makes the graphical session almost work but the brightness of the screen is so low that I cannot use it and can't make it brighter either. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Thu Mar 8 11:08:35 2018 InstallationDate: Installed on 2017-10-21 (137 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1754401/+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 1785550] Re: Huge memory usage when changing background
Hi Sebastien, it contains 1288 pictures and a folder with 24000 pictures... so it is a normal photo collection. In any case nautilus handles them without particular effort. Taddeo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1785550 Title: Huge memory usage when changing background Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I open "change background" window in Settings, RAM usage of gnome-control-center goes over 2 gb. In practice I can't change background since gnome-control-center fills all memory, freezing the system. In general, system will freeze without return every time a program fills the memory faster than the system moving memory to swap. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.28.2-0ubuntu1 Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 6 07:32:28 2018 InstallationDate: Installed on 2017-01-12 (570 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to cosmic on 2018-07-24 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1785550/+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 1808576] [NEW] gnome-control-center segfaults when unit bolt.service is masked
Public bug reported: I don't have any Thunderbolt devices so I masked the unused the bolt.service. This causes problem with gnome-control-center. Steps to reproduce: 1) launch gnome-control-center $ gnome-control-center 2) navigate to Thunderbolt section go to Devices, then Thunderbolt and close gnome-control-center 3) mask bold.service $ sudo systemctl stop bolt.service $ sudo systemctl mask bolt.service 4) re-launch gnome-control-center $ gnome-control-center (gnome-control-center:21859): thunderbolt-cc-panel-WARNING **: 14:04:53.423: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Expected result: no segfault. Additional information: $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy gnome-control-center bolt gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.2 Candidate: 1:3.28.2-0ubuntu0.18.04.2 Version table: *** 1:3.28.2-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages bolt: Installed: 0.5-0ubuntu0.18.04.1 Candidate: 0.5-0ubuntu0.18.04.1 Version table: *** 0.5-0ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 14:05:26 2018 InstallationDate: Installed on 2018-07-15 (152 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: LANG=en_CA.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1808576 Title: gnome-control-center segfaults when unit bolt.service is masked Status in gnome-control-center package in Ubuntu: New Bug description: I don't have any Thunderbolt devices so I masked the unused the bolt.service. This causes problem with gnome-control-center. Steps to reproduce: 1) launch gnome-control-center $ gnome-control-center 2) navigate to Thunderbolt section go to Devices, then Thunderbolt and close gnome-control-center 3) mask bold.service $ sudo systemctl stop bolt.service $ sudo systemctl mask bolt.service 4) re-launch gnome-control-center $ gnome-control-center (gnome-control-center:21859): thunderbolt-cc-panel-WARNING **: 14:04:53.423: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Expected result: no segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy gnome-control-center bolt gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.2 Candidate: 1:3.28.2-0ubuntu0.18.04.2 Version table: *** 1:3.28.2-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages bolt: Installed: 0.5-0ubuntu0.18.04.1 Candidate: 0.5-0ubuntu0.18.04.1 Version table: *** 0.5-0ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 14:05:26 2018 InstallationDate: Installed on 2018-07-15 (152 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release
[Desktop-packages] [Bug 694910] Re: Regression: patch to bug 539477 breaks Super+P keybindings
Gnome bug 651571 was marked as a dupe of 792892; updating remote watch accordingly. ** Bug watch added: GNOME Bug Tracker #792892 https://bugzilla.gnome.org/show_bug.cgi?id=792892 ** Changed in: gnome-settings-daemon Importance: Medium => Unknown ** Changed in: gnome-settings-daemon Status: Invalid => Unknown ** Changed in: gnome-settings-daemon Remote watch: GNOME Bug Tracker #651571 => GNOME Bug Tracker #792892 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/694910 Title: Regression: patch to bug 539477 breaks Super+P keybindings Status in GNOME Settings Daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-settings-daemon The current patch to bug 539477 breaks the super+p keybinding for all user applications when running gnone-settings-daemon. This behavior is hard-coded, not discoverable, and not configurable. The "workaround" is to disable parts of xrandr such that screen switching is no longer possible. The patch has been checked in and released as a bugfix to Ubuntu 10.10, causing regressions in several applications. For more details, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/ particularly https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/comments/68 and immediately above. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/694910/+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 1297790] Re: "Unknown audio device" dialog pops up every time I plug in headphones
Praise jesus. They finally fixed this bug. -- 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/1297790 Title: "Unknown audio device" dialog pops up every time I plug in headphones Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: I've got a combined headphone/headset socket on my Laptop. Every time I plug in my headphones, an "unknown audio device" dialog pops up asking whether I've plugged in headphones or a headset. This is isn't a great user experience as my phone can auto-detect the device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1949 F pulseaudio /dev/snd/controlC0: mark 1949 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 26 11:03:29 2014 InstallationDate: Installed on 2014-03-24 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Latitude E7440, Realtek ALC292, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.asset.tag: DE004505 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: DE004505 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1297790/+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 1641928] Re: "Unknown audio device" dialog pops up every time I plug in headphones
Finally fixed. ** Changed in: alsa-driver (Ubuntu) Status: New => Fix Released -- 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/1641928 Title: "Unknown audio device" dialog pops up every time I plug in headphones Status in alsa-driver package in Ubuntu: Fix Released Bug description: I used to use Ubuntu 15.10 for a long time and everything was fine. As soon as I installed (clean install) Ubuntu 16.04 the dialog started appearing every time I plugged in my earphones. Problem still present on 16.10. -Saw this bug report https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1297790 -In there someone posted a link to http://voices.canonical.com/david.henningsson/2014/03/07/headset-jacks-on-newer-laptops/ -which encourages users to submit their own bug reports using ubuntu-bug audio in order to collect hw info, so I did. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zoltan F pulseaudio /dev/snd/controlC1: zoltan F pulseaudio CurrentDesktop: Unity Date: Tue Nov 15 11:48:15 2016 InstallationDate: Installed on 2016-10-15 (30 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 13 9343, Realtek ALC3263, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to yakkety on 2016-10-23 (22 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1641928/+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 1795342] Re: High Power Consumption
Disabled snapd service and left the laptop idle, almost same power usage. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795342 Title: High Power Consumption Status in The Ubuntu Power Consumption Project: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I am running Ubuntu on Thinkpad. I am facing battery back up issues on both 18.04 and 18.10 versions. Before that I was running Ubuntu 16.04 with a normal back of almost 4 hours ( 2 Sony Batteries with normal back up of up to min of 6 hours on Linux Mint 19) and when upgrading to 18.04 it reduced to 3 hours max on normal usage and less than 2 hours on heavy use. I tried installing Unity session on 18.04/10, the back up increased. I think it is Gnome doing the mess. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1795342/+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 1808193] Re: Battery percentage changes suddenly depending on whether AC is plugged in
apport information ** Description changed: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-12-10 (4 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + Package: upower + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 + Tags: cosmic + Uname: Linux 4.18.0-12-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1808193/+attachment/5222351/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+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 1808193] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1808193/+attachment/5222352/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+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 1808193] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1808193/+attachment/5222353/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+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 1808193] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1808193/+attachment/5222354/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+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 1808557] Re: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt
** Tags removed: need-duplicate-check -- 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/1808557 Title: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in network-manager package in Ubuntu: New Bug description: the installing gui 'Ubuntu Software' is repeatedly outphased in X revealing instability somewhere. Ubuntu 16.04.5 LTS is the output from lsb_release -rd. As a result I had to restart installation for updates several times. Such disfunctioning occured a number of times before with the gui, so I was using apt instead, but as it was stated that the gui would be improved, I gave it a try. It showed a large number of errors. Moreover it does not show any progress of what is going on during install of updates. In the small window it was stated that libnm-glib-vpn1:i386 would be in total bad shape so it should be removed and reinstalled. This is now done. But that seems only the result of an instability occuring lately quite often with Ubuntu, starting with some larger uodate a couple of months ago. I know this is not a very precise description. I will now clean up the system starting with verifying all packages. The instability will probably remain though. In the process the gui was also updated and seems now to be functioning, so the version is now ubuntu-software 3.20.5-0ubuntu0 i386 . There are similar issues of being outphased with libreoffice, evince and probably some more which we seldom use. The common link between these errors is that contact with X is temporarily lost while free memory is low. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Fri Dec 14 15:49:36 2018 DuplicateSignature: package:libnm-glib-vpn1:i386:1.2.6-0ubuntu0.16.04.3 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ... dpkg: error processing package libnm-glib-vpn1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-25 (476 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) IpRoute: default via 192.168.0.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.103 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager Title: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2017-08-25 (476 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 dlink-5C98 af76c1cc-4c5d-4991-af25-a2fdfd7a5b5c /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1808557/+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 1808557] [NEW] package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem
Public bug reported: the installing gui 'Ubuntu Software' is repeatedly outphased in X revealing instability somewhere. Ubuntu 16.04.5 LTS is the output from lsb_release -rd. As a result I had to restart installation for updates several times. Such disfunctioning occured a number of times before with the gui, so I was using apt instead, but as it was stated that the gui would be improved, I gave it a try. It showed a large number of errors. Moreover it does not show any progress of what is going on during install of updates. In the small window it was stated that libnm-glib-vpn1:i386 would be in total bad shape so it should be removed and reinstalled. This is now done. But that seems only the result of an instability occuring lately quite often with Ubuntu, starting with some larger uodate a couple of months ago. I know this is not a very precise description. I will now clean up the system starting with verifying all packages. The instability will probably remain though. In the process the gui was also updated and seems now to be functioning, so the version is now ubuntu-software 3.20.5-0ubuntu0 i386 . There are similar issues of being outphased with libreoffice, evince and probably some more which we seldom use. The common link between these errors is that contact with X is temporarily lost while free memory is low. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Fri Dec 14 15:49:36 2018 DuplicateSignature: package:libnm-glib-vpn1:i386:1.2.6-0ubuntu0.16.04.3 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ... dpkg: error processing package libnm-glib-vpn1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-25 (476 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) IpRoute: default via 192.168.0.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.103 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager Title: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2017-08-25 (476 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 dlink-5C98 af76c1cc-4c5d-4991-af25-a2fdfd7a5b5c /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- 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/1808557 Title: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in network-manager package in Ubuntu: New Bug description: the installing gui 'Ubuntu Software' is repeatedly outphased in X revealing instability somewhere. Ubuntu 16.04.5 LTS is the output from lsb_release -rd. As a result I had to restart installation for updates several times. Such disfunctioning occured a number of times before with the gui, so I was using apt instead, but as it was stated that the gui would be improved, I gave it a try. It showed a large number of errors. Moreover it does not show any progress of what is going on during install of updates. In the
[Desktop-packages] [Bug 996552] Re: file roller does not open files with odt ending
Still present in 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/996552 Title: file roller does not open files with odt ending Status in File Roller: New Status in file-roller package in Ubuntu: Confirmed Bug description: I am a systemdeveloper developing reporting systems for University Management Software. we are using Libreoffice as reporting Engine and do some non-standard stuff with the odt files, we use as templates for pdf output. In the past I was able to open an odt file with a right-click and choosing "Open in file-roller", but with 12.04 I get an Error message: "Archive is not supported". When I change the filesuffix from .odt to .zip, file-roller has no problems opening the file. Of course not, since an odt file IS ACTUALLY an zip archive and therefore it should be able to open it with file-roller. I really hope this is not an intended "feature", since it would be an odd one... ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: file-roller 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 8 15:46:12 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120412) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/996552/+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 1807056] Re: Occasional Keyboard freeze
I am sorry. This is my primary laptop. I plan to keep the Ubuntu as default as possible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+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 1017274] Re: package ttf-sil-scheherazade (not installed) failed to install/upgrade: package ttf-sil-scheherazade is not ready for configuration cannot configure (current statu
The defoma configuration file is no longer in the package, so this issue should not occur in newer packages. ** Changed in: fonts-sil-scheherazade (Ubuntu) Status: New => Fix Released ** Changed in: fonts-sil-scheherazade (Ubuntu) Assignee: (unassigned) => Bobby de Vos (bobby-devos) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-sil-scheherazade in Ubuntu. https://bugs.launchpad.net/bugs/1017274 Title: package ttf-sil-scheherazade (not installed) failed to install/upgrade: package ttf-sil-scheherazade is not ready for configuration cannot configure (current status `config-files') Status in fonts-sil-scheherazade package in Ubuntu: Fix Released Bug description: i wanna install zekr, and i got this message. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: ttf-sil-scheherazade (not installed) ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18 Uname: Linux 3.2.0-25-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Sat Jun 23 09:10:03 2012 DuplicateSignature: Setting up fonts-sil-scheherazade (1.001-7) ... dpkg: error processing ttf-sil-scheherazade (--configure): package ttf-sil-scheherazade is not ready for configuration ErrorMessage: package ttf-sil-scheherazade is not ready for configuration cannot configure (current status `config-files') InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: fonts-sil-scheherazade Title: package ttf-sil-scheherazade (not installed) failed to install/upgrade: package ttf-sil-scheherazade is not ready for configuration cannot configure (current status `config-files') UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.defoma.hints.ttf.sil.scheherazade.hints: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-sil-scheherazade/+bug/1017274/+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 1724793] Re: Error localization
** Package changed: ufw (Ubuntu) => language-selector (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1724793 Title: Error localization Status in language-selector package in Ubuntu: New Bug description: After some manipulation of the system interface of the OS was in English, as all the default startup application. I tried to change the locale via GUI, however, everything on the ground. --- После некоторых манипуляций с системой интерфейс ОС стал на английском, как и все запускаемые по умолчанию приложения. Пробовал изменить локаль через ГУИ, однако там всё на местах. locale LANG=ru_RU.UTF-8 LANGUAGE=C.UTF-8 LC_CTYPE="ru_RU.UTF-8" LC_NUMERIC="ru_RU.UTF-8" LC_TIME="ru_RU.UTF-8" LC_COLLATE="ru_RU.UTF-8" LC_MONETARY="ru_RU.UTF-8" LC_MESSAGES="ru_RU.UTF-8" LC_PAPER="ru_RU.UTF-8" LC_NAME="ru_RU.UTF-8" LC_ADDRESS="ru_RU.UTF-8" LC_TELEPHONE="ru_RU.UTF-8" LC_MEASUREMENT="ru_RU.UTF-8" LC_IDENTIFICATION="ru_RU.UTF-8" LC_ALL=ru_RU.UTF-8 locale -a C C.UTF-8 en_AG en_AG.utf8 en_AU.utf8 en_BW.utf8 en_CA.utf8 en_DK.utf8 en_GB.utf8 en_HK.utf8 en_IE.utf8 en_IN en_IN.utf8 en_NG en_NG.utf8 en_NZ.utf8 en_PH.utf8 en_SG.utf8 en_US.utf8 en_ZA.utf8 en_ZM en_ZM.utf8 en_ZW.utf8 POSIX ru_RU.utf8 ru_UA.utf8 cat /etc/default/locale # File generated by update-locale LANG="ru_RU.UTF-8" LANGUAGE="ru:en" LC_NUMERIC="ru_RU.UTF-8" LC_TIME="ru_RU.UTF-8" LC_MONETARY="ru_RU.UTF-8" LC_PAPER="ru_RU.UTF-8" LC_IDENTIFICATION="ru_RU.UTF-8" LC_NAME="ru_RU.UTF-8" LC_ADDRESS="ru_RU.UTF-8" LC_TELEPHONE="ru_RU.UTF-8" LC_MEASUREMENT="ru_RU.UTF-8" nano ~/.bashrc # ~/.bashrc: executed by bash(1) for non-login shells. # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) # for examples #export LC_xxx=C.UTF-8 export LC_ALL=ru_RU.UTF-8 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1724793/+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 1792835] Re: Bash completion for Inkscape does not work
The ufw bug is being tracking in bug 1775043. Removing that task.
** No longer affects: ufw (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1792835
Title:
Bash completion for Inkscape does not work
Status in apt-xapian-index package in Ubuntu:
New
Status in cowdancer package in Ubuntu:
Fix Committed
Status in dpatch package in Ubuntu:
New
Status in inkscape package in Ubuntu:
Fix Released
Status in jackd2 package in Ubuntu:
New
Bug description:
Bash completion for Inkscape does not work in Ubuntu 18.04. It will
for example suggest non-svg files.
The reason seems to be that /usr/share/bash-
completion/completions/inkscape uses the have() function, which is
temporarily defined in /usr/share/bash-completion/bash_completion, but
then unset at the end of that file.
Workaround: Copy /usr/share/bash-completion/completions/inkscape to
~/.local/share/bash-completion/completions/inkscape and remove the
uses of "have".
The bash completion for some other commands seem to use have() too,
e.g. jackd, ufw, cowbuilder, dpatch_edit_patch, and axi-cache, so bash
completion for these commands will presumably not work either.
From /usr/share/bash-completion/bash_completion:
-
# Backwards compatibility for compat completions that use have().
# @deprecated should no longer be used; generally not needed with dynamically
# loaded completions, and _have is suitable for runtime use.
have()
{
unset -v have
_have $1 && have=yes
}
[...]
unset -f have
unset have
-
From /usr/share/bash-completion/completions/inkscape:
-
[...]
have inkscape &&
_inkscape()
{
[...]
}
[ "${have:-}" ] && complete -F _inkscape $filenames inkscape
-
System information:
$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
$ apt-cache policy inkscape
inkscape:
Installed: 0.92.3-1
Candidate: 0.92.3-1
Version table:
*** 0.92.3-1 500
500 http://no.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1792835/+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 1766503] Re: ibus-* randomly use high CPU
OK. I got it. In my case processes starts in similar way /tmp/XXX-XXX... that's was suspicious after search info about similar cases I found this: https://ubuntuforums.org/showthread.php?t=2389313 https://www.reddit.com/r/Addons4Kodi/comments/8eto78/people_using_unofficial_kodi_addon_on_linux/ Please check if ~/.config/autostart/dbus-daemon.desktop exists. After cleaning ~/.config/autostart/ folder situation is better also i found suspicious inictl file in ~/.cache/fontconfig I will check files with ClamAV but this will take some time. For now CPU usage looks good for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1724793] [NEW] Error localization
You have been subscribed to a public bug: After some manipulation of the system interface of the OS was in English, as all the default startup application. I tried to change the locale via GUI, however, everything on the ground. --- После некоторых манипуляций с системой интерфейс ОС стал на английском, как и все запускаемые по умолчанию приложения. Пробовал изменить локаль через ГУИ, однако там всё на местах. locale LANG=ru_RU.UTF-8 LANGUAGE=C.UTF-8 LC_CTYPE="ru_RU.UTF-8" LC_NUMERIC="ru_RU.UTF-8" LC_TIME="ru_RU.UTF-8" LC_COLLATE="ru_RU.UTF-8" LC_MONETARY="ru_RU.UTF-8" LC_MESSAGES="ru_RU.UTF-8" LC_PAPER="ru_RU.UTF-8" LC_NAME="ru_RU.UTF-8" LC_ADDRESS="ru_RU.UTF-8" LC_TELEPHONE="ru_RU.UTF-8" LC_MEASUREMENT="ru_RU.UTF-8" LC_IDENTIFICATION="ru_RU.UTF-8" LC_ALL=ru_RU.UTF-8 locale -a C C.UTF-8 en_AG en_AG.utf8 en_AU.utf8 en_BW.utf8 en_CA.utf8 en_DK.utf8 en_GB.utf8 en_HK.utf8 en_IE.utf8 en_IN en_IN.utf8 en_NG en_NG.utf8 en_NZ.utf8 en_PH.utf8 en_SG.utf8 en_US.utf8 en_ZA.utf8 en_ZM en_ZM.utf8 en_ZW.utf8 POSIX ru_RU.utf8 ru_UA.utf8 cat /etc/default/locale # File generated by update-locale LANG="ru_RU.UTF-8" LANGUAGE="ru:en" LC_NUMERIC="ru_RU.UTF-8" LC_TIME="ru_RU.UTF-8" LC_MONETARY="ru_RU.UTF-8" LC_PAPER="ru_RU.UTF-8" LC_IDENTIFICATION="ru_RU.UTF-8" LC_NAME="ru_RU.UTF-8" LC_ADDRESS="ru_RU.UTF-8" LC_TELEPHONE="ru_RU.UTF-8" LC_MEASUREMENT="ru_RU.UTF-8" nano ~/.bashrc # ~/.bashrc: executed by bash(1) for non-login shells. # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) # for examples #export LC_xxx=C.UTF-8 export LC_ALL=ru_RU.UTF-8 ... ** Affects: language-selector (Ubuntu) Importance: Undecided Status: New -- Error localization https://bugs.launchpad.net/bugs/1724793 You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector 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 1431322] Re: UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: duplicity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1431322 Title: UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff' Status in duplicity package in Ubuntu: Confirmed Bug description: Guys, This error is ocurring when I try to execute a full backup to Windows Azure. duplicity 0.7.01 ($reldate) Args: /usr/bin/duplicity --archive-dir /backup/duplicity_cache/ --no-encryption --volsize 1000 --extra-clean --verbosity 8 --name s3 /backup/s3/ azure://aws-s3 Linux SV-BACKUP-AMAZON 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 x86_64 x86_64 /usr/bin/python 2.7.6 (default, Mar 22 2014, 22:59:56) [GCC 4.8.2] AsyncScheduler: running task synchronously (asynchronicity disabled) Writing duplicity-full.20150312T104506Z.vol5.difftar.gz Traceback (most recent call last): File "/usr/bin/duplicity", line 1497, in with_tempdir(main) File "/usr/bin/duplicity", line 1491, in with_tempdir fn() File "/usr/bin/duplicity", line 1340, in main do_backup(action) File "/usr/bin/duplicity", line 1466, in do_backup full_backup(col_stats) File "/usr/bin/duplicity", line 536, in full_backup globals.backend) File "/usr/bin/duplicity", line 418, in write_multivol (tdp, dest_filename, vol_num))) File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 145, in schedule_task return self.__run_synchronously(fn, params) File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 171, in __run_synchronously ret = fn(*params) File "/usr/bin/duplicity", line 417, in async_waiters.append(io_scheduler.schedule_task(lambda tdp, dest_filename, vol_num: put(tdp, dest_filename, vol_num), File "/usr/bin/duplicity", line 308, in put backend.put(tdp, dest_filename) File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 387, in inner_retry % (n, e.__class__.__name__, util.uexc(e))) File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 78, in uexc return ufn(str(e)) UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff' in position 76: ordinal not in range(128) # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 Codename: trusty # dpkg -l |grep duplicity ii duplicity0.7.01-0ubuntu0ppa1063~ubuntu14.04.1 amd64encrypted bandwidth-efficient backup # locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1431322/+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 1431322] Re: UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff'
Mine looks similar - ubuntu 10.04:
saving data fails with unknown error:
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1511, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 572, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 33:
ordinal not in range(128)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1431322
Title:
UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff'
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
Guys,
This error is ocurring when I try to execute a full backup to
Windows Azure.
duplicity 0.7.01 ($reldate)
Args: /usr/bin/duplicity --archive-dir /backup/duplicity_cache/
--no-encryption --volsize 1000 --extra-clean --verbosity 8 --name s3
/backup/s3/ azure://aws-s3
Linux SV-BACKUP-AMAZON 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39
UTC 2015 x86_64 x86_64
/usr/bin/python 2.7.6 (default, Mar 22 2014, 22:59:56)
[GCC 4.8.2]
AsyncScheduler: running task synchronously (asynchronicity disabled)
Writing duplicity-full.20150312T104506Z.vol5.difftar.gz
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1497, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1491, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1340, in main
do_backup(action)
File "/usr/bin/duplicity", line 1466, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 536, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 418, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
145, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
171, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 417, in
async_waiters.append(io_scheduler.schedule_task(lambda tdp,
dest_filename, vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 308, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 387, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 78, in uexc
return ufn(str(e))
UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff' in
position 76: ordinal not in range(128)
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
# dpkg -l |grep duplicity
ii duplicity0.7.01-0ubuntu0ppa1063~ubuntu14.04.1
amd64encrypted bandwidth-efficient backup
# locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1431322/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
Confirmed fixed with live ubuntu, working with gnome-shell 3.28.3-0ubuntu0.18.04.4 from bionic-proposed. Thanks guys, was a pesky bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+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 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xorg-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- hwe-18.04/1:7.7+19ubuntu8~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Package changed: xorg (Ubuntu Bionic) => xorg-hwe-18.04 (Ubuntu Bionic) ** Changed in: xorg-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series,
[Desktop-packages] [Bug 887331] Re: file-roller cannot open filetypes with derived mimetypes (e.g. epub and ods files)
Bug still exists in 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/887331 Title: file-roller cannot open filetypes with derived mimetypes (e.g. epub and ods files) Status in file-roller package in Ubuntu: Confirmed Bug description: Given three files A, B and C, where A is a zip file (a.zip), B is an ePub file (b.epub) and C is an ODF Spreadsheet file (c.ods) ... All files have "Open With > Archive Manager" as a menu option in nautilus. This is likely due to the shared-mime-info database having the ePub and ODS mimetypes as . File A will open successfully, while files B and C report "Could not open 'A'" / "Archive type not supported". However, renaming B and C so they have a .zip extension will cause the files to be opened correctly. This is likely due to file-roller checking the filetype to load by extension, not magic. This is indeed the case as giving a text file a .zip extension causes file-roller to report "An error occurred while loading the archive" (End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive.) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: file-roller 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CheckboxSubmission: 5434425585a31b50d9fa7c3153a37fe1 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 Date: Mon Nov 7 21:12:54 2011 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: file-roller UpgradeStatus: Upgraded to oneiric on 2011-09-24 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/887331/+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 1808535] [NEW] package nvidia-opencl-icd-340 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-340
Public bug reported: Ubuntu 18.10 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: nvidia-opencl-icd-340 (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 AptOrdering: libcuda1-340:amd64: Install nvidia-340:amd64: Install nvidia-opencl-icd-340:amd64: Install nvidia-settings:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Dec 14 15:11:58 2018 ErrorMessage: conflicting packages - not installing nvidia-opencl-icd-340 InstallationDate: Installed on 2018-12-03 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-opencl-icd-340 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-340 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1808535 Title: package nvidia-opencl-icd-340 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl- icd-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Ubuntu 18.10 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: nvidia-opencl-icd-340 (not installed) ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 AptOrdering: libcuda1-340:amd64: Install nvidia-340:amd64: Install nvidia-opencl-icd-340:amd64: Install nvidia-settings:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Dec 14 15:11:58 2018 ErrorMessage: conflicting packages - not installing nvidia-opencl-icd-340 InstallationDate: Installed on 2018-12-03 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-opencl-icd-340 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-340 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1808535/+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 1388169] Re: Keyboard Input Methods crashes on every startup
Now, I also found this bug for vscode when minimizing, so it's not a chrome related bug I guess. -- 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/1388169 Title: Keyboard Input Methods crashes on every startup Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Release:Lubuntu 14.10 Executable path: /usr/lib/ibus/ibus-ui-gtk3 Package: ibus 1.5.8-2ubuntu2 Apport version: 2.14.7-0ubuntu8 Keyboard Input Methods crashes on almost every start-up. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-05-04 (217 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Tags: utopic Uname: Linux 3.16.0-25-generic i686 UpgradeStatus: Upgraded to utopic on 2014-10-23 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1388169/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Thanks to craig-jackson if you want to check before compiling your kernel if you have the same problem that I had, you can check if the sound can work for a few seconds with the command below : sudo apt install git git clone https://github.com/VanVan/check_sound.git sudo ./check_sound/check_sound If you can hear a sound from your internal speaker it's good, if not, compiling a new kernel can still give you sound, depends on your laptop. When you compile a new kernel, do not forget do to a git pull inside the linux folder or you can remove and clone again the repository to have the latest commit (hda_codec.h correction): git clone https://github.com/VanVan/linux.git -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1388169] Re: Keyboard Input Methods crashes on every startup
I've just installed chrome on ubuntu, but I faced this issue. I can change url for first time, but after the first site is loaded it freezes, if a change the language back and forth, it starts working tho. Ubuntu version: Ubuntu 18.04.1 LTS Chrome version: Version 70.0.3538.110 (Official Build) (64-bit) -- 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/1388169 Title: Keyboard Input Methods crashes on every startup Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Release:Lubuntu 14.10 Executable path: /usr/lib/ibus/ibus-ui-gtk3 Package: ibus 1.5.8-2ubuntu2 Apport version: 2.14.7-0ubuntu8 Keyboard Input Methods crashes on almost every start-up. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-05-04 (217 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Tags: utopic Uname: Linux 3.16.0-25-generic i686 UpgradeStatus: Upgraded to utopic on 2014-10-23 (45 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1388169/+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 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-dummy-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-dummy- hwe-18.04/1:0.3.8-1build3~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic.
[Desktop-packages] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Changed in: xorg-server Status: Confirmed => Unknown -- 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/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: There's already an upstream bug report here: https://bugs.freedesktop.org/show_bug.cgi?id=99555 Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear: steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. X Error of failed request: 255 Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 1 (X_GLXRender) Serial number of failed request: 42 Current serial number in output stream: 936 I am trying to run what is effectively a traditional X Terminal, but as the hardware I am using has a 3D accelerated chipset it seems sensible to try to use it.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Jun 12 10:09:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2018-05-31 (11 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: AZW S I ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 00.12 dmi.board.asset.tag: Default string dmi.board.name: AB1 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr00.12:bd12/18/2017:svnAZW:pnSI:pvrDefaultstring:rvnIP3Tech:rnAB1:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: S I dmi.product.version: Default string dmi.sys.vendor: AZW version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+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 1776447]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/211. -- 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/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: There's already an upstream bug report here: https://bugs.freedesktop.org/show_bug.cgi?id=99555 Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear: steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. X Error of failed request: 255 Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 1 (X_GLXRender) Serial number of failed request: 42 Current serial number in output stream: 936 I am trying to run what is effectively a traditional X Terminal, but as the hardware I am using has a 3D accelerated chipset it seems sensible to try to use it.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Jun 12 10:09:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2018-05-31 (11 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: AZW S I ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 00.12 dmi.board.asset.tag: Default string dmi.board.name: AB1 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr00.12:bd12/18/2017:svnAZW:pnSI:pvrDefaultstring:rvnIP3Tech:rnAB1:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: S I dmi.product.version: Default string dmi.sys.vendor: AZW version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+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 1778088] Re: DjVu Files cannot be opened
Cross-reference to Debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=876710 As suggested there, removing the "djvulibre-desktop" package worked around the problem. ** Bug watch added: Debian Bug tracker #876710 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876710 -- 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/1778088 Title: DjVu Files cannot be opened Status in evince package in Ubuntu: Confirmed Bug description: When trying to open a .djvu document, evince shows an error: File type DjVu image (image/vnd.djvu) is not supported Apparently, upstream has removed the image/vnd.djvu mimetype in an effort to treat single-page .djvu files more like images (https://bugzilla.gnome.org/show_bug.cgi?id=754467). The file in question is however a multi-page, yet the mime-type is not the expected "image/vnd.djvu+multipage": $ file book.djvu book.djvu: DjVu multiple page document $ file --mime-type book.djvu book.djvu: image/vnd.djvu This happens on all bionic machines I have access to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1778088/+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 1808415] Re: i dont no
** Information type changed from Private Security to Public -- 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/1808415 Title: i dont no Status in xorg package in Ubuntu: New Bug description: plus de son en sortie et la clef bluethoot pas detecter ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: pata_acpi r8169 radeon pata_atiixp wmi .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Dec 13 21:27:17 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 6310] [1043:101c] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-05-23 (569 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK Computer Inc. K53BY ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a12e05bc-12f2-4433-9815-2d789360b75c ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53BY dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr210:bd05/12/2011:svnASUSTeKComputerInc.:pnK53BY:pvr1.0:rvnASUSTeKComputerInc.:rnK53BY:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53BY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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 13 21:22:15 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1808415/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The above worked for (k)ubuntu 18.10. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
For those following https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel, I had to do some extra things to get kernel compilation working. The workaround steps are described here: https://askubuntu.com/questions/1085411/unable-to-follow-kernel- buildyourownkernel/1099988. Substitute the kernel version relevant to you wherever you see "4.18.0"... -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1778088] Re: DjVu Files cannot be opened
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- 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/1778088 Title: DjVu Files cannot be opened Status in evince package in Ubuntu: Confirmed Bug description: When trying to open a .djvu document, evince shows an error: File type DjVu image (image/vnd.djvu) is not supported Apparently, upstream has removed the image/vnd.djvu mimetype in an effort to treat single-page .djvu files more like images (https://bugzilla.gnome.org/show_bug.cgi?id=754467). The file in question is however a multi-page, yet the mime-type is not the expected "image/vnd.djvu+multipage": $ file book.djvu book.djvu: DjVu multiple page document $ file --mime-type book.djvu book.djvu: image/vnd.djvu This happens on all bionic machines I have access to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1778088/+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
