[Desktop-packages] [Bug 1819816] Re: Gnome-shell-dbgsym is out of date
My system was indeed mis-configured. Thanks for helping, I apologize for the distraction. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: Invalid Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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 1819816] Re: Gnome-shell-dbgsym is out of date
bram@ubuntupc:/etc/apt/sources.list.d$ cat ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-proposed main restricted universe multiverse -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: Invalid Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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 1819816] Re: Gnome-shell-dbgsym is out of date
$ cat /etc/apt/sources.list # deb cdrom:[Ubuntu 18.04 LTS _Bionic Beaver_ - Release amd64 (20180426)]/ bionic main restricted # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://ca.archive.ubuntu.com/ubuntu/ bionic main restricted # deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic main restricted ## Major bug fix updates produced after the final release of the ## distribution. deb http://ca.archive.ubuntu.com/ubuntu/ bionic-updates main restricted # deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic-updates main restricted ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. deb http://ca.archive.ubuntu.com/ubuntu/ bionic universe # deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic universe deb http://ca.archive.ubuntu.com/ubuntu/ bionic-updates universe # deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic-updates universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb http://ca.archive.ubuntu.com/ubuntu/ bionic multiverse # deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic multiverse deb http://ca.archive.ubuntu.com/ubuntu/ bionic-updates multiverse # deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic-updates multiverse ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb http://ca.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse # deb-src http://ca.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse ## Uncomment the following two lines to add software from Canonical's ## 'partner' repository. ## This software is not part of Ubuntu, but is offered by Canonical and the ## respective vendors as a service to Ubuntu users. # deb http://archive.canonical.com/ubuntu bionic partner # deb-src http://archive.canonical.com/ubuntu bionic partner deb http://security.ubuntu.com/ubuntu bionic-security main restricted # deb-src http://security.ubuntu.com/ubuntu bionic-security main restricted deb http://security.ubuntu.com/ubuntu bionic-security universe # deb-src http://security.ubuntu.com/ubuntu bionic-security universe deb http://security.ubuntu.com/ubuntu bionic-security multiverse # deb-src http://security.ubuntu.com/ubuntu bionic-security multiverse -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: Invalid Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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 1819816] Re: Gnome-shell-dbgsym is out of date
It sounds like your system is somehow configured to get debug packages from proposed, but binary packages from updates. Please attach a copy of your /etc/apt/sources.list and /etc/apt/sources.list.d/* ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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 1819816] Re: Gnome-shell-dbgsym is out of date
Please try: sudo apt purge -f gnome-shell-dbgsym ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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 1188569] Re: Some keyboard shortcuts randomly stop working
unity-settings-daemon 15.04.1+19.04.20190209-0ubuntu2 built for Ubuntu-18.04 bionic works for me. Please, backport changes to the LTS version. I have faced a problem with non-working keyboard language switcher in unity desktop. It works till next screen lock. An irritating workaround is to set shortcut again in system settings → Keyboard → Shortcuts → Typing → Switch to next source. The trivial patch I have had to apply is removing gnome-settings-daemon- common dependency. --- unity-settings-daemon-15.04.1+19.04.20190209.orig/debian/control 2019-03-13 04:44:44.0 + +++ unity-settings-daemon-15.04.1+19.04.20190209/debian/control 2019-03-13 03:56:15.778916801 + @@ -58,7 +58,6 @@ accountsservice (>= 0.6.34), gsettings-desktop-schemas (>= 3.15.4), nautilus-data (>= 2.91.3-1), - gnome-settings-daemon-common (>= 3.16), gsettings-ubuntu-schemas (>= 0.0.7+17.10.20170922), Recommends: ibus (>= 1.5.0), pulseaudio, -- 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/1188569 Title: Some keyboard shortcuts randomly stop working Status in GNOME Shell: New Status in Unity: Confirmed Status in unity package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Hi, Certain shortcuts randomly stops working in my computer. They are Super+s (workspace switcher), Super+Up (switch to workspace above) and Super+Down (switch to workspace below). Other shortcuts work fine. A few notes that might help: 1- Reassigning shortcuts make them work again except for Super+s. 2- Rebooting make shortcuts work. 3- I have been using these shortcuts with many previous ubuntu versions and my preferences are old. 4- I am not sure of certain steps that produces the problem. The shortcuts sometimes stop working but once they stop, they do not work unless I reassign them or reboot. I am using Ubuntu 13.04. Thank you ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell] Date: Fri Jun 7 13:40:06 2013 InstallationDate: Installed on 2013-05-27 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1188569/+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 1819788] Re: Applications panel doesn't show snap interfaces
This bug was fixed in the package gnome-control-center - 1:3.32.0.1-1ubuntu3 --- gnome-control-center (1:3.32.0.1-1ubuntu3) disco; urgency=medium * debian/control: - Add libsnapd-glib-deb to build-depends -- Robert Ancell Wed, 13 Mar 2019 16:41:46 +1300 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1819788 Title: Applications panel doesn't show snap interfaces Status in gnome-control-center package in Ubuntu: Fix Released Bug description: In 3.32 a new applications panel was introduced. It shows portal permissions for flatpak apps. It is logical that snaps should show both their portal permissions if they are being used and interface controls (as gnome-software currently does). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1819788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1819816] Re: Gnome-shell-dbgsym is out of date
Same problem, after doing those steps. There is *no* old version of dbgsym installed. When I try to install it: $ dpkg --list | grep gnome-shell ii gnome-shell 3.28.3-0ubuntu0.18.04.4 amd64graphical shell for the GNOME desktop ii gnome-shell-common 3.28.3-0ubuntu0.18.04.4 all common files for the GNOME graphical shell ii gnome-shell-extension-appindicator 18.04.1 all App indicators for GNOME Shell ii gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 all Ubuntu Dock for GNOME Shell $ sudo apt-get install gnome-shell-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help resolve the situation: The following packages have unmet dependencies: gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. On Tue, Mar 12, 2019 at 9:30 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Also, it appears the problem is arising from your existing debug package > being a higher version than the binary package not yet installed. I > don't know how to reproduce this situation without intentionally > breaking the system... > > Please try this as a fix: > > sudo apt update > sudo apt install -f > sudo apt update > sudo apt full-upgrade > > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1819816 > > Title: > Gnome-shell-dbgsym is out of date > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+subscriptions > -- Owner/Director of Game Studio Abraham Stolk Inc. Vancouver BC, Canada b.st...@gmail.com -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1819816] Re: Gnome-shell-dbgsym is out of date
I do not have gnome-shell-dbgsym installed. On Tue, Mar 12, 2019 at 9:30 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Hmm, gnome-shell-dbgsym (3.28.3+git20190124-0ubuntu18.04.1) installs > just fine if you install it afterwards. > > AFAIK most packages avoid this problem by automatically uninstalling > debug symbol packages before updating the binary packages (which is > annoying in itself). It appears that didn't happen in your case. > > Possible workaround: Just uninstall gnome-shell-dbgsym, update the > system and then reinstall gnome-shell-dbgsym. > > ** Tags added: bionic > > ** Changed in: gnome-shell (Ubuntu) >Importance: Undecided => Low > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1819816 > > Title: > Gnome-shell-dbgsym is out of date > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+subscriptions > -- Owner/Director of Game Studio Abraham Stolk Inc. Vancouver BC, Canada b.st...@gmail.com -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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 1433300] Re: Ubuntu 15.04 Wallpaper is mis-aglined to unity-greeter grid.
I think it’s safe to say this is a “Won’t Fix” now. ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1433300 Title: Ubuntu 15.04 Wallpaper is mis-aglined to unity-greeter grid. Status in ubuntu-wallpapers package in Ubuntu: Won't Fix Bug description: If you choose the official Ubuntu 15.04 wallpaper as your desktop background, and then lock or log out your session to unity-greeter, you will notice that the area the folds meet is slightly off direction from the unity-greeter grid. I reported it to warn you before the final release that it was mis-aglined just like it was before 14.04 Stable when you fixed it then. I just reported it to make sure you awesome developers at Ubuntu doing ubuntu-wallpapers were warned so you have more time to do it in. Details: Tested on the following version: Description: Ubuntu 14.04.2 LTS Release: 14.04 (Using 15.04 wallpaper in place of 14.04's) ubuntu-wallpapers: Installed: 14.04.0.1-0ubuntu1 Candidate: 14.04.0.1-0ubuntu1 Version table: *** 14.04.0.1-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status Expected to happen: The wallpaper would be aglined to the dot on the grid. What happened instead: Mis-aglined to the dot on the grid (A little bit off the dot). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-wallpapers 14.04.0.1-0ubuntu1 [modified: usr/share/backgrounds/warty-final-ubuntu.png] ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic i686 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 CurrentDesktop: Unity Date: Tue Mar 17 20:08:28 2015 Dependencies: ubuntu-wallpapers-trusty 14.04.0.1-0ubuntu1 InstallationDate: Installed on 2015-03-11 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all SourcePackage: ubuntu-wallpapers UpgradeStatus: No upgrade log present (probably fresh install) There is a screenshot in the comments section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1433300/+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 1819816] Re: Gnome-shell-dbgsym is out of date
Also, it appears the problem is arising from your existing debug package being a higher version than the binary package not yet installed. I don't know how to reproduce this situation without intentionally breaking the system... Please try this as a fix: sudo apt update sudo apt install -f sudo apt update sudo apt full-upgrade ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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
So I switched to Linux Kernel 5 since RC-5 and I was switching to the latest version ever since a new one is released. It seems that the 5 branch has fixed the issue for good. I am on 5.0.1 and have no issue with output. *fingers crossed* However I do have an issue with the input. Cannot recognize my internal microphone. Not a big issue as I don't speak that much or I can use different devices for that communication but the mic is the last bit that is not working on that "damn" Asus Zenbook. -- 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: Fix Committed Status in linux package in Ubuntu: Fix Committed 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 1819816] Re: Gnome-shell-dbgsym is out of date
Hmm, gnome-shell-dbgsym (3.28.3+git20190124-0ubuntu18.04.1) installs just fine if you install it afterwards. AFAIK most packages avoid this problem by automatically uninstalling debug symbol packages before updating the binary packages (which is annoying in itself). It appears that didn't happen in your case. Possible workaround: Just uninstall gnome-shell-dbgsym, update the system and then reinstall gnome-shell-dbgsym. ** Tags added: bionic ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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 1819769] Re: The color of the Nautilus app icon (grey) differs from the color of the desktop icons (orange).
** Project changed: ubuntu-ux => hundredpapercuts ** No longer affects: nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1819769 Title: The color of the Nautilus app icon (grey) differs from the color of the desktop icons (orange). Status in One Hundred Papercuts: New Status in yaru-theme package in Ubuntu: New Bug description: Hello guys The color tone of the file folder icon differs from the color of the desktop icons. I really liked the update of the Yaru icon version on Ubuntu 19.04 Disk, but the color of the desktop files folder icon is different from the color of the sidebar file folder icon icon and the plank files folder icon, as can be seen in the attached image with VECTOR in bold. It would be good tone and refinement that these icons also had the same tonality. Thank you Edson Santos To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1819769/+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 1782422] Re: Desktop icons are way too big
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1782422 Title: Desktop icons are way too big Status in nautilus package in Ubuntu: Expired Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 The icons on the desktop are too big and even reducing the size at 50% through the nautilus window they do not become small enough. It would be useful to reduce the size even more. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'222' b'org.gnome.nautilus.window-state' b'geometry' b"'890x549+95+55'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-07-07 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: nautilus 1:3.26.3-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1782422/+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 1819816] Re: Gnome-shell-dbgsym is out of date
gnome-shell-dbgsym: Installed: (none) Candidate: 3.28.3+git20190124-0ubuntu18.04.1 Version table: 3.28.3+git20190124-0ubuntu18.04.1 500 500 http://ddebs.ubuntu.com bionic-proposed/main amd64 Packages 3.28.3-0ubuntu0.18.04.4 500 500 http://ddebs.ubuntu.com bionic-updates/main amd64 Packages 3.28.1-0ubuntu2 500 500 http://ddebs.ubuntu.com bionic/main amd64 Packages gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.4 Candidate: 3.28.3-0ubuntu0.18.04.4 Version table: *** 3.28.3-0ubuntu0.18.04.4 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: New Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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 1819816] [NEW] Gnome-shell-dbgsym is out of date
Public bug reported: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1819816 Title: Gnome-shell-dbgsym is out of date Status in gnome-shell package in Ubuntu: New Bug description: I am using bionic updates repository, and I can't install the debug symbols for gnome-shell. gnome-shell-dbgsym Is out of date gnome-shell-dbgsym : Depends: gnome-shell (= 3.28.3+git20190124-0ubuntu18.04.1) but 3.28.3-0ubuntu0.18.04.4 is to be installed E: Unable to correct problems, you have held broken packages. More info: https://stackoverflow.com/questions/55129053/how-to-install-debug-symbols-for-gnome-shell-package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819816/+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 1819744] Re: 19.04 Disco default wallpapers
There appears to be a mistake with the greyscale wallpaper, in the top right there is a square in the greyscale variant while the coloured variant has a diagonal line. It is only very faint but is noticeable when used as a wallpaper. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1819744 Title: 19.04 Disco default wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Attached will be the Disco default wallpapers. One in colour, one in black and white. Both 4096 x 2304. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1819744/+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 1818790] Re: [regression] Desktop zoom is missing the mouse pointer
** Changed in: gnome-shell Status: Unknown => New -- 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/1818790 Title: [regression] Desktop zoom is missing the mouse pointer Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454 --- Desktop zoom is missing the mouse pointer. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Wed Mar 6 15:12:04 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1818790/+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 1819769] Re: The color of the Nautilus app icon differs from the color of the desktop icons.
** Summary changed: - The color tone of the file folder icon differs from the color of the desktop icons. + The color of the Nautilus app icon differs from the color of the desktop icons. ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Low ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Summary changed: - The color of the Nautilus app icon differs from the color of the desktop icons. + The color of the Nautilus app icon (grey) differs from the color of the desktop icons (orange). ** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1819769 Title: The color of the Nautilus app icon (grey) differs from the color of the desktop icons (orange). Status in Ubuntu UX: New Status in nautilus package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: Hello guys The color tone of the file folder icon differs from the color of the desktop icons. I really liked the update of the Yaru icon version on Ubuntu 19.04 Disk, but the color of the desktop files folder icon is different from the color of the sidebar file folder icon icon and the plank files folder icon, as can be seen in the attached image with VECTOR in bold. It would be good tone and refinement that these icons also had the same tonality. Thank you Edson Santos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1819769/+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 1772811] Re: [SRU] different behaviors for switch display mode between xenial and bionic
** Summary changed: - different behaviors for switch display mode between xenial and bionic + [SRU] different behaviors for switch display mode between xenial and bionic ** Description changed: + * Impact + + Need this SUR so that use OEM laptop hotkey won't be uesless. + + * Test case + + 1. Install the new mutter and gnome-shell on the target machine. + 2. connect an external display. + 3. Press either the monitor switch HOT key (each note book have different one), or the generic hot key (Meta-P) + 4. Make sure the display mode is switch to next mode, not the first mode. + + * Regression potential + + very low, because it's merged upstream. + + -- + When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 ** Description changed: * Impact Need this SUR so that use OEM laptop hotkey won't be uesless. * Test case 1. Install the new mutter and gnome-shell on the target machine. 2. connect an external display. 3. Press either the monitor switch HOT key (each note book have different one), or the generic hot key (Meta-P) 4. Make sure the display mode is switch to next mode, not the first mode. * Regression potential - very low, because it's merged upstream. + very low, because it's merged upstream and also tested in oem platforms. -- When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 -- 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/1772811 Title: [SRU] different behaviors for switch display mode between xenial and bionic Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: New Status in mutter source package in Bionic: New Status in gnome-shell source package in Disco: Fix Released Status in mutter source package in Disco: Fix Released Bug description: * Impact Need this SUR so that use OEM laptop hotkey won't be uesless. * Test case 1. Install the new mutter and gnome-shell on the target machine. 2. connect an external display. 3. Press either the monitor switch HOT key (each note book have different one), or the generic hot key (Meta-P) 4. Make sure the display mode is switch to next mode, not the first mode. * Regression potential very low, because it's merged upstream and also tested in oem platforms. -- When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772811/+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 1818790] Re: [regression] Desktop zoom is missing the mouse pointer
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1020 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 Importance: Unknown Status: Unknown -- 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/1818790 Title: [regression] Desktop zoom is missing the mouse pointer Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454 --- Desktop zoom is missing the mouse pointer. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Wed Mar 6 15:12:04 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1818790/+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 1742714] Re: MIR: mesa-vulkan-drivers FFE: install by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1742714 Title: MIR: mesa-vulkan-drivers FFE: install by default Status in mesa package in Ubuntu: New Status in vulkan-loader package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: New Bug description: MIR mesa-vulkan-drivers: - is from mesa, which is already in main - maintained just as mesa is, by ubuntu-x-swat MIR vulkan-loader: https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711 FFE: - new packages in the default install (mesa-vulkan-drivers, libvulkan1) -> no chance of regressing anything -- A Vulkan related bug was filed at https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in a related note, having mesa-vulkan-drivers moved from Universe to Main and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten mature and since the OpenGL drivers are installed, it will very complimentary. Having this available will aid game developers and users who load up a Vulkan application and get errors. They may not know to enable Universe in their Software Manager and to manually install mesa- vulkan-drivers for their video card. They may just load up that Vulkan application, find out it doesn't work, and then give up on it. We cannot have that for future adoption of the API. Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV are implementing experimental support for Vulkan. For Ubuntu being a leader for the desktop and a base for GNU/Linux gaming, shouldn't it be painless for Ubuntu 18.04? Especially since it is a long term release for 5 years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1742714/+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 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
You can download the .deb files containing the proposed fix for 18.04 from here: https://launchpad.net/ubuntu/+source/gnome- shell/3.28.3+git20190124-0ubuntu18.04.1/+build/16422548 -- 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/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I
[Desktop-packages] [Bug 1742714] Re: MIR: mesa-vulkan-drivers FFE: install by default
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1742714 Title: MIR: mesa-vulkan-drivers FFE: install by default Status in mesa package in Ubuntu: New Status in vulkan-loader package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: New Bug description: MIR mesa-vulkan-drivers: - is from mesa, which is already in main - maintained just as mesa is, by ubuntu-x-swat MIR vulkan-loader: https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711 FFE: - new packages in the default install (mesa-vulkan-drivers, libvulkan1) -> no chance of regressing anything -- A Vulkan related bug was filed at https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in a related note, having mesa-vulkan-drivers moved from Universe to Main and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten mature and since the OpenGL drivers are installed, it will very complimentary. Having this available will aid game developers and users who load up a Vulkan application and get errors. They may not know to enable Universe in their Software Manager and to manually install mesa- vulkan-drivers for their video card. They may just load up that Vulkan application, find out it doesn't work, and then give up on it. We cannot have that for future adoption of the API. Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV are implementing experimental support for Vulkan. For Ubuntu being a leader for the desktop and a base for GNU/Linux gaming, shouldn't it be painless for Ubuntu 18.04? Especially since it is a long term release for 5 years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1742714/+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 1613570] Re: Suru save icon looks too much like download icon
The Suru icon theme is from the 'ubuntu-themes' source package. ** Package changed: yaru-theme (Ubuntu) => ubuntu-themes (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1613570 Title: Suru save icon looks too much like download icon Status in ubuntu-themes package in Ubuntu: New Bug description: Google for "download icon" and you'll see that an arrow down to a horizontal line is generally accepted as the icon for "download". See: https://www.google.be/search?q=download+icon In Suru icon theme, this icon however is the "save" icon. This has already created some confusion in Ubuntu Touch apps: https://bugs.launchpad.net/talaan-app/+bug/1612931 What I propose is that the "save" icon is changed into something that resembles the universal "save" icon more (a floppy). An example: https://d13yacurqjgara.cloudfront.net/users/71134/screenshots/1020838 /save-icon.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1613570/+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 1720901] Re: VLC under Wayland causes system freezes in fullscreen mode
** No longer affects: gnome-shell (Ubuntu) -- 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/1720901 Title: VLC under Wayland causes system freezes in fullscreen mode Status in VLC media player: New Status in vlc package in Ubuntu: Fix Released Status in vlc package in Debian: Fix Released Bug description: Ubuntu version: 17.10 (most recent updates as of October 3rd) vlc version: 2.2.6-6 Whan I expect to happen: When playing a video in vlc and switching to fullscreen mode everything should work fine. Also when changing to a different position of a movie in fullscreen I expect the player to just switch to that position. What actually happens: It seems to depend a little on the file type of the video, mostly I get problems when going to fullscreen mode and then switching to a different position with the playback position bar. With some videos it was even enough to just open the fullscreen mode. The video freezes just displaying a frame while the audio keeps playing. The computer does not react any more to mouse or keyboard input, I have to perform a hard reboot. This problem only appears under the Wayland session, in the Xorg session everything works fine as expected. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-30 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: vlc 2.2.6-6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1720901/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
** Changed in: pulseaudio (Ubuntu Disco) Status: Invalid => New -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Status in gnome-control-center source package in Disco: Confirmed Status in pulseaudio source package in Disco: New Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO 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:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
I am also getting this error in my Ubuntu 18.04 logs during boot. I tried disabling it under Startup Applications: Spice vdagent /usr/bin/spice-vdagent Agent for Spice guests ... yet I still get the error. I tested the service path by temporarily renaming /usr/bin/spice-vdagent and rebooting, which stopped the error occurring in the log. I don't need the Spice vdagent service, so is there an elegant way to prevent the service from even trying to run? The easiest solution would be to uninstall spice-vdagent, but that doesn't seem to be possible, since it would also remove ubuntu-desktop, which would be unfortunate, to say the least. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Hello, $ journalctl -b [...] oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: spice-vdagent 0.17.0-1ubuntu2 Uname: Linux 4.19.0-gnu x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 14:34:00 2018 InstallationDate: Installed on 2017-10-13 (378 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+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 1818777] Re: Lubuntu 19.04 qa-test; suspend then wake & keyboard & mouse movement, but not mouse-buttons
** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid -- 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/1818777 Title: Lubuntu 19.04 qa-test; suspend then wake & keyboard & mouse movement, but not mouse-buttons Status in xorg-server package in Ubuntu: Invalid Bug description: Update (see comment #5) another QA-Test on same dc7700 This time i firstly confirmed issue was still there - YEP suspend & no mouse buttons. Then i turned on another machine sharing KVM switch (more power is my theory for this) and the issue disappeared. It was tried again a few times with other machine on, and no issues with mouse buttons on wake.. I'm going to change this to INCOMPLETE as I'm suspicious it's hardware related; lack of power from my old boxes (old psu's) to my KVM switch I'm marking this as INCOMPLETE - if I change my mind (another qa-test) I can always put it back to NEW --- Notes: The box I tested this on has shared keyboard/mouse/video I tried to re-produce on two other boxes (same thumb-drive so same daily 19.04 image) I always check-media on first box tested after media is written (x201 I think today) Also note: lynorian (lubuntu-devel) also said guiverc: I think I filed something about this in a vm a few weeks ago What I found doesn't apply in my opinion. I consider this issue [really] MINOR or wishlist at most; in fact I still wonder if it's a hardware issue related to my KVM switch (not getting enough power or something like that) Lubuntu 19.04 QA-TEST on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) // info from QA-TEST comments .. firefox paused; suspended machine (using menu) ISSUE: on wake (used keyboard to wake system) the mouse couldn't click on anything, but keyboard functions worked perfectly (ctrl+alt+t to open term etc). i'll reboot & reload, re-try reboot & retried.. same issue (on reboot; after reboot I ctrl+alt+T to open term & ran `htop` so I had some changing data on screen to confirm more than just mouse was moving on screen, then suspended.. on wake [2nd boot], notification boxes appeared... mouse moves correctly, keyboard keys appear all good (can switch to tty & back) but no mouse buttons work ran `xev` & is see all keyboard, and mouse movements, but no buttons appear in window on pressing (unless I accidentally cause mouse to move) Of note: I've experienced this behavior BEFORE & not reported, as the reboot & re-try has always worked flawlessly. Rebooted again & re-tested it a third time (menu->suspend, used mouse to click yes [normally I hit enter]) & counted to 20 Woke machine (using power-button instead of keyboard) & keyboard perfect, mouse movement perfect, alas no mouse-button function on screen or menu, nor appearing in `xev` .. mouse wheel is recognized in `xev`. // this is typed into another box - no mouse function on ubuntu-bug machine since suspend ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu9 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.402 CompositorRunning: None CurrentDesktop: LXQt Date: Wed Mar 6 04:22:12 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1794033]
(In reply to Yoshinori Gento from comment #18) > I saw this once. This occurred in our product. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Confirmed Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1794033]
Yoshinori: Mesa i965 team is seeking a way to reproduce this bug, so we can analyze and fix it. How often does this occur in your product? If it is reproducible, then perhaps we can use an apitrace to investigate the root cause. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Confirmed Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1794033]
I saw this once. [Environment] CPU: SkyLake(core i5 6500TE) Distribution: debian(customised) Kernel: 4.14.98 Mesa: 18.3.3 libdrm: 2.4.89 Message from stdout of drawing module was i965: Failed to submit batchbuffer: Bad address and back-trace were following : : #5 0x7f4496240b35 in exit () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7f44864d1a5d in submit_batch (out_fence_fd=0x0, in_fence_fd=, brw=0x47ee030) at intel_batchbuffer.c:838 #7 _intel_batchbuffer_flush_fence (line=, file=, out_fence_fd=0x0, in_fence_fd=, brw=0x47ee030) at intel_batchbuffer.c:891 #8 _intel_batchbuffer_flush_fence (brw=0x47ee030, in_fence_fd=, out_fence_fd=0x0, file=, line=) at intel_batchbuffer.c:852 #9 0x7f44864a558a in brw_draw_single_prim (stream=, xfb_obj=0x0, prim_id=0, prim=0x79aa77d0, ctx=0x47ee030, indirect=) at brw_draw.c:898 #10 brw_draw_prims (ctx=0x47ee030, prims=, nr_prims=1, ib=, index_bounds_valid=, min_index=0, max_index=3, gl_xfb_obj=0x0, stream=0, indirect=0x0) at brw_draw.c:1107 #11 0x7f448608063c in _mesa_draw_arrays (drawID=0, baseInstance=0, numInstances=1, count=4, start=0, mode=6, ctx=0x47ee030) at main/draw.c:408 #12 _mesa_draw_arrays (ctx=0x47ee030, mode=6, start=0, count=4, numInstances=1, baseInstance=0, drawID=0) at main/draw.c:385 #13 0x7f4486081344 in _mesa_exec_DrawArrays (mode=6, start=0, count=4) at main/draw.c:565 : : -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Confirmed Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1819795] Re: Launcher & panel are solid so..
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Triaged ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Disco) Importance: Medium Status: Triaged -- 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/1819795 Title: Launcher & panel are solid so.. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Disco: Triaged Bug description: See this - sudo glib-compile-schemas /usr/share/glib-2.0/schemas [sudo] password for doug: override for key “transparency-mode” in schema “org.gnome.shell.extensions.dash-to-dock” in override file “/usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override” is not in the list of valid choices; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 19:50:54 2019 InstallationDate: Installed on 2019-03-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1819795/+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 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Apologies for my previous message. Somehow I missed that a proposed fix was available for testing. I'm having trouble figuring out how to download the proposed fix, but I'm sure I can figure it out with time and research. It's been years since any variant of Linux has been my primary personal OS, so I'm still in the early stages of re- familiarizing myself with everything. By the way, since I forgot to include it before: uname -a Linux Ubuntu-Desktop 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux gnome-shell --version GNOME Shell 3.28.3 -- 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/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5
[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Is there any fix or workaround for this bug? I installed a brand new copy of Ubuntu 18.04 on a brand new 512 GB SSD three days ago on Saturday evening (2019-03-09). I installed online updates during installation. It is now Tuesday evening (2019-03-12). The computer has been locked for most of the time since installation. In my /var/log directory, I have two enormous files: syslog (188.2 GB) syslog.1 (264.5 GB) And one smaller compressed older file: syslog.2.gz (313.6 MB) (I can confirm the issue I am experiencing is the error related to "osdWindow.js:207" on 18.04.) This needs a fix ASAP! I can't have my desktop filling up its storage with hundreds of gigs of errors every day! (~188 + ~264= ~452 GB in two or three days) I've attached the output of ls -l /var/log for proof since these are some of the largest hard numbers I've seen mentioned in this thread. ** Attachment added: "Output of: ls -l /var/log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+attachment/5245730/+files/filesizes.txt -- 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/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2
[Desktop-packages] [Bug 1613570] Re: Suru save icon looks too much like download icon
** Project changed: ubuntu-themes => yaru-theme (Ubuntu) ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1613570 Title: Suru save icon looks too much like download icon Status in yaru-theme package in Ubuntu: New Bug description: Google for "download icon" and you'll see that an arrow down to a horizontal line is generally accepted as the icon for "download". See: https://www.google.be/search?q=download+icon In Suru icon theme, this icon however is the "save" icon. This has already created some confusion in Ubuntu Touch apps: https://bugs.launchpad.net/talaan-app/+bug/1612931 What I propose is that the "save" icon is changed into something that resembles the universal "save" icon more (a floppy). An example: https://d13yacurqjgara.cloudfront.net/users/71134/screenshots/1020838 /save-icon.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1613570/+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 1613570] [NEW] Suru save icon looks too much like download icon
You have been subscribed to a public bug: Google for "download icon" and you'll see that an arrow down to a horizontal line is generally accepted as the icon for "download". See: https://www.google.be/search?q=download+icon In Suru icon theme, this icon however is the "save" icon. This has already created some confusion in Ubuntu Touch apps: https://bugs.launchpad.net/talaan-app/+bug/1612931 What I propose is that the "save" icon is changed into something that resembles the universal "save" icon more (a floppy). An example: https://d13yacurqjgara.cloudfront.net/users/71134/screenshots/1020838 /save-icon.png ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- Suru save icon looks too much like download icon https://bugs.launchpad.net/bugs/1613570 You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme 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 1819795] Re: Launcher & panel are solid so..
A g-s update made panel solid so at least on same page. The override file needs editing.. -- 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/1819795 Title: Launcher & panel are solid so.. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: See this - sudo glib-compile-schemas /usr/share/glib-2.0/schemas [sudo] password for doug: override for key “transparency-mode” in schema “org.gnome.shell.extensions.dash-to-dock” in override file “/usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override” is not in the list of valid choices; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 19:50:54 2019 InstallationDate: Installed on 2019-03-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1819795/+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 1819795] [NEW] Launcher & panel are solid so..
Public bug reported: See this - sudo glib-compile-schemas /usr/share/glib-2.0/schemas [sudo] password for doug: override for key “transparency-mode” in schema “org.gnome.shell.extensions.dash-to-dock” in override file “/usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override” is not in the list of valid choices; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 19:50:54 2019 InstallationDate: Installed on 2019-03-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Summary changed: - Launcher is solid color, panel is transparent + Launcher is solid color, panel is translucent ** Summary changed: - Launcher is solid color, panel is translucent + Launcher & panel are solid so.. -- 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/1819795 Title: Launcher & panel are solid so.. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: See this - sudo glib-compile-schemas /usr/share/glib-2.0/schemas [sudo] password for doug: override for key “transparency-mode” in schema “org.gnome.shell.extensions.dash-to-dock” in override file “/usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override” is not in the list of valid choices; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 19:50:54 2019 InstallationDate: Installed on 2019-03-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1819795/+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 1819757] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1819757 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() Status in Nautilus: New Status in nautilus package in Ubuntu: Confirmed Bug description: Crash while display content trash ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 15:55:24 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'208' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2019-02-10 (30 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_UY:es LANG=es_UY.UTF-8 SegvAnalysis: Segfault happened at: 0x56397cd040d9 : mov(%rbx),%rdi PC (0x56397cd040d9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_view_get_selection () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1819757/+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 1637988] Re: Enable the nfs backend
Updating the bug for cosmic/bionics SRUs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1637988 Title: Enable the nfs backend Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact The gio/nautilus nfs:// locations handling is missing * Test case Try to connect to/browse a nfs server from nautilus by using a nfs:// location * Regression potential It's a new backend being enabled, it shouldn't have an impact on the existing ones Note that the backend relies on libnfs which got promoted in disco and would need to be promoted in cosmic/bionic as well then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988/+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 1730451] Re: MemoryError while verifying backup
I received a pretty similar error and thought I'd share my workaround. It may be OT but people are bound to come across this bug when they google. The process would look like the backup was working (and for < 200MB and a small number of files it did) - but larger folders would do up to 4 MemoryErrors before they would time out. I received the error with the main version (I believe it was 0.7.12) as well as with a more recent version (0.7.18.2). My workaround was that I would MOUNT the remote folder (with sshfs) before executing my backup against the mounted folder. The commands remained otherwise unchanged. I've since done a full 100GB backup with > 400K files successfully. Former statement: duplicity full --encrypt-key="XXX" /source/files scp://a...@server.provider.com/files Working statement: duplicity full --encrypt-key="XXX" /source/files file:///mnt/destination/files Curious indeed. Hope this helps anyone. -- 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/1730451 Title: MemoryError while verifying backup Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Released Bug description: While trying to verify a backup (launched from deja-dup), I receive the following error. My system currently shows 11G of RAM available plus 23G of swap. Possibly related to #1720159? Traceback (most recent call last): File "/usr/bin/duplicity", line 1546, in with_tempdir(main) File "/usr/bin/duplicity", line 1540, in with_tempdir fn() File "/usr/bin/duplicity", line 1391, in main do_backup(action) File "/usr/bin/duplicity", line 1468, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 731, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 763, in get_fileobj_iter manifest = backup_set.get_manifest() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, in get_manifest return self.get_local_manifest() File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, in get_local_manifest return manifest.Manifest().from_string(manifest_buffer) File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in from_string for match in vi_iterator: MemoryError ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: duplicity 0.7.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 6 10:50:12 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-03 (1190 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: duplicity UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1730451/+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 1814964] Re: No audio when logging in as second user. Only dummy audio device seen
thats actually really useful information. the Arch link in particular. think i am happy to have my family members able to change volume etc, but not sure how to set up a systemd service. think i will just log everyone out when the bug happens, at least starting a new session gets the sound working again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1814964 Title: No audio when logging in as second user. Only dummy audio device seen Status in pulseaudio package in Ubuntu: Triaged Bug description: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814964/+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 1637988] Re: Enable the nfs backend
** Summary changed: - gvfsd-nfs not present in gvfs-backends, why? + Enable the nfs backend ** Description changed: - We're at the end of 2016 and it's still impossible to browse nfs shares - through nautilus, even though this is supported since version 1.23 of - gvfs. What's keeping gvfsd-nfs out of the gvfs-backends package? + * Impact + The gio/nautilus nfs:// locations handling is missing + + * Test case + Try to connect to/browse a nfs server from nautilus by using a nfs:// location + + * Regression potential + It's a new backend being enabled, it shouldn't have an impact on the existing ones + + Note that the backend relies on libnfs which got promoted in disco and + would need to be promoted in cosmic/bionic as well then -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1637988 Title: Enable the nfs backend Status in gvfs package in Ubuntu: Fix Released Bug description: * Impact The gio/nautilus nfs:// locations handling is missing * Test case Try to connect to/browse a nfs server from nautilus by using a nfs:// location * Regression potential It's a new backend being enabled, it shouldn't have an impact on the existing ones Note that the backend relies on libnfs which got promoted in disco and would need to be promoted in cosmic/bionic as well then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988/+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 1746598] Re: [MIR] libnfs
I'm removing the lines for other series and using bug #1637988 for the SRU instead ** No longer affects: libnfs (Ubuntu Bionic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnfs in Ubuntu. https://bugs.launchpad.net/bugs/1746598 Title: [MIR] libnfs Status in libnfs package in Ubuntu: Fix Released Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year ago, but we can't enable it in Ubuntu until libnfs is promoted to main. The Ubuntu bug for this feature to be enabled in gvfs is LP: #1637988 qemu-block-extra could also enable libnfs support. Security No known CVEs. https://security-tracker.debian.org/tracker/source-package/libnfs https://launchpad.net/ubuntu/+source/libnfs/+cve Quality assurance = - Desktop Packages team is subscribed. - dh_auto_test runs but the tests shipped by upstream cant'b be run at build time since they modify the system. - Autopkgtests are added in 3.0.0-1, running upstream's test suite which includes running tests with valgrind, too. https://bugs.launchpad.net/ubuntu/+source/libnfs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libnfs https://github.com/sahlberg/libnfs/issues https://autopkgtest.ubuntu.com/packages/libn/libnfs (failing, never passed: see https://bugs.debian.org/921578 ) https://ci.debian.net/packages/libn/libnfs/ (tests aren't run in Debian because they request machine isolation which isn't implemented there yet) Dependencies No universe binary dependencies Standards compliance 3.9.8, debhelper compat 9, dh7 simple rules Maintenance === Actively maintained: https://github.com/sahlberg/libnfs Not team maintained in Debian. https://tracker.debian.org/pkg/libnfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598/+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 1819788] Re: Applications panel doesn't show snap interfaces
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed -- 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/1819788 Title: Applications panel doesn't show snap interfaces Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: In 3.32 a new applications panel was introduced. It shows portal permissions for flatpak apps. It is logical that snaps should show both their portal permissions if they are being used and interface controls (as gnome-software currently does). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1819788/+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 1747646] Re: Authentication error with google drive
I have the same error while recovering a ~ 20 GB backup from Google Drive. While recovering the encrypted .gpg files from the mounted Google Drive in Ubuntu's File Explorer directly to my disk i noticed that the connection hanged each 5 minutes at the same time i was trying to recover the data through Deja Dup Recovery function. The recovery through Deja Dup failed with the "Invalid Credentials" error, and the File Transfer through the file explorer raised an: "Error while copying *.gpg: Authentication required: Unauthorized" So this fact support @mterry & cody35367's hypothesis of some kind of token expiration and renewal of the online accounts module. Taking this is fact makes me wonder if maybe only 5 retries is too low? Maybe rising the timeout time to 30 sec-1 minute could be the solution meanwhile the token negotiation is slow. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1747646 Title: Authentication error with google drive Status in Déjà Dup: Confirmed Status in Duplicity: Confirmed Status in deja-dup package in Ubuntu: Triaged Bug description: Hi, I'm having an issue using deja-dup to back up my laptop to my google drive. When backing only a small folder (eg: ~/Documents) every thing works fine. However when trying to backup my whole home folder (/home/myusername) I get an "Invalid credentials" error after 5-10 min. The back up seems to start normally and my destination folder starts filling with "duplicity-full...difftar.gz" files, but eventually I get the Invalid Credentials error. lsb_release -d Fedora release 27 (Twenty Seven) rpm -q deja-dup duplicity deja-dup-37.1-1.fc27.x86_64 duplicity-0.7.16-1.fc27.x86_64 deja-dup.log attached. I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1747646/+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 1819788] [NEW] Applications panel doesn't show snap interfaces
Public bug reported: In 3.32 a new applications panel was introduced. It shows portal permissions for flatpak apps. It is logical that snaps should show both their portal permissions if they are being used and interface controls (as gnome-software currently does). ** Affects: gnome-control-center (Ubuntu) Importance: High Assignee: Robert Ancell (robert-ancell) Status: Triaged ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1819788 Title: Applications panel doesn't show snap interfaces Status in gnome-control-center package in Ubuntu: Triaged Bug description: In 3.32 a new applications panel was introduced. It shows portal permissions for flatpak apps. It is logical that snaps should show both their portal permissions if they are being used and interface controls (as gnome-software currently does). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1819788/+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 1817223] Re: [disco-proposed] The list of applications in Ubuntu Software is empty
Closing as wontfix for disco, we decided to stay on 3.30, it's too much work and not enough testing now to land the new version this cycle (see bug #1819779) ** Changed in: gnome-software (Ubuntu Disco) Status: Triaged => Won't Fix ** Changed in: libxmlb (Ubuntu Disco) Status: Triaged => Won't Fix -- 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/1817223 Title: [disco-proposed] The list of applications in Ubuntu Software is empty Status in gnome-software package in Ubuntu: Triaged Status in libxmlb package in Ubuntu: Triaged Status in gnome-software source package in Disco: Won't Fix Status in libxmlb source package in Disco: Won't Fix Bug description: Hi The COMPLETE LIST of applications in Ubuntu Software is not showing up See attached image Thank you ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.31.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 19:11:23 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-02-11 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.31.2-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1817223/+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 1819779] Re: Stick to the 3.30 serie for Disco
** Description changed: - The new serie/version is having stability issues (see bug #1814997 for example, which means we got no testing of the refactoring at this point) and we don't have the resources to deal with the fallout. + The new serie/version is having stability issues (see bug #1817223 for example, which means we got no testing of the refactoring at this point) and we don't have the resources to deal with the fallout. There are also no change in the NEWS that we consider essential to get this cycle (backporting the new icon/appmenu change might be worth doing though) -- 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/1819779 Title: Stick to the 3.30 serie for Disco Status in gnome-software package in Ubuntu: Triaged Bug description: The new serie/version is having stability issues (see bug #1817223 for example, which means we got no testing of the refactoring at this point) and we don't have the resources to deal with the fallout. There are also no change in the NEWS that we consider essential to get this cycle (backporting the new icon/appmenu change might be worth doing though) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1819779/+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 1819779] [NEW] Stick to the 3.30 serie for Disco
Public bug reported: The new serie/version is having stability issues (see bug #1814997 for example, which means we got no testing of the refactoring at this point) and we don't have the resources to deal with the fallout. There are also no change in the NEWS that we consider essential to get this cycle (backporting the new icon/appmenu change might be worth doing though) ** Affects: gnome-software (Ubuntu) Importance: High Status: Triaged ** Tags: upgrade-software-version version-blocked ** Changed in: gnome-software (Ubuntu) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu) Status: New => Triaged ** Tags added: upgrade-software-version version-blocked -- 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/1819779 Title: Stick to the 3.30 serie for Disco Status in gnome-software package in Ubuntu: Triaged Bug description: The new serie/version is having stability issues (see bug #1814997 for example, which means we got no testing of the refactoring at this point) and we don't have the resources to deal with the fallout. There are also no change in the NEWS that we consider essential to get this cycle (backporting the new icon/appmenu change might be worth doing though) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1819779/+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 1818766] Re: Update to 1.47
** Changed in: snapd-glib (Ubuntu Cosmic) Status: Fix Committed => New ** Changed in: snapd-glib (Ubuntu Bionic) Status: Fix Committed => New ** Changed in: snapd-glib (Ubuntu Xenial) Status: Fix Committed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: New Status in snapd-glib source package in Bionic: New Status in snapd-glib source package in Cosmic: New Status in snapd-glib source package in Disco: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+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 1818595] Re: Update to 1.46
This is superseded by the 1.47 release (#1818766). That release is the same as this one but fixed compilation on older releases. ** Changed in: snapd-glib (Ubuntu Cosmic) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818595 Title: Update to 1.46 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Cosmic: Won't Fix Status in snapd-glib source package in Disco: Fix Released Bug description: https://wiki.ubuntu.com/SnapdGlibUpdates Overview of changes in snapd-glib 1.46 * New API: - snapd_channel_get_released_at - SNAPD_ERROR_DNS_FAILURE * Fix tests breaking due to undefined order of results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818595/+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 1818879] Re: pull cirrus.ko into main kernel package
This bug was fixed in the package xserver-xorg-video-vesa - 1:2.4.0-2 --- xserver-xorg-video-vesa (1:2.4.0-2) unstable; urgency=medium * Cherry-pick a commit to fix default bpp selection. (LP: #1818879) -- Timo Aaltonen Fri, 08 Mar 2019 10:46:08 +0200 ** Changed in: xserver-xorg-video-vesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vesa in Ubuntu. https://bugs.launchpad.net/bugs/1818879 Title: pull cirrus.ko into main kernel package Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-vesa package in Ubuntu: Fix Released Bug description: In disco, xorg stopped shipping a cirrus module/driver, instead relying on the kernel one. But the kernel one is in the linux-modules- extra--generic package, which is not installed by default in vms. That breaks some assumptions: uvtool, for example, doesn't specify a video device when creating a vm, and the default in libvirt in such cases is to use cirrus. As a conseguence, disco VMs created by tools that do not specify a default video device won't have the cirrus.ko module, and X won't start there. It's a bit more complicated, however, because X just tries other fallbacks, but they also don't work. In particular, vesa doesn't work: [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted value (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/) We can change uvtool and specify a video device instead of leaving it blank (see bug #1818877), but there might be other tools out there spawning guests without telling them which video device to use, and they would also fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818879/+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 1725955] Re: "Printer added" notification
Could those having the issue add their journalctl log? -- 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/1725955 Title: "Printer added" notification Status in GNOME Settings Daemon: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: I've recently installed Ubuntu 17.10 (Gnome shell). After a while I saw an OSD notification with the message "printer added", and thought that must be because of the new driverless printers feature in the kernel. I have a brother printer in the network, and I tested it and it worked. The thing is that the message repeats itself, approximately every two minutes, and it's really distracting. I saw a question about this on AskUbuntu (https://askubuntu.com/questions/918462/ubuntu-17-04 -printer-added-notifications-under-gnome), and a solution, but it seemed like no one had filed a bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1725955/+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 1818922] Re: [disco-proposed] User photo on login screen is huge (not shrunken)
The issue should be fixed in https://bugs.launchpad.net/ubuntu/+source /gnome-shell/3.32.0-1ubuntu1 ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1818922 Title: [disco-proposed] User photo on login screen is huge (not shrunken) Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1024 --- Hello guys I do not know what predisposition will be given to the login screen, but at the moment it is reassembled the images and needing refinement, both in the initial screen and in the unlocking of the screen. The image is gigantic. See attachment *** Olá Pessoal Não sei qual predisposição que será dada a tela de login, mas no momento a mesma está remontado as imagens e precisando de refinamento, tanto na tela inicial quanto no desbloqueio da tela. A imagem está gigantesca Vide anexo Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818922/+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 1818766] Re: Update to 1.47
** Description changed: - https://wiki.ubuntu.com/SnapdGlibUpdates + [Impact] + A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates - Overview of changes in snapd-glib 1.47 + [Test Case] + The reverse depends of snapd-glib should continue to function, this is currently: + - gnome-software + - gnome-initial-setup + - pulseaudio - * Remove generated MOC file from tarball + [Regression Potential] + Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. ** Changed in: snapd-glib (Ubuntu Cosmic) Status: Incomplete => Fix Committed ** Changed in: snapd-glib (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Changed in: snapd-glib (Ubuntu Xenial) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: New Status in snapd-glib source package in Bionic: New Status in snapd-glib source package in Cosmic: New Status in snapd-glib source package in Disco: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+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 1819757] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
** Changed in: nautilus (Ubuntu) Importance: Medium => High ** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #862 https://gitlab.gnome.org/GNOME/nautilus/issues/862 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/862 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1819757 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: Crash while display content trash ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 15:55:24 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'208' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2019-02-10 (30 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_UY:es LANG=es_UY.UTF-8 SegvAnalysis: Segfault happened at: 0x56397cd040d9 : mov(%rbx),%rdi PC (0x56397cd040d9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_view_get_selection () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1819757/+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 1813130] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
*** This bug is a duplicate of bug 1819757 *** https://bugs.launchpad.net/bugs/1819757 ** This bug is no longer a duplicate of bug 1812570 nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() ** This bug has been marked a duplicate of private bug 1819757 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1813130 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() Status in nautilus package in Ubuntu: New Bug description: Click on trash icon on the desktop. Folder does not open but nautilus crashed. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.30.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 24 09:50:04 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1037, 658)' InstallationDate: Installed on 2019-01-22 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x56470cc80119 : mov(%rbx),%rdi PC (0x56470cc80119) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_view_get_selection () ?? () ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1813130/+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 1818472] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
*** This bug is a duplicate of bug 1819757 *** https://bugs.launchpad.net/bugs/1819757 ** This bug has been marked a duplicate of bug 1812570 nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() ** This bug is no longer a duplicate of bug 1812570 nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() ** This bug has been marked a duplicate of private bug 1819757 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1818472 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu Disco (19.04 after removing microcode to install gnome- wallpapers. Later re-installed microcode. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 Uname: Linux 4.20.13-042013-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 4 01:02:56 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-03-03 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x56216635a0d9 : mov(%rbx),%rdi PC (0x56216635a0d9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_view_get_selection () ?? () ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1818472/+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 1817924] Re: apps launched from gnome shell do not get input focus
** Tags added: rls-dd-incoming -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1817924/+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 1819661] Re: since update, cant get into 'dropbox' or 'brasero' or install anything else?????
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- 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/1819661 Title: since update,cant get into 'dropbox' or 'brasero' or install anything else? Status in gnome-software package in Ubuntu: Incomplete Bug description: since update,cant get into 'dropbox' or 'brasero' or install anything else??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1819661/+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 1812570] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
*** This bug is a duplicate of bug 1819757 *** https://bugs.launchpad.net/bugs/1819757 ** This bug has been marked a duplicate of private bug 1819757 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1812570 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() Status in nautilus package in Ubuntu: Incomplete Bug description: Daily build ubuntu (Ubuntu Disco Dingo, image downloaded 20/01/19), installed without proprietary software. Version of nautilus is 3.30.4-1ubuntu1. Following list describes steps for reproduce bug: 1) Install and start new system. 2) Crash should happens on the first start of nautilus (Files app). ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.30.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 22:27:57 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-01-20 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x55f831f3d119 : mov(%rbx),%rdi PC (0x55f831f3d119) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_view_get_selection () ?? () ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1812570/+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 1819769] [NEW] The color tone of the file folder icon differs from the color of the desktop icons.
Public bug reported: Hello guys The color tone of the file folder icon differs from the color of the desktop icons. I really liked the update of the Yaru icon version on Ubuntu 19.04 Disk, but the color of the desktop files folder icon is different from the color of the sidebar file folder icon icon and the plank files folder icon, as can be seen in the attached image with VECTOR in bold. It would be good tone and refinement that these icons also had the same tonality. Thank you Edson Santos ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The color tone of the file folder icon differs from the color of the desktop icons." https://bugs.launchpad.net/bugs/1819769/+attachment/5245703/+files/Novo%20Yaru%20Captura%20de%20tela%20de%202019-03-12%2017-10-56.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1819769 Title: The color tone of the file folder icon differs from the color of the desktop icons. Status in yaru-theme package in Ubuntu: New Bug description: Hello guys The color tone of the file folder icon differs from the color of the desktop icons. I really liked the update of the Yaru icon version on Ubuntu 19.04 Disk, but the color of the desktop files folder icon is different from the color of the sidebar file folder icon icon and the plank files folder icon, as can be seen in the attached image with VECTOR in bold. It would be good tone and refinement that these icons also had the same tonality. Thank you Edson Santos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1819769/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
debdiff for libmbim 1.18.0 in Bionic. The upstream source tarball is the same as for Disco. ** Patch added: "libmbim_1.14.2-2.1ubuntu1_1.18.0-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/1819615/+attachment/5245700/+files/libmbim_1.14.2-2.1ubuntu1_1.18.0-0ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: In Progress Status in libqmi source package in Bionic: In Progress Status in modemmanager source package in Bionic: In Progress Bug description: To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
I have made Bionic packages for ModemManager 1.10 and the needed libraries now. I have attached the debdiffs and the upstream tarballs are the same as of the Disco packages. Ken, could you upload these packages for me. Alex, if we need to go through the SRU process (is this needed for hardware enablement), could you add the info about impact, reproducer, regression potential, ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: In Progress Status in libqmi source package in Bionic: In Progress Status in modemmanager source package in Bionic: In Progress Bug description: To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
debdiff for libqmi 1.22.0 in Bionic. The upstream source tarball is the same as for Disco. ** Patch added: "libqmi_1.18.0-3ubuntu1_1.22.0-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/1819615/+attachment/5245702/+files/libqmi_1.18.0-3ubuntu1_1.22.0-0ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: In Progress Status in libqmi source package in Bionic: In Progress Status in modemmanager source package in Bionic: In Progress Bug description: To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
debdiff for modemmanager 1.10 in Bionic. The upstream source tarball is the same as for Disco. ** Patch added: "modemmanager_1.6.8-2ubuntu1_1.10.0-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/1819615/+attachment/5245699/+files/modemmanager_1.6.8-2ubuntu1_1.10.0-0ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: In Progress Status in libqmi source package in Bionic: In Progress Status in modemmanager source package in Bionic: In Progress Bug description: To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+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 1818879] Re: pull cirrus.ko into main kernel package
** Changed in: xserver-xorg-video-vesa (Ubuntu) Importance: Undecided => High ** Changed in: xserver-xorg-video-vesa (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vesa in Ubuntu. https://bugs.launchpad.net/bugs/1818879 Title: pull cirrus.ko into main kernel package Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-vesa package in Ubuntu: Fix Committed Bug description: In disco, xorg stopped shipping a cirrus module/driver, instead relying on the kernel one. But the kernel one is in the linux-modules- extra--generic package, which is not installed by default in vms. That breaks some assumptions: uvtool, for example, doesn't specify a video device when creating a vm, and the default in libvirt in such cases is to use cirrus. As a conseguence, disco VMs created by tools that do not specify a default video device won't have the cirrus.ko module, and X won't start there. It's a bit more complicated, however, because X just tries other fallbacks, but they also don't work. In particular, vesa doesn't work: [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted value (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/) We can change uvtool and specify a video device instead of leaving it blank (see bug #1818877), but there might be other tools out there spawning guests without telling them which video device to use, and they would also fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818879/+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 1818516] Re: FFe: Mesa 19.0.x for disco
@lain: https://bugs.freedesktop.org/show_bug.cgi?id=109535 -- 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/1818516 Title: FFe: Mesa 19.0.x for disco Status in mesa package in Ubuntu: New Bug description: Mesa 19.0.0 will be soon released, and we should get that for disco, and then follow point-releases until the last one is released (roughly next July, will need an SRU). We'll also migrate it to use LLVM 8. New features according to upstream release notes: GL_AMD_texture_texture4 on all GL 4.0 drivers. GL_EXT_shader_implicit_conversions on all drivers (ES extension). GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension). GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension). GL_EXT_render_snorm on gallium drivers (ES extension). GL_EXT_texture_view on drivers supporting texture views (ES extension). GL_OES_texture_view on drivers supporting texture views (ES extension). GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only). Shader-based software implementations of GL_ARB_gpu_shader_fp64, GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot on i965. VK_ANDROID_external_memory_android_hardware_buffer on Intel Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV VK_EXT_scalar_block_layout on Intel and RADV VK_KHR_depth_stencil_resolve on Intel VK_KHR_draw_indirect_count on Intel VK_EXT_conditional_rendering on Intel VK_EXT_memory_budget on RADV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1720901] Re: VLC under Wayland causes system freezes in fullscreen mode
** Also affects: vlc Importance: Undecided Status: New -- 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/1720901 Title: VLC under Wayland causes system freezes in fullscreen mode Status in VLC media player: New Status in gnome-shell package in Ubuntu: Invalid Status in vlc package in Ubuntu: Fix Released Status in vlc package in Debian: Fix Released Bug description: Ubuntu version: 17.10 (most recent updates as of October 3rd) vlc version: 2.2.6-6 Whan I expect to happen: When playing a video in vlc and switching to fullscreen mode everything should work fine. Also when changing to a different position of a movie in fullscreen I expect the player to just switch to that position. What actually happens: It seems to depend a little on the file type of the video, mostly I get problems when going to fullscreen mode and then switching to a different position with the playback position bar. With some videos it was even enough to just open the fullscreen mode. The video freezes just displaying a frame while the audio keeps playing. The computer does not react any more to mouse or keyboard input, I have to perform a hard reboot. This problem only appears under the Wayland session, in the Xorg session everything works fine as expected. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-30 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: vlc 2.2.6-6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1720901/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
** Changed in: libmbim (Ubuntu Bionic) Status: New => In Progress ** Changed in: libqmi (Ubuntu Bionic) Status: New => In Progress ** Changed in: modemmanager (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: In Progress Status in libqmi source package in Bionic: In Progress Status in modemmanager source package in Bionic: In Progress Bug description: To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+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 1819744] Re: 19.04 Disco default wallpapers
Attaching xz with JPG and PNG files. I tried crushing the PNG, but couldn't get it any smaller. The online tools I have used previously did manage to save 20%, but at the expense of worsening the banding. The PNG is 2.3MB, the JPG is 651KB. I actually think the JPG looks a bit better. Look at the diagonal in the bottom right 3rd for example, there's more detail to the line. ** Attachment added: "disco_wallpaper.tar.xz" https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1819744/+attachment/5245681/+files/disco_wallpaper.tar.xz ** Tags added: desktop-trello-import -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1819744 Title: 19.04 Disco default wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Attached will be the Disco default wallpapers. One in colour, one in black and white. Both 4096 x 2304. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1819744/+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 1819744] Automatically added comment
Added to Trello: https://trello.com/c/6i5deivb/276-bug1819744-1904 -disco-default-wallpapers ** Tags removed: desktop-trello-import -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1819744 Title: 19.04 Disco default wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Attached will be the Disco default wallpapers. One in colour, one in black and white. Both 4096 x 2304. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1819744/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
Added tasks for libmbim and libqmi as their current versions are needed by ModemManeger 1.10. ** Also affects: libmbim (Ubuntu) Importance: Undecided Status: New ** Changed in: libmbim (Ubuntu) Importance: Undecided => High ** Also affects: libqmi (Ubuntu) Importance: Undecided Status: New ** Changed in: libqmi (Ubuntu) Importance: Undecided => High ** Also affects: modemmanager (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libqmi (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libmbim (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libmbim (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libqmi (Ubuntu Bionic) Importance: Undecided => High ** Changed in: modemmanager (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libmbim (Ubuntu) Status: New => Fix Released ** Changed in: libqmi (Ubuntu) Status: New => Fix Released ** Changed in: modemmanager (Ubuntu) Status: New => Fix Released ** Changed in: libmbim (Ubuntu Bionic) Milestone: None => bionic-updates ** Changed in: libqmi (Ubuntu Bionic) Milestone: None => bionic-updates ** Changed in: modemmanager (Ubuntu Bionic) Milestone: None => bionic-updates ** Changed in: modemmanager (Ubuntu) Milestone: bionic-updates => None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: New Status in libqmi source package in Bionic: New Status in modemmanager source package in Bionic: New Bug description: To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+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 1819729] Re: Add support for installing gpgpu drivers
** Description changed: - Provide an additional parameter to install gpgpu driver packages. In - this first implementation, only the NVIDIA driver packages are - supported. + SRU Request: + + [Impact] + We need the ubuntu-drivers tool to be able to install gpgpu driver meta-packages (without pulling in the kernel modules). + + An additional "--gpgpu" parameter, paired with the "install" parameter + will provide this feature. + + Note: in this first implementation - already available in Ubuntu 19.04 - + only the NVIDIA driver packages are supported. + + [Test Case] + 1) Enable the -proposed repository, and install the new ubuntu-drivers-common (340.107-0ubuntu0.16.04.2). + + 2) Make sure to have compatible NVIDIA hardware + + 3) Install the gpgpu driver: + ubuntu-drivers install --gpgpu + + 4) Make sure that the new driver is installed. + + [Regression Potential] + Low. The changes do not affect the currently supported features. ** Also affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: ubuntu-drivers-common (Ubuntu) Status: In Progress => Confirmed ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1819729 Title: Add support for installing gpgpu drivers Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] We need the ubuntu-drivers tool to be able to install gpgpu driver meta-packages (without pulling in the kernel modules). An additional "--gpgpu" parameter, paired with the "install" parameter will provide this feature. Note: in this first implementation - already available in Ubuntu 19.04 - only the NVIDIA driver packages are supported. [Test Case] 1) Enable the -proposed repository, and install the new ubuntu-drivers-common (340.107-0ubuntu0.16.04.2). 2) Make sure to have compatible NVIDIA hardware 3) Install the gpgpu driver: ubuntu-drivers install --gpgpu 4) Make sure that the new driver is installed. [Regression Potential] Low. The changes do not affect the currently supported features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1819729/+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 1819744] [NEW] 19.04 Disco default wallpapers
Public bug reported: Attached will be the Disco default wallpapers. One in colour, one in black and white. Both 4096 x 2304. ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1819744 Title: 19.04 Disco default wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Attached will be the Disco default wallpapers. One in colour, one in black and white. Both 4096 x 2304. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1819744/+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 1817924] Re: apps launched from gnome shell do not get input focus
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1043 Importance: Unknown Status: Unknown -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1817924/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
Added to Trello: https://trello.com/c/XNVW4Tpp/275-bug1817338-hdmi- sound-output-not-selectable-in-1904-but-works-in-1810 -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in gnome-control-center source package in Disco: Confirmed Status in pulseaudio source package in Disco: Invalid Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO 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:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
Opening pavucontrol after changing the setting in gnome-control-center switches it half of the time, so there seems to be a problem in pulseaudio with listening to changes and applying them. -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in gnome-control-center source package in Disco: Confirmed Status in pulseaudio source package in Disco: Invalid Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO 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:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
** Also affects: pulseaudio (Ubuntu Disco) Importance: Undecided Status: Invalid ** Also affects: gnome-control-center (Ubuntu Disco) Importance: High Assignee: Robert Ancell (robert-ancell) Status: Confirmed -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in gnome-control-center source package in Disco: Confirmed Status in pulseaudio source package in Disco: Invalid Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO 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:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
FWIW, the same seems to apply to me, but not just HDMI. I have: * Digital output on external DAC * Analog output on external DAC * HDMI * Speakers I can change as I want to, the active output device does not change. I think it's the same for recording devices, seeing as pacmd stat lists the same source before and after a change. -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in gnome-control-center source package in Disco: Confirmed Status in pulseaudio source package in Disco: Invalid Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO 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:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1818516] Re: FFe: Mesa 19.0.x for disco
@laney: https://bugs.freedesktop.org/show_bug.cgi?id=109535 -- 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/1818516 Title: FFe: Mesa 19.0.x for disco Status in mesa package in Ubuntu: New Bug description: Mesa 19.0.0 will be soon released, and we should get that for disco, and then follow point-releases until the last one is released (roughly next July, will need an SRU). We'll also migrate it to use LLVM 8. New features according to upstream release notes: GL_AMD_texture_texture4 on all GL 4.0 drivers. GL_EXT_shader_implicit_conversions on all drivers (ES extension). GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension). GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension). GL_EXT_render_snorm on gallium drivers (ES extension). GL_EXT_texture_view on drivers supporting texture views (ES extension). GL_OES_texture_view on drivers supporting texture views (ES extension). GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only). Shader-based software implementations of GL_ARB_gpu_shader_fp64, GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot on i965. VK_ANDROID_external_memory_android_hardware_buffer on Intel Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV VK_EXT_scalar_block_layout on Intel and RADV VK_KHR_depth_stencil_resolve on Intel VK_KHR_draw_indirect_count on Intel VK_EXT_conditional_rendering on Intel VK_EXT_memory_budget on RADV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 73536]
I'd like this feature, however if this is difficult to implement then a workaround for my use case would be if the firefox command could support a '--close' or similar option to exit gracefully, even if handled asynchronously and I had to poll to wait for exit. -- 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/73536 Title: MASTER Firefox crashes on instant X server shutdown Status in Mozilla Firefox: In Progress Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Triaged Bug description: Firefox crashes when X server is forcefully torn down (e.g. by pressing ctrl-alt-backspace) and a crash report gets generated on next login. (Original Report: I've reproduced it once on my machine with the following steps. With, oh, about 5 tabs open, I just pressed ctrl-alt-backspace, logged back in when the X server restarted, and FF crashed with a bug report when Gnome tried to restore the session. It's not terribly important, I don't think anyone does this very often, but maybe it'll be helpful. ) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/73536/+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 1818516] Re: FFe: Mesa 19.0.x for disco
@Iain: https://bugs.freedesktop.org/show_bug.cgi?id=109535 ** Bug watch added: freedesktop.org Bugzilla #109535 https://bugs.freedesktop.org/show_bug.cgi?id=109535 -- 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/1818516 Title: FFe: Mesa 19.0.x for disco Status in mesa package in Ubuntu: New Bug description: Mesa 19.0.0 will be soon released, and we should get that for disco, and then follow point-releases until the last one is released (roughly next July, will need an SRU). We'll also migrate it to use LLVM 8. New features according to upstream release notes: GL_AMD_texture_texture4 on all GL 4.0 drivers. GL_EXT_shader_implicit_conversions on all drivers (ES extension). GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension). GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension). GL_EXT_render_snorm on gallium drivers (ES extension). GL_EXT_texture_view on drivers supporting texture views (ES extension). GL_OES_texture_view on drivers supporting texture views (ES extension). GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only). Shader-based software implementations of GL_ARB_gpu_shader_fp64, GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot on i965. VK_ANDROID_external_memory_android_hardware_buffer on Intel Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV VK_EXT_scalar_block_layout on Intel and RADV VK_KHR_depth_stencil_resolve on Intel VK_KHR_draw_indirect_count on Intel VK_EXT_conditional_rendering on Intel VK_EXT_memory_budget on RADV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1819729] [NEW] Add support for installing gpgpu drivers
Public bug reported: Provide an additional parameter to install gpgpu driver packages. In this first implementation, only the NVIDIA driver packages are supported. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Wishlist Assignee: Alberto Milone (albertomilone) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1819729 Title: Add support for installing gpgpu drivers Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: Provide an additional parameter to install gpgpu driver packages. In this first implementation, only the NVIDIA driver packages are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1819729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
Hi sir I'm not sure about any of that, but if you click the drop down button in the top right then click the button between the wrench/screwdriver and the lock button and that middle button is the one that stops the obnoxious screen rotation. On Tue, Mar 12, 2019 at 9:56 AM Antonello wrote: > Problem in Elitebook 840 g2 solved by removing/purging iio sensor > package after the first installation (Debian) updated to the testing > version . The problem affected screen and touchpad/mouse. It seems to me > that it is a unnecessary package for laptop with no position sensors is > it not? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1726160 > > Title: > On login, display rotates to wrong orientation [HP Pavilion] > > Status in IIO Sensor Proxy: > Fix Released > Status in systemd: > New > Status in iio-sensor-proxy package in Ubuntu: > Invalid > Status in linux package in Ubuntu: > Confirmed > Status in systemd package in Ubuntu: > Confirmed > > Bug description: > I'm using a laptop, and on 17.04 the display always showed correctly, > but after upgrading to 17.10, when I log in the display rotates to > the right (portrait), and I have to open a terminal and run 'xrandr -o > 1' to get it back to the correct (landscape) orientation. In previous > versions 'xrandr -o 0' was landscape, and '1' was portrait the other > way. > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: xorg 1:7.7+19ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Uname: Linux 4.13.0-16-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia > .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:01:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 > 17:13:13 PDT 2017 >GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) > .tmp.unity_support_test.0: > > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sun Oct 22 15:15:08 2017 > DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, > re-reading > DistroCodename: artful > DistroVariant: ubuntu > DkmsStatus: >bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed >bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed >nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed >nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GraphicsCard: >NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) > (prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] > [103c:363c] > InstallationDate: Installed on 2017-01-11 (284 days ago) > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 > (20161012.2) > LightdmDisplayLog: (II) Server terminated successfully (0). Closing log > file. > MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash > SourcePackage: xorg > Symptom: display > UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) > dmi.bios.date: 10/05/2010 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: F.1D > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 363C > dmi.board.vendor: Hewlett-Packard > dmi.board.version: 32.25 > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: > dmi.product.family: 103C_5335KV > dmi.product.name: HP Pavilion dv7 Notebook PC > dmi.product.version: 039D222412102 > dmi.sys.vendor: Hewlett-Packard > version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 > version.libdrm2: libdrm2 2.4.83-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 > version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20170309-0ubuntu1 > 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/iio-sensor-proxy/+bug/1726160/+subscriptions >
[Desktop-packages] [Bug 1746598] Re: [MIR] libnfs
** No longer affects: libnfs (Ubuntu Xenial) ** No longer affects: libnfs (Ubuntu Cosmic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnfs in Ubuntu. https://bugs.launchpad.net/bugs/1746598 Title: [MIR] libnfs Status in libnfs package in Ubuntu: Fix Released Status in libnfs source package in Bionic: New Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year ago, but we can't enable it in Ubuntu until libnfs is promoted to main. The Ubuntu bug for this feature to be enabled in gvfs is LP: #1637988 qemu-block-extra could also enable libnfs support. Security No known CVEs. https://security-tracker.debian.org/tracker/source-package/libnfs https://launchpad.net/ubuntu/+source/libnfs/+cve Quality assurance = - Desktop Packages team is subscribed. - dh_auto_test runs but the tests shipped by upstream cant'b be run at build time since they modify the system. - Autopkgtests are added in 3.0.0-1, running upstream's test suite which includes running tests with valgrind, too. https://bugs.launchpad.net/ubuntu/+source/libnfs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libnfs https://github.com/sahlberg/libnfs/issues https://autopkgtest.ubuntu.com/packages/libn/libnfs (failing, never passed: see https://bugs.debian.org/921578 ) https://ci.debian.net/packages/libn/libnfs/ (tests aren't run in Debian because they request machine isolation which isn't implemented there yet) Dependencies No universe binary dependencies Standards compliance 3.9.8, debhelper compat 9, dh7 simple rules Maintenance === Actively maintained: https://github.com/sahlberg/libnfs Not team maintained in Debian. https://tracker.debian.org/pkg/libnfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598/+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 1819572] Re: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction
I'm untargetting the specific releases so that this doesn't show up in our weekly reports. I would like to see some more debugging and to better understand why it's just this one machine. It doesn't yet sound like this is a release critical bug. ** No longer affects: Ubuntu Cosmic ** No longer affects: Ubuntu Disco ** No longer affects: network-manager (Ubuntu Cosmic) ** No longer affects: network-manager (Ubuntu Disco) -- 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/1819572 Title: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction Status in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Dell Vostro 5568 (CID 201606-22344) [Steps To Reproduce] 1. Install cosmic on this machine 2. Connect to the internet with ethernet 3. do-release-upgrade [Expected Result] Upgrade completes. The wired connection is ready to access the internet. [Actual Result] - The ethernet interface has an IP address assigned by the associated DHCP (checked by "ip -a") - "ping 8.8.8.8" will get "Destination Host Unreachable" [More Information] I tried the same steps on different machine-distro matrix[1] and could only reproduce the issue on this machine. [1] distro are: xenial-to-bionic, bionic-to-cosmic, cosmic-to-disco --- [Logs] - /var/log tarball of the system: the attachment 201606-22344-network- manager-nplusone-190312.var-log.tar.gz - Collected by "ubuntu-bug network-manager": /media/tai271828/certsd/201606-22344-network-manager- nplusone-190312.ubuntu.bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1819572/+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 1817020] Re: Touching and dragging an icon on the dock blocks input to other apps
For me things got a lot better when i deleted a "pixel saver" plugin from ~/.config/ or ~/.local or some such. But now, I don't know if my gnome shell is in a "stock" configuration w.r.t. enabled default extensions. So personally I was "fixed" for a while. I will upgrade to that gnome- shell, and will report if this issue (or something similar) regresses again like that. -- 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/1817020 Title: Touching and dragging an icon on the dock blocks input to other apps Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Bionic: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: Steps to reproduce In GNOME Shell, make sure the Ubuntu dock is visible Using a finger drag, for example, a LibreOffice icon up and down the dock and then drop it on Nautilus. Notice that (sometimes?) the icon will continue to float above the dock and that the mouse will keep the clicky-finger icon. Notice that you can still open Activities and launch an application Notice however, that you can't actually interact with the application you have just launched = What I expected to happen = When releasing the drag the icon would land back on the dock and I could continue to use the desktop as usual. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1817020/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
** No longer affects: libnotify (Ubuntu Xenial) ** No longer affects: libnotify (Ubuntu Bionic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: In Progress Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap: git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path Running them with G_MESSAGES_DEBUG=all should provide translation logging [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gnome-shell (Ubuntu Disco) Importance: Undecided Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Confirmed ** Tags removed: rls-dd-incoming -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell source package in Disco: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 --- 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/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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/1796606/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell source package in Disco: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 --- 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/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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/1796606/+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 1819712] [NEW] It would be significantly better to save image files in reverse order
Public bug reported: Use case: Scan enough pages for your XUbuntu to start dumping memory into swap Save as image files What happens: You first wait for the last pages to be swapped out and first pages converted You then wait for the opposite thing What would be significantly better: You can write later pages first, using the fact that it is already in the memory at the end I believe that it can be done as easily as changing the line 224 in book.vala from: for (var i = 0; i < n_pages; i++) to: for (var i = n_pages; i >= ; --i) But i cannot test it, being unable to compile ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 12 17:51:03 2019 InstallationDate: Installed on 2018-11-24 (107 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. N76VB ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N76VB.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N76VB 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.:bvrN76VB.205:bd05/24/2013:svnASUSTeKCOMPUTERINC.:pnN76VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N76VB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: simple-scan (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 simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1819712 Title: It would be significantly better to save image files in reverse order Status in simple-scan package in Ubuntu: New Bug description: Use case: Scan enough pages for your XUbuntu to start dumping memory into swap Save as image files What happens: You first wait for the last pages to be swapped out and first pages converted You then wait for the opposite thing What would be significantly better: You can write later pages first, using the fact that it is already in the memory at the end I believe that it can be done as easily as changing the line 224 in book.vala from: for (var i = 0; i < n_pages; i++) to: for (var i = n_pages; i >= ; --i) But i cannot test it, being unable to compile ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 12 17:51:03 2019 InstallationDate: Installed on 2018-11-24 (107 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. N76VB ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N76VB.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N76VB 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.:bvrN76VB.205:bd05/24/2013:svnASUSTeKCOMPUTERINC.:pnN76VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N76VB 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/simple-scan/+bug/1819712/+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 1818790] Re: [regression] Desktop zoom is missing the mouse pointer
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Tags removed: rls-dd-incoming -- 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/1818790 Title: [regression] Desktop zoom is missing the mouse pointer Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454 --- Desktop zoom is missing the mouse pointer. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Wed Mar 6 15:12:04 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)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/1818790/+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 1818246] Re: update-notifier's notification is huge due to large icon
** Also affects: gnome-shell (Ubuntu Disco) Importance: High Status: Confirmed ** Tags removed: rls-dd-incoming ** Changed in: gnome-shell (Ubuntu Disco) Assignee: (unassigned) => Didier Roche (didrocks) -- 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/1818246 Title: update-notifier's notification is huge due to large icon Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Disco: Confirmed Bug description: I got a "update-notifier is ready" notification, with a HUGE icon which made the notification huge. update-notifier is a service, so shouldn't be opening a window itself. After the notification I never actually got a window. Also the shell should scale the icon to a proper size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818246/+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 1818790] Re: [regression] Desktop zoom is missing the mouse pointer
** Description changed: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 + Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454 --- Desktop zoom is missing the mouse pointer. - ProblemType: Bug - DistroRelease: Ubuntu 19.04 + ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Wed Mar 6 15:12:04 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (92 days ago) - InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) - SourcePackage: gnome-shell + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1818790 Title: [regression] Desktop zoom is missing the mouse pointer Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454 --- Desktop zoom is missing the mouse pointer. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Wed Mar 6 15:12:04 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)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/1818790/+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 1818790] Re: [regression] Desktop zoom is missing the mouse pointer
** No longer affects: mutter (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress -- 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/1818790 Title: [regression] Desktop zoom is missing the mouse pointer Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Disco: In Progress Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1020 Proposed fix: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/454 --- Desktop zoom is missing the mouse pointer. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Wed Mar 6 15:12:04 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-04 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)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/1818790/+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 1819207] Re: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers
** Also affects: ubiquity (Ubuntu Disco) Importance: Undecided Assignee: Jean-Baptiste Lallement (jibel) Status: Triaged ** Also affects: open-vm-tools (Ubuntu Disco) Importance: High Assignee: Jean-Baptiste Lallement (jibel) Status: Triaged ** Also affects: ubuntu-drivers-common (Ubuntu Disco) Importance: High Assignee: Jean-Baptiste Lallement (jibel) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1819207 Title: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers Status in open-vm-tools package in Ubuntu: Triaged Status in ubiquity package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in open-vm-tools source package in Disco: Triaged Status in ubiquity source package in Disco: Triaged Status in ubuntu-drivers-common source package in Disco: In Progress Bug description: [Rationale] On Ubuntu Desktop, we want to install automatically at installation time open-vm-tools-desktop and its dependencies to provide an improved user experience on first boot after installation of the guest. This method also provides an easy way to install the drivers after installation if they have not been installed at installation time. It is achieved adding an XB-Modaliases field to the control file for the record 'open-vm-tools-desktop' so ubuntu-drivers can detect the packages to install when running in a VMware guest and adding open-vm- tools to the list of whitelisted packages in ubuntu-drivers [Impact] The change adds an additional field to the control file used by ubuntu-drivers to detect the drivers to install automatically. In the worst case scenario either the field is not added or the detection by ubuntu-drivers fails. In both cases the package o-v-t-desktop is not installed and can still be installed manually. Note: open-vm-tools-desktop is in universe and must be in main. [Test Case] With the patched versions of ubuntu-drivers and open-vm-tools 1. Boot a daily ISO of Ubuntu Desktop to the live session in a VMware Guest (with VMWare Workstation for example) 2. Open a terminal, make sure the package cache is up to date with the version of o-v-t containing the Modaliases field 3. Run the command: $ ubuntu-drivers list and verify that o-v-t-desktop is in the output 4. Run the command: $ ubuntu-drivers devices And verify that the output shows the details of the sys entry for this device 5. Run the command: $ sudo ubuntu-drivers install and verify that the package o-v-t-desktop is installed [Regression Potential] Very Low. Package may fail to build if for some reason dh-gencontrol fails. Otherwise, given that the package is not already installed automatically, if automated installation doesn't work then we're still in the same situation than today. On ubuntu-drivers side, the change just adds o-v-t-desktop to the whitelist using an existing mechanism so other than a typo there is no risk of regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: open-vm-tools-desktop (not installed) ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 20:02:49 2019 InstallationDate: Installed on 2014-07-15 (1697 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: open-vm-tools UpgradeStatus: Upgraded to disco on 2018-03-24 (349 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1819207/+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
