[Desktop-packages] [Bug 1433774] Re: When double clicking an executable bash script in file manager, it opens in gedit rather than executing
As I said on [this][1] probable upstream issue this bug seems to be reduced just to have by default 'ask' or 'launch' as the default value for key `executable-text-activation` (on org.gnome.nautilus.preferences), or I'm missing something? [1]: https://gitlab.gnome.org/GNOME/nautilus/issues/443#note_497621 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #443 https://gitlab.gnome.org/GNOME/nautilus/issues/443 -- 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/1433774 Title: When double clicking an executable bash script in file manager, it opens in gedit rather than executing Status in nautilus package in Ubuntu: Confirmed Bug description: Download https://www.torproject.org/dist/torbrowser/4.0.4/tor-browser- linux64-4.0.4_en-US.tar.xz and extract it to a folder. Navigate to that folder in the GNOME file manager. Double click "start-tor-browser". Expected result: The script executes and launches the browser. Actual result: The script opens in gedit. Even when right clicking it, "Run" is not listed as an option anywhere. It's not even an option under "Open With... -> Other Application". The only way to run it is from a terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 18 16:00:48 2015 GsettingsChanges: InstallationDate: Installed on 2015-03-06 (12 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1433774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826316] Re: two monitor setup - resolution not properly recognized
journal.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259189/+files/journal.txt -- 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/1826316 Title: two monitor setup - resolution not properly recognized Status in mutter package in Ubuntu: Incomplete Bug description: i have 2 monitor setup, both with hidpi monitors: when 1 monitor (either one) is connected to the pc, resolution of the monitor is properly recognized. when 2 monitors are connected, maximum of 1200x800 is recognized. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 07:46:32 2019 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826316] Re: two monitor setup - resolution not properly recognized
about xrandr.txt... this happens with wayland session (the bug is tagged properly i think) honestly, i didnt try the xorg session... so the file is empty root@r7:/home/mspehar# xrandr --verbose > xrandr.txt No protocol specified Can't open display :0 -- 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/1826316 Title: two monitor setup - resolution not properly recognized Status in mutter package in Ubuntu: Incomplete Bug description: i have 2 monitor setup, both with hidpi monitors: when 1 monitor (either one) is connected to the pc, resolution of the monitor is properly recognized. when 2 monitors are connected, maximum of 1200x800 is recognized. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 07:46:32 2019 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826316] Re: two monitor setup - resolution not properly recognized
edids.txt ** Attachment added: "edids.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259188/+files/edids.txt -- 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/1826316 Title: two monitor setup - resolution not properly recognized Status in mutter package in Ubuntu: Incomplete Bug description: i have 2 monitor setup, both with hidpi monitors: when 1 monitor (either one) is connected to the pc, resolution of the monitor is properly recognized. when 2 monitors are connected, maximum of 1200x800 is recognized. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 07:46:32 2019 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826316] Re: two monitor setup - resolution not properly recognized
lspci.txt ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259190/+files/lspcik.txt -- 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/1826316 Title: two monitor setup - resolution not properly recognized Status in mutter package in Ubuntu: Incomplete Bug description: i have 2 monitor setup, both with hidpi monitors: when 1 monitor (either one) is connected to the pc, resolution of the monitor is properly recognized. when 2 monitors are connected, maximum of 1200x800 is recognized. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 07:46:32 2019 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826316] Re: two monitor setup - resolution not properly recognized
dmesg.txt ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259187/+files/dmesg.txt -- 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/1826316 Title: two monitor setup - resolution not properly recognized Status in mutter package in Ubuntu: Incomplete Bug description: i have 2 monitor setup, both with hidpi monitors: when 1 monitor (either one) is connected to the pc, resolution of the monitor is properly recognized. when 2 monitors are connected, maximum of 1200x800 is recognized. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 07:46:32 2019 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
per test in bionic, turn on proposed channel, do a 'apt install modemmanager'. it will upgrade to version 1.10.0-1~ubuntu18.04.1 and also upgrade related libmbim and libqmi library. I do that separate on two machine, that have DW5820e and DW5821e separately with a sim card inside. I confim I can properly add a new connection and connect to internet successfully. Note: for today, need to set DW5820e to USB mode in BIOS per information from HW vendor. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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 OEM Priority Project: In Progress 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: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original 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/oem-priority/+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 1826316] Re: two monitor setup - resolution not properly recognized
Please also: 5. Run: xrandr > xrandr.txt and send us the file 'xrandr.txt'. -- 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/1826316 Title: two monitor setup - resolution not properly recognized Status in mutter package in Ubuntu: Incomplete Bug description: i have 2 monitor setup, both with hidpi monitors: when 1 monitor (either one) is connected to the pc, resolution of the monitor is properly recognized. when 2 monitors are connected, maximum of 1200x800 is recognized. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 07:46:32 2019 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826316] Re: two monitor setup - resolution not properly recognized
Please also: 5. Run: xrandr --verbose > xrandr.txt and send us the file 'xrandr.txt'. -- 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/1826316 Title: two monitor setup - resolution not properly recognized Status in mutter package in Ubuntu: Incomplete Bug description: i have 2 monitor setup, both with hidpi monitors: when 1 monitor (either one) is connected to the pc, resolution of the monitor is properly recognized. when 2 monitors are connected, maximum of 1200x800 is recognized. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 07:46:32 2019 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826316] Re: two monitor setup - resolution not properly recognized
Please: 1. Run: lspci -k > lspcik.txt and send us the file 'lspcik.txt'. 2. Run: strings -f /sys/class/drm/*/edid > edids.txt and send us the file 'edids.txt'. 3. Run: dmesg > dmesg.txt and send us the file 'dmesg.txt'. 4. Run: journalctl -b0 > journal.txt and send us the file 'journal.txt'. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1826316 Title: two monitor setup - resolution not properly recognized Status in mutter package in Ubuntu: Incomplete Bug description: i have 2 monitor setup, both with hidpi monitors: when 1 monitor (either one) is connected to the pc, resolution of the monitor is properly recognized. when 2 monitors are connected, maximum of 1200x800 is recognized. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 07:46:32 2019 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826310] Re: display driver issue
Also, it appears you are using the old graphics driver ("intel"). The
newer driver which should work better is called "modesetting".
If you have made a custom xorg.conf that enables the Intel driver then
please remove it. Please also try uninstalling the driver since you
shouldn't need it:
sudo apt remove xserver-xorg-video-intel
** Package changed: ubuntu => xserver-xorg-video-intel (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1826310
Title:
display driver issue
Status in xserver-xorg-video-intel package in Ubuntu:
Incomplete
Bug description:
display driver issue
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Apr 25 09:24:56 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor
Graphics Controller [103c:3397]
InstallationDate: Installed on 2013-12-07 (1964 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
LANG=en_IN
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic
root=UUID=e586694b-5243-4be0-924c-d519be6aa981 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.asset.tag: INA346Z6BB
dmi.board.name: 3397
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: INA346Z6BB
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Elite 8300 SFF
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.98+git1904191830.be3b07~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1904241930.09e477~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1904241930.09e477~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati
1:19.0.1+git1903191930.36703f~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git1903011933.6afed3~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.16+git1904230730.ec2b45~oibaf~b
xserver.bootTime: Sat Feb 23 19:10:12 2019
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.18.4-0ubuntu0.8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1826310/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826310] Re: display driver issue
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! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1826310 Title: display driver issue Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: display driver issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 25 09:24:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [103c:3397] InstallationDate: Installed on 2013-12-07 (1964 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=e586694b-5243-4be0-924c-d519be6aa981 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: INA346Z6BB dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: INA346Z6BB dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 SFF dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.98+git1904191830.be3b07~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1904241930.09e477~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1904241930.09e477~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1+git1903191930.36703f~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1903011933.6afed3~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git1904230730.ec2b45~oibaf~b xserver.bootTime: Sat Feb 23 19:10:12 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1826310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade
The log messages you mention seem to be describing symptoms of the problem but not the cause. In order to find the cause of the problem, first please try uninstalling the 'gsconnect' extension and then reboot. Then tell us if the problem still happens. Please also run these commands and send us the output of each: lspci -k glxinfo | grep OpenGL ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: performance -- 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/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade Status in gnome-shell package in Ubuntu: Incomplete Bug description: I recently upgraded from 18.10 to 19.04. What I expected to happen: same performance as before. What happens instead: - I experience frequent locks of input lasting from 0.5–5 seconds, during which: - The mouse cannot be moved or clicked. - Any pressed key is repeated for the duration of the lock. Various events seem to trigger the locks: - Typing this bug report in Google Chrome (locks for 0.5 s every ~20–30 s). - Changing tabs in Google Chrome (locks for 0.5 s). - Changing tabs in the Atom editor (locks for 1–5 s). - Typing in gedit with no other applications running (locks for ~0.5s). Accompanying symptoms: - CPU usage for gnome-shell is high: - Always around 20% - Appears to spike to 100% for longer locks (from eyeballing htop open in gnome-terminal) - The following appear in 'journalctl -f': Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: last_user_time (169670562) is greater than comparison timestamp (169670067). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: 0x181 appears to be one of the offending windows with a timestamp of 169670562. Working around... Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: W1369 appears to be one of the offending windows with a timestamp of 1798201456. Working around... - The following also appear: Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: client bug: timer event20 debounce: offset negative (-313ms) Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: client bug: timer event20 debounce short: offset negative (-326ms) $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 19.04 Release:19.04 gnome-shell: Installed: 3.32.0+git20190410-1ubuntu1 Candidate: 3.32.0+git20190410-1ubuntu1 Version table: *** 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:52:32 2019 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (559 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826310] [NEW] display driver issue
You have been subscribed to a public bug: display driver issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 25 09:24:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [103c:3397] InstallationDate: Installed on 2013-12-07 (1964 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=e586694b-5243-4be0-924c-d519be6aa981 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: INA346Z6BB dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: INA346Z6BB dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 SFF dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.98+git1904191830.be3b07~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1904241930.09e477~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1904241930.09e477~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1+git1903191930.36703f~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1903011933.6afed3~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git1904230730.ec2b45~oibaf~b xserver.bootTime: Sat Feb 23 19:10:12 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- display driver issue https://bugs.launchpad.net/bugs/1826310 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel 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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I am using 18.10 and I have not yet experienced this issue. For me, in 18.04, something that consistently triggered this bug was whenever I accidentally touched the touch-screen on my laptop while adjusting it. In 19.04, I am able to interact with the touch-screen using my fingers, and this issue has not appeared yet. Also, I never used workspace related extensions. So, it is possible that there are multiple issues here, that all have the same symptom. Perhaps there is a common underlying cause, such as a memory issue, as Daniel van Vugt had suggested. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash 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/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
I suspect the Xorg modesetting driver's atomic logic might have something to do with this. Can someone experiencing the problem please try logging into 'Ubuntu on Wayland' and tell us if that avoids the issue? ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1826176] Re: Applications started from the dash often do not receive focus
** Changed in: gnome-shell Status: Unknown => Fix Released ** Changed in: mutter Status: Unknown => 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/1826176 Title: Applications started from the dash often do not receive focus Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu 19.04 applications that are started from the dash inside a Wayland session often do not receive focus. The behavior is inconsistent. Some applications (like the terminal) always properly get the focus. Some like GEdit en Chromium mostly do not receive focus until suddenly they do. It seems to depend on other applications that are already open and may have the focus but I could not discover the exact pattern. Once clicked or Alt-tabbed into the applications work as expected. But when you simply start typing after opening, for example, GEdit the keystrokes may go to an application window that has just been obscured buy the newly opened one. This bug is similar to bug 1817924 but that one apparently is limited to X sessions. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 11:43:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) 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/1826176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826182] Re: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor
** Changed in: mutter Status: Unknown => Fix Released -- 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/1826182 Title: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor Status in Mutter: Fix Released Status in mutter package in Ubuntu: Triaged Status in mutter source package in Disco: Triaged Status in mutter source package in Eoan: Triaged Bug description: Ubuntu 19.04 DisplayLink properietary driver installed. Log in to GNOME desktop in Wayland mode. Hotplug a DisplayLink USB dock with one monitor connected. What happens: The desktop session shuts down and throws me back into the login screen, where Wayland sessions are no longer available. What I would expect: the new monitor is taken into use and the desktop session continues normally. Installed: libmutter-4-0 3.32.0+git20190410-1ubuntu1 This issue is already fixed upstream: https://gitlab.gnome.org/GNOME/mutter/merge_requests/521 The fix has been released as part of mutter 3.32.1. I would hope the mutter package would be updated to the new upstream point release. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1826182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826311] Re: Cannot Login to Google with Advanced Protection Enabled
Looks like there is a similar open bug, so I will add a comment to it with additional info -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1826311 Title: Cannot Login to Google with Advanced Protection Enabled Status in gnome-online-accounts package in Ubuntu: New Bug description: Description: Ubuntu 19.04 Release: 19.04 gnome-online-accounts: Installed: 3.32.0-1ubuntu1 Candidate: 3.32.0-1ubuntu1 Version table: *** 3.32.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 1) Open Online accounts and select google (From settings or during OS setup) 2) enter username and password. What I expect: I get the prompt to plug-in my 2 factor hardware key What actually happens: I get a prompt saying, "You can only use your Security keys with Google Chrome" Not sure if this is actually fixable, I know desktop firefox has hidden settings to allow u2f, but not sure if that extends to the embedded browsers (if gnome-online-accounts even uses an embedded firefox for its browser) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 00:16:27 2019 InstallationDate: Installed on 2019-04-25 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1826311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826210] Re: monitor not refreshing
*** This bug is a duplicate of bug 1550779 *** https://bugs.launchpad.net/bugs/1550779 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1550779, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1550779 [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun -- 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/1826210 Title: monitor not refreshing Status in gnome-shell package in Ubuntu: Incomplete Bug description: two monitors neither refreshing for a few seconds $dmesg -w [14144.339109] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [14144.339154] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [14144.339176] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:09:57 2019 DisplayManager: gdm3 InstallationDate: Installed on 2015-08-23 (1339 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826196] Re: The Dock cannot scroll without a mouse when multiple programs are open
This sounds a little like bug 1716232. But mostly the issue here seems to be that your touchpad doesn't support scrolling(?). Have you tried configuring the various scrolling methods available in: Settings > Devices > Mouse & Touchpad > ... ? ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- 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/1826196 Title: The Dock cannot scroll without a mouse when multiple programs are open Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: This only happened after upgrading to 19.04. Everything works fine if i attach a mouse to my laptop. But without it i cannot scroll through the programs because my touchpad does not have a built-in side scroller. All was fine with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-release-upgrader-core 1:19.04.16.1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 12:51:20 2019 InstallationDate: Installed on 2018-06-12 (315 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to disco on 2019-04-20 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1826196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826182] Re: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor
Thanks Pekka. Since I know you're the upstream developer of the fix there's no need for us to ask any further questions. ** Tags added: fixed-in-3.32.1 fixed-upstream ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #542 https://gitlab.gnome.org/GNOME/mutter/issues/542 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/542 Importance: Unknown Status: Unknown ** Tags added: disco ** Also affects: mutter (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Eoan) Importance: High Status: Triaged ** Changed in: mutter (Ubuntu Disco) Importance: Undecided => High ** Changed in: mutter (Ubuntu Disco) Status: New => Triaged -- 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/1826182 Title: [DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor Status in Mutter: Fix Released Status in mutter package in Ubuntu: Triaged Status in mutter source package in Disco: Triaged Status in mutter source package in Eoan: Triaged Bug description: Ubuntu 19.04 DisplayLink properietary driver installed. Log in to GNOME desktop in Wayland mode. Hotplug a DisplayLink USB dock with one monitor connected. What happens: The desktop session shuts down and throws me back into the login screen, where Wayland sessions are no longer available. What I would expect: the new monitor is taken into use and the desktop session continues normally. Installed: libmutter-4-0 3.32.0+git20190410-1ubuntu1 This issue is already fixed upstream: https://gitlab.gnome.org/GNOME/mutter/merge_requests/521 The fix has been released as part of mutter 3.32.1. I would hope the mutter package would be updated to the new upstream point release. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1826182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826025] Re: gnome-shell trap int3 no desktop
Thanks. I wonder if this comes under the "send info to canonical" option chosen on first login. Maybe if you choose "No" then that also means crash reports don't get sent...? :( We'll need to find out how to flip that option to test it. -- 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/1826025 Title: gnome-shell trap int3 no desktop Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking cursor. [ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955 sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8] Restarting gdm3 service results in the same trap. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell] Date: Tue Apr 23 09:56:22 2019 DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-13-generic, x86_64: installed nvidia, 390.116, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3703] InstallationDate: Installed on 2012-02-14 (2625 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Supermicro X8DT3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: 1234567890 dmi.board.name: X8DT3 dmi.board.vendor: Supermicro dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890: dmi.product.family: 1234567890 dmi.product.name: X8DT3 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Apr 22 20:53:09 2019 xserver.configfile: /home/greg/xorg.conf.new xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.4-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825297] Re: When OSK is present, typing on physical keyboard usually dose not trigger the OSK to disappear (X11 only)
@Sebastien Bacher verdre responded: This is caused by x11 not sending a device-changed event if no interaction happened with the OSK before using the physical keyboard. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1185 -- 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/1825297 Title: When OSK is present, typing on physical keyboard usually dose not trigger the OSK to disappear (X11 only) Status in gnome-shell package in Ubuntu: Triaged Bug description: I use a XPS 13 9380 laptop with Disco. When On-Screen-Keyboard is present, typing on physical keyboard usually doesn't trigger the OSK to disappear. The problem only happen on X11 not on Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826176] Re: Applications started from the dash often do not receive focus
Just in case, please try uninstalling your extensions: b'org.gnome.shell' b'enabled-extensions' b"['workspace- g...@mathematical.coffee.gmail.com', 'nohotcor...@azuri.free.fr', 'gnomeGlobalAppMenu@lestcape', 'static_workspa...@rmy.pobox.com', 'user- th...@gnome-shell-extensions.gcampax.github.com', 'pixel- sa...@deadalnix.me', 'gse-show-workspa...@ns.petersimonyi.ca', 'customcor...@eccheng.gitlab.com', 'arc-m...@linxgem33.com', 'workspaces-to-d...@passingthru67.gmail.com', 'dash-to- d...@micxgx.gmail.com', 'desktop-icons@csoriano', 'sound-output-device- choo...@kgshank.net', 'display-profile-mana...@bodedejavu.github.com', 'output-audio-devices@muflone']" since we find a large number of bugs are caused by extensions. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1211 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1211 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1211 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #541 https://gitlab.gnome.org/GNOME/mutter/issues/541 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/541 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1826176 Title: Applications started from the dash often do not receive focus Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu 19.04 applications that are started from the dash inside a Wayland session often do not receive focus. The behavior is inconsistent. Some applications (like the terminal) always properly get the focus. Some like GEdit en Chromium mostly do not receive focus until suddenly they do. It seems to depend on other applications that are already open and may have the focus but I could not discover the exact pattern. Once clicked or Alt-tabbed into the applications work as expected. But when you simply start typing after opening, for example, GEdit the keystrokes may go to an application window that has just been obscured buy the newly opened one. This bug is similar to bug 1817924 but that one apparently is limited to X sessions. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 11:43:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) 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/1826176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779615] Re: Shell text and some icons have sharp edges during zoom
Also verified in February in comment #9. -- 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/1779615 Title: Shell text and some icons have sharp edges during zoom Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] Shell text and some icons have sharp edges during zoom. Screenshot attached. https://gitlab.gnome.org/GNOME/gnome-shell/issues/387 [Test Case] 1. Settings > Universal Access > Zoom = ON 2. Click on the time/calendar and look closely at the font edges. Expect: the edges should be smooth when zoomed. [Regression Potential] Low potential effect on other parts of Gnome Shell. The code being changed is only used in shell popup menus at the moment. [Other Info] This is not an important bug at all. Its fix is just a happy consequence of fixing the more important bug 1767648, so that's why it is getting SRU'd - for bug 1767648. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1779615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779615] Re: Shell text and some icons have sharp edges during zoom
I was using 3.28.3+git20190124-0ubuntu18.04.2 -- 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/1779615 Title: Shell text and some icons have sharp edges during zoom Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] Shell text and some icons have sharp edges during zoom. Screenshot attached. https://gitlab.gnome.org/GNOME/gnome-shell/issues/387 [Test Case] 1. Settings > Universal Access > Zoom = ON 2. Click on the time/calendar and look closely at the font edges. Expect: the edges should be smooth when zoomed. [Regression Potential] Low potential effect on other parts of Gnome Shell. The code being changed is only used in shell popup menus at the moment. [Other Info] This is not an important bug at all. Its fix is just a happy consequence of fixing the more important bug 1767648, so that's why it is getting SRU'd - for bug 1767648. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1779615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
This bug is closed because: (a) The original reporter can't reproduce it any more; and (b) The developer can't reproduce it any more. If there are any remaining issues then please open a new bug by running: ubuntu-bug gnome-shell -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Fix Released Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Also worth mentioning that the issue was present when running under both Wayland and XOrg. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash 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/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I believe that I managed to fix this on my machine. I'd suggest to anyone having this issue to check for and uninstall any workspace- related extensions in gnome-tweaks. Read on for more detail. This problem appeared for me after updating to 19.04 from 18.10. Like everyone else, I could click on items in the top bar (date/time, dock icons) and they would respond as expected, but applications weren't responding to keyboard or mouse input. It seemed that pressing the super key was triggering this, as things would work more or less fine until the application switcher overlay thing was shown. After reading through this thread and seeing a lot of mentions of workspace extensions I remembered that I'd enabled the Workspace Grid extension via gnome-tweaks. Loading gnome-tweaks showed a warning indicator next to this extension, with a mouseover tooltip that read something to the effect of "problem loading extension." After removing this extension, things seem to work fine. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash 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/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822062] Re: Race condition on boot between cups and sssd
** Changed in: cups (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cups (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: cups (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: cups (Ubuntu Disco) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1822062 Title: Race condition on boot between cups and sssd Status in cups package in Ubuntu: In Progress Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Cosmic: New Status in cups source package in Disco: New Status in cups source package in Eoan: In Progress Bug description: [Impact] * When cups has set the "SystemGroup" directive to an external group provided through sss and cups starts before sssd has finished booting, cups will crash because the group does not exist. * The patch adds an "After=sssd.service" clause to the service unit file. [Test Case] * Configure an external authentication service (LDAP, AD...) and create a group, for instance "lpadmins@tests.local" * Set SystemGroup to match that group in /etc/cups/cups-files.conf: SystemGroup lpadmins@tests.local * Reboot * If cups has started before sssd has finished booting, cups will crash: Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup "lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf. * If cups starts after sssd, it will work fine. [Regression Potential] * Minimal: this patch affects just the ordering of the service unit file. [Other Info] * Upstream: https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d [Original description] When cups has set the "SystemGroup" directive to an external group provided through sss and cups starts before sssd has finished booting, cups will crash because the group does not exist. For instance, with a group named lpadmins@tests.local served from Active Directory through sssd, if the sssd service hasn't booted before cups: Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler. Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler. Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers available locally. Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup "lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf. Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read "/etc/cups/cups-files.conf" due to errors. Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 'exit-code'. Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time over, scheduling restart. Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, restart counter is at 2. Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers available locally... Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers available locally. Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler. If sssd is running before cups starts, everything works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic
** Also affects: mutter (Ubuntu Eoan) Importance: Medium Status: Invalid ** Also affects: gnome-shell (Ubuntu Eoan) Importance: Medium Status: Invalid -- 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/1811900 Title: SRU 3.28 latest git to bionic Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Released Status in mutter source package in Bionic: Fix Released Status in gnome-shell source package in Disco: Invalid Status in mutter source package in Disco: Invalid Status in gnome-shell source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: [ Description ] 3.28 gnome git branch has various upstream approved fixes for many months now, but no release has been done yet, thus we're releasing a git snapshot of the latest approved fixes. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been included in upstream git now, various optimizations to clutter actors could cause drawing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 ** This bug has been marked a duplicate of bug 1809407 [nvidia] Corrupted wallpaper after resuming from suspend -- 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/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in gnome-shell package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
One of IHV parnter get this issues too during stressapp + iperf testing. LP#1823615 -- 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/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Confirmed Bug description: I have no idea about the package to blame: gvfs/udev/kernel ? This is now logged: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 27 14:21:10 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
I believe that I found a "solution", I don't know what caused it. After suffering with the problem for 2 weeks I discovered that emptying the trash the terminal way solved it. It seems Nautilus was having issues with something in the rubbish bin via the below command. rm -rf ~/.local/share/Trash/* Will post here again if the problem arises again. -- 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/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Expired Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826468] [NEW] Libreoffice Calc cannot export PDF to a network drive
Public bug reported: After upgrading from 18.10 to 19.04 I lost possibility to export a document to PDF, if a document is on a network drive (it's a DAVS network folder in my case). I receive a pop-up windows about general I/O error. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 23:35:20 2019 InstallationDate: Installed on 2018-05-05 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1826468 Title: Libreoffice Calc cannot export PDF to a network drive Status in libreoffice package in Ubuntu: New Bug description: After upgrading from 18.10 to 19.04 I lost possibility to export a document to PDF, if a document is on a network drive (it's a DAVS network folder in my case). I receive a pop-up windows about general I/O error. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 23:35:20 2019 InstallationDate: Installed on 2018-05-05 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787332] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen ...") from xf86VTEnter() from systemd_logind_vtenter()
This bug seems to have stopped for me a couple of months back. Now I get
black screens that have to be toggled off and back on with xrandr before
they display again after undocking/redocking.
That's a minor inconvenience compared to a crashing desktop environment,
so I'm quite happy. It would be good to know if anyone else has seen an
improvement in this behavior.
--
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/1787332
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
systemd_logind_vtenter()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: xserver-xorg-core 2:1.19.6-1ubuntu4
ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
Uname: Linux 4.17.0-6-generic x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 16 14:15:46 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA
controller])
Subsystem: Lenovo HD Graphics 630 [17aa:3102]
InstallationDate: Installed on 2018-05-26 (81 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 10M7CTO1WW
ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 7
-core
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-6-generic
root=UUID=d7ecc709-02c2-4413-b7e7-dfce1d2b3703 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
()
()
()
xf86VTEnter ()
()
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/06/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: M16KT47A
dmi.board.name: 3102
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN 3259627060530
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M710s
dmi.product.name: 10M7CTO1WW
dmi.product.version: ThinkCentre M710s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.93-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787332/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)
WaylandEnable=false workaround also works for 19.04 Nvidia 340 and 390 drivers still having issues with 19.04 but does not seem to be the cause of the gdm problem. -- 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/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/435 --- The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- Mailing list: https://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 1823363] Re: Running "Junk Mail Controls" does not appear in Activity Manager
Thank you for thanking me and letting me know! It's greatly appreciated. On Thu, Apr 25, 2019, 9:20 AM Olivier Tilloy wrote: > Thanks Paul for the upstream report! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1823363 > > Title: > Running "Junk Mail Controls" does not appear in Activity Manager > > Status in Mozilla Thunderbird: > Confirmed > Status in thunderbird package in Ubuntu: > Confirmed > > Bug description: > "Running Junk Mail Controls" does not appear in Activity Manager > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1 > ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 > Uname: Linux 4.18.0-17-generic x86_64 > AddonCompatCheckDisabled: False > ApportVersion: 2.20.10-0ubuntu13.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC2: jeb3837 F pulseaudio >/dev/snd/controlC1: jeb3837 F pulseaudio >/dev/snd/controlC0: jeb3837 F pulseaudio > BuildID: 20190325141154 > Channel: Unavailable > CurrentDesktop: ubuntu:GNOME > Date: Fri Apr 5 11:09:14 2019 > Extensions: extensions.sqlite corrupt or missing > ForcedLayersAccel: False > IfupdownConfig: ># interfaces(5) file used by ifup(8) and ifdown(8) >auto lo >iface lo inet loopback > IncompatibleExtensions: Unavailable (corrupt or non-existant > compatibility.ini or extensions.sqlite) > InstallationDate: Installed on 2018-08-17 (231 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > IpRoute: >default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 >169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 >192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src > 192.168.86.25 metric 600 >192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 > linkdown > Locales: extensions.sqlite corrupt or missing > MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 > PrefSources: prefs.js > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use) > RunningIncompatibleAddons: False > SourcePackage: thunderbird > SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 > Themes: extensions.sqlite corrupt or missing > UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago) > dmi.bios.date: 09/21/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 080016 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: A880G+ > dmi.board.vendor: BIOSTAR Group > dmi.chassis.asset.tag: None > dmi.chassis.type: 3 > dmi.chassis.vendor: BIOSTAR Group > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: A880G+ > dmi.product.sku: To Be Filled By O.E.M. > dmi.sys.vendor: BIOSTAR Group > > To manage notifications about this bug go to: > https://bugs.launchpad.net/thunderbird/+bug/1823363/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1823363 Title: Running "Junk Mail Controls" does not appear in Activity Manager Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: "Running Junk Mail Controls" does not appear in Activity Manager ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeb3837 F pulseaudio /dev/snd/controlC1: jeb3837 F pulseaudio /dev/snd/controlC0: jeb3837 F pulseaudio BuildID: 20190325141154 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 11:09:14 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-08-17 (231 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
Same.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}
Hopefully we can get Mozilla to up the limit for the API key.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
I tried it again just now (roughly around the same time of day I tried
this previously):
$ curl https://location.services.mozilla.com/v1/geolocate?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825741] Re: Multiple instances of global menu entries
Ok thank you for that. I’ve managed to reproduce the issue locally now. ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Triaged ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1825741 Title: Multiple instances of global menu entries Status in libreoffice package in Ubuntu: Triaged Bug description: I see 2 instances of each global menu entries. It's cluttering up my top panel. This also happens in Plasma. Build ID: libreoffice-6.2.2.2-snap1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826273] Re: Potential Side-channel during Graphics Rendering
** Information type changed from Private Security to Public Security ** Changed in: onboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1826273 Title: Potential Side-channel during Graphics Rendering Status in onboard package in Ubuntu: Confirmed Bug description: Dear Ubuntu Development Team, We're a group of researchers from University of California Riverside. We recently discovered that the Onboard keyboard application takes a variable amount of time to render the highlight effect depending on the input character. As a result, an unprivileged attacker could potentially utilize flush+reload cache side-channel attack to measure the execution time of said functions to infer users' text input. We verified this using the Onboard 1.2.0-0ubuntu5 that comes with Ubuntu 16.04.03 LTS. The side-channel resides in Cairo graphics library. We contacted the Cairo development team and they instruct us to contact you instead. For detailed information please refer to our paper in the link below. We would be very happy to work with you to address this issue. Please let us know what you think. https://www.cs.ucr.edu/~zhiyunq/pub/ndss19_cache_keystrokes.pdf Sincerely, Daimeng Wang ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: onboard 1.2.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 24 14:19:48 2019 InstallationDate: Installed on 2016-01-07 (1203 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: onboard UpgradeStatus: Upgraded to xenial on 2017-11-21 (519 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1826273/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825497] Re: flash player does not work in chromium
I upgraded my xubuntu 18.04 to 18.10 and then right away to 19.04 2 days ago. After this, Flash player on Firefox works, but on not Chromium and all derivates like Opera, Chrome, etc. I tried to reinstall them all, did all the workarounds that Google and Adobe say on troubleshooting help sites, tried to install and uninstall different packages through Synaptic package manager, clean caches, but no success. I installed a snap version of Chromium from command line, and that one says "plug in not supported", the others are on a permission looping without displaying content. In some time i will o a fresh install of 19.04, because maybe it can be related to installation errors or Kernel version TX! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1825497 Title: flash player does not work in chromium Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Invalid Bug description: after you allow it to run it doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 73.0.3683.103-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcqMAdkcABTIUAQOANR146mCFplZKnCUSUFSzDABxT4EAlQDRwIGAAQEBAQEBAjqAGHE4LUBYLEUAEyohAAAa/ABWMjQzSAogICAgICAg/QA4TB9TEgAKICAgICAg/wBMRlYwQzAyMTQwRjEKAPU= modes: 1920x1080 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Fri Apr 19 04:29:19 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2017-04-20 (729 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 1.18 Load-Processes-Running-Percent: 0.4% Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04ca:0050 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=71d156ea-3173-43e9-9a5e-00edcd2137f2 ro splash quiet vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) dmi.bios.date: 02/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4202 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4202:bd02/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1825497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
IBus is not always launched via im-config when GNOME is involved. In Ubuntu 19.10 im-config will be disabled by default in Wayland sessions. So to achieve a consistent address of ibus daemon, it's better to change the default in ibus itself. Attached please find a debdiff with a proposed fix. Once this change is in the archive, the equivalent im-config patch can be dropped. ** Patch added: "ibus-fix-eoan_lp1580463.debdiff" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463/+attachment/5259090/+files/ibus-fix-eoan_lp1580463.debdiff ** Tags added: patch ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New ** No longer affects: ibus (Ubuntu Xenial) ** No longer affects: ibus (Ubuntu Yakkety) ** Changed in: ibus (Ubuntu) Importance: Undecided => Medium ** Changed in: ibus (Ubuntu) Status: New => In Progress ** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: In Progress Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon
[Desktop-packages] [Bug 1826438] Re: Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files
I've inferred that the reporting process itself possibly interferes with the misbehaviour. After submitting this report (before the terminal session was closed, however) (began through a terminal session and not the Alt-F2 launcher, using ubuntu-bug [PID of nautilus]) the reported behaviour is present again. The behaviour is identical to that recorded in the attached webm. To confirm this interference I am beginning a second report, which won't be submitted. Using the Alt-F2 method to begin the reporting process doesn't interfere with the misbehaviour; beginning the process again through a terminal session did not reproduce the interference. -- 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/1826438 Title: Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files Status in nautilus package in Ubuntu: New Bug description: I've recently upgraded from 18.10 to 19.04. When I right-click on any folder the context menu has extra padding on the bottom edge, below the 'properties' item. Performing the same action on files doesn't produce the problem. Strangely, while reporting this bug the noted (and recorded) behaviour doesn't occur, when minutes before reporting process began the observed behaviour was still observed following a cold boot (I witnessed and recorded the behaviour last night, and this morning). Attached is a recording of the behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 11:45:34 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'detailed_type', 'starred']" InstallationDate: Installed on 2018-12-30 (116 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
** Changed in: gnome-online-accounts Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked. I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:38:32 2019 InstallationDate: Installed on 2018-03-24 (391 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826438] [NEW] Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files
Public bug reported: I've recently upgraded from 18.10 to 19.04. When I right-click on any folder the context menu has extra padding on the bottom edge, below the 'properties' item. Performing the same action on files doesn't produce the problem. Strangely, while reporting this bug the noted (and recorded) behaviour doesn't occur, when minutes before reporting process began the observed behaviour was still observed following a cold boot (I witnessed and recorded the behaviour last night, and this morning). Attached is a recording of the behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 11:45:34 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'detailed_type', 'starred']" InstallationDate: Installed on 2018-12-30 (116 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Recording of extra padding in nautilus context menu of folders." https://bugs.launchpad.net/bugs/1826438/+attachment/5259083/+files/19.04%20Disco%20Dingo%20-%20Folder%20RMB%20Vertical%20Padding.webm -- 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/1826438 Title: Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files Status in nautilus package in Ubuntu: New Bug description: I've recently upgraded from 18.10 to 19.04. When I right-click on any folder the context menu has extra padding on the bottom edge, below the 'properties' item. Performing the same action on files doesn't produce the problem. Strangely, while reporting this bug the noted (and recorded) behaviour doesn't occur, when minutes before reporting process began the observed behaviour was still observed following a cold boot (I witnessed and recorded the behaviour last night, and this morning). Attached is a recording of the behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 11:45:34 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'260' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'detailed_type', 'starred']" InstallationDate: Installed on 2018-12-30 (116 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826439] [NEW] tracker-extract causes system lock-up due to 100% CPU and memory usage
Public bug reported: Immediately after upgrading from 18.10 to 19.04, my computer froze about 30-40 secs after I logged in. I finally tracked this down to the tracker-extract process. This process starts within about half a minute after logging in. When it starts, it's a matter of seconds until it consumes 100% CPU and all available system memory (I have 16 GB on an Intel 8700k @ 4.8 GHz and SSD/M.2) This only happens with my regular user. It does not occur with a newly created user (I guess due to the large amount of files within my home directory). It happens every time I log in. I'm filing this bug against the Ubuntu package because this phenomenon causes the entire system to freeze up completely. The wheels seem to fall off the wagon in such a way the system can't recover. The only alternative at this point is a hard reset or SysRQ REISUB. It is not possible to switch to a TTY (ctrl-alt-fX), and it's not possible to ssh in from another machine. SysRQ-k does not work. I've tried logging in to a TTY before logging in to the GUI, and then switching to the TTY quickly after logging in to the GUI. Surely enough - a few seconds later the TTY locks up as well. I can reproduce the problem easily, but I'm not sure how to go about debugging it - would be happy to assist. I can't let the process run for more than a few seconds at a time so bear that in mind. I tried grabbing the process in gdb, but the package seem to be stripped of debug symbols. I did a strace -p for a few seconds and the process _appears_ to be symlinking files in my homedirectory to a subdirectory within /tmp (?!?) - I can get more details here if it helps. A bonus question from me is how it's possible that a process run by a user can take down the entire system in this manner. tracker-extract and tracker-miner-fs: 2.1.6-1 tracker: 2.1.8-2 kernel: 5.0.0-13-generic (I've also tried 5.0.9) I've attached a photo(!) of top illustrating what's going on (at this point the machine has already frozen up. There appears to still be some memory available, but this is just because top never got around to report the true numbers before the machine died.) ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Tags: freeze lock-up tracker-extract ** Attachment added: "2019-04-25 18.26.23.jpg" https://bugs.launchpad.net/bugs/1826439/+attachment/5259089/+files/2019-04-25%2018.26.23.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1826439 Title: tracker-extract causes system lock-up due to 100% CPU and memory usage Status in tracker-miners package in Ubuntu: New Bug description: Immediately after upgrading from 18.10 to 19.04, my computer froze about 30-40 secs after I logged in. I finally tracked this down to the tracker-extract process. This process starts within about half a minute after logging in. When it starts, it's a matter of seconds until it consumes 100% CPU and all available system memory (I have 16 GB on an Intel 8700k @ 4.8 GHz and SSD/M.2) This only happens with my regular user. It does not occur with a newly created user (I guess due to the large amount of files within my home directory). It happens every time I log in. I'm filing this bug against the Ubuntu package because this phenomenon causes the entire system to freeze up completely. The wheels seem to fall off the wagon in such a way the system can't recover. The only alternative at this point is a hard reset or SysRQ REISUB. It is not possible to switch to a TTY (ctrl-alt-fX), and it's not possible to ssh in from another machine. SysRQ-k does not work. I've tried logging in to a TTY before logging in to the GUI, and then switching to the TTY quickly after logging in to the GUI. Surely enough - a few seconds later the TTY locks up as well. I can reproduce the problem easily, but I'm not sure how to go about debugging it - would be happy to assist. I can't let the process run for more than a few seconds at a time so bear that in mind. I tried grabbing the process in gdb, but the package seem to be stripped of debug symbols. I did a strace -p for a few seconds and the process _appears_ to be symlinking files in my homedirectory to a subdirectory within /tmp (?!?) - I can get more details here if it helps. A bonus question from me is how it's possible that a process run by a user can take down the entire system in this manner. tracker-extract and tracker-miner-fs: 2.1.6-1 tracker: 2.1.8-2 kernel: 5.0.0-13-generic (I've also tried 5.0.9) I've attached a photo(!) of top illustrating what's going on (at this point the machine has already frozen up. There appears to still be some memory available, but this is just because top never got around to report the true numbers before the machine died.) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1825741] Re: Multiple instances of global menu entries
Yes it still occurs. I'm currently using Ubuntu 19.04 with Unity desktop. I'll test it with my Neon & Kubuntu install when I get the chance. ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/+attachment/5259076/+files/Flameshot19Apr25-130843.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1825741 Title: Multiple instances of global menu entries Status in libreoffice package in Ubuntu: Incomplete Bug description: I see 2 instances of each global menu entries. It's cluttering up my top panel. This also happens in Plasma. Build ID: libreoffice-6.2.2.2-snap1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825735] Re: Display is corrupted after waking from sleep
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Another thing that I have noticed is that this problem only arises when I click suspend or close the lid. If the laptop naturally goes sleep then this problem doesn't occur. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1825735 Title: Display is corrupted after waking from sleep Status in xorg package in Ubuntu: New Bug description: After I shut the lid of the laptop and turn it back on, I see my open windows for a second and then the lock screen appears. When I log in, my wallpaper is replaced with the image I have attached. This image is also shown in the lock screen. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset 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 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 13:58:09 2019 DistUpgraded: 2019-04-18 21:28:53,352 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-17-generic, x86_64: installed nvidia, 390.116, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83f9] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:83f9] InstallationDate: Installed on 2019-04-16 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 275d:0ba6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cc1xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (2 days ago) dmi.bios.date: 01/12/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/12/2018:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.sku: 2SS26UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1825735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792329] Re: Firefox freezes continuously on Ubuntu 16.04
It happens with more than one open card, especially with Facebook. I have the swap configured, with Ubuntu it can be about 300 Mb in swap. It seems to me that random happens without apparent similarities between the cases, and since February it has never happened again. -- 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/1792329 Title: Firefox freezes continuously on Ubuntu 16.04 Status in firefox package in Ubuntu: New Bug description: FireFox 62 freezes continuously. (64 bit Ubuntu 16.04.5) Lock mouse and keyboard on Ubuntu, I have to switch off with the On / Off button. Minor defect, but appeared simultaneously, I open a second / third page, do not load, I go back to the previous one and is no longer loaded, you only see the wheel of time. In this case, restart Firefox. glxinfo | grep "OpenGL version" OpenGL version string: 3.0 Mesa 18.0.5 WM_CLASS(STRING) = "Navigator", "Firefox" Description: Ubuntu 16.04.5 LTS Release: 16.04 Intel® Celeron(R) CPU N2840 @ 2.16GHz × 2 Intel® Bay Trail --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stefano1933 F...m pulseaudio /dev/snd/controlC0: stefano1933 F pulseaudio BuildID: 20181023214907 Channel: Unavailable CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-12 (59 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.3 metric 600 Locales: extensions.sqlite corrupt or missing Package: firefox 63.0+build2-0ubuntu0.16.04.2 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Profiles: Profile0 (Default) - LastVersion=63.0/20181023214907 (In use) RunningIncompatibleAddons: False Tags: xenial Themes: extensions.sqlite corrupt or missing Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1792329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
I tried it around 02:00 UTC on 25 April so the daily limit was probably
reset by the time you tested it. I did check around and came across this
issue on geoclue's GitLab
https://gitlab.freedesktop.org/geoclue/geoclue/issues/101
The geoclue key probably has a high daily limit but it's probably being
reached a few hours before the daily limit is reset.
** Bug watch added: gitlab.freedesktop.org/geoclue/geoclue/issues #101
https://gitlab.freedesktop.org/geoclue/geoclue/issues/101
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826394] Re: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW
Additional information: I've tried to reproduce this with a virtual machine to no effect - including installing cosmic, enabling firewall, upgrading to disco and seeing if it still occurs. As of yet, I have not managed to reproduce it (save for the fact that this exact problem is affecting two disco installations with very similar software setup). I will continue trying to reproduce and update when I have more information. -- 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/1826394 Title: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW Status in network-manager package in Ubuntu: New Bug description: Have an unusual issue. I have (native) IPv6 on my network. Typically, each connection has two dhclient processes; one for a v4 address, and dhclient with the -6 parameter for the v6 connection. Upon running 'ufw enable' in a console, a firewall is activated. After restarting NetworkManager, only one dhclient process is started by NetworkManager. This was undesirable, so I ran 'ufw disable', and rebooted just to be sure nothing had been left around. All rules gone, but now NetworkManager is point blankly refusing to start a dhclient process for the IPv6 side of networking. I've tried starting NetworkManager with --log-level=DEBUG and watching syslog; nothing seems to indicate that dhclient is even started for IPv6. The only potential indicator of something unusual is 'ipv6.method' being set to 'ignore' periodically, e.g.: Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9076] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9080] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9168] ++ ipv6.method = 'ignore' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9224] ++ ipv6.method = 'ignore' Any clues would be most helpful! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 12:17:43 2019 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Update to 2 hours ago: Started getting segfault problems with libglib. Again re-install fixed that but then I was getting segfaults elsewhere too. I have now reverted to a full system backup of 18.10 that I made earlier && will probably stay on that for a bit longer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
I went back to the 4.18 kernel but am not running VirtualBox (running bare metal). Also seeing issues with libglib. gnome-shell won't run due to a trap in libglib-2.0.so: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826025 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826420] [NEW] Nautilus disk properties shows black circle
Public bug reported: Ubuntu 19.04 / Nautilus 3.32.0 stable (?) Mounting a disk (which does not show on the desktop may I add here as well) and asking for disk properties gives a black circle. Expected behaviour: different colours for used and unused parts, maybe gray for the unusable meta data. Current behaviour: a black disk telling me nothing. (I have no idea as to why a perfectly working file manager had to get crippled further, but someone managed). I do have a custom theme but it happens with the default theme as well. (Sorry my tone gets harsher every time but I really get tired being an alpha tester). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:48:33 2019 InstallationDate: Installed on 2018-04-30 (360 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-19 (5 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "So much information" https://bugs.launchpad.net/bugs/1826420/+attachment/5259049/+files/Screenshot%20from%202019-04-25%2016-48-58.png -- 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/1826420 Title: Nautilus disk properties shows black circle Status in nautilus package in Ubuntu: New Bug description: Ubuntu 19.04 / Nautilus 3.32.0 stable (?) Mounting a disk (which does not show on the desktop may I add here as well) and asking for disk properties gives a black circle. Expected behaviour: different colours for used and unused parts, maybe gray for the unusable meta data. Current behaviour: a black disk telling me nothing. (I have no idea as to why a perfectly working file manager had to get crippled further, but someone managed). I do have a custom theme but it happens with the default theme as well. (Sorry my tone gets harsher every time but I really get tired being an alpha tester). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:48:33 2019 InstallationDate: Installed on 2018-04-30 (360 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-19 (5 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826081] Re: Ability to automatically arrange desktop icons gone in 19.04
** Changed in: gnome-shell-extension-desktop-icons Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1826081 Title: Ability to automatically arrange desktop icons gone in 19.04 Status in gnome-shell-extension-desktop-icons: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: Upgraded from Ubuntu 18.10 to Ubuntu 19.04. On the upside, Ubuntu 19.04 now handles my unusual desktop geometry, and displays desktop icons within physical monitor dimensions (I have one landscape, one portrait display). The downside is there's no sort option for desktop icons anymore. Icons are snapped to grid automatically, but all arrangement for now is manual. The restoration of "Sort by name" functionality at the very least, and perhaps the addition of "Sort by type" would be even better. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1826081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825919] Re: Gedit right click context menu stops working
Apr 25 10:17:42 PS006 systemd[1]: snapd.service: Succeeded. Apr 25 10:17:45 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != NULL' failed Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Logs' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="u Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Characters.BackgroundService' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.clocks' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.clocks' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Characters.BackgroundService' Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Calculator.SearchProvider' Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: M Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after attribute name “Less-than” of element “:” Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:21 PS006 systemd[1]: Starting Snappy daemon... Apr 25 10:19:21 PS006 snapd[1036]: AppArmor status: apparmor is enabled and all features are available Apr 25 10:19:21 PS006 snapd[1036]: daemon.go:379: started snapd/2.38+19.04 (series 16; classic) ubuntu/19.04 (amd64) linux/5.0.0-13-generic. Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:21 PS006 systemd[1]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1745]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1217]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1]: Started Snappy daemon. Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after attribute name “Less-than” of element “:” Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMet Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 Apr 25 10:19:21 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != NULL' failed Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:19:21 PS006
[Desktop-packages] [Bug 1825919] Re: Gedit right click context menu stops working
It just happened now... When this happened, I had right clicked on a misspelled work in a Firefox text area. I didn't get a popup context menu; I thought it was just Firefox acting up. So, I switched to my open Gedit window, to cut the correctly spelled word from my text document, and the context menu in Gedit wouldn't work either. It didn't work for a while. But as I started to research and copy logs in order to collect information to post here, the right click context menu magically started to work again, after some time. I'll post the journalctl out put here. The issue happened around 10:19 in the logs... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1825919 Title: Gedit right click context menu stops working Status in gedit package in Ubuntu: Incomplete Bug description: The Gedit text area right-click context menu stops appearing. This bug affects Ubuntu 19.04, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826415] [NEW] Videos do not play in presentation mode
Public bug reported: It is not possible to play embedded videos in the presentation mode. This affects PDF slides created with the beamer/multimedia latex package. Initially, no controls are shown on the slide with the video. In the normal mode, video controls appear when the video is clicked with the mouse. However, in the presentation mode, evince goes to the next page when one clicks with the mouse so that the controls do not appear and the video can only be played by exiting the presentation mode. Playing videos works fine in presentation mode with the okular PDF- viewer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 Uname: Linux 4.15.0-041500rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 16:15:43 2019 InstallationDate: Installed on 2015-11-05 (1267 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: evince UpgradeStatus: Upgraded to bionic on 2018-05-24 (335 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1826415 Title: Videos do not play in presentation mode Status in evince package in Ubuntu: New Bug description: It is not possible to play embedded videos in the presentation mode. This affects PDF slides created with the beamer/multimedia latex package. Initially, no controls are shown on the slide with the video. In the normal mode, video controls appear when the video is clicked with the mouse. However, in the presentation mode, evince goes to the next page when one clicks with the mouse so that the controls do not appear and the video can only be played by exiting the presentation mode. Playing videos works fine in presentation mode with the okular PDF-viewer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 Uname: Linux 4.15.0-041500rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 16:15:43 2019 InstallationDate: Installed on 2015-11-05 (1267 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: evince UpgradeStatus: Upgraded to bionic on 2018-05-24 (335 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1826415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Nothing helpful in this post but can confirm this issue still exists in 19.04. :( -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1514423] Re: package libreoffice-impress 1:4.2.8-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
*** This bug is a duplicate of bug 1824446 *** https://bugs.launchpad.net/bugs/1824446 ** This bug has been marked a duplicate of bug 1824446 package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1514423 Title: package libreoffice-impress 1:4.2.8-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: New Bug description: dpkg: error processing package libreoffice-impress (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: libreoffice-impress E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libreoffice-impress 1:4.2.8-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 Date: Mon Nov 9 08:17:04 2015 DuplicateSignature: package:libreoffice-impress:1:4.2.8-0ubuntu3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-11-04 (4 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: libreoffice Title: package libreoffice-impress 1:4.2.8-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1514423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1593945] Re: package libreoffice-impress 1:5.1.3-0ubuntu1 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten insta
*** This bug is a duplicate of bug 1824446 *** https://bugs.launchpad.net/bugs/1824446 ** This bug has been marked a duplicate of bug 1824446 package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1593945 Title: package libreoffice-impress 1:5.1.3-0ubuntu1 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. Status in libreoffice package in Ubuntu: New Bug description: Update pocedures break up whenever I try to install them. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:5.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Jun 17 12:57:59 2016 ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. InstallationDate: Installed on 2016-05-26 (22 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: libreoffice Title: package libreoffice-impress 1:5.1.3-0ubuntu1 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1593945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778135] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1778135 Title: /usr/bin/gnome- software:11:as_icon_get_name:gs_refine_item_pixbuf:gs_appstream_refine_app:gs_plugin_refine_from_pkgname:gs_plugin_refine_app Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Bug description: [Impact] GNOME Software can crash when failing to get an icon from the cache: https://errors.ubuntu.com/problem/333736cd145e0c8722aba054d9d202310b1447f0 [Test Case] Run updated version on a system that is hitting the problem, observe crash no longer occurs. [Regression Potential] Low, the fix is cherry-picked from a newer branch and fixes and obvious NULL pointer dereference. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1778135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789336] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1789336 Title: Show publisher display name and verified status Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Released Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides the display name for a snap (e.g. "Skype" instead of the username "skype") and the validation status for the account (used to show a tick against special accounts). This should be shown in GNOME Software. [Test Case] 1. Open GNOME Software 2. Select Skype Expected outcome: Developer is shown as "Skype" and account has tick icon beside it. Observed result: Developer is shown as "skype" and account has no tick icon. [Regression Potential] Chance of new parsing and UI code introducing bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1789336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790563] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1790563 Title: Many JsonArray critical warnings on command line Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Bug description: [Impact] Running GNOME Software gives many JsonArray warnings on the command line: Json-CRITICAL **: json_object_get_array_member: assertion 'node != NULL' failed Json-CRITICAL **: json_array_get_length: assertion 'array != NULL' failed This is due to the code not handling there being no plugs defined in the interface table (which is valid when it is empty). [Test Case] 1. Run GNOME Software from the command line $ killall gnome-software $ gnome-software Expected result: No JsonArray critical warnings are show. Observed result: Many JsonArray critical warnings are show. [Regression Potential] Risk of additional checks breaking expected behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1790563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754655] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1754655 Title: Installing snap from command line confuses GNOME Software Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Artful: Won't Fix Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] Installing snaps from the command line (or any other client) causes the state in GNOME Software to wrongly represented. [Test Case] 1. Ensure you don't have moon-buggy installed $ sudo snap remove moon-buggy 2. Start GNOME Software 3. Install moon-buggy from the command line: $ sudo snap install moon-buggy 4. Search for "moon" in GNOME Software Expected result: Moon Buggy shows in search results as installed Observed result: Moon Buggy not returned in search results. [Regression Potential] Low, we fix a bug where were reading invalid metadata and a check that makes stops unexpected (but valid) state notification from the snap plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738164] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1738164 Title: [snap] U2F doesn't work with yubikey Status in chromium-browser package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Confirmed Bug description: [Impact] Installing a snap that requires the u2f-devices interface doesn't show a UI element to enable/disable this in GNOME Software. Initially Chromium didn't have this enabled by default, and thus the feature wouldn't work without going to the command line. It now is enabled by default. [Test Case] 1. Open GNOME Software 2. Install the Chromium snap 3. Click "Permissions" Expected result: A switch is shown to control "Read/write access to U2F devices exposed". Clicking it connects/disconnects the u2f-devices interface. Observed result: No switch is shown for this interface. [Regression Potential] A string for this interface was added to GNOME Software, low risk of introducing a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778160] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1778160 Title: /usr/bin/gnome- software:11:g_type_check_instance:g_signal_emit_valist:g_signal_emit:g_closure_invoke:signal_emit_unlocked_R Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Configuring the permissions for a snap that has a plug that can connect to multiple slots causes a crash: https://errors.ubuntu.com/problem/46232e57fbbc469ce3e5f5c0f12bc24f95cd27c6 [Test Case] 1. Open GNOME Software 2. Search for and install TBD snap 3. Open Permissions dialog 4. Toggle TBD permission that uses a combo box Expected result: Permission is changed Observed result: GNOME Software crashes [Regression Potential] Fix is to rename a signal to avoid a name collision, low chance of introducing new bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1778160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799614] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824446] Re: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1824446 Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: Confirmed Bug description: it does not get updated with sudo apt-get update and keeps causing problems ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 21:24:06 2019 DpkgHistoryLog: Start-Date: 2019-04-10 21:23:53 Commandline: apt-get -f install Requested-By: vinaya (1000) Upgrade: libreoffice-core:amd64 (1:5.1.6~rc2-0ubuntu1~xenial3, 1:5.1.6~rc2-0ubuntu1~xenial6) DuplicateSignature: package:libreoffice-impress:1:5.1.6~rc2-0ubuntu1~xenial6 Setting up libreoffice-gnome (1:5.1.6~rc2-0ubuntu1~xenial6) ... dpkg: error processing package libreoffice-impress (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-27 (592 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.29ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824446] Re: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
Please try running the following command and let us know whether that fixes the problem: sudo apt install --reinstall libreoffice-impress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1824446 Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: Confirmed Bug description: it does not get updated with sudo apt-get update and keeps causing problems ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 21:24:06 2019 DpkgHistoryLog: Start-Date: 2019-04-10 21:23:53 Commandline: apt-get -f install Requested-By: vinaya (1000) Upgrade: libreoffice-core:amd64 (1:5.1.6~rc2-0ubuntu1~xenial3, 1:5.1.6~rc2-0ubuntu1~xenial6) DuplicateSignature: package:libreoffice-impress:1:5.1.6~rc2-0ubuntu1~xenial6 Setting up libreoffice-gnome (1:5.1.6~rc2-0ubuntu1~xenial6) ... dpkg: error processing package libreoffice-impress (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-27 (592 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.29ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799614] Please test proposed package
Hello Robert, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup
Sorry for the lack of feedback on that report Stuart. Are you still seeing this startup crash with the latest update for libreoffice on 18.04 (version 1:6.0.7-0ubuntu0.18.04.5)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1798074 Title: LIbreoffice crashes on startup Status in libreoffice package in Ubuntu: Confirmed Bug description: On starting up LibreOffice, it crashes. Starting from a terminal with just "libreoffice", I see the "general open a document" libreoffice window and a popup dialog titled "LibreOffice 6.0 Document Recovery", with text "Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. The following files will be recovered:" (and no files to be recovered are listed). Clicking "OK" on this dialog hides it and the general window, and then shows them both again; clicking OK on that dialog exits. LibreOffice does not start. Running "libreoffice --norestore" gives a stack trace: $ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5] /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97] /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca] I have tried entirely removing my profile, ~/.config/libreoffice , but the same problem still exhibits. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Tue Oct 16 12:58:04 2018 InstallationDate: Installed on 2014-04-07 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-04-28 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1798074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799614] Re: Use new media API
Hello Robert, or anyone else affected, Accepted gnome-software into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.30.2-0ubuntu11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-cosmic ** Tags added: verification-needed verification-needed-cosmic ** Tags added: verification-needed-bionic -- 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/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825064] Please test proposed package
Hello Robert, or anyone else affected, Accepted gnome-software into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.30.2-0ubuntu11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-software (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed-bionic -- 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/1825064 Title: Show only reviews from Ubuntu Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Committed Status in gnome-software source package in Disco: Fix Committed Bug description: [Impact] GNOME Software shows all reviews from ODRS, which includes reviews from other distributions. This can be misleading to Ubuntu users, as they may indicate issues or limitations that don't apply in Ubuntu. Solution is to filter reviews to show those reported on Ubuntu only. [Test Case] 1. Open GNOME Software 2. Select an app with reviews Expected result: The reviews should relate to Ubuntu Observed result: Some apps have reviews saying "Failed to start on ", which doesn't occur on Ubuntu. [Regression Potential] A filter was added to check the "distro" field on the review matches the distro GNOME Software is running on. This has a small risk of introducing a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825064] Re: Show only reviews from Ubuntu
Hello Robert, or anyone else affected, Accepted gnome-software into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.30.6-2ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-software (Ubuntu Disco) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-disco ** Changed in: gnome-software (Ubuntu Cosmic) Status: Triaged => Fix Committed ** Tags added: verification-needed-cosmic -- 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/1825064 Title: Show only reviews from Ubuntu Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Committed Status in gnome-software source package in Disco: Fix Committed Bug description: [Impact] GNOME Software shows all reviews from ODRS, which includes reviews from other distributions. This can be misleading to Ubuntu users, as they may indicate issues or limitations that don't apply in Ubuntu. Solution is to filter reviews to show those reported on Ubuntu only. [Test Case] 1. Open GNOME Software 2. Select an app with reviews Expected result: The reviews should relate to Ubuntu Observed result: Some apps have reviews saying "Failed to start on ", which doesn't occur on Ubuntu. [Regression Potential] A filter was added to check the "distro" field on the review matches the distro GNOME Software is running on. This has a small risk of introducing a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825064] Please test proposed package
Hello Robert, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1825064 Title: Show only reviews from Ubuntu Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Committed Status in gnome-software source package in Disco: Fix Committed Bug description: [Impact] GNOME Software shows all reviews from ODRS, which includes reviews from other distributions. This can be misleading to Ubuntu users, as they may indicate issues or limitations that don't apply in Ubuntu. Solution is to filter reviews to show those reported on Ubuntu only. [Test Case] 1. Open GNOME Software 2. Select an app with reviews Expected result: The reviews should relate to Ubuntu Observed result: Some apps have reviews saying "Failed to start on ", which doesn't occur on Ubuntu. [Regression Potential] A filter was added to check the "distro" field on the review matches the distro GNOME Software is running on. This has a small risk of introducing a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812563] Re: The Chromium window is corrupted only on initial startup.
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Is this issue still happening with the latest version of chromium? Could you please attach additional information to the bug report by running the following command in a terminal: apport-collect 1812563 Thanks in advance! ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1812563 Title: The Chromium window is corrupted only on initial startup. Status in Ubuntu Manual Tests: Invalid Status in chromium-browser package in Ubuntu: Incomplete Bug description: The Chromium window is corrupted only on it's first launch. Both on VM and acer laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1812563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737012] Re: Chromium random segfaults: error 4 in libnspr4.so
Thanks for the feedback. Marking fixed per last comment. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1737012 Title: Chromium random segfaults: error 4 in libnspr4.so Status in chromium-browser package in Ubuntu: Fix Released Bug description: [109127.127307] chromium-browse[15588]: segfault at a1 ip 7f298eb57cc3 sp 7ffc956c8fc0 Just random and seldom crashes. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 62.0.3202.94-0ubuntu0.17.10.1388 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE DRM.card0-DVI-D-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDAHBomUAAC4aAQOAMx14KtkFpVdRnicPUFS9SwDRwJUAlQ+zAIHAgYCBQAEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxNjQ2MDI2MDE4/ABQSEwgMjM3RTcKICAg/QA4TB5TEQAKICAgICAgANk= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x720 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Thu Dec 7 21:10:33 2017 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/home/user/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2017-08-28 (101 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 2.98 Load-Processes-Running-Percent: 0.2% MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-18-generic.efi.signed root=UUID=355fccdc-c430-43b5-929b-f38e35136c1c ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to artful on 2017-09-16 (81 days ago) dmi.bios.date: 03/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1I-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd03/10/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1I-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1737012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824667] Re: Flash in Chrome does not work
*** This bug is a duplicate of bug 1825497 *** https://bugs.launchpad.net/bugs/1825497 This upstream bug also affects chromium-browser, and is being tracked by bug #1825497. ** This bug has been marked a duplicate of bug 1825497 flash player does not work in chromium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1824667 Title: Flash in Chrome does not work Status in chromium-browser package in Ubuntu: Invalid Bug description: ubuntu 19.04 Flash wbudowany w przeglądarkę Chrome nie działa. Sprawdziłem chromowaną wersję 73 i 74. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1824667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792329] Re: Firefox freezes continuously on Ubuntu 16.04
Stefano, can you elaborate on the exact problem you're seeing now? Is there a series of steps that can reliably reproduce the problem? -- 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/1792329 Title: Firefox freezes continuously on Ubuntu 16.04 Status in firefox package in Ubuntu: New Bug description: FireFox 62 freezes continuously. (64 bit Ubuntu 16.04.5) Lock mouse and keyboard on Ubuntu, I have to switch off with the On / Off button. Minor defect, but appeared simultaneously, I open a second / third page, do not load, I go back to the previous one and is no longer loaded, you only see the wheel of time. In this case, restart Firefox. glxinfo | grep "OpenGL version" OpenGL version string: 3.0 Mesa 18.0.5 WM_CLASS(STRING) = "Navigator", "Firefox" Description: Ubuntu 16.04.5 LTS Release: 16.04 Intel® Celeron(R) CPU N2840 @ 2.16GHz × 2 Intel® Bay Trail --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stefano1933 F...m pulseaudio /dev/snd/controlC0: stefano1933 F pulseaudio BuildID: 20181023214907 Channel: Unavailable CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-12 (59 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.3 metric 600 Locales: extensions.sqlite corrupt or missing Package: firefox 63.0+build2-0ubuntu0.16.04.2 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Profiles: Profile0 (Default) - LastVersion=63.0/20181023214907 (In use) RunningIncompatibleAddons: False Tags: xenial Themes: extensions.sqlite corrupt or missing Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1792329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823363] Re: Running "Junk Mail Controls" does not appear in Activity Manager
Thanks Paul for the upstream report! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1823363 Title: Running "Junk Mail Controls" does not appear in Activity Manager Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: "Running Junk Mail Controls" does not appear in Activity Manager ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeb3837 F pulseaudio /dev/snd/controlC1: jeb3837 F pulseaudio /dev/snd/controlC0: jeb3837 F pulseaudio BuildID: 20190325141154 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 11:09:14 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-08-17 (231 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src 192.168.86.25 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.product.sku: To Be Filled By O.E.M. dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1823363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819129] Re: No CPU record on Virtualbox
** Description changed:
+ [Impact]
+
+ * Any new report after an installation in a Virtualbox machine won't
+ show up CPU informations.
+
+ [Test Case]
+
+ * Make a new installation in virtualbox
+ * Run "ubuntu-report show".
+ -> you won't have any "CPU" field in the output
+ * Install the new version from proposed
+ * Run "ubuntu-report show"
+ -> note the CPU field is now present.
+
+ [Regression Potential]
+ * The regexp to match lspcu information lines has been relaxed. The
testsuite has been enhanced and existing cases keeps working.
+
+
+
On a virtualbox guest ubuntu-report doesn't report CPU information.
u@pc:~$ ubuntu-report show
{
- "Version": "19.04",
- "OEM": {
- "Vendor": "innotek GmbH",
- "Product": "VirtualBox"
- },
- "BIOS": {
- "Vendor": "innotek GmbH",
- "Version": "VirtualBox"
- },
- "Arch": "amd64",
- "GPU": [
- {
- "Vendor": "15ad",
- "Model": "0405"
- }
- ],
- "RAM": 2,
- "Disks": [
- 21.5
- ],
- "Partitions": [
- 20.5
- ],
- "Screens": [
- {
- "Size": "0mmx0mm",
- "Resolution": "800x600",
- "Frequency": "60.00"
- }
- ],
- "Autologin": true,
- "LivePatch": false,
- "Session": {
- "DE": "ubuntu:GNOME",
- "Name": "ubuntu",
- "Type": "x11"
- },
- "Language": "en_US",
- "Timezone": "America/New_York",
- "Install": {
- "Media": "Ubuntu 19.04 \"Disco Dingo\" - Alpha amd64 (20190305.1)",
- "Type": "GTK",
- "OEM": false,
- "PartitionMethod": "use_device",
- "DownloadUpdates": true,
- "Language": "en",
- "Minimal": false,
- "RestrictedAddons": false,
- "Stages": {
- "0": "language",
- "2": "language",
- "8": "console_setup",
- "16": "console_setup",
- "20": "prepare",
- "24": "partman",
- "26": "start_install",
- "86": "timezone",
- "90": "usersetup",
- "97": "user_done",
- "582": "done"
- }
- }
+ "Version": "19.04",
+ "OEM": {
+ "Vendor": "innotek GmbH",
+ "Product": "VirtualBox"
+ },
+ "BIOS": {
+ "Vendor": "innotek GmbH",
+ "Version": "VirtualBox"
+ },
+ "Arch": "amd64",
+ "GPU": [
+ {
+ "Vendor": "15ad",
+ "Model": "0405"
+ }
+ ],
+ "RAM": 2,
+ "Disks": [
+ 21.5
+ ],
+ "Partitions": [
+ 20.5
+ ],
+ "Screens": [
+ {
+ "Size": "0mmx0mm",
+ "Resolution": "800x600",
+ "Frequency": "60.00"
+ }
+ ],
+ "Autologin": true,
+ "LivePatch": false,
+ "Session": {
+ "DE": "ubuntu:GNOME",
+ "Name": "ubuntu",
+ "Type": "x11"
+ },
+ "Language": "en_US",
+ "Timezone": "America/New_York",
+ "Install": {
+ "Media": "Ubuntu 19.04 \"Disco Dingo\" - Alpha amd64 (20190305.1)",
+ "Type": "GTK",
+ "OEM": false,
+ "PartitionMethod": "use_device",
+ "DownloadUpdates": true,
+ "Language": "en",
+ "Minimal": false,
+ "RestrictedAddons": false,
+ "Stages": {
+ "0": "language",
+ "2": "language",
+ "8": "console_setup",
+ "16": "console_setup",
+ "20": "prepare",
+ "24": "partman",
+ "26": "start_install",
+ "86": "timezone",
+ "90": "usersetup",
+ "97": "user_done",
+ "582": "done"
+ }
+ }
}
-
- @pc:~$ lscpu
+ @pc:~$ lscpu
Architecture:x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
NUMA node(s):1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 10
Model name: AMD Phenom(tm) II X6 1055T Processor
Stepping:0
CPU MHz: 2812.342
BogoMIPS:5624.68
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache:512K
L3 cache:6144K
NUMA node0 CPU(s): 0
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp
lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid
tsc_known_freq pni monitor cx16 x2apic popcnt hypervisor lahf_lm cr8_legacy abm
sse4a misalignsse 3dnowprefetch vmmcall
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-report 1.4.0
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: Fri Mar 8 04:06:58 2019
Dependencies:
- gcc-9-base 9-20190220-0ubuntu1
- libc6 2.28-0ubuntu1
- libgcc1 1:9-20190220-0ubuntu1
- libidn2-0 2.0.5-1
- libunistring2 0.9.10-1ubuntu1
+ gcc-9-base 9-20190220-0ubuntu1
+ libc6 2.28-0ubuntu1
+
[Desktop-packages] [Bug 1826403] [NEW] Ethernet won't connect when cable is plugged in at boot
Public bug reported: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in network-manager package in Ubuntu: New Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000
[Desktop-packages] [Bug 1741843] Re: caribou (gnome-shell osk): special characters not working
*** This bug is a duplicate of bug 1760399 *** https://bugs.launchpad.net/bugs/1760399 ** This bug is no longer a duplicate of bug 1761554 [bionic] Extended characters in GNOME screen keyboard don't get entered ** This bug has been marked a duplicate of bug 1760399 New On-screen keyboard does not appear automatically when selecting some text fields -- 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/1741843 Title: caribou (gnome-shell osk): special characters not working Status in Caribou: In Progress Status in caribou package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 17.10 (fully updated, including Gnome-Shell). Hardware is a Lenovo X1 Carbon Laptop with Touchscreen. I've reproduced this issue on both Wayland and XOrg. I've reproduced this issue on the 17.10 live CD (Xorg) and on a fresh 17.10 (Wayland) install in VBox. Bug: Caribou/Gnome-Shell Wayland support for Caribou does not display the vast majority of special characters (the ones that you long press on vowels to get). Nor do the upside down question and exclamation marks work on it either. Nor do the Euro or Sterling signs work. This makes it impossible to use when writing in any other languages than English. 1) lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2) package version: caribou: Installed: 0.4.21-2 Candidate: 0.4.21-2 Version table: *** 0.4.21-2 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status gnome-shell: Installed: 3.26.2-0ubuntu0.1 Candidate: 3.26.2-0ubuntu0.1 Version table: *** 3.26.2-0ubuntu0.1 500 500 http://ca.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 3) What do I expect to happen: I expect that when I long press on e and get the popup and select ê, ë that these letter appear 4) they do not. nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/caribou/+bug/1741843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
*** This bug is a duplicate of bug 1760399 *** https://bugs.launchpad.net/bugs/1760399 My understanding is that this bug has been taken care of through the fixes of bug #1760399 and bug #1816808. Marking it a duplicate of the former. ** This bug has been marked a duplicate of bug 1760399 New On-screen keyboard does not appear automatically when selecting some text fields -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1761554 Title: [bionic] Extended characters in GNOME screen keyboard don't get entered Status in gnome-shell package in Ubuntu: Triaged Status in gnome-user-docs package in Ubuntu: Confirmed Status in im-config package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Status in gnome-user-docs source package in Bionic: Confirmed Status in im-config source package in Bionic: Triaged Bug description: im-config SRU request = [Impact] When in a Wayland session, accented characters as well as some special characters can't be entered via the screen keyboard. The issue is fixed via the proposed upload of im-config, which has been changed to not set the GTK_IM_MODULE environment variable for IBus on Wayland (previously GTK_IM_MODULE was set to "ibus"). Making this accessibility tool work without issues on Wayland is important enough to justify this SRU. [Test Case] 1. Log in to an Ubuntu on Wayland session 2. Open gedit and enable the screen keyboard (Settings -> Universal Access -> Typing) -> Accented characters via long-press does not work. Example: long-press a and select à from the popup Also, certain keys for special characters result in incorrect characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢ 3. Install im-config from bionic-proposed 4. Relogin and repeat step 2. -> Everything works as expected [Regression Potential] There are reasons to presuppose that GTK_IM_MODULE does not need to be set at all for IBus on a GNOME desktop: * GTK has a mechanism for selecting a built-in IM. * IBus is default in GNOME, and vanilla GNOME (which does not make use of im-config) does not set the GTK_IM_MODULE environment variable. But the change is only made for Wayland sessions, which is not default in 18.04. Given this limitation, the regression risk is deemed to be low. [Original description] I filed this bug upstream last month but it hasn't gotten much attention so I'm filing it here because I think we need to track this issue for the Ubuntu 18.04 release https://gitlab.gnome.org/GNOME/gnome-shell/issues/109 Test Case - 1. Open the Settings app. Click Universal Access. 2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal Access Menu" to make turning the Screen Keyboard on and off easier.) 3. Open Text Editor 4. Click the u button on the Screen Keyboard 5. Long-press the u button on the Screen Keyboard for a few seconds. On the popup, click the ü character. What Happens In Step 4, u is entered in the Text Editor document. Nothing is entered in Step 5. This bug affects any of the "extended characters" clicked on from the long-press popup in the Screen Keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819129] Re: No CPU record on Virtualbox
** Also affects: ubuntu-report (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: ubuntu-report (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1819129
Title:
No CPU record on Virtualbox
Status in ubuntu-report package in Ubuntu:
New
Status in ubuntu-report source package in Bionic:
New
Status in ubuntu-report source package in Disco:
New
Bug description:
On a virtualbox guest ubuntu-report doesn't report CPU information.
u@pc:~$ ubuntu-report show
{
"Version": "19.04",
"OEM": {
"Vendor": "innotek GmbH",
"Product": "VirtualBox"
},
"BIOS": {
"Vendor": "innotek GmbH",
"Version": "VirtualBox"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "15ad",
"Model": "0405"
}
],
"RAM": 2,
"Disks": [
21.5
],
"Partitions": [
20.5
],
"Screens": [
{
"Size": "0mmx0mm",
"Resolution": "800x600",
"Frequency": "60.00"
}
],
"Autologin": true,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu",
"Type": "x11"
},
"Language": "en_US",
"Timezone": "America/New_York",
"Install": {
"Media": "Ubuntu 19.04 \"Disco Dingo\" - Alpha amd64 (20190305.1)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "use_device",
"DownloadUpdates": true,
"Language": "en",
"Minimal": false,
"RestrictedAddons": false,
"Stages": {
"0": "language",
"2": "language",
"8": "console_setup",
"16": "console_setup",
"20": "prepare",
"24": "partman",
"26": "start_install",
"86": "timezone",
"90": "usersetup",
"97": "user_done",
"582": "done"
}
}
}
@pc:~$ lscpu
Architecture:x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
NUMA node(s):1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 10
Model name: AMD Phenom(tm) II X6 1055T Processor
Stepping:0
CPU MHz: 2812.342
BogoMIPS:5624.68
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache:512K
L3 cache:6144K
NUMA node0 CPU(s): 0
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp
lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid
tsc_known_freq pni monitor cx16 x2apic popcnt hypervisor lahf_lm cr8_legacy abm
sse4a misalignsse 3dnowprefetch vmmcall
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-report 1.4.0
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: Fri Mar 8 04:06:58 2019
Dependencies:
gcc-9-base 9-20190220-0ubuntu1
libc6 2.28-0ubuntu1
libgcc1 1:9-20190220-0ubuntu1
libidn2-0 2.0.5-1
libunistring2 0.9.10-1ubuntu1
InstallationDate: Installed on 2019-03-07 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-report
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1819129/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826400] [NEW] Event jumps to preceding date after edit
Public bug reported: Full-day events jump a date back if edited and saved, even when no information about date or time is changed. Tested in local and Google calendars, happens in both. To reproduce: 1. Create a full-day event (say on May 5) 2. Click on the event to open event editor 3. Keep the date and time unchanged (full day, May 5) 4. Press "Finish" 5. The event is now registered as a full-day event on the previous date, in this case May 4. Tested on several events in different months, the result is always the same. I reproduced the bug in both month and week view. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-calendar 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 14:17:07 2019 InstallationDate: Installed on 2018-05-09 (350 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to disco on 2019-04-03 (21 days ago) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1826400 Title: Event jumps to preceding date after edit Status in gnome-calendar package in Ubuntu: New Bug description: Full-day events jump a date back if edited and saved, even when no information about date or time is changed. Tested in local and Google calendars, happens in both. To reproduce: 1. Create a full-day event (say on May 5) 2. Click on the event to open event editor 3. Keep the date and time unchanged (full day, May 5) 4. Press "Finish" 5. The event is now registered as a full-day event on the previous date, in this case May 4. Tested on several events in different months, the result is always the same. I reproduced the bug in both month and week view. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-calendar 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 14:17:07 2019 InstallationDate: Installed on 2018-05-09 (350 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to disco on 2019-04-03 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1826400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
Same problem here. Nvidia GeForce 920MX, latest driver installed. -- 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/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in gnome-shell package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
I noticed that the OP had VirtualBox installed, same for me. This taints the kernel ... Are people who posted about going back to the old kernel using VBox? So, re-installing 'VirtualBox' and ubuntu package 'menu' worked for me, and keeping the new kernel Suggest "dmesg | grep vbox" (YMMV) I also noticed that I had installed the .deb as a direct download from Oracle & and not noticed there was an Ubuntu package in the repositories. The Ubuntu package has some extra bits to it. Apport/Whoopsie kept popping up with a crash message shortly after login but when I clicked to see the report everything disappeared. Anyone else get this? Re-install of 'menu' seems to work here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826395] Re: i tried to print a pdf file using Document viwer and printer prints garbage page
** Attachment added: "pdf" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826395/+attachment/5259000/+files/0425-0430.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1826395 Title: i tried to print a pdf file using Document viwer and printer prints garbage page Status in cups package in Ubuntu: New Bug description: 1. Ubuntu 19.04 2. HP Deskjet 400, hpcups 3.19.3 Examine the file obtained in the previous step by running the command ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:52:44 2019 InstallationDate: Installed on 2019-03-20 (35 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for HP: socket://172.16.206.55 MachineType: Micro-Star International Co., Ltd. PL62 7RC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=838b2683-bfe0-4dac-8c5e-d920aa70b420 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-18 (6 days ago) dmi.bios.date: 12/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16JDIMS.10A dmi.board.asset.tag: Default string dmi.board.name: MS-16JD dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16JDIMS.10A:bd12/26/2017:svnMicro-StarInternationalCo.,Ltd.:pnPL627RC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16JD:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: PL dmi.product.name: PL62 7RC dmi.product.sku: 16JD.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826395] [NEW] i tried to print a pdf file using Document viwer and printer prints garbage page
Public bug reported: 1. Ubuntu 19.04 2. HP Deskjet 400, hpcups 3.19.3 Examine the file obtained in the previous step by running the command ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:52:44 2019 InstallationDate: Installed on 2019-03-20 (35 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for HP: socket://172.16.206.55 MachineType: Micro-Star International Co., Ltd. PL62 7RC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=838b2683-bfe0-4dac-8c5e-d920aa70b420 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-18 (6 days ago) dmi.bios.date: 12/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16JDIMS.10A dmi.board.asset.tag: Default string dmi.board.name: MS-16JD dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16JDIMS.10A:bd12/26/2017:svnMicro-StarInternationalCo.,Ltd.:pnPL627RC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16JD:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: PL dmi.product.name: PL62 7RC dmi.product.sku: 16JD.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ** Attachment added: "appout" https://bugs.launchpad.net/bugs/1826395/+attachment/5258985/+files/appout -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1826395 Title: i tried to print a pdf file using Document viwer and printer prints garbage page Status in cups package in Ubuntu: New Bug description: 1. Ubuntu 19.04 2. HP Deskjet 400, hpcups 3.19.3 Examine the file obtained in the previous step by running the command ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:52:44 2019 InstallationDate: Installed on 2019-03-20 (35 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for HP: socket://172.16.206.55 MachineType: Micro-Star International Co., Ltd. PL62 7RC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=838b2683-bfe0-4dac-8c5e-d920aa70b420 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-18 (6 days ago) dmi.bios.date: 12/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16JDIMS.10A dmi.board.asset.tag: Default string dmi.board.name: MS-16JD dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16JDIMS.10A:bd12/26/2017:svnMicro-StarInternationalCo.,Ltd.:pnPL627RC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16JD:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: PL dmi.product.name: PL62 7RC dmi.product.sku: 16JD.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
I forwarded the proposed kbd fix upstream: https://lists.altlinux.org/pipermail/kbd/2019-April/000653.html ** Changed in: kbd (Ubuntu Eoan) Status: Confirmed => In Progress -- 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/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Committed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Committed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Committed Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: In Progress Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: $ sudo kbd_mode -s -C /dev/tty1 $ sudo kbd_mode -C /dev/tty1 The keyboard is in raw (scancode) mode * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1): $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826394] [NEW] IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW
Public bug reported: Have an unusual issue. I have (native) IPv6 on my network. Typically, each connection has two dhclient processes; one for a v4 address, and dhclient with the -6 parameter for the v6 connection. Upon running 'ufw enable' in a console, a firewall is activated. After restarting NetworkManager, only one dhclient process is started by NetworkManager. This was undesirable, so I ran 'ufw disable', and rebooted just to be sure nothing had been left around. All rules gone, but now NetworkManager is point blankly refusing to start a dhclient process for the IPv6 side of networking. I've tried starting NetworkManager with --log-level=DEBUG and watching syslog; nothing seems to indicate that dhclient is even started for IPv6. The only potential indicator of something unusual is 'ipv6.method' being set to 'ignore' periodically, e.g.: Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9076] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9080] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9168] ++ ipv6.method = 'ignore' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9224] ++ ipv6.method = 'ignore' Any clues would be most helpful! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 12:17:43 2019 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- 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/1826394 Title: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW Status in network-manager package in Ubuntu: New Bug description: Have an unusual issue. I have (native) IPv6 on my network. Typically, each connection has two dhclient processes; one for a v4 address, and dhclient with the -6 parameter for the v6 connection. Upon running 'ufw enable' in a console, a firewall is activated. After restarting NetworkManager, only one dhclient process is started by NetworkManager. This was undesirable, so I ran 'ufw disable', and rebooted just to be sure nothing had been left around. All rules gone, but now NetworkManager is point blankly refusing to start a dhclient process for the IPv6 side of networking. I've tried starting NetworkManager with --log-level=DEBUG and watching syslog; nothing seems to indicate that dhclient is even started for IPv6. The only potential indicator of something unusual is 'ipv6.method' being set to 'ignore' periodically, e.g.: Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9076] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9080] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9168] ++ ipv6.method = 'ignore' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9224] ++ ipv6.method = 'ignore' Any clues would be most helpful! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 12:17:43 2019 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown NetworkManager.state: [main] NetworkingEnabled=true
[Desktop-packages] [Bug 1826391] [NEW] UI allows dangerous mistakes
Public bug reported: Version: 3.28.3 I managed to format my system drive to NTFS by accident, the UI did nothing to prevent it or even warn me. Last week I was formatting a thumb drive to NTFS. I forgot to select it and my system NVME was selected. I noticed it after I created the NTFS partition but it made no sense since my laptop was running well... I though: it must be a bug in the UI and nothing serious. I'm used to partition programs that allow you to design the partitions and then you click a button to actually write your desired partition map. End result: My system NVME was formatted to NTFS, grub was still present in the drive. I though I had my boot damaged but no: I lost all my data. Can we make the argument: Is the user an idiot? Yes. Does Gnome Disks UI is UX friendly? No. Does it prevents the user from formatting the system partition/drive or mistakes in general? No. I believe Gnome Disks must warn/prevent the user from formatting the system drive. The fact the partition is created right away without a second step makes mistakes very easy. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1826391 Title: UI allows dangerous mistakes Status in gnome-disk-utility package in Ubuntu: New Bug description: Version: 3.28.3 I managed to format my system drive to NTFS by accident, the UI did nothing to prevent it or even warn me. Last week I was formatting a thumb drive to NTFS. I forgot to select it and my system NVME was selected. I noticed it after I created the NTFS partition but it made no sense since my laptop was running well... I though: it must be a bug in the UI and nothing serious. I'm used to partition programs that allow you to design the partitions and then you click a button to actually write your desired partition map. End result: My system NVME was formatted to NTFS, grub was still present in the drive. I though I had my boot damaged but no: I lost all my data. Can we make the argument: Is the user an idiot? Yes. Does Gnome Disks UI is UX friendly? No. Does it prevents the user from formatting the system partition/drive or mistakes in general? No. I believe Gnome Disks must warn/prevent the user from formatting the system drive. The fact the partition is created right away without a second step makes mistakes very easy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1826391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807744] Re: Print to File writes to incorrect file
** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=122075 Importance: Unknown Status: Unknown ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1807744 Title: Print to File writes to incorrect file Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Fix Released Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1807744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808123] Re: [upstream] Fullscreen view lands on another monitor
** Summary changed: - Fullscreen view lands on another monitor + [upstream] Fullscreen view lands on another monitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1808123 Title: [upstream] Fullscreen view lands on another monitor Status in LibreOffice: New Status in libreoffice package in Ubuntu: New Bug description: As described above. I work in the classroom with my notebook, to which I have connected a beamer. Sometimes I write things down in the Writer and show it via the beamer. I would like to use the fullscreen mode here. Unfortunately, the fullscreen mode is always displayed on the internal monitor, even if the window with the Writer maximized was previously displayed on the beamer. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 10:44:00 2018 InstallationDate: Installed on 2018-11-30 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1808123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826215] Re: /usr/lib/chromium-browser/chromium-browser:5:operator:~LogMessage:OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus_connection_dispatch
*** This bug is a duplicate of bug 1729963 *** https://bugs.launchpad.net/bugs/1729963 ** This bug has been marked a duplicate of bug 1729963 chromium-browser crashed in OnConnectionDisconnectedFilter() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1826215 Title: /usr/lib/chromium-browser/chromium- browser:5:operator:~LogMessage:OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus_connection_dispatch Status in chromium-browser package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 73.0.3683.103-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e0e63ef80dd16f02330b92c6af9e21591b2f47f0 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/chromium-browser/+bug/1826215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
