[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04
> While I am sure LIRC has a lot of uses. I would wager 90% of its users are using kodi. This might be the truth as seen from the kodi community. However, from an upstream lirc point of view I cannot really see that the number of kodi users are dominating in any way. > forgot a couple steps, here was all of them: While these steps worked for you, other users will have other needs. That said, disabling/stopping lircd-uinput might be a good idea in many cases. The last update to lirc has it disabled by default. > also some discussion here: https://forum.kodi.tv/showthread.php?tid=324727 That discussion is utterly confused and does not mention the need to migrate (manual or automatic) the old 0.9.0 setup to the new one. Also, some users in that thread are using the default driver while other seem to be using the devinput one. No one seems to be reading the documentation, but still seems to be able to establish the "fact" that lirc is broken. If it was possible to file a bug against the Kodi community overall I would consider doing that ;) On top of that Kodi is the one and only application which misuses lirc by using the raw events from the socket -- this makes lirc seriously crippled compared to the real stuff. I filed a bug on this long ago, but at a glance it seems to be lost. Unless there is more input I will close this as not-a-bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 Status in lirc package in Ubuntu: Confirmed Bug description: Lirc 0.10.0-2 is never configured after installation. Manually running "dpkg-reconfigure lirc " also does not do anything. I also noticed that /usr/share/lirc/remotes is empty, which is where I had my config file for Ubuntu 16.04. This was an upgrade install from 16.04. Searching the web indicates others have this problem. Some have reverted to the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I have been unsuccessful so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789356] Re: Dark purple (noise) background flashes up briefly during the login animation since Yaru was introduced
I don't have the time to do a testround again, but I can give pointers
for whoever has time to have a look:
The patch is
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-shell/commit/?id=ddc4f511abd64d69c1150a41475d0a1ebac01dbb,
in particular:
systemBackground = new Meta.Background({ meta_display: global.display });
[res, topColor] = Clutter.Color.from_string('#6D2169');
[res, bottomColor] = Clutter.Color.from_string('#370026');
systemBackground.set_gradient(GDesktopEnums.BackgroundShading.VERTICAL,
topColor, bottomColor);
This is hardcoded in the Shell code (I made it conditional by session
type). This was made to match what is in the Yaru.css file:
#lockDialogGroup {
background: none;
background-color: none;
background-gradient-direction: vertical;
background-gradient-start: #6D2169;
background-gradient-end: #370026; }
As I don't have bionic/cosmic eyes as yours, for me, for the short while
this screen appeared, ti seemed the same gradient, with the same
VERTICAL transition.
--
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/1789356
Title:
Dark purple (noise) background flashes up briefly during the login
animation since Yaru was introduced
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Dark purple (noise) background flashes up briefly (for a split second) during
the login animation.
The login screen and gnome-shell's system background are meant to be the same
image so that the login procedure can VT switch without the user noticing. Then
the final desktop expands over the system background. However it appears the
login background and system background are not the same image any more, causing
a visible glitch during login.
[Test Case]
1. Install new version, logout
2. Log in into GDM
-> Check that at login startup, the background matches GDM ones (same color,
same gradient)
3. Logout, install gnome-session
4. Reboot so that GDM takes gnome-session into account
5. Select GNOME session and login
-> At login startup, the background will matche the GNOME default one (from
the lockscreen: grey noise), which matches GDM one if reset to default GNOME
via update-alternatives.
[Regression Potential]
This code is loaded at session startup, if there is a syntax error, the
session wouldn't start at all.
This has been of course tested before committed (both on ubuntu and GNOME
sessions)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: yaru-theme-gnome-shell 18.10.2
ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
Uname: Linux 4.17.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
Date: Tue Aug 28 14:19:48 2018
Dependencies:
InstallationDate: Installed on 2018-05-26 (93 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_AU.UTF-8
SHELL=/bin/bash
SourcePackage: yaru-theme
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791421] Re: Nautilus hangs when opening a password protected .7z file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1791421 Title: Nautilus hangs when opening a password protected .7z file Status in nautilus package in Ubuntu: Confirmed Bug description: Very simple scenario: On a fresh Ubuntu 18.04 installation (with Unity and pzip-full installed) I try to open a password protected .7z file (created in an older Ubuntu version). Nautilus starts flickering, CPU usage rises to 80% for minutes and Nautilus is not usable for a long time. Minimising doesn't work, however terminating does, where after CPU usage turns to normal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 8 12:30:29 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'890x540+226+183'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-09-01 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788235] Re: lirc broken on 18.04
While I am sure LIRC has a lot of uses. I would wager 90% of its users are using kodi. At times it can be difficult to find a good howoto guide, that walks you through a freshly installed ubuntu system, to a working LIRC remote. I am very happy to have mine working again. I forgot a couple steps, here was all of them: sudo apt purge ir-keytable lirc sudo apt-get install -y lirc lirc-compat-remotes sudo dpkg-reconfigure lirc sudo irw sudo systemctl stop lircd-uinput.service sudo systemctl disable lircd-uinput.service also some discussion here: https://forum.kodi.tv/showthread.php?tid=324727 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1788235 Title: lirc broken on 18.04 Status in lirc package in Ubuntu: Confirmed Bug description: Lirc 0.10.0-2 is never configured after installation. Manually running "dpkg-reconfigure lirc " also does not do anything. I also noticed that /usr/share/lirc/remotes is empty, which is where I had my config file for Ubuntu 16.04. This was an upgrade install from 16.04. Searching the web indicates others have this problem. Some have reverted to the lirc from 16.04. Others recommend using pip3 to install lirc 0.10.10, but I have been unsuccessful so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1788235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802911] Re: [snap] LibreOffice 6.1.3.2 (90) doesn't launch
No worries, and thanks for the report anyway. I suggest you try to uninstall the snap and install it again from scratch, and let us know here whether that "fixes" the problem. -- 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/1802911 Title: [snap] LibreOffice 6.1.3.2 (90) doesn't launch Status in libreoffice package in Ubuntu: Invalid Bug description: LibreOffice doesn't launch on 6.1.3.2 (90) in `candidate` on core 16-2.36.1+git1007.f72779e (5920) in `edge`, it just hangs, with no Terminal output, but has the following denials in `journalctl -f`: ``` Nov 12 12:38:19 adam-thinkpad-t430 audit[31984]: AVC apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 12 12:38:19 adam-thinkpad-t430 kernel: audit: type=1400 audit(1542026299.589:542): apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ``` ``` $ snap info libreoffice tracking: candidate refresh-date: 6 days ago, at 08:50 GMT channels: stable:6.1.2.1 (86) 501MB - candidate: 6.1.3.2 (90) 507MB - < beta: ↑ edge: ↑ installed: 6.1.3.2 (90) 507MB - $ snap version snap2.36.1+git1007.f72779e~ubuntu16.04.1 snapd 2.36.1+git1007.f72779e~ubuntu16.04.1 series 16 ubuntu 18.10 kernel 4.18.0-11-generic $ snap info core tracking: edge refresh-date: today at 12:08 GMT channels: stable:16-2.35.5 (5742) 92MB - candidate: 16-2.35.5 (5742) 92MB - beta: 16-2.36.1 (5897) 92MB - edge: 16-2.36.1+git1007.f72779e (5920) 92MB -< installed: 16-2.36.1+git1007.f72779e (5920) 92MB core ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770831] Re: [i915] Screen problems
** Changed in: xorg-server (Ubuntu) Status: Expired => New ** Summary changed: - [i915] Screen problems + Screen corruption on startup using an Atom N270 (i945 graphics) -- 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/1770831 Title: Screen corruption on startup using an Atom N270 (i945 graphics) Status in xorg-server package in Ubuntu: New Bug description: When I sart I have a screen black and white pixels I put in stand by when I leave standby then screen is normal ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat May 12 12:42:38 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Integrated Graphics Controller [1025:015b] Subsystem: Acer Incorporated [ALI] Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1025:015b] InstallationDate: Installed on 2018-04-09 (33 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) MachineType: Acer AOA150 ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic root=UUID=f11f3698-678f-4e8e-8a2d-27ef88b479a0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2008 dmi.bios.vendor: Acer dmi.bios.version: v0.3309 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrv0.3309:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: AOA150 dmi.product.version: 1 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat May 12 12:20:25 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4546 vendor AUO xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1770831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770831] Re: [i915] Screen problems
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1770831 Title: [i915] Screen problems Status in xorg-server package in Ubuntu: Expired Bug description: When I sart I have a screen black and white pixels I put in stand by when I leave standby then screen is normal ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat May 12 12:42:38 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Integrated Graphics Controller [1025:015b] Subsystem: Acer Incorporated [ALI] Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1025:015b] InstallationDate: Installed on 2018-04-09 (33 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) MachineType: Acer AOA150 ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic root=UUID=f11f3698-678f-4e8e-8a2d-27ef88b479a0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2008 dmi.bios.vendor: Acer dmi.bios.version: v0.3309 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrv0.3309:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: AOA150 dmi.product.version: 1 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat May 12 12:20:25 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4546 vendor AUO xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1770831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
On cosmic, even without turn on the proposed channel, with gnome-shell 3.30.1-2ubuntu1, I can't reproduce this issue. With the gnome-shell 3.30.1-2ubuntu1.18.10.1 from the proposed channel, it still works fine. -- 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/1745888 Title: Two instances of a program launch whenever you touch a favorites icon Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Bug description: [ Impact ] Using a touch screen, if you tap on a favorites icon on the ubuntu dock, two (or more) instances of an application launch. [ Test case ] - Look for xterm in gnome-shell activities and add it to favourtes - With the ubuntu-dock showing in the desktop, touch the xterm icon - Only one instance if it should open - Tapping the app icons grid should properly open the g-s overview - Tapping on dock icons when in overview mode should work normally [ Regression potential ] Taps on other gnome-shell buttons could not work poperly (like some menu items or app grid) ProblemType: BugDistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 28 19:47:17 2018 InstallationDate: Installed on 2018-01-28 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802700] Re: Cannot install graphic drivers
It seems you manually installed AMDGPU-Pro. Your system should go back to normal if you remove it. -- 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/1802700 Title: Cannot install graphic drivers Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: i just instal linux 18.04 but the graphic drivers not installed, so my maximum resolution is 360p. I use Lenovo G50-80 with graphic AMR radeon M330 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 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 Nov 11 12:01:41 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 18.20-673703, 4.15.0-29-generic, x86_64: installed amdgpu, 18.20-673703, 4.15.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:390c] Subsystem: Lenovo Radeon R5 M330 [17aa:390c] InstallationDate: Installed on 2018-11-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO INVALID ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=2c4eae76-fae9-48ac-98de-2dfbd276535b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN93WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: NANANANA NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNANANANANODPK:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.version: INVALID dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/linux/+bug/1802700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803032] [NEW] LibreOffice crashes kernel while trying to open 500+ new windows.
Public bug reported: I am trying to combine 500+ .tiff files into a single .pdf file. I read that LibreOffice could do this. I started LibreOffice and selected the .tiff files. LibreOffice immediately tried to open 500+ new windows. I tried to close LibreOffice but got an error window warning that LibreOffice is not responding. When I selected kill any way, nothing happened. Eventually the entire screen went black - the kernel had crashed. Had to reboot my machine. Still need to convert many tiff files to a single pdf file (preferably without using ghostscript like tiff2pdf). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 12 22:19:13 2018 InstallationDate: Installed on 2018-10-25 (19 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1803032 Title: LibreOffice crashes kernel while trying to open 500+ new windows. Status in libreoffice package in Ubuntu: New Bug description: I am trying to combine 500+ .tiff files into a single .pdf file. I read that LibreOffice could do this. I started LibreOffice and selected the .tiff files. LibreOffice immediately tried to open 500+ new windows. I tried to close LibreOffice but got an error window warning that LibreOffice is not responding. When I selected kill any way, nothing happened. Eventually the entire screen went black - the kernel had crashed. Had to reboot my machine. Still need to convert many tiff files to a single pdf file (preferably without using ghostscript like tiff2pdf). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 12 22:19:13 2018 InstallationDate: Installed on 2018-10-25 (19 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803021] [NEW] No tutorials
Public bug reported: When selecting `Help -> Tutorials` the error message is shown and no tutorial is loaded. Failed to load the requested file /usr/share/inkscape/tutorials /tutorial-basic.svg ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: i3 Date: Tue Nov 13 05:18:54 2018 InstallationDate: Installed on 2018-11-01 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: inkscape UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1803021 Title: No tutorials Status in inkscape package in Ubuntu: New Bug description: When selecting `Help -> Tutorials` the error message is shown and no tutorial is loaded. Failed to load the requested file /usr/share/inkscape/tutorials /tutorial-basic.svg ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: i3 Date: Tue Nov 13 05:18:54 2018 InstallationDate: Installed on 2018-11-01 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: inkscape UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1803021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1739931] Re: Separator lines in shell popup menus are too faint to see
OK, I wiped another laptop and installed 18.04.1 fresh with only the above fix. Verified bug fixed with no regressions, using 3.28.3-0ubuntu0.18.04.3. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1739931 Title: Separator lines in shell popup menus are too faint to see Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Bionic: Won't Fix Status in ubuntu-themes source package in Bionic: Won't Fix Bug description: [ Impact ] Separators in gnome-shell menuitems are not visible [ Test case ] 1. Right - Click on a dock icon 2. Separators between menu items should be visible [ Regression potential ] Nothing known when I click on the dock icons, some of the lines in the popup menus are blank and some of them appear to be incorrect. see top left of attached screenshot. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 23 22:24:40 2017 InstallationDate: Installed on 2016-08-18 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743058] Re: Input field height changes slightly when entering in st password fields.
OK, I wiped another laptop and installed 18.04.1 fresh with only the above fix. Verified bug fixed with no regressions, using 3.28.3-0ubuntu0.18.04.3. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1743058 Title: Input field height changes slightly when entering in st password fields. Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Bug description: It appears there is the font/height rendering issue in multiple places. With the textentry "jumping" in height slightly upon entering anything. I have observed this on the login screen password entry screen, lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard. It almost feels as if the "dots" of the hidden password are either of larger font size and/or bold, whilst an empty text field and/or unfocused text field font is either smaller and or regular (non-bold). Resulting in a rendering / layout jiggles. [ Impact ] Password input field increase the vertical size as soon as the user types something [ Test case ] 1. Run: pkexec true 2. Start typing something 3. The input field should not resize vertically This works only in case the big-font a11y option is not enabled [ Regression potential ] Input Text entries might be slightly taller than they were To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard Status in OEM Priority Project: Fix Committed Status in OEM Priority Project bionic series: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Bug description: [Impact] Unable to type capital letters using onscreen keyboard: [Test Case] 1. Launch a program where you can type text (gedit for example). 2. Activate on screen keyboard (by touching the screen, foe example). 3. Notice all the keys on the on screen keyboard display lowercase letters. 4. Begin typing. Lowercase characters are typed into the text area. 5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the on screen keyboard. 6. Notice all the keys on the on screen keyboard now display capital letters. 7. Begin typing. 8. A lowercase character will be typed into the text area. This is not expected behavior. Instead, a capital letter should have been typed. (All the keys on the on screen keyboard revert to lower case. This is expected, since the on screen shift key would need to be pressed again in order to attempt to type another capital character). [Regression Potential] Please make sure that osk correctly revert to lower case. Also make sure the physical keyboard correctly works after using the osk. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: caribou 0.4.21-2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 5 10:57:04 2017 InstallationDate: Installed on 2017-11-03 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: caribou UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] Re: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds
Please run this command to automatically send more system information: apport-collect 1803016 Please also run this command: dpkg -l > allpackages.txt and attach the resulting file 'allpackages.txt'. ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) ** Tags added: cosmic ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802976] Re: Horizontal black bars flicker across the screen
** Tags added: amdgpu radeon ** Summary changed: - Horizontal black bars flicker across the screen + [amdgpu] Horizontal black bars flicker across the screen ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1802976 Title: [amdgpu] Horizontal black bars flicker across the screen Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: 1) Ubuntu 18.04.1 LTS 31.4 GiB Ram AMD® Ryzen 5 1600 six-core processor × 12 AMD® Radeon (tm) rx 480 graphics 3.28.2 gnome 64-bit os 2) ?what? 3) see the desktop and apps without horizontal black bars flickering across the screen 4) horizontal black bars flicker across the screen over the desktop, apps and whatever is on screen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 12 19:45:06 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 [174b:e347] InstallationDate: Installed on 2018-11-10 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=e7adf075-12a7-4981-980a-dcdb43eeb260 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4023 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS 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.:bvr4023:bd08/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/xserver-xorg-video-amdgpu/+bug/1802976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727225] Re: Excessive window snapping while dragging, looks glitchy
** Changed in: gnome-shell (Ubuntu) Importance: Low => Medium ** Changed in: mutter (Ubuntu) Importance: Low => Medium ** Tags removed: artful -- 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/1727225 Title: Excessive window snapping while dragging, looks glitchy Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Gnome Shell seems to do excessive window snapping while dragging windows. If I drag a window over the top of another, the top of both windows briefly snap together before the window drag continues. To the untrained eye this just looks like a visual glitch in the rendering and an excuse to declare gnome-shell is less smooth than other shells. It's also not useful to snap all such combinations of window edges like that, so I suggest turning some of them off. For example, don't snap the same edges of two windows when one is overlapping the other already. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 15:55:31 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (175 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1727225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803016] [NEW] Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds
Public bug reported: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description:Ubuntu 18.10 Release:18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa-driver ** Tags added: alsa-driver -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1803016 Title: Ubuntu 18.10 and ASUS Q536FD integrated Speakers not sounds Status in alsa-driver package in Ubuntu: New Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1803016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802574] Re: laptop screen never comes on after undock / sleep / open of laptop
OK. This sounds related to bug 1723025 or one of: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=multimonitor ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Tags added: multimonitor ** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1802574 Title: laptop screen never comes on after undock / sleep / open of laptop Status in gdm3 package in Ubuntu: New Bug description: I use a ThinkPad dock with two monitors plugged into it. I have a udev job configured to automatically put my laptop to sleep when I undock it. So, I'm working on my laptop in the dock. I undock it and drop it into my backpack. All by itself, it goes to sleep. A few minutes later, I open the laptop and it wakes up. I know it's up because the power light and LED on the lid both go to solid. But the laptop screen never comes on. I've undocked twice since upgrading to 18.10. This has happened both times. It's a regression from 18.04.1. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 9 13:18:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (43 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-11-08 (1 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1802574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802584] Re: A good amount of pulseaudio modules can't be loaded
Sorry, but we can't support packages from PPAs here. You have installed: libpulse0 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] libpulsedsp 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] pulseaudio-utils 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] Please try (at least temporarily) removing that PPA from the machine, reboot, and tell us if that fixes the problem. If not, then please run: dpkg -l > allpackages.txt and attach the file 'allpackages.txt'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1802584 Title: A good amount of pulseaudio modules can't be loaded Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . Am I forgetting something? Why can't I load them? Why are they not listed? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hadware 17117 F...m pulseaudio /dev/snd/controlC1: hadware 17117 F pulseaudio /dev/snd/controlC0: hadware 17117 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-07 (309 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: pulseaudio 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-36-generic x86_64 UnreportableReason: Ce paquet n'est pas officiellement pris en charge par Ubuntu. Veuillez désinstaller tout paquet tiers et réessayer. UpgradeStatus: Upgraded to bionic on 2018-10-07 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET49WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV000BUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BV000BUS:pvrThinkPadT450:rvnLENOVO:rn20BV000BUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV000BUS dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen
On the login screen, click on the gear (cog) icon :) -- 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/1802573 Title: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a fresh install of 18.10 on an old Thinkpad x220. Everything works fine with the internal display or an external Dell G2410 (1920x1080) connected via VGA. But when I try to switch to an external BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a time and then it flashes to black. This happens consistently for minutes--it never "settles down". I've tried the default configuration as well as copying xorg.conf from /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both xorg configurations with nomodeset in the bootloader and without. I have not been able to find any configuration that allows this external DisplayPort display to work. The same hardware combination works fine in Windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Nov 9 13:10:59 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2018-11-09 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 42872WU ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel" Driver "intel" #Option "AccelMethod" "uxa" EndSection dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 42872WU 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:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 42872WU dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802573/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802402] Re: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound
Sorry, that suggestion was based on the package not being in Ubuntu 18.10. I did not realize it is a required package in 18.04. To fix what was removed by the previous command you can reinstall the missing packages by running: sudo apt install cheese gnome-control-center gnome-initial-setup gnome- video-effects gstreamer1.0-plugins-good libasound2-plugins libcanberra- pulse libcheese-gtk25 libcheese8 libjack-jackd2-0 pulseaudio pulseaudio- module-bluetooth rhythmbox rhythmbox-plugin-alternative-toolbar rhythmbox-plugins totem totem-plugins ubuntu-desktop ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1802402 Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound Status in pulseaudio package in Ubuntu: New Bug description: I expected speaker and headphones to work. I found speaker silent and headphones slight popping sound only. But HDMI audio works, also speaker and headphones work on my dualbooted windows 10. Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jita 1798 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 22:45:36 2018 InstallationDate: Installed on 2018-11-07 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jita 1798 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UNR.T157 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UNR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: Tarasovic Jiri dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.T157:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UNR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-11-08T22:34:00.520280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
the mutter tested version is: 3.28.3-2~ubuntu18.04.2, which is the same as in #14. -- 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/1730211 Title: Unable to type capital letters using onscreen keyboard Status in OEM Priority Project: Fix Committed Status in OEM Priority Project bionic series: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Bug description: [Impact] Unable to type capital letters using onscreen keyboard: [Test Case] 1. Launch a program where you can type text (gedit for example). 2. Activate on screen keyboard (by touching the screen, foe example). 3. Notice all the keys on the on screen keyboard display lowercase letters. 4. Begin typing. Lowercase characters are typed into the text area. 5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the on screen keyboard. 6. Notice all the keys on the on screen keyboard now display capital letters. 7. Begin typing. 8. A lowercase character will be typed into the text area. This is not expected behavior. Instead, a capital letter should have been typed. (All the keys on the on screen keyboard revert to lower case. This is expected, since the on screen shift key would need to be pressed again in order to attempt to type another capital character). [Regression Potential] Please make sure that osk correctly revert to lower case. Also make sure the physical keyboard correctly works after using the osk. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: caribou 0.4.21-2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 5 10:57:04 2017 InstallationDate: Installed on 2017-11-03 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: caribou UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
Test pass on bionic: 1. on a laptop with a touch screen, touch the file manager icon on the launcher. Saw two file manager is launched. 2. enable proposed channel 3. apt install gnome-shell, it upgrades to version 3.28.3-0ubuntu0.18.04.3 4. log out and log in. 5. touch file manager icon on the launcher, confirmed that only one file manager is launched. ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1745888 Title: Two instances of a program launch whenever you touch a favorites icon Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Bug description: [ Impact ] Using a touch screen, if you tap on a favorites icon on the ubuntu dock, two (or more) instances of an application launch. [ Test case ] - Look for xterm in gnome-shell activities and add it to favourtes - With the ubuntu-dock showing in the desktop, touch the xterm icon - Only one instance if it should open - Tapping the app icons grid should properly open the g-s overview - Tapping on dock icons when in overview mode should work normally [ Regression potential ] Taps on other gnome-shell buttons could not work poperly (like some menu items or app grid) ProblemType: BugDistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 28 19:47:17 2018 InstallationDate: Installed on 2018-01-28 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789356] Re: Dark purple (noise) background flashes up briefly during the login animation since Yaru was introduced
It does make this bug worse. The original bug was barely noticeable, but with that fix it's really a bright and obvious glitch. What we could do is release the SRU but just keep this bug open. -- 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/1789356 Title: Dark purple (noise) background flashes up briefly during the login animation since Yaru was introduced Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Cosmic: Fix Committed Bug description: [Impact] Dark purple (noise) background flashes up briefly (for a split second) during the login animation. The login screen and gnome-shell's system background are meant to be the same image so that the login procedure can VT switch without the user noticing. Then the final desktop expands over the system background. However it appears the login background and system background are not the same image any more, causing a visible glitch during login. [Test Case] 1. Install new version, logout 2. Log in into GDM -> Check that at login startup, the background matches GDM ones (same color, same gradient) 3. Logout, install gnome-session 4. Reboot so that GDM takes gnome-session into account 5. Select GNOME session and login -> At login startup, the background will matche the GNOME default one (from the lockscreen: grey noise), which matches GDM one if reset to default GNOME via update-alternatives. [Regression Potential] This code is loaded at session startup, if there is a syntax error, the session wouldn't start at all. This has been of course tested before committed (both on ubuntu and GNOME sessions) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.2 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Aug 28 14:19:48 2018 Dependencies: InstallationDate: Installed on 2018-05-26 (93 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
Hmm, that's not quite right. The Xorg fix has landed, but the Wayland fix has not. Both require changes to mutter. ** Changed in: mutter (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: Monitor is set to 144hz, but on Wayland it visually fails to go above 60Hz. I have confirmed the monitor is running at 144Hz during the Wayland session, and that is also the setting in the Settings control panel. Using the additional NVidia drivers installed using the Ubuntu software control panel. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libwayland-bin (not installed) ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 08:43:29 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070] [1462:3301] InstallationDate: Installed on 2018-03-30 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-P 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.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802911] Re: [snap] LibreOffice 6.1.3.2 (90) doesn't launch
``` $ snap changes libreoffice IDStatus Spawn Ready Summary 1032 Doneyesterday at 12:53 GMT yesterday at 13:00 GMT Refresh "libreoffice" snap $ snap changes libreoffice --abs-time IDStatus Spawn Ready Summary 1032 Done2018-11-12T12:53:53Z 2018-11-12T13:00:01Z Refresh "libreoffice" snap ``` That was just my refresh from `edge` to `beta` and then `candidate`/`stable`... I'm going to assume this was a problem with the strange and frustrating problem in #2 that I was unable to diagnose (and that I'm pretty sure I've come across before) and close the bug, sorry for the noise :( ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Invalid -- 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/1802911 Title: [snap] LibreOffice 6.1.3.2 (90) doesn't launch Status in libreoffice package in Ubuntu: Invalid Bug description: LibreOffice doesn't launch on 6.1.3.2 (90) in `candidate` on core 16-2.36.1+git1007.f72779e (5920) in `edge`, it just hangs, with no Terminal output, but has the following denials in `journalctl -f`: ``` Nov 12 12:38:19 adam-thinkpad-t430 audit[31984]: AVC apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 12 12:38:19 adam-thinkpad-t430 kernel: audit: type=1400 audit(1542026299.589:542): apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ``` ``` $ snap info libreoffice tracking: candidate refresh-date: 6 days ago, at 08:50 GMT channels: stable:6.1.2.1 (86) 501MB - candidate: 6.1.3.2 (90) 507MB - < beta: ↑ edge: ↑ installed: 6.1.3.2 (90) 507MB - $ snap version snap2.36.1+git1007.f72779e~ubuntu16.04.1 snapd 2.36.1+git1007.f72779e~ubuntu16.04.1 series 16 ubuntu 18.10 kernel 4.18.0-11-generic $ snap info core tracking: edge refresh-date: today at 12:08 GMT channels: stable:16-2.35.5 (5742) 92MB - candidate: 16-2.35.5 (5742) 92MB - beta: 16-2.36.1 (5897) 92MB - edge: 16-2.36.1+git1007.f72779e (5920) 92MB -< installed: 16-2.36.1+git1007.f72779e (5920) 92MB core ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802911/+subscriptions -- Mailing list: https://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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
There is not yet a fix for this problem. Do you known any reliable way to reproduce it? Il giorno lun 12 nov 2018, 23:50 Mike L <1769...@bugs.launchpad.net> ha scritto: > Land for dingo? What are the possibilities of a backport to both 18.04 > and 18.10? Couldn't this be considered a security vulnerability? It can > theoretically be used to close someone else's work out without saving, > depending on the application. > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1769383 > > Title: > Ubuntu dock/launcher is shown on the lock screen > > Status in gnome-shell package in Ubuntu: > Incomplete > Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: > In Progress > > Bug description: > After an update from ubuntu 16.04 to 18.04 the dock is aviable on the > lockscreen after user login. > I did not configure this knowingly. Also i can start every application > which is available on the dock. > Settings, virtual box, visualstudio code and so on. > > After the update to 18.04 i just configure the screen frequency to > 144Hz and the night mode on. And attach the dock on bottom. > > I later undid these customizations back to configuration before, but > the dock is stil aviable on lockscreen. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gnome-settings-daemon 3.28.1-0ubuntu1 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sat May 5 18:30:16 2018 > InstallationDate: Installed on 2018-04-08 (27 days ago) > InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 > (20180228) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=de_DE.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-settings-daemon > UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) > --- > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.04 > InstallationDate: Installed on 2018-04-08 (27 days ago) > InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 > (20180228) > NonfreeKernelModules: nvidia_modeset nvidia > Package: gnome-shell-extension-ubuntu-dock 0.9.1 > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=de_DE.UTF-8 >SHELL=/bin/bash > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Tags: bionic > Uname: Linux 4.15.0-20-generic x86_64 > UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-shell; > component=main; status=Incomplete; importance=High; assignee=None; > Launchpad-Bug: distribution=ubuntu; > sourcepackage=gnome-shell-extension-ubuntu-dock; component=main; status=In > Progress; importance=High; assignee=andrea.azzar...@canonical.com; > Launchpad-Bug-Tags: amd64 apport-bug apport-collected bionic > Launchpad-Bug-Information-Type: Public Security > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: yes > Launchpad-Bug-Commenters: ads2 azzar1 bog-radu didrocks helgalo > janitor jenia leozinho29-eu mchaberski merlijn-sebrechts plurtu seb128 > simpre tomreyn > Launchpad-Bug-Reporter: Jenka Hanson (jenia) > Launchpad-Bug-Modifier: Mike L (helgalo) > Launchpad-Message-Rationale: Assignee > Launchpad-Message-For: azzar1 > -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Land for dingo? What are the possibilities of a backport to both 18.04 and 18.10? Couldn't this be considered a security vulnerability? It can theoretically be used to close someone else's work out without saving, depending on the application. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I did a clean install of Cosmic and the bug is present as well for me also. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802700] Re: Cannot install graphic drivers
Yes, i have these graphics card : GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:390c] Subsystem: Lenovo Radeon R5 M330 [17aa:390c] But they are not installed in my ubuntu. I just install Ubuntu, where before i use windows. When windows, i just install the drivers of graphics card, but in linux ubuntu, i dont know how to install that. So that my graphics resolution is bad. I see my friend's ubuntu updates and he has installed driver graphics card, but i dont have that. like the pict i attcahed. ** Attachment added: "Screenshot from 2018-11-13 06-08-26.png" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802700/+attachment/5212036/+files/Screenshot%20from%202018-11-13%2006-08-26.png -- 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/1802700 Title: Cannot install graphic drivers Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: i just instal linux 18.04 but the graphic drivers not installed, so my maximum resolution is 360p. I use Lenovo G50-80 with graphic AMR radeon M330 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 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 Nov 11 12:01:41 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 18.20-673703, 4.15.0-29-generic, x86_64: installed amdgpu, 18.20-673703, 4.15.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:390c] Subsystem: Lenovo Radeon R5 M330 [17aa:390c] InstallationDate: Installed on 2018-11-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO INVALID ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=2c4eae76-fae9-48ac-98de-2dfbd276535b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN93WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: NANANANA NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNANANANANODPK:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.version: INVALID dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/linux/+bug/1802700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802999] Re: /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:cancel_current_search:execute_search
*** This bug is a duplicate of bug 1797851 *** https://bugs.launchpad.net/bugs/1797851 ** This bug has been marked a duplicate of bug 1797851 /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:stop_search:disconnect_model_handlers -- 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/1802999 Title: /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:cancel_current_search:execute_search Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/c4d1582805253e729827c2fdce288bcca162ddca 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/nautilus/+bug/1802999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802998] [NEW] /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:cancel_current_search:handle_xubuntu_cancel
*** This bug is a duplicate of bug 1797851 *** https://bugs.launchpad.net/bugs/1797851 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/ab71b8c5bbbf4c24ea5d06688a828d8fd0fff27b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1802998 Title: /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:cancel_current_search:handle_xubuntu_cancel Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/ab71b8c5bbbf4c24ea5d06688a828d8fd0fff27b 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/nautilus/+bug/1802998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802998] Re: /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:cancel_current_search:handle_xubuntu_cancel
*** This bug is a duplicate of bug 1797851 *** https://bugs.launchpad.net/bugs/1797851 ** This bug has been marked a duplicate of bug 1797851 /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:stop_search:disconnect_model_handlers -- 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/1802998 Title: /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:cancel_current_search:handle_xubuntu_cancel Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/ab71b8c5bbbf4c24ea5d06688a828d8fd0fff27b 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/nautilus/+bug/1802998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802999] [NEW] /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:cancel_current_search:execute_search
*** This bug is a duplicate of bug 1797851 *** https://bugs.launchpad.net/bugs/1797851 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/c4d1582805253e729827c2fdce288bcca162ddca contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1802999 Title: /usr/bin/nautilus:11:g_type_check_instance_cast:NAUTILUS_SEARCH_PROVIDER:nautilus_search_engine_stop:cancel_current_search:execute_search Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/c4d1582805253e729827c2fdce288bcca162ddca 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/nautilus/+bug/1802999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1671339] Re: After resumed from suspend, desktop wallpaper does not get drawn correctly on Nvidia graphics
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1671339 Title: After resumed from suspend, desktop wallpaper does not get drawn correctly on Nvidia graphics Status in nautilus package in Ubuntu: Confirmed Bug description: This is a known issue on Nvidia driver for a long time. Originally it only happens on Unity Launcher, now it also affects desktop background. To solve/workaround this, the background needs to be redrawn upon resume. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nautilus 1:3.20.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 8 23:34:27 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+24'" InstallationDate: Installed on 2017-03-08 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170307) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1671339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755232] Re: Xorg crashes when tapping Unity system tray icons
This is fixed in https://gitlab.freedesktop.org/xorg/xserver/commit/35e5a76cc1d02801fadd49d12e60664b02e4bebc Will be in next xorg revision (if not cherry-picked earlier) ** Changed in: xorg (Ubuntu) Status: New => In Progress ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1755232 Title: Xorg crashes when tapping Unity system tray icons Status in xorg package in Ubuntu: In Progress Bug description: This bug requires some prerequisites to reproduce: 0. Make sure you've got multitouch-enable display 1. Start Unity+xorg session 2. Verify that four-finger tap gesture works (shows unity app search tool) 3. Wait some time for this gesture to stop working - this is another bug, not necessarily xorg one, already known and thought to be connected with Google Chrome running. 4. Once it stops working, quickly tap all icons in the Unity system tray like you would be pretending to play a piano (tapping them individually or slowly does not cause any problems). 5. Xorg crashes immediately. This scenario is 100% reproducible on my setup. I recompiled xorg with debug info enabled and got this nice trace: [ 22705.385] (EE) [ 22705.385] (EE) Backtrace: [ 22705.385] (EE) 0: /usr/lib/xorg/Xorg (OsSigHandler+0x3b) [0x562a36b6f25f] [ 22705.387] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (__restore_rt+0x0) [0x7f382f64414f] [ 22705.389] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f382f2880bb] [ 22705.391] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16d) [0x7f382f289f5d] [ 22705.393] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x2fd) [0x7f382f2d22bd] [ 22705.395] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0xa3a) [0x7f382f2d9f7a] [ 22705.397] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0x2b2e) [0x7f382f2de0fe] [ 22705.399] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (cfree+0x6e) [0x7f382f2e044e] [ 22705.400] (EE) 8: /usr/lib/xorg/Xorg (FreeGrab+0xb8) [0x562a3699ac32] [ 22705.400] (EE) 9: /usr/lib/xorg/Xorg (DeactivatePointerGrab+0x279) [0x562a3698428f] [ 22705.400] (EE) 10: /usr/lib/xorg/Xorg (DeleteWindowFromAnyEvents+0x70) [0x562a3698ea8b] [ 22705.401] (EE) 11: /usr/lib/xorg/Xorg (UnrealizeTree+0x100) [0x562a369bc371] [ 22705.401] (EE) 12: /usr/lib/xorg/Xorg (UnmapWindow+0x195) [0x562a369bc689] [ 22705.402] (EE) 13: /usr/lib/xorg/Xorg (ProcUnmapWindow+0x74) [0x562a3696e488] [ 22705.402] (EE) 14: /usr/lib/xorg/Xorg (Dispatch+0x21e) [0x562a3696d2d9] [ 22705.402] (EE) 15: /usr/lib/xorg/Xorg (dix_main+0x651) [0x562a3697c4e3] [ 22705.403] (EE) 16: /usr/lib/xorg/Xorg (main+0x28) [0x562a3695cf22] [ 22705.405] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7f382f2721c1] [ 22705.405] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x562a3695ce1a] [ 22705.407] (EE) 19: ? (?+0x2a) [0x2a] Looks like FreeGrab tries to free pGrab for the second time (some multithreading issue?) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Mar 12 17:03:34 2018 DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2017-09-01 (192 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HES2130Q ProcEnviron: LANGUAGE=pl_PL PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi.ec_freeze_events=Y acpi.ec_suspend_yield=Y intel_pstate=skylake_hwp i915.enable_guc_loading=1 i915.enable_guc_submission=1
[Desktop-packages] [Bug 1799230] Re: [SRU] libreoffice 6.0.7 for bionic
** Changed in: libreoffice (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: libreoffice-l10n (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-l10n in Ubuntu. https://bugs.launchpad.net/bugs/1799230 Title: [SRU] libreoffice 6.0.7 for bionic Status in libreoffice package in Ubuntu: Triaged Status in libreoffice-l10n package in Ubuntu: Triaged Status in libreoffice source package in Bionic: In Progress Status in libreoffice-l10n source package in Bionic: In Progress Bug description: [Impact] * LibreOffice 6.0.7 is the seventh bugfix release of the fresh 6.0 line. Version 6.0.6 is currently in bionic. For a list of fixed bugs compared to 6.0.6 see the list of bugs fixed in the three release candidates: https://wiki.documentfoundation.org/Releases/6.0.7/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.0.7/RC2#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.0.7/RC3#List_of_fixed_bugs (that's a total of 66 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 66 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802982] [NEW] GNOME Software keeps logging out of the Ubuntu One account
Public bug reported: Every time I restart the system, my Ubuntu One account that is was connected to ubuntu Software keeps disconnected. This doesn't happen with the Snap account, only with the Ubuntu One account. Description:Ubuntu 18.10 Release:18.10 gnome-software: Instalado: 3.30.2-0ubuntu8 Candidato: 3.30.2-0ubuntu8 Tabela de versão: *** 3.30.2-0ubuntu8 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.30.2-0ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 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/1802982 Title: GNOME Software keeps logging out of the Ubuntu One account Status in gnome-software package in Ubuntu: New Bug description: Every time I restart the system, my Ubuntu One account that is was connected to ubuntu Software keeps disconnected. This doesn't happen with the Snap account, only with the Ubuntu One account. Description: Ubuntu 18.10 Release: 18.10 gnome-software: Instalado: 3.30.2-0ubuntu8 Candidato: 3.30.2-0ubuntu8 Tabela de versão: *** 3.30.2-0ubuntu8 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.30.2-0ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1802982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802981] [NEW] Lockscreen shown dash when screen was locked
Public bug reported: I decided to leave my laptop and came back a few minutes later, and I noticed that the dash was visible from the lockscreen. Not good. Running Ubuntu 18.10 as a fresh install. Was able to quit and open applications from the dash. Uncertain if that's a security risk or not. Uncertain of how to reproduce as in what triggered it. Dash should definitely not be visible when the lockscreen is active. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 12 15:41:14 2018 InstallationDate: Installed on 2018-11-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1802981 Title: Lockscreen shown dash when screen was locked Status in gdm3 package in Ubuntu: New Bug description: I decided to leave my laptop and came back a few minutes later, and I noticed that the dash was visible from the lockscreen. Not good. Running Ubuntu 18.10 as a fresh install. Was able to quit and open applications from the dash. Uncertain if that's a security risk or not. Uncertain of how to reproduce as in what triggered it. Dash should definitely not be visible when the lockscreen is active. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 12 15:41:14 2018 InstallationDate: Installed on 2018-11-11 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1802981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743058] Re: Input field height changes slightly when entering in st password fields.
I don't think this is the case... At least I didn't get this regression in my vm. Is it yours clean? Aslo I don't see how this could happen, as per the pure diff. Is your gdm3 altrnative setup properly? -- 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/1743058 Title: Input field height changes slightly when entering in st password fields. Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Bug description: It appears there is the font/height rendering issue in multiple places. With the textentry "jumping" in height slightly upon entering anything. I have observed this on the login screen password entry screen, lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard. It almost feels as if the "dots" of the hidden password are either of larger font size and/or bold, whilst an empty text field and/or unfocused text field font is either smaller and or regular (non-bold). Resulting in a rendering / layout jiggles. [ Impact ] Password input field increase the vertical size as soon as the user types something [ Test case ] 1. Run: pkexec true 2. Start typing something 3. The input field should not resize vertically This works only in case the big-font a11y option is not enabled [ Regression potential ] Input Text entries might be slightly taller than they were To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797147] Re: Backport PRIME switching fixes to Ubuntu 18.04
This bug was fixed in the package ubuntu-drivers-common - 1:0.5.2.2 --- ubuntu-drivers-common (1:0.5.2.2) bionic; urgency=medium * gpu-manager.c: - Improve pid detection, and restore the default pci power control profile in performance mode (LP: #1797147). -- Alberto Milone Wed, 10 Oct 2018 17:01:27 +0200 ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-prime (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1797147 Title: Backport PRIME switching fixes to Ubuntu 18.04 Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] A recent update (LP: #1778011) in 18.04 has restored the PRIME switching mechanism in Gdm 3 only, while still leaving out support for other login managers (such as Lightdm, and SDDM). In addition to this, we should restore the default pci power control profile for the dGPU when re-enabling performance mode, as we do in Ubuntu 18.10. [Test Case] 1) Make sure that you are using a login manager such as Lightdm or SDDM. 2) Enable the bionic-proposed repository, and install the new "ubuntu- drivers-common", and the new nvidia-prime. 3) Make sure the nvidia packages are installed and working, and enable power saving mode: sudo prime-select intel 4) Log out, log back in, and check that the nvidia kernel module is not loaded: lsmod | grep nvidia 5) Select performance mode: sudo prime-select nvidia 6) Log out, and log back in 7) Check if the nvidia driver loaded: lsmod | grep nvidia [Regression Potential] Low, as switching already fails in 18.04, since X is started before udev adds back the dGPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1797147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797147] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1797147 Title: Backport PRIME switching fixes to Ubuntu 18.04 Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] A recent update (LP: #1778011) in 18.04 has restored the PRIME switching mechanism in Gdm 3 only, while still leaving out support for other login managers (such as Lightdm, and SDDM). In addition to this, we should restore the default pci power control profile for the dGPU when re-enabling performance mode, as we do in Ubuntu 18.10. [Test Case] 1) Make sure that you are using a login manager such as Lightdm or SDDM. 2) Enable the bionic-proposed repository, and install the new "ubuntu- drivers-common", and the new nvidia-prime. 3) Make sure the nvidia packages are installed and working, and enable power saving mode: sudo prime-select intel 4) Log out, log back in, and check that the nvidia kernel module is not loaded: lsmod | grep nvidia 5) Select performance mode: sudo prime-select nvidia 6) Log out, and log back in 7) Check if the nvidia driver loaded: lsmod | grep nvidia [Regression Potential] Low, as switching already fails in 18.04, since X is started before udev adds back the dGPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1797147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797147] Re: Backport PRIME switching fixes to Ubuntu 18.04
This bug was fixed in the package nvidia-prime - 0.8.8.2 --- nvidia-prime (0.8.8.2) bionic; urgency=medium * prime-switch: - Give udev the time to add the drm device. Fixes a race condition that causes problems when using lightdm and sddm (LP: #1797147). -- Alberto Milone Wed, 10 Oct 2018 17:59:03 +0200 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1797147 Title: Backport PRIME switching fixes to Ubuntu 18.04 Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] A recent update (LP: #1778011) in 18.04 has restored the PRIME switching mechanism in Gdm 3 only, while still leaving out support for other login managers (such as Lightdm, and SDDM). In addition to this, we should restore the default pci power control profile for the dGPU when re-enabling performance mode, as we do in Ubuntu 18.10. [Test Case] 1) Make sure that you are using a login manager such as Lightdm or SDDM. 2) Enable the bionic-proposed repository, and install the new "ubuntu- drivers-common", and the new nvidia-prime. 3) Make sure the nvidia packages are installed and working, and enable power saving mode: sudo prime-select intel 4) Log out, log back in, and check that the nvidia kernel module is not loaded: lsmod | grep nvidia 5) Select performance mode: sudo prime-select nvidia 6) Log out, and log back in 7) Check if the nvidia driver loaded: lsmod | grep nvidia [Regression Potential] Low, as switching already fails in 18.04, since X is started before udev adds back the dGPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1797147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802976] [NEW] Horizontal black bars flicker across the screen
Public bug reported: 1) Ubuntu 18.04.1 LTS 31.4 GiB Ram AMD® Ryzen 5 1600 six-core processor × 12 AMD® Radeon (tm) rx 480 graphics 3.28.2 gnome 64-bit os 2) ?what? 3) see the desktop and apps without horizontal black bars flickering across the screen 4) horizontal black bars flicker across the screen over the desktop, apps and whatever is on screen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 12 19:45:06 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 [174b:e347] InstallationDate: Installed on 2018-11-10 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=e7adf075-12a7-4981-980a-dcdb43eeb260 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4023 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS 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.:bvr4023:bd08/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1802976 Title: Horizontal black bars flicker across the screen Status in xorg package in Ubuntu: New Bug description: 1) Ubuntu 18.04.1 LTS 31.4 GiB Ram AMD® Ryzen 5 1600 six-core processor × 12 AMD® Radeon (tm) rx 480 graphics 3.28.2 gnome 64-bit os 2) ?what? 3) see the desktop and apps without horizontal black bars flickering across the screen 4) horizontal black bars flicker across the screen over the desktop, apps and whatever is on screen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 12 19:45:06 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 [174b:e347] InstallationDate: Installed on 2018-11-10 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=e7adf075-12a7-4981-980a-dcdb43eeb260 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
This bug was fixed in the package mutter - 3.30.1-4 --- mutter (3.30.1-4) unstable; urgency=medium [ Andrea Azzarone ] * d/p/x11-close-display-in-an-idle-function.patch: - close the x11 display in an idle function. This fixes a crash when running 'gnome-shell --replace'. [ Daniel van Vugt] * Drop clutter-Smooth-out-master-clock-to-smooth-visuals.patch: It was abandoned upstream, but also seems to be limiting refresh rates in Xorg sessions to 60Hz when previously they were unlimited (LP: #1763892). -- Andrea Azzarone Mon, 12 Nov 2018 11:53:37 + ** Changed in: mutter (Ubuntu) Status: In Progress => 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/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Confirmed Status in mutter package in Ubuntu: Fix Released Bug description: Monitor is set to 144hz, but on Wayland it visually fails to go above 60Hz. I have confirmed the monitor is running at 144Hz during the Wayland session, and that is also the setting in the Settings control panel. Using the additional NVidia drivers installed using the Ubuntu software control panel. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libwayland-bin (not installed) ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 08:43:29 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070] [1462:3301] InstallationDate: Installed on 2018-03-30 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-P 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.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789476] Re: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled
This bug was fixed in the package glib2.0 - 2.56.3-0ubuntu0.18.04.1 --- glib2.0 (2.56.3-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1794544) + The documentation for G_GNUC_MALLOC has changed to be more restrictive to avoid miscompilations; you should check whether any uses of it in your code are appropriate + Fix cancellation of g_subprocess_communicate_async() calls + Bug fixes: + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 + GBookmarkFile: nullptr access in current_element + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char + Backport g_subprocess_communicate() cancellation fixes from !266 to glib-2-56 (LP: #1789476) + Many uses of G_GNUC_MALLOC are incorrect + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw + Fix persistent CI failure on glib-2-56 * debian/watch: Only find 2.56 versions. * Drop CVE-2018-16428.patch and CVE-2018-16429.patch: applied in this release -- Iain Lane Wed, 26 Sep 2018 17:35:59 +0100 ** Changed in: glib2.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16428 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16429 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1789476 Title: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Bug description: [ Impact ] Glib apps using subprocess communicate and cancellable is cancelled crashes [ Test case ] Run the attached example with gjs subprocess-cancelled.js Should not crash, or running: valgrind gjs subprocess-cancelled.js should not return any read error (as the one mentioned below) [ Regression potential ] Really low, the only thing that could happen is that the subprocess isn't really cancelled. --- Fixed upstream in https://gitlab.gnome.org/GNOME/glib/merge_requests/266 #0 g_cancellable_cancel (cancellable=0x6) at ../../glib/gio/gcancellable.c:486 #1 0x77ab8d1d in g_subprocess_communicate_cancelled (user_data=) at ../../glib/gio/gsubprocess.c:1535 -- ==25871== Memcheck, a memory error detector ==25871== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25871== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==25871== Command: gjs /tmp/subprocess-cancelled.js ==25871== ==25871== Warning: set address range perms: large range [0x377ee1e21000, 0x377f21e21000) (noaccess) ==25871== Invalid read of size 8 ==25871==at 0x4EC5604: g_subprocess_communicate_cancelled (gsubprocess.c:1535) ==25871==by 0x547A0F4: g_main_dispatch (gmain.c:3177) ==25871==by 0x547A0F4: g_main_context_dispatch (gmain.c:3830) ==25871==by 0x547A4BF: g_main_context_iterate.isra.26 (gmain.c:3903) ==25871==by 0x547A54B: g_main_context_iteration (gmain.c:3964) ==25871==by 0x6C4EDAD: ffi_call_unix64 (in /usr/lib/x86_64-linux-gnu/libffi.so.6.0.4) ==25871==by 0x6C4E71E: ffi_call (in /usr/lib/x86_64-linux-gnu/libffi.so.6.0.4) ==25871==by 0x5775607: ??? (in /usr/lib/libgjs.so.0.0.0) ==25871==by 0x5776F53: ??? (in /usr/lib/libgjs.so.0.0.0) ==25871==by 0x8A3FF6B: CallJSNative (jscntxtinlines.h:239) ==25871==by 0x8A3FF6B: js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (Interpreter.cpp:447) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1789476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794544] Re: [SRU] 2.56.3
This bug was fixed in the package glib2.0 - 2.56.3-0ubuntu0.18.04.1 --- glib2.0 (2.56.3-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1794544) + The documentation for G_GNUC_MALLOC has changed to be more restrictive to avoid miscompilations; you should check whether any uses of it in your code are appropriate + Fix cancellation of g_subprocess_communicate_async() calls + Bug fixes: + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 + GBookmarkFile: nullptr access in current_element + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char + Backport g_subprocess_communicate() cancellation fixes from !266 to glib-2-56 (LP: #1789476) + Many uses of G_GNUC_MALLOC are incorrect + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw + Fix persistent CI failure on glib-2-56 * debian/watch: Only find 2.56 versions. * Drop CVE-2018-16428.patch and CVE-2018-16429.patch: applied in this release -- Iain Lane Wed, 26 Sep 2018 17:35:59 +0100 ** Changed in: glib2.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16428 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16429 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794544 Title: [SRU] 2.56.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Bug description: [ Description ] The third stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. * New upstream release (LP: #xxx) + The documentation for G_GNUC_MALLOC has changed to be more restrictive to avoid miscompilations; you should check whether any uses of it in your code are appropriate + Fix cancellation of g_subprocess_communicate_async() calls + Bug fixes: + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 + GBookmarkFile: nullptr access in current_element + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char + Backport g_subprocess_communicate() cancellation fixes from !266 to glib-2-56 (LP: #1789476) + Many uses of G_GNUC_MALLOC are incorrect + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw + Fix persistent CI failure on glib-2-56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1794544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789476] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1789476 Title: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Bug description: [ Impact ] Glib apps using subprocess communicate and cancellable is cancelled crashes [ Test case ] Run the attached example with gjs subprocess-cancelled.js Should not crash, or running: valgrind gjs subprocess-cancelled.js should not return any read error (as the one mentioned below) [ Regression potential ] Really low, the only thing that could happen is that the subprocess isn't really cancelled. --- Fixed upstream in https://gitlab.gnome.org/GNOME/glib/merge_requests/266 #0 g_cancellable_cancel (cancellable=0x6) at ../../glib/gio/gcancellable.c:486 #1 0x77ab8d1d in g_subprocess_communicate_cancelled (user_data=) at ../../glib/gio/gsubprocess.c:1535 -- ==25871== Memcheck, a memory error detector ==25871== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25871== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==25871== Command: gjs /tmp/subprocess-cancelled.js ==25871== ==25871== Warning: set address range perms: large range [0x377ee1e21000, 0x377f21e21000) (noaccess) ==25871== Invalid read of size 8 ==25871==at 0x4EC5604: g_subprocess_communicate_cancelled (gsubprocess.c:1535) ==25871==by 0x547A0F4: g_main_dispatch (gmain.c:3177) ==25871==by 0x547A0F4: g_main_context_dispatch (gmain.c:3830) ==25871==by 0x547A4BF: g_main_context_iterate.isra.26 (gmain.c:3903) ==25871==by 0x547A54B: g_main_context_iteration (gmain.c:3964) ==25871==by 0x6C4EDAD: ffi_call_unix64 (in /usr/lib/x86_64-linux-gnu/libffi.so.6.0.4) ==25871==by 0x6C4E71E: ffi_call (in /usr/lib/x86_64-linux-gnu/libffi.so.6.0.4) ==25871==by 0x5775607: ??? (in /usr/lib/libgjs.so.0.0.0) ==25871==by 0x5776F53: ??? (in /usr/lib/libgjs.so.0.0.0) ==25871==by 0x8A3FF6B: CallJSNative (jscntxtinlines.h:239) ==25871==by 0x8A3FF6B: js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (Interpreter.cpp:447) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1789476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794544] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794544 Title: [SRU] 2.56.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Bug description: [ Description ] The third stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. * New upstream release (LP: #xxx) + The documentation for G_GNUC_MALLOC has changed to be more restrictive to avoid miscompilations; you should check whether any uses of it in your code are appropriate + Fix cancellation of g_subprocess_communicate_async() calls + Bug fixes: + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 + GBookmarkFile: nullptr access in current_element + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char + Backport g_subprocess_communicate() cancellation fixes from !266 to glib-2-56 (LP: #1789476) + Many uses of G_GNUC_MALLOC are incorrect + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw + Fix persistent CI failure on glib-2-56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1794544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802975] [NEW] package libgtkmm-2.4-doc (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/share/doc/libgtkmm-2.4-dev/examples/README" presente anche ne
Public bug reported: it appens booting my pc. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgtkmm-2.4-doc (not installed) ProcVersionSignature: Ubuntu 4.15.0-38.41-lowlatency 4.15.18 Uname: Linux 4.15.0-38-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: libgtkmm-2.4-doc:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 6 05:55:39 2018 ErrorMessage: tentata sovrascrittura di "/usr/share/doc/libgtkmm-2.4-dev/examples/README" presente anche nel pacchetto libgtkmm-2.4-dev:amd64 1:2.24.5-2 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: gtkmm2.4 Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/share/doc/libgtkmm-2.4-dev/examples/README" presente anche nel pacchetto libgtkmm-2.4-dev:amd64 1:2.24.5-2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtkmm2.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtkmm2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1802975 Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/share/doc/libgtkmm-2.4-dev/examples/README" presente anche nel pacchetto libgtkmm-2.4-dev:amd64 1:2.24.5-2 Status in gtkmm2.4 package in Ubuntu: New Bug description: it appens booting my pc. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgtkmm-2.4-doc (not installed) ProcVersionSignature: Ubuntu 4.15.0-38.41-lowlatency 4.15.18 Uname: Linux 4.15.0-38-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: libgtkmm-2.4-doc:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 6 05:55:39 2018 ErrorMessage: tentata sovrascrittura di "/usr/share/doc/libgtkmm-2.4-dev/examples/README" presente anche nel pacchetto libgtkmm-2.4-dev:amd64 1:2.24.5-2 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: gtkmm2.4 Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/share/doc/libgtkmm-2.4-dev/examples/README" presente anche nel pacchetto libgtkmm-2.4-dev:amd64 1:2.24.5-2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkmm2.4/+bug/1802975/+subscriptions -- Mailing list: https://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 1802402] Re: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound
Hello, is this a troll? I did what you said and now I cannot even enter the settings via top right corner button. I click it nothing happens. -- Původní e-mail -- Od: Daniel van Vugt Komu: jiri.taraso...@seznam.cz Datum: 12. 11. 2018 3:28:12 Předmět: [Bug 1802402] Re: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound "Please try this: sudo apt remove libjack-jackd2-0:amd64 and then reboot. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1802402 Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: I expected speaker and headphones to work. I found speaker silent and headphones slight popping sound only. But HDMI audio works, also speaker and headphones work on my dualbooted windows 10. Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jita 1798 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 22:45:36 2018 InstallationDate: Installed on 2018-11-07 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jita 1798 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UNR.T157 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UNR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: Tarasovic Jiri dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.T157:bd03/13/2018: svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR: rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UNR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-11-08T22:34:00.520280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802402/+ subscriptions " -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1802402 Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: I expected speaker and headphones to work. I found speaker silent and headphones slight popping sound only. But HDMI audio works, also speaker and headphones work on my dualbooted windows 10. Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jita 1798 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 22:45:36 2018 InstallationDate: Installed on 2018-11-07 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jita 1798 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UNR.T157 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UNR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: Tarasovic Jiri dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Desktop-packages] [Bug 1802958] Re: libgs9-common not upgraded when libgs9 upgraded
uploaded to trusty and xenial queues, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: In Progress Bug description: [Impact] ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. [Test Case] To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck [Regression Potential] Might cause problems when upgrading or installing ghostscript or libgs9 [Other Info] This bug affects trusty and xenial. It is already fixed in bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748895]
(In reply to Bernard Moreton from comment #15) > GEARY works simply because it is not named in program senddoc, which then > uses xdg-email as a default, to call the system email client, whatever it > is. But hey, as an entry in Tools/.../Internet, it works! > > So, possibly, would "/usr/bin/wxyz" ... :) Did not get you Bernard ! So there is a bug or not ??? Because since LO 6.0.7 Thunderbird was working for me with exactly same configuration. Now Geary is working but not the thunderbird. For whatever reason same configs are working for Geary and not for Thunderbird Or Kmail Or Claws Mail , isn't it a bit odd ? I am habituated to use Thunderbird, Geary even though works; I feel compromised while using it. Thus earlier this bug is resolved ... it will be better !! Meanwhile I have fallen back to LO 6.0.7 & enjoying using Thunderbird. -- 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 continuosly on Ubuntu 16.04
When I made the report it happened more often, and I seem to remember (but I'm not sure) that it did it even without extensions. Now it happens much less. It happens randomly, but sometimes it blocks the PC. -- 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 continuosly 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 1798541] Re: Please update to actual 3.18.9 version
Synced. I had waited until today for the Disco archive to open. ** Changed in: hplip (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1798541 Title: Please update to actual 3.18.9 version Status in hplip package in Ubuntu: Fix Committed Bug description: Please update to actual 3.18.9 version: a lot of new printers were added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1798541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802958] Re: libgs9-common not upgraded when libgs9 upgraded
This fixes the libgs9-common dependency in xenial. ** Patch added: "debdiff for xenial" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+attachment/5211973/+files/lp1802958_xenial.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: In Progress Bug description: [Impact] ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. [Test Case] To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck [Regression Potential] Might cause problems when upgrading or installing ghostscript or libgs9 [Other Info] This bug affects trusty and xenial. It is already fixed in bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802958] Re: libgs9-common not upgraded when libgs9 upgraded
This fixes the libgs9-common dependency in trusty. ** Description changed: - Impact + [Impact] ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. - Test Case + + [Test Case] To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. - ps2pdf stops working : - $ ps2pdf ascii.ps + ps2pdf stops working : + $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: - --nostringval-- typecheck --nostringval-- scheck .gcheck + --nostringval-- typecheck --nostringval-- scheck .gcheck + + + [Regression Potential] + + Might cause problems when upgrading or installing ghostscript or libgs9 + + + [Other Info] + + This bug affects trusty and xenial. + It is already fixed in bionic and later. ** Patch added: "debdiff for trusty" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+attachment/5211972/+files/lp1802958_trusty.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: In Progress Bug description: [Impact] ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. [Test Case] To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck [Regression Potential] Might cause problems when upgrading or installing ghostscript or libgs9 [Other Info] This bug affects trusty and xenial. It is already fixed in bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799665] Re: [cosmic regression] fails to parse known_hosts, resulting in SSH_SERVER_FOUND_OTHER error for hostkey verification
The verification of the Stable Release Update for libssh has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
** Changed in: libssh (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
https://bugs.launchpad.net/bugs/1799665
Title:
[cosmic regression] fails to parse known_hosts, resulting in
SSH_SERVER_FOUND_OTHER error for hostkey verification
Status in libssh package in Ubuntu:
Fix Released
Status in libssh source package in Cosmic:
Fix Released
Bug description:
Ubuntu 18.10's libssh 0.8.1 regresses parsing of known_hosts. This
happens (sometimes) if there are multiple known_host key types (e. g.
ssh-rsa and ssh-ed25519), then it can happen that
ssh_session_is_known_server() fails with SSH_SERVER_FOUND_OTHER [1].
I noticed this with testing Cockpit on Ubuntu 18.10 [2], which has a
few test cases exercising cockpit-ssh (which uses libssh), e. g. [3].
The scenario is a FreeIPA centrally managed known_hosts file with
these entries:
x0.cockpit.lan ssh-rsa
B3NzaC1yc2EDAQABAAABAQCv5sLKfLDuEAbTcHC3eOgJM+Ot7F077KewD4e1lGzfw300Jo4xnuPsoJEVSCR7OjsYQCnuVGlqtlavMCLFzIBNk06iTBg/nl+W+xa3CFNITbAjiBif7SeY0XL6Xeqzb1VYXNVfwKQKpcGIbDne6jyou4wRZV1eay03FHTSkd2+XKM6GOUGlkEUoPyAwYPHqoKUYiiyBxJs20l/peXVx6jsGgs2Sc6gl3KJP0TB2E7ncD1pWHGRtiNshFFVarw/YKr+Rs+KhiVS3CAAfYDhpBNWXOwTKyx2euJjAhsRF10bx6pnuadSEpT8Ufo5/YFIVAD1GHptULSzVjUoJm6ktoHB
x0.cockpit.lan ecdsa-sha2-nistp256
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBCkJ6CaqhzUhrbpbVmZ8BmZZgM3u6BukZ6HFB2a4NLQBdgpHlHbxoJ47ocTImctyFMiDi0y6vCb4tFuZgp6Krmk=
root@(none)
x0.cockpit.lan ssh-ed25519
C3NzaC1lZDI1NTE5INK6gcOyH4OhiKPcNr33Kl6e+wFAUy9tGFBU/o4yWkxh root@(none)
Connecting to that host with the standard ssh client works:
$ ssh -vv x0.cockpit.lan
[...]
debug1: Server host key: ecdsa-sha2-nistp256
SHA256:MgfkN6HEl+pdz0X7+6q08IVkUZOtEDzfA6V18Wm9DgA
debug1: Host 'x0.cockpit.lan' is known and matches the ECDSA host key.
debug1: Found key in /var/lib/sss/pubconf/known_hosts:3
[...]
ad...@cockpit.lan@x0:~$
But not with cockpit-ssh. This shows the JSON protocol (note that you
need to copy the correct cookie value from the response):
$ G_MESSAGES_DEBUG=cockpit-ssh cockpit-bridge --interact=---
{ "command": "open", "channel": "c", "payload": "echo", "host":
"x0.cockpit.lan", "user": "ad...@cockpit.lan" }
---
{"command":"authorize","challenge":"*","cookie":"session107271540364829"}
---
{"command":"authorize", "response": "password foobarfoo", "cookie":
"session107271540364829"}
---
(cockpit-ssh:10814): cockpit-ssh-DEBUG: 03:11:51.049: cockpit-ssh
x0.cockpit.lan: host not known in any local file, asking sssd
(cockpit-ssh:10814): cockpit-ssh-DEBUG: 03:11:51.472: cockpit-ssh
x0.cockpit.lan: using known hosts file /tmp/known-hosts.IDKNRZ
(cockpit-ssh:10814): cockpit-ssh-DEBUG: 03:11:51.542: cockpit-ssh
x0.cockpit.lan: connected
cockpit-ssh-Message: 03:07:30.828: cockpit-ssh x0.cockpit.lan: host key for
this server changed key type: ssh-ed25519
{"command":"close","host-key":"x0.cockpit.lan ssh-ed25519
C3NzaC1lZDI1NTE5INK6gcOyH4OhiKPcNr33Kl6e+wFAUy9tGFBU/o4yWkxh\n","host-fingerprint":"a0:27:1e:80:de:fd:4b:8a:0d:9d:a9:b6:42:7d:5c:b9","problem":"invalid-hostkey","error":"invalid-hostkey","auth-method-results":{},"channel":"c"}
---
The "host key for this server changed key type" is the effect of this
bug.
SRU INFORMATION:
[IMPACT]: libssh connections that worked in previous Ubuntu releases
now may fail on host key verification
[TEST CASE]: See reproducer below. This isn't too easy to reproduce
for someone else, so I'm happy to do the validation myself. This can
also be verified with the Cockpit integration tests:
bots/image-prepare ubuntu-stable
TEST_OS=ubuntu-stable test/verify/check-realms TestRealms.testIpa
[REGRESSION POTENTIAL]: In principle these patches could break known_hosts
validation further. However, these fixes have been in Debian testing for a
while and validated through e. g. Cockpit's tests (which exercise cockpit-ssh
quite heavily). There are also upstream unit tests, and while they didn't pick
up that particular regression, they at least make sure that known_hosts
verification still works for common cases.
Also, libssh-4 does not have that many reverse dependencies. So overall, I
think this is bearable for an SRU, especially as the impact is quite high.
[1]
[Desktop-packages] [Bug 1799665] Re: [cosmic regression] fails to parse known_hosts, resulting in SSH_SERVER_FOUND_OTHER error for hostkey verification
This bug was fixed in the package libssh - 0.8.1-1ubuntu0.2
---
libssh (0.8.1-1ubuntu0.2) cosmic-proposed; urgency=medium
* Fix regressions with known_host parsing: ssh_session_is_known_server()
sometimes fails with SSH_SERVER_FOUND_OTHER if known_hosts contains
multiple key types for the target host. (LP: #1799665)
* Also backport fixes for some related bugs:
- Use all supported hostkey algorithms for negotiation
- Honor more host key algorithms than the first one (ssh-ed25519)
- Use the correct name for ECDSA keys for host key negotiation
-- Martin Pitt Wed, 24 Oct 2018 08:20:23
+
** Changed in: libssh (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
https://bugs.launchpad.net/bugs/1799665
Title:
[cosmic regression] fails to parse known_hosts, resulting in
SSH_SERVER_FOUND_OTHER error for hostkey verification
Status in libssh package in Ubuntu:
Fix Released
Status in libssh source package in Cosmic:
Fix Released
Bug description:
Ubuntu 18.10's libssh 0.8.1 regresses parsing of known_hosts. This
happens (sometimes) if there are multiple known_host key types (e. g.
ssh-rsa and ssh-ed25519), then it can happen that
ssh_session_is_known_server() fails with SSH_SERVER_FOUND_OTHER [1].
I noticed this with testing Cockpit on Ubuntu 18.10 [2], which has a
few test cases exercising cockpit-ssh (which uses libssh), e. g. [3].
The scenario is a FreeIPA centrally managed known_hosts file with
these entries:
x0.cockpit.lan ssh-rsa
B3NzaC1yc2EDAQABAAABAQCv5sLKfLDuEAbTcHC3eOgJM+Ot7F077KewD4e1lGzfw300Jo4xnuPsoJEVSCR7OjsYQCnuVGlqtlavMCLFzIBNk06iTBg/nl+W+xa3CFNITbAjiBif7SeY0XL6Xeqzb1VYXNVfwKQKpcGIbDne6jyou4wRZV1eay03FHTSkd2+XKM6GOUGlkEUoPyAwYPHqoKUYiiyBxJs20l/peXVx6jsGgs2Sc6gl3KJP0TB2E7ncD1pWHGRtiNshFFVarw/YKr+Rs+KhiVS3CAAfYDhpBNWXOwTKyx2euJjAhsRF10bx6pnuadSEpT8Ufo5/YFIVAD1GHptULSzVjUoJm6ktoHB
x0.cockpit.lan ecdsa-sha2-nistp256
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBCkJ6CaqhzUhrbpbVmZ8BmZZgM3u6BukZ6HFB2a4NLQBdgpHlHbxoJ47ocTImctyFMiDi0y6vCb4tFuZgp6Krmk=
root@(none)
x0.cockpit.lan ssh-ed25519
C3NzaC1lZDI1NTE5INK6gcOyH4OhiKPcNr33Kl6e+wFAUy9tGFBU/o4yWkxh root@(none)
Connecting to that host with the standard ssh client works:
$ ssh -vv x0.cockpit.lan
[...]
debug1: Server host key: ecdsa-sha2-nistp256
SHA256:MgfkN6HEl+pdz0X7+6q08IVkUZOtEDzfA6V18Wm9DgA
debug1: Host 'x0.cockpit.lan' is known and matches the ECDSA host key.
debug1: Found key in /var/lib/sss/pubconf/known_hosts:3
[...]
ad...@cockpit.lan@x0:~$
But not with cockpit-ssh. This shows the JSON protocol (note that you
need to copy the correct cookie value from the response):
$ G_MESSAGES_DEBUG=cockpit-ssh cockpit-bridge --interact=---
{ "command": "open", "channel": "c", "payload": "echo", "host":
"x0.cockpit.lan", "user": "ad...@cockpit.lan" }
---
{"command":"authorize","challenge":"*","cookie":"session107271540364829"}
---
{"command":"authorize", "response": "password foobarfoo", "cookie":
"session107271540364829"}
---
(cockpit-ssh:10814): cockpit-ssh-DEBUG: 03:11:51.049: cockpit-ssh
x0.cockpit.lan: host not known in any local file, asking sssd
(cockpit-ssh:10814): cockpit-ssh-DEBUG: 03:11:51.472: cockpit-ssh
x0.cockpit.lan: using known hosts file /tmp/known-hosts.IDKNRZ
(cockpit-ssh:10814): cockpit-ssh-DEBUG: 03:11:51.542: cockpit-ssh
x0.cockpit.lan: connected
cockpit-ssh-Message: 03:07:30.828: cockpit-ssh x0.cockpit.lan: host key for
this server changed key type: ssh-ed25519
{"command":"close","host-key":"x0.cockpit.lan ssh-ed25519
C3NzaC1lZDI1NTE5INK6gcOyH4OhiKPcNr33Kl6e+wFAUy9tGFBU/o4yWkxh\n","host-fingerprint":"a0:27:1e:80:de:fd:4b:8a:0d:9d:a9:b6:42:7d:5c:b9","problem":"invalid-hostkey","error":"invalid-hostkey","auth-method-results":{},"channel":"c"}
---
The "host key for this server changed key type" is the effect of this
bug.
SRU INFORMATION:
[IMPACT]: libssh connections that worked in previous Ubuntu releases
now may fail on host key verification
[TEST CASE]: See reproducer below. This isn't too easy to reproduce
for someone else, so I'm happy to do the validation myself. This can
also be verified with the Cockpit integration tests:
bots/image-prepare ubuntu-stable
TEST_OS=ubuntu-stable test/verify/check-realms TestRealms.testIpa
[REGRESSION POTENTIAL]: In principle these patches could break known_hosts
validation further. However, these fixes have been in Debian testing for a
while and validated through e. g. Cockpit's tests (which exercise cockpit-ssh
quite heavily). There are also upstream unit tests, and while they didn't pick
up that particular regression, they at least make sure that known_hosts
verification still works for common cases.
Also, libssh-4 does not have that many reverse
[Desktop-packages] [Bug 1798091] Re: thumbnailer cannot create tempfiles (with apparmor denials)
This bug was fixed in the package evince - 3.30.1-1ubuntu1.2 --- evince (3.30.1-1ubuntu1.2) cosmic; urgency=medium * debian/apparmor-profile: - fine-tune the apparmor profile to allow the previous access in addition to the new accesses to fix LP: #1798091 evince (3.30.1-1ubuntu1.1) cosmic; urgency=medium * debian/apparmor-profile: - use the correct thumbnailer temp filename, fixes nautilus failing to generate pdf previews (lp: #1798091) -- Jamie Strandboge Wed, 31 Oct 2018 19:26:39 + ** Changed in: evince (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1798091 Title: thumbnailer cannot create tempfiles (with apparmor denials) Status in evince package in Ubuntu: Fix Released Status in evince source package in Cosmic: Fix Released Status in evince source package in Disco: Fix Released Status in evince package in Debian: Fix Released Bug description: * Impact Nautilus fails to generate previews for pdf files * Test case Download/copy a pdf, open the directory in nautilus, a preview image should be displayed * Regression potential Check that there are no other apparmor denials and the thumbnailer works - While trying to create thumbnails in a directory from within nautilus, I got: [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 14:59:00 2018 InstallationDate: Installed on 2014-06-19 (1580 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1798091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798091] Update Released
The verification of the Stable Release Update for evince has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1798091 Title: thumbnailer cannot create tempfiles (with apparmor denials) Status in evince package in Ubuntu: Fix Released Status in evince source package in Cosmic: Fix Released Status in evince source package in Disco: Fix Released Status in evince package in Debian: Fix Released Bug description: * Impact Nautilus fails to generate previews for pdf files * Test case Download/copy a pdf, open the directory in nautilus, a preview image should be displayed * Regression potential Check that there are no other apparmor denials and the thumbnailer works - While trying to create thumbnails in a directory from within nautilus, I got: [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 14:59:00 2018 InstallationDate: Installed on 2014-06-19 (1580 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1798091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802574] Re: laptop screen never comes on after undock / sleep / open of laptop
I've already got apport configured to report everything (i.e., I've already done the workaround suggested in bug 994921), and there is no crash either in /var/crash or on https://errors.ubuntu.com. I don't think a crash is what's happening here. Additional data: * If, after I've woken up my laptop and the screen is blank, I put it back in the dock with the lid closed, the dock's two monitors come alive just fine. * If I then open the laptop lid, the monitors reconfigure themselves and I correctly end up with both the two monitors and the laptop screen all live. * Ditto if I then close the lid -- the displays reconfigure themselves and only the two dock monitors are enabled. * If I temporarily disable the udev script that causes the laptop to go to sleep automatically when I undock it, then when I undock it and open the lid the screen comes on just fine. * When the screen is in the off-but-should-be-on state I've reported here, Ctrl-Alt-F* doesn't switch to a different VTY. * This problem happens _almost_ every time I undock, but not every time. I've tried it seven or eight times, and one of those times, the screen came on properly when I woke the laptop by opening the lid. All the other times the screen never came on until I either power-cycled or put the laptop back in the dock. -- 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/1802574 Title: laptop screen never comes on after undock / sleep / open of laptop Status in gnome-shell package in Ubuntu: Incomplete Bug description: I use a ThinkPad dock with two monitors plugged into it. I have a udev job configured to automatically put my laptop to sleep when I undock it. So, I'm working on my laptop in the dock. I undock it and drop it into my backpack. All by itself, it goes to sleep. A few minutes later, I open the laptop and it wakes up. I know it's up because the power light and LED on the lid both go to solid. But the laptop screen never comes on. I've undocked twice since upgrading to 18.10. This has happened both times. It's a regression from 18.04.1. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 9 13:18:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (43 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-11-08 (1 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1802574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802958] Re: libgs9-common not upgraded when libgs9 upgraded
** Changed in: ghostscript (Ubuntu Trusty) Status: New => In Progress ** Changed in: ghostscript (Ubuntu Xenial) Status: New => In Progress ** Changed in: ghostscript (Ubuntu) Status: In Progress => Fix Released ** Changed in: ghostscript (Ubuntu Trusty) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: ghostscript (Ubuntu Xenial) Assignee: (unassigned) => Ioanna Alifieraki (joalif) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: In Progress Bug description: Impact ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. Test Case To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802958] Re: libgs9-common not upgraded when libgs9 upgraded
** Changed in: ghostscript (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: In Progress Bug description: Impact ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. Test Case To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802958] Re: libgs9-common not upgraded when libgs9 upgraded
** Also affects: ghostscript (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ghostscript (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: ghostscript (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: ghostscript (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: In Progress Bug description: Impact ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. Test Case To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://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 1802497] Re: cannot open a VT2
HI Thanks for handling this. The newly opened bug number is 1802961 https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1802961 Thank you Olivier Em 12/11/2018 00:26, Daniel van Vugt escreveu: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > -- Olivier Hallot Rio de Janeiro - Brasil -- 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/1802497 Title: cannot open a VT2 Status in xorg-server package in Ubuntu: Incomplete Bug description: On switching to a new session, the existing session is closed and the new opens at the same VT1. Xorg crashes and restart, thus assigning VT1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 9 10:02:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:056e] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-05-10 (182 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Vostro 3560 ProcEnviron: LANGUAGE=pt_BR:en_US TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-38-generic root=UUID=89a47e85-475c-4f6c-a0d8-d3aae572e9a5 ro rootflags=subvol=@ plymouth:debug=1=1 vesafb.invalid=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0R9N46 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A17 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd04/14/2014:svnDellInc.:pnVostro3560:pvrA17:rvnDellInc.:rn0R9N46:rvrA01:cvnDellInc.:ct8:cvrA17: dmi.product.family: 103C_5335KV dmi.product.name: Vostro 3560 dmi.product.version: A17 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/1802497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802958] Re: libgs9-common not upgraded when libgs9 upgraded
** Changed in: ghostscript (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: In Progress Bug description: Impact ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. Test Case To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen
I'm having trouble finding a way to switch Ubuntu 18.10 to Wayland. I have Xwayland installed but don't see a way to switch the session. I did enable it in gdm3 custom.conf but it doesn't seem to be running. Can you point me to some directions? -- 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/1802573 Title: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a fresh install of 18.10 on an old Thinkpad x220. Everything works fine with the internal display or an external Dell G2410 (1920x1080) connected via VGA. But when I try to switch to an external BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a time and then it flashes to black. This happens consistently for minutes--it never "settles down". I've tried the default configuration as well as copying xorg.conf from /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both xorg configurations with nomodeset in the bootloader and without. I have not been able to find any configuration that allows this external DisplayPort display to work. The same hardware combination works fine in Windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Nov 9 13:10:59 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2018-11-09 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 42872WU ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel" Driver "intel" #Option "AccelMethod" "uxa" EndSection dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 42872WU 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:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 42872WU dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802573/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802958] Re: libgs9-common not upgraded when libgs9 upgraded
** Changed in: ghostscript (Ubuntu) Assignee: (unassigned) => Ioanna Alifieraki (joalif) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: In Progress Status in ghostscript source package in Xenial: In Progress Bug description: Impact ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. Test Case To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802958] [NEW] libgs9-common not upgraded when libgs9 upgraded
Public bug reported: Impact ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. Test Case To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck ** Affects: ghostscript (Ubuntu) Importance: Undecided Assignee: Ioanna Alifieraki (joalif) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1802958 Title: libgs9-common not upgraded when libgs9 upgraded Status in ghostscript package in Ubuntu: New Bug description: Impact ps2pdf stops working after upgrade of ghostscript to 9.25~dfsg+1-0ubuntu0.14.04.2 . ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2, but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version. Test Case To reproduce the bug: Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and libgs9-common. At this point ps2pdf should be working fine. Then sudo apt install ghostscript. ghostscript and libgs9 are upgraded but not libgs9-common. ps2pdf stops working : $ ps2pdf ascii.ps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- scheck .gcheck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1516332] Re: Add policy to Polkit
There is still no easy way to edit files that need root, example files in /etc/ in gedit. Even as of gedit 3.30.1. -- 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/1516332 Title: Add policy to Polkit Status in gedit package in Ubuntu: Won't Fix Bug description: http://www.webupd8.org/2015/03/how-to-run-gedit-and-nautilus-as- root.html Add the file https://raw.githubusercontent.com/hotice/webupd8/master/org.gnome.gedit.policy to /usr/share/polkit-1/actions/ So the user can start a gedit session with superuser privileges to edit files outside the home directory using 'pkexec gedit'. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Sun Nov 15 02:36:55 2015 InstallationDate: Installed on 2013-12-26 (688 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1516332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu
** Changed in: moonshot-trust-router (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1802569 Title: RM openssl1.0 from Ubuntu Status in cfengine2 package in Ubuntu: Confirmed Status in ckermit package in Ubuntu: Confirmed Status in conserver package in Ubuntu: Confirmed Status in cqrlog package in Ubuntu: Confirmed Status in ekiga package in Ubuntu: Confirmed Status in freerdp package in Ubuntu: New Status in mailavenger package in Ubuntu: Confirmed Status in moonshot-trust-router package in Ubuntu: Confirmed Status in netkit-ftp-ssl package in Ubuntu: Confirmed Status in opal package in Ubuntu: Confirmed Status in openssl1.0 package in Ubuntu: Incomplete Status in ptlib package in Ubuntu: Confirmed Status in reconserver package in Ubuntu: Confirmed Status in t38modem package in Ubuntu: Confirmed Status in cfengine2 package in Debian: New Status in ckermit package in Debian: New Status in conserver package in Debian: New Status in cqrlog package in Debian: New Status in ekiga package in Debian: New Status in freerdp package in Debian: Fix Released Status in mailavenger package in Debian: Confirmed Status in moonshot-trust-router package in Debian: New Status in netkit-ftp-ssl package in Debian: New Status in opal package in Debian: New Status in ptlib package in Debian: New Status in reconserver package in Debian: New Status in t38modem package in Debian: New Bug description: RM openssl1.0 from Ubuntu reconserver has multiple ftbfs issues / bugs. opal/ptlib all of their reverse-deps are included for removal in this bug too. freerdp is superseeded by freerdp2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cfengine2/+bug/1802569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783514] Re: firefox password field not accessable in popup dialog
It is the same for me! Ubuntu 18.04 Firefox 63.0 But it works with Chromium 70.0.3538.77 My workaround: change the style of the page to "no style" on Firefox but it is just a workaround. -- 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/1783514 Title: firefox password field not accessable in popup dialog Status in firefox package in Ubuntu: New Bug description: if you open the popup dialog "My Sunrise" on this site: https://www.sunrise.ch/en/residential/welcome-page.html you are not able to access the password field. Not by clicking and not with tab-key. on the given expample site you can check the box "Show password", the you can enter the password. But if you don't have this option, you can't login. Another example is the Firefox addon "Windscribe". You have to login with popup dialog and it's not possible to enter the password. This bug affects only the Linux version of firefox as I now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 61.0.1+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BuildID: 20180704192850 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 25 10:32:34 2018 ExecutablePath: /usr/lib/firefox/firefox SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1783514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802911] Re: [snap] LibreOffice 6.1.3.2 (90) doesn't launch
I cannot reproduce the problem in a 18.10 VM with the core snap from various channels (tried stable, beta, edge). What's the output of: snap changes libreoffice ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete -- 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/1802911 Title: [snap] LibreOffice 6.1.3.2 (90) doesn't launch Status in libreoffice package in Ubuntu: Incomplete Bug description: LibreOffice doesn't launch on 6.1.3.2 (90) in `candidate` on core 16-2.36.1+git1007.f72779e (5920) in `edge`, it just hangs, with no Terminal output, but has the following denials in `journalctl -f`: ``` Nov 12 12:38:19 adam-thinkpad-t430 audit[31984]: AVC apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 12 12:38:19 adam-thinkpad-t430 kernel: audit: type=1400 audit(1542026299.589:542): apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ``` ``` $ snap info libreoffice tracking: candidate refresh-date: 6 days ago, at 08:50 GMT channels: stable:6.1.2.1 (86) 501MB - candidate: 6.1.3.2 (90) 507MB - < beta: ↑ edge: ↑ installed: 6.1.3.2 (90) 507MB - $ snap version snap2.36.1+git1007.f72779e~ubuntu16.04.1 snapd 2.36.1+git1007.f72779e~ubuntu16.04.1 series 16 ubuntu 18.10 kernel 4.18.0-11-generic $ snap info core tracking: edge refresh-date: today at 12:08 GMT channels: stable:16-2.35.5 (5742) 92MB - candidate: 16-2.35.5 (5742) 92MB - beta: 16-2.36.1 (5897) 92MB - edge: 16-2.36.1+git1007.f72779e (5920) 92MB -< installed: 16-2.36.1+git1007.f72779e (5920) 92MB core ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802902] Re: 18.10 gdk-pixbuf-thumbnailer 100% cpu makes system completely unresponsive
** Package changed: ubuntu => gdk-pixbuf (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1802902 Title: 18.10 gdk-pixbuf-thumbnailer 100% cpu makes system completely unresponsive Status in gdk-pixbuf package in Ubuntu: New Bug description: Nothing gets logged by dmesg or journalctl, and the system suddenly becomes unresponsive so even ttys are slow and unusable. This happened on 3 installs of 18.10. It mostly happens when waking my external monitor but also at random times about every other hour. Despite no logs, I fixed the problem by deleting the folder .cache/thumbnails/fail Don't know why or how this happens and I don't have the log files to upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1802902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802902] [NEW] 18.10 gdk-pixbuf-thumbnailer 100% cpu makes system completely unresponsive
You have been subscribed to a public bug: Nothing gets logged by dmesg or journalctl, and the system suddenly becomes unresponsive so even ttys are slow and unusable. This happened on 3 installs of 18.10. It mostly happens when waking my external monitor but also at random times about every other hour. Despite no logs, I fixed the problem by deleting the folder .cache/thumbnails/fail Don't know why or how this happens and I don't have the log files to upload. ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment freeze gdk-pixbuf-thumbnailer unresponsive -- 18.10 gdk-pixbuf-thumbnailer 100% cpu makes system completely unresponsive https://bugs.launchpad.net/bugs/1802902 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf 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 1798541] Re: Please update to actual 3.18.9 version
3.18.10 is out and in Debian, can be updated in Ubuntu Disco now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1798541 Title: Please update to actual 3.18.9 version Status in hplip package in Ubuntu: New Bug description: Please update to actual 3.18.9 version: a lot of new printers were added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1798541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801602] Re: Gnome 3 fullscreen doesn't work for some applications when a custom display mode (960x540) is active
"when a custom display mode (960x540) is active" has been added to description but (as I mentioned before) it's not true for the Steam Way To Go game. -- 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/1801602 Title: Gnome 3 fullscreen doesn't work for some applications when a custom display mode (960x540) is active Status in mutter package in Ubuntu: Triaged Bug description: Using Gnome 3 or Ubuntu session (default in 18.04) when you try to run some game in fullscreen mode instead it opens at top left small window. This happens for example for Way to Go! Steam game and perhaps any SDL 1 game. It's easy to reproduce, install a game using SDL 1 library for example abe (apt install abe) and try to run it. There are two kinds of effect, the abe and perhaps other games from Ubuntu repository fails to run properly fullscreen only on first use after login. On second and further run they launch properly on fullscreen. The Steam game (Way to Go !) fails to run fullscreen each time. Sometimes you see only part of the game screen at top left window and you even can't operate it, sometimes whole screen is shown. When you manage to reach game settings switching fullscreen on and off few times makes the fullscreen run properly. The problem doesn't exist for example using Unity or Windowmaker sessions. It exists using any Gnome 3 Xorg sessions, even the classic one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1801602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799675] Re: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Upstream doesn't want to fix the obvious problem because they disagree g-c-c should be used outside out of GNOME, unassigning/setting back to triaged since we don't want to enter into arguing about that ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Triaged ** Changed in: gnome-control-center (Ubuntu) Assignee: Andrea Azzarone (azzar1) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1799675 Title: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell- model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) Status in gnome-control-center package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8de5ebcde9e4492a3bc570a4caa376cefbdfcbec contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1799675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797205] Re: /usr/bin/gnome-control-center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call
The upstream fix was included in 3.30.2 which is disco now https://gitlab.gnome.org/GNOME/gnome-control-center/commit/b8e2fd92 ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1797205 Title: /usr/bin/gnome-control- center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2ddf38bad57fd999c49468a7407614123cac3e11 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1797205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785819] Re: nautilus crashed with SIGABRT in g_assertion_message() (g_hash_table_lookup (directory->details->file_hash, name) == NULL)
** Summary changed: - nautilus crashed with SIGABRT in g_assertion_message() + nautilus crashed with SIGABRT in g_assertion_message() (g_hash_table_lookup (directory->details->file_hash, name) == NULL) ** Summary changed: - nautilus crashed with SIGABRT in g_assertion_message() (g_hash_table_lookup (directory->details->file_hash, name) == NULL) + nautilus SIGABRT (g_hash_table_lookup (directory->details->file_hash, name) == NULL) -- 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/1785819 Title: nautilus SIGABRT (g_hash_table_lookup (directory->details->file_hash, name) == NULL) Status in nautilus package in Ubuntu: Confirmed Bug description: after oopen nautilus, click on my hard external and searching...! ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 7 17:43:41 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'235' b'org.gnome.nautilus.window-state' b'geometry' b"'942x494+341+27'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" InstallationDate: Installed on 2018-04-19 (109 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () nautilus_directory_add_file () ?? () Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1785819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Fernando: we don't support hybrid graphics without using a display manager, as that would prevent gpu-manager from running at the right time. @Michael: I can only assume there was some failure somewhere when setting the power state of the NVIDIA GPU (the dmesg output might help). There are indeed cases in which bbswitch works best on some GPUs. This sounds like one of them. @Stefan: good. Thanks for reporting :) @Krzysztof: in your case, the NVIDIA GPU seems to be first, and the Intel GPU is seen as last. Can you set Intel as first in the BIOS, please? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802584] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1802584/+attachment/5211869/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1802584 Title: A good amount of pulseaudio modules can't be loaded Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . Am I forgetting something? Why can't I load them? Why are they not listed? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hadware 17117 F...m pulseaudio /dev/snd/controlC1: hadware 17117 F pulseaudio /dev/snd/controlC0: hadware 17117 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-07 (309 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: pulseaudio 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-36-generic x86_64 UnreportableReason: Ce paquet n'est pas officiellement pris en charge par Ubuntu. Veuillez désinstaller tout paquet tiers et réessayer. UpgradeStatus: Upgraded to bionic on 2018-10-07 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET49WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV000BUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BV000BUS:pvrThinkPadT450:rvnLENOVO:rn20BV000BUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV000BUS dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802584] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1802584/+attachment/5211872/+files/PulseList.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1802584 Title: A good amount of pulseaudio modules can't be loaded Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . Am I forgetting something? Why can't I load them? Why are they not listed? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hadware 17117 F...m pulseaudio /dev/snd/controlC1: hadware 17117 F pulseaudio /dev/snd/controlC0: hadware 17117 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-07 (309 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: pulseaudio 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-36-generic x86_64 UnreportableReason: Ce paquet n'est pas officiellement pris en charge par Ubuntu. Veuillez désinstaller tout paquet tiers et réessayer. UpgradeStatus: Upgraded to bionic on 2018-10-07 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET49WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV000BUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BV000BUS:pvrThinkPadT450:rvnLENOVO:rn20BV000BUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV000BUS dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802584] Re: A good amount of pulseaudio modules can't be loaded
apport information ** Tags added: apport-collected third-party-packages ** Description changed: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . - Am I forgetting something? Why can't I load them? Why are they not - listed? + Am I forgetting something? Why can't I load them? Why are they not listed? + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0p: hadware 17117 F...m pulseaudio + /dev/snd/controlC1: hadware 17117 F pulseaudio + /dev/snd/controlC0: hadware 17117 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-01-07 (309 days ago) + InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + Package: pulseaudio 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 + Tags: bionic third-party-packages + Uname: Linux 4.15.0-36-generic x86_64 + UnreportableReason: Ce paquet n'est pas officiellement pris en charge par Ubuntu. Veuillez désinstaller tout paquet tiers et réessayer. + UpgradeStatus: Upgraded to bionic on 2018-10-07 (35 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/21/2015 + dmi.bios.vendor: LENOVO + dmi.bios.version: JBET49WW (1.14 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20BV000BUS + dmi.board.vendor: LENOVO + dmi.board.version: SDK0E50510 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BV000BUS:pvrThinkPadT450:rvnLENOVO:rn20BV000BUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T450 + dmi.product.name: 20BV000BUS + dmi.product.version: ThinkPad T450 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1802584/+attachment/5211868/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1802584 Title: A good amount of pulseaudio modules can't be loaded Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . Am I forgetting something? Why can't I load them? Why are they not listed? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hadware 17117 F...m pulseaudio /dev/snd/controlC1: hadware 17117 F pulseaudio /dev/snd/controlC0: hadware 17117 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-07 (309 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: pulseaudio 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-36-generic x86_64 UnreportableReason: Ce paquet n'est pas officiellement pris en charge par Ubuntu. Veuillez désinstaller tout paquet tiers et réessayer. UpgradeStatus: Upgraded to bionic on 2018-10-07 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET49WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV000BUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Desktop-packages] [Bug 1802584] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1802584/+attachment/5211871/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1802584 Title: A good amount of pulseaudio modules can't be loaded Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . Am I forgetting something? Why can't I load them? Why are they not listed? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hadware 17117 F...m pulseaudio /dev/snd/controlC1: hadware 17117 F pulseaudio /dev/snd/controlC0: hadware 17117 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-07 (309 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: pulseaudio 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-36-generic x86_64 UnreportableReason: Ce paquet n'est pas officiellement pris en charge par Ubuntu. Veuillez désinstaller tout paquet tiers et réessayer. UpgradeStatus: Upgraded to bionic on 2018-10-07 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET49WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV000BUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BV000BUS:pvrThinkPadT450:rvnLENOVO:rn20BV000BUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV000BUS dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802584] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1802584/+attachment/5211870/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1802584 Title: A good amount of pulseaudio modules can't be loaded Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . Am I forgetting something? Why can't I load them? Why are they not listed? --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hadware 17117 F...m pulseaudio /dev/snd/controlC1: hadware 17117 F pulseaudio /dev/snd/controlC0: hadware 17117 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-01-07 (309 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: pulseaudio 1:12.2-5~bionic1 [origin: LP-PPA-mikhailnov-pulseeffects] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-36-generic x86_64 UnreportableReason: Ce paquet n'est pas officiellement pris en charge par Ubuntu. Veuillez désinstaller tout paquet tiers et réessayer. UpgradeStatus: Upgraded to bionic on 2018-10-07 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET49WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV000BUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BV000BUS:pvrThinkPadT450:rvnLENOVO:rn20BV000BUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV000BUS dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797734] Re: slow calculator startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-calculator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Confirmed Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1656790] Re: print-notifications: Don't show error for job in progress
First, run the following commands to check whether your system-config- printer got completely upgraded: dpkg -l | grep 1.5.7+2016 dpkg -l | grep 1.5.9+2017 dpkg -l | grep system-config-printer Is this the case? If so, please log out and log in again to assure that there are no stale processes in your running desktop. If you still get the notifications, reboot. If you still get the notification also after this, it seems that they do not come from system-config-printer, but perhaps from Mate's desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1656790 Title: print-notifications: Don't show error for job in progress Status in ubuntu-mate: Invalid Status in mate-settings-daemon package in Ubuntu: Invalid Status in system-config-printer package in Ubuntu: Fix Released Bug description: Running Ubuntu MATE 16.04.1 LTS Every single time I print something, I get an error notification. Unfortunly, I'm running a Norwegian desktop, so this will be a translation of what I suppose the notification says on an English desktop: Printer error Printer 'NAME':'cups-waiting-for-job-completed' It is a bit annoying, but it disappears after a couple of seconds, when the print job is done. After a bit of Googling, I found this is a known error from earlier, with gnome-settings-daemon. I guess the fix never have been included in mate-settings-daemon ? This is the bug in Red Hat for the same problem: https://bugzilla.redhat.com/show_bug.cgi?id=1207154 This is the patch for gnome-settings-daemon from May 20 2015 : https://mail.gnome.org/archives/commits-list/2015-May/msg03447.html The 'cups-waiting-for-job-completed' is a notification in Cups, which should not be ignored by gnome-settings-daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1656790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
Is there a manual way to have it come-up ? From comment #10 : "Because of alien toolkits there is always a need to summon on demand." Ido not have touch screen Ineed the keyboard because my space key does not work asitshould. Still a very annoying bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear Status in OEM Priority Project: Confirmed Status in caribou package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- Mailing list: https://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 1726861] Re: bookmarks & history system not available
That was kind of my assumption when I installed the Firefox snap - that it would be somewhat isolated from the rest of my system by the snap "container". I'm going to do a clean install of 18.04.1 in the near future so I'm not sure how much effort needs to be put into following up on this. Regardless, here are the results from find: brent@brent-desktop:~$ find \! -user brent ./.npm/anonymous-cli-metrics.json ./.config/configstore find: ‘./.config/configstore’: Permission denied ./.gvfs find: ‘./.gvfs’: Permission denied ./.rpmdb ./.rpmdb/Sigmd5 ./.rpmdb/Installtid ./.rpmdb/Group ./.rpmdb/Name ./.rpmdb/Providename ./.rpmdb/__db.001 ./.rpmdb/Conflictname ./.rpmdb/__db.003 ./.rpmdb/Obsoletename ./.rpmdb/Dirnames ./.rpmdb/Packages ./.rpmdb/Basenames ./.rpmdb/Triggername ./.rpmdb/.dbenv.lock ./.rpmdb/__db.002 ./.rpmdb/Requirename ./.rpmdb/Sha1header ./.dbus find: ‘./.dbus’: Permission denied - Brent Crossland br...@thecrosslands.net On Sat, Nov 10, 2018 at 2:20 PM Paul White <1726...@bugs.launchpad.net> wrote: > As far as I am aware the snap version of Firefox will store settings in > a different area to that of the .deb. I wonder if you have some settings > in the ~/.mozilla directory owned by a user other than you. If you still > have those settings in place you could search for anything owned by > another user. > > In the past I've found running in the home directory: > > find \! -user yourusername > > to have revealed several files owned by root that have stopped various > applications from working correctly. Correcting the owner allowed those > applications to then function as expected. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1726861 > > Title: > bookmarks & history system not available > > Status in firefox package in Ubuntu: > Incomplete > > Bug description: > I've followed the troubleshooting information suggested in Firefox > with no results including multiple reboots. Also uninstalled & > reinstalled firefox. Still cannot restore bookmarks or import > bookmarks from html. Cannot sync bookmarks using firefox sync. > > Firefox still reports that the bookmark & history system is not > available because some files are in use by another application. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: firefox 56.0+build6-0ubuntu0.16.04.2 > ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 > Uname: Linux 4.4.0-97-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > AddonCompatCheckDisabled: False > ApportVersion: 2.20.1-0ubuntu2.10 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: brent 2321 F pulseaudio >/dev/snd/controlC2: brent 2321 F pulseaudio >/dev/snd/controlC0: brent 2321 F pulseaudio > BuildID: 20171003101344 > Channel: Unavailable > CurrentDesktop: GNOME > Date: Tue Oct 24 07:49:01 2017 > 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 2015-03-09 (959 days ago) > InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 > (20141022.1) > IpRoute: >default via 192.168.1.1 dev eth0 proto static metric 100 >169.254.0.0/16 dev eth0 scope link metric 1000 >192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.203 > metric 100 > IwConfig: >lono wireless extensions. > >eth0 no wireless extensions. > Locales: extensions.sqlite corrupt or missing > MostRecentCrashID: bp-c54702b4-1092-4d28-8224-51ecd1171023 > Plugins: Shockwave Flash - > /usr/lib/flashplugin-installer/libflashplayer.so > PrefSources: prefs.js > ProcEnviron: >LANGUAGE=en_US >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use) > RfKill: > > RunningIncompatibleAddons: False > SourcePackage: firefox > Themes: extensions.sqlite corrupt or missing > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/03/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1102 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: P7P55 LX > 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: >
[Desktop-packages] [Bug 1801496] Re: Printing job in 16.04 is slower than in 14.04
I have looked into the error_log files and the processing by the filters
on 16.04 takes ~20 seconds and on 14.04 less time. The 326 seconds you
observe on 16.04 is caused by the printer's processing of the PostScript
it receives. The PostScript is generated by Ghostscript (you find the
Ghostscript command lines used in the error_log files).
So it seems that the newer Ghostscript version used by 16.04 is
processed much slower by your printer than the PostScript of 14.04's
Ghostscript version.
Next thing you should investigate is to directly run the Ghostscript
command lines with your file in a terminal window, once on 14.04 and
once on 16.04. Send the resulting files directly to the printer ("lp -d
... -o raw ..." or "nc -w1 9100 < ".) If you get the same
time difference, please post a bug report on Ghostscript,
http://www.ghostscript.org/.
--
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/1801496
Title:
Printing job in 16.04 is slower than in 14.04
Status in cups package in Ubuntu:
Incomplete
Bug description:
Ubuntu 16.04LTS
OS Version： 16.04.5
CUPS Version： 2.1.3
Ghostscript Version： 9.25 （2018-09-13）
Printing job in 16.04 is slower than in 14.04
We(RICOH printer driver developer) are report a problem from our printer
users:
I print file Ubuntu 14.04.5, CUPS 2.1.3,Ghostscript 9.25 is fast(12 Seconds).
But, after I update to Ubuntu 16.04, CUPS 2.1.3, Ghostscript 9.25, I
print the same file with the same driver is slow(326 Seconds).
I figure out that all the print jobs is much slower on Ubuntu 16.04.
I view the "CUPS Error Log", it shows that there are three points
which maybe the reasons that makes the print job slowly.
FIRST:
By counting the time from "Starting renderer" to "renderer exited with status
0", we figure out that 16.04 spend more time than 14.04 on "renderer" process.
So we assuming that："renderer" is one of the key process that makes the print
job slowly.
"Starting renderer with command: \"printf \'\\033%%-12345X@PJL
JOB\\012\';printf \'@PJL SET DATAMODE=TWIN\\ @PJL
EOJ\\012\\033%%-12345X\'\""
.
renderer exited with status 0"
SECOND:
On 16.04, a print job outputs lots of logs as below:
"[Job xxx] Removing document files."
This step(“Removing document files”)does not exsit on 14.04.
The phenomenon that print jobs slower in 16.04 is more obvious when printing
many jobs in the same time.
THIRD
We tried drivers form other company(HP,Brother…), the printings also slow
down in Ubuntu 16.04 than 14.04.
Our question is:
1. Do you have any plan to improve the performance of printing on Ubuntu
16.04?
2. Do you have any workaround before this problems fixed?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801496/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802584] Re: A good amount of pulseaudio modules can't be loaded
It's done. I did however fix the problem so the information you'll get isn't exact. I used this thread: https://github.com/wwmm/pulseeffects/issues/365 (so basically removing the pulseaudio binary and doing a reinstall) ** Bug watch added: github.com/wwmm/pulseeffects/issues #365 https://github.com/wwmm/pulseeffects/issues/365 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1802584 Title: A good amount of pulseaudio modules can't be loaded Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . Am I forgetting something? Why can't I load them? Why are they not listed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802911] Re: [snap] LibreOffice 6.1.3.2 (90) doesn't launch
I should also note that when I was downloading snap and Deb updates, the UI of the whole OS stopped responding to clicks, I switched to tty6 and then back again after a while and then closed LibreOffice (it was open) and it wouldn't re-open, so this issue could be related to that. I wasn't able to get journal records of the OS break. -- 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/1802911 Title: [snap] LibreOffice 6.1.3.2 (90) doesn't launch Status in libreoffice package in Ubuntu: New Bug description: LibreOffice doesn't launch on 6.1.3.2 (90) in `candidate` on core 16-2.36.1+git1007.f72779e (5920) in `edge`, it just hangs, with no Terminal output, but has the following denials in `journalctl -f`: ``` Nov 12 12:38:19 adam-thinkpad-t430 audit[31984]: AVC apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 12 12:38:19 adam-thinkpad-t430 kernel: audit: type=1400 audit(1542026299.589:542): apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ``` ``` $ snap info libreoffice tracking: candidate refresh-date: 6 days ago, at 08:50 GMT channels: stable:6.1.2.1 (86) 501MB - candidate: 6.1.3.2 (90) 507MB - < beta: ↑ edge: ↑ installed: 6.1.3.2 (90) 507MB - $ snap version snap2.36.1+git1007.f72779e~ubuntu16.04.1 snapd 2.36.1+git1007.f72779e~ubuntu16.04.1 series 16 ubuntu 18.10 kernel 4.18.0-11-generic $ snap info core tracking: edge refresh-date: today at 12:08 GMT channels: stable:16-2.35.5 (5742) 92MB - candidate: 16-2.35.5 (5742) 92MB - beta: 16-2.36.1 (5897) 92MB - edge: 16-2.36.1+git1007.f72779e (5920) 92MB -< installed: 16-2.36.1+git1007.f72779e (5920) 92MB core ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802911] Re: [snap] LibreOffice doesn't launch
Running on core 16-2.36.1 (5897) in `beta` hangs with no denials and 16-2.35.5 (5742) in `stable` and `candidate` also hangs with no denials. LibreOffice 6.1.2.1 (86) in `stable` works fine (on core 16-2.35.5 (5742)) so I assume the problem is with 6.1.3.2 (90). ** Summary changed: - [snap] LibreOffice doesn't launch + [snap] LibreOffice 6.1.3.2 (90) doesn't launch ** Tags added: regression -- 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/1802911 Title: [snap] LibreOffice 6.1.3.2 (90) doesn't launch Status in libreoffice package in Ubuntu: New Bug description: LibreOffice doesn't launch on 6.1.3.2 (90) in `candidate` on core 16-2.36.1+git1007.f72779e (5920) in `edge`, it just hangs, with no Terminal output, but has the following denials in `journalctl -f`: ``` Nov 12 12:38:19 adam-thinkpad-t430 audit[31984]: AVC apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 12 12:38:19 adam-thinkpad-t430 kernel: audit: type=1400 audit(1542026299.589:542): apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ``` ``` $ snap info libreoffice tracking: candidate refresh-date: 6 days ago, at 08:50 GMT channels: stable:6.1.2.1 (86) 501MB - candidate: 6.1.3.2 (90) 507MB - < beta: ↑ edge: ↑ installed: 6.1.3.2 (90) 507MB - $ snap version snap2.36.1+git1007.f72779e~ubuntu16.04.1 snapd 2.36.1+git1007.f72779e~ubuntu16.04.1 series 16 ubuntu 18.10 kernel 4.18.0-11-generic $ snap info core tracking: edge refresh-date: today at 12:08 GMT channels: stable:16-2.35.5 (5742) 92MB - candidate: 16-2.35.5 (5742) 92MB - beta: 16-2.36.1 (5897) 92MB - edge: 16-2.36.1+git1007.f72779e (5920) 92MB -< installed: 16-2.36.1+git1007.f72779e (5920) 92MB core ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => In Progress -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802909] [NEW] package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: Happened during upgrade fro 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Nov 12 13:25:56 2018 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-01-26 (655 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-11-12 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1802909 Title: package tex-common 6.09 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Happened during upgrade fro 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Nov 12 13:25:56 2018 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-01-26 (655 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-11-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1802909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802911] [NEW] [snap] LibreOffice doesn't launch
Public bug reported: LibreOffice doesn't launch on 6.1.3.2 (90) in `candidate` on core 16-2.36.1+git1007.f72779e (5920) in `edge`, it just hangs, with no Terminal output, but has the following denials in `journalctl -f`: ``` Nov 12 12:38:19 adam-thinkpad-t430 audit[31984]: AVC apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 12 12:38:19 adam-thinkpad-t430 kernel: audit: type=1400 audit(1542026299.589:542): apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ``` ``` $ snap info libreoffice tracking: candidate refresh-date: 6 days ago, at 08:50 GMT channels: stable:6.1.2.1 (86) 501MB - candidate: 6.1.3.2 (90) 507MB - < beta: ↑ edge: ↑ installed: 6.1.3.2 (90) 507MB - $ snap version snap2.36.1+git1007.f72779e~ubuntu16.04.1 snapd 2.36.1+git1007.f72779e~ubuntu16.04.1 series 16 ubuntu 18.10 kernel 4.18.0-11-generic $ snap info core tracking: edge refresh-date: today at 12:08 GMT channels: stable:16-2.35.5 (5742) 92MB - candidate: 16-2.35.5 (5742) 92MB - beta: 16-2.36.1 (5897) 92MB - edge: 16-2.36.1+git1007.f72779e (5920) 92MB -< installed: 16-2.36.1+git1007.f72779e (5920) 92MB core ``` ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Tags added: snap -- 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/1802911 Title: [snap] LibreOffice doesn't launch Status in libreoffice package in Ubuntu: New Bug description: LibreOffice doesn't launch on 6.1.3.2 (90) in `candidate` on core 16-2.36.1+git1007.f72779e (5920) in `edge`, it just hangs, with no Terminal output, but has the following denials in `journalctl -f`: ``` Nov 12 12:38:19 adam-thinkpad-t430 audit[31984]: AVC apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 12 12:38:19 adam-thinkpad-t430 kernel: audit: type=1400 audit(1542026299.589:542): apparmor="DENIED" operation="open" profile="snap-update-ns.libreoffice" name="/proc/version" pid=31984 comm="3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ``` ``` $ snap info libreoffice tracking: candidate refresh-date: 6 days ago, at 08:50 GMT channels: stable:6.1.2.1 (86) 501MB - candidate: 6.1.3.2 (90) 507MB - < beta: ↑ edge: ↑ installed: 6.1.3.2 (90) 507MB - $ snap version snap2.36.1+git1007.f72779e~ubuntu16.04.1 snapd 2.36.1+git1007.f72779e~ubuntu16.04.1 series 16 ubuntu 18.10 kernel 4.18.0-11-generic $ snap info core tracking: edge refresh-date: today at 12:08 GMT channels: stable:16-2.35.5 (5742) 92MB - candidate: 16-2.35.5 (5742) 92MB - beta: 16-2.36.1 (5897) 92MB - edge: 16-2.36.1+git1007.f72779e (5920) 92MB -< installed: 16-2.36.1+git1007.f72779e (5920) 92MB core ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1401484] Re: Europe/Moscow timezone if out of date
Extracted from xul-ext-lightning 1:60.2.1+build1-0ubuntu1: BEGIN:VTIMEZONE TZID:Europe/Moscow BEGIN:STANDARD TZOFFSETFROM:+0300 TZOFFSETTO:+0300 TZNAME:MSK DTSTART:19700101T00 Now showing as 3 hours so marking as "Fix Released" ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Fix Released -- 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/1401484 Title: Europe/Moscow timezone if out of date Status in thunderbird package in Ubuntu: Fix Released Bug description: xul-ext-lightning 1:31.3.0+build1-0ubuntu0.12.04.1 still has old timezone info for Europe/Moscow: BEGIN:VTIMEZONE TZID:Europe/Moscow X-LIC-LOCATION:Europe/Moscow BEGIN:STANDARD TZOFFSETFROM:+0400 TZOFFSETTO:+0400 TZNAME:MSK DTSTART:19700101T00 END:STANDARD END:VTIMEZONE Russia has changed its timezones recently, so Moscow now has 3 hours delta, not 4. This have been addressed in tzdata 2014f. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1401484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
