[Desktop-packages] [Bug 1350390] Re: Streamming player stops - very high cpu and memory usage
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
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/1350390
Title:
Streamming player stops - very high cpu and memory usage
Status in firefox package in Ubuntu:
Expired
Bug description:
When playing videos via youtube, the second video stops after a few
seconds. Firefox becomes slow, cpu and memory usage increases.
Firefox does not terminate normally, the firefox process(es) keep
running and only stop after being killed.
Easily reproducible.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 33.0~a2~hg20140729r209170-0ubuntu1~umd1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: fglrx
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: strix 7587 F pulseaudio
BuildID: 20140730081036
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed Jul 30 22:39:50 2014
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 2014-06-27 (33 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IpRoute:
default via 172.29.128.1 dev eth0 proto static
172.29.128.0/22 dev eth0 proto kernel scope link src 172.29.128.41
metric 1
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Locales: extensions.sqlite corrupt or missing
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
Gnome Shell Integration -
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so
(google-talkplugin)
Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so
(google-talkplugin)
iTunes Application Detector -
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
(rhythmbox-mozilla)
PrefSources:
prefs.js
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ubu...@ubuntu.com/defaults/preferences/001ubuntu-gnome-mods.js
Profiles: Profile0 (Default) - LastVersion=33.0a2/20140730081036 (In use)
RelatedPackageVersions:
gnome-shell 3.10.4-0ubuntu5.2
google-talkplugin 5.4.2.0-1
rhythmbox-mozilla 3.0.2-0ubuntu2
RfKill:
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 06D7TR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA02:bd02/26/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 990
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1350390/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1662435] Re: Chromium stops XUbuntu 16.04 from going into a screensaver
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1662435 Title: Chromium stops XUbuntu 16.04 from going into a screensaver Status in chromium-browser package in Ubuntu: Expired Bug description: My computer is going into the locked screen of Light Locker just fine if Chromium is turned off. However, if it is running, the computer will *not* turn the screensaver on, regardless of the length of time. Youtube and similar video sites are not loaded into any of the tabs, so it's not a feature that might have been useful. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-LVDS-1: edid-base64: AP///wAGr50hAAAWAQSQJhV4AsiVnldUkiYPUFQBAQEBAQEBAQEBAQEBAQEBFDeAwHA4IEAwZDYAfdYQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTczSFcwMiBWMSAKAFE= dpms: On modes: 1920x1080 enabled: enabled status: connected DRM.card0-VGA-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected Date: Tue Feb 7 09:55:49 2017 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2015-01-19 (749 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) Load-Avg-1min: 2.50 Load-Processes-Running-Percent: 0.1% MachineType: ASUSTeK COMPUTER INC. N76VB ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to xenial on 2016-07-29 (192 days ago) dmi.bios.date: 05/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N76VB.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N76VB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN76VB.205:bd05/24/2013:svnASUSTeKCOMPUTERINC.:pnN76VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N76VB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.chromium-browser.default: [modified] modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2015-01-19T17:52:56.396931 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1662435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1739875] Re: keyboard lost in Firefox after suspend to memory
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
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/1739875
Title:
keyboard lost in Firefox after suspend to memory
Status in firefox package in Ubuntu:
Expired
Bug description:
I'm using Firefox on the web. Then I suspend my computer to memory.
When the computer start again, then I can't type anything into
Firefox. However I can copy the URL with the mouse, close Firefox,
launch Firefox again and paste the URL. Finally I can type characters
again into the new Firefox instance.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 57.0.1+build2-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lecointa 2139 F pulseaudio
BuildID: 20171129230835
Channel: Unavailable
CurrentDesktop: XFCE
Date: Sat Dec 23 13:10:09 2017
ForcedLayersAccel: False
IncompatibleExtensions:
Français Language Pack - langpack...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.254 dev eth0 proto static metric 100
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.10 metric
100
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint: You are currently not seeing messages from other
users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
MostRecentCrashID: bp-b43ba15b-9e75-4f68-9e30-c66a62151002
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=57.0.1/20171129230835 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-b43ba15b-9e75-4f68-9e30-c66a62151002
UpgradeStatus: Upgraded to xenial on 2017-09-02 (111 days ago)
WifiSyslog:
dmi.bios.date: 10/08/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 08R94K
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn08R94K:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6430
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1739875/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747312] Re: firefox freezes
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1747312 Title: firefox freezes Status in firefox package in Ubuntu: Expired Bug description: Firefox freezes a lot https://askubuntu.com/questions/958131/launching-firefox-on-16-04-causes-system-freeze https://askubuntu.com/questions/958715/16-04-freezes-randomly-mostly-while-using-firefox https://askubuntu.com/questions/818800/firefox-freezes-frequently-in-ubuntu-16-04 https://askubuntu.com/questions/818800/firefox-freezes-frequently-in-ubuntu-16-04 So I thought it would be good to submit a feedback to your team to see what's happening and I'll try to do the same with Ubuntu team I was zooming in and out this file http://www.tug.org/texshowcase/diminuendo.pdf, with few opened tabs and it freezes often with other pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1747312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824894] Re: Xorg freeze
[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/1824894 Title: Xorg freeze Status in xorg-server package in Ubuntu: Expired Bug description: When it freezes I typically try and go through my logs. I haven't been successful at finding where it crashes in my syslog. However, I did find what is listed below this time. I've also ran a memory test on my machine which passed. I originally had the nvidia drivers installed but after the first few lockups, I thought it might be driver related so I uninstalled the driver. Apr 15 17:13:09 Ben gnome-shell[2251]: Some code accessed the property 'WindowPreviewMenu' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. \00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Apr 15 17:15:23 Ben systemd-modules-load[394]: Inserted module 'lp' Apr 15 17:15:23 Ben systemd-modules-load[394]: Inserted module 'ppdev' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 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: Mon Apr 15 17:26:09 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: openrazer-driver, 2.5.0, 4.18.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: I don't know GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] [19da:1438] InstallationDate: Installed on 2019-03-29 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=758c51d3-8f49-4a44-860b-49982aebbe46 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0504 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58-E PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/28/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58-EPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1824894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1824671] Re: message reporting app crash on system startup
[Expired for spice-vdagent (Ubuntu) because there has been no activity for 60 days.] ** Changed in: spice-vdagent (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1824671 Title: message reporting app crash on system startup Status in spice-vdagent package in Ubuntu: Expired Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Release: Ubuntu 18.04.2 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center robert@robert-HP-Pavilion-dm4-Notebook-PC:~$ apt-cache policy spice-vdagent spice-vdagent: Installed: 0.17.0-1ubuntu2 Candidate: 0.17.0-1ubuntu2 Version table: *** 0.17.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen The computer was rebooting from the first update following the OS installation, I expected nothing to happen. 4) What happened instead A message popped up on the desktop saying an app crashed asking permission to send a report. I found a log file description of the problem:"Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1824671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824647] Re: Recurrent, annoying clicking sound but not showing any notifications
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1824647 Title: Recurrent, annoying clicking sound but not showing any notifications Status in alsa-driver package in Ubuntu: Expired Bug description: About two weeks ago, my computer began to make a recurrent, irregular, clicking noise every few seconds. It occurs regardless if the computer is running on battery or electrical outlet. There are no notifications associated with this clicking noise. Changing the notifications section in systems does not stop this annoying clicking noise. This noise continues even when all browsers are shut off. Only turning the volume off stops the clicking noise. I cannot watch movies or youtube without hearing this annoying clicking noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bob2260 F pulseaudio /dev/snd/controlC0: bob2260 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 12:17:32 2019 InstallationDate: Installed on 2019-03-30 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnAspireE5-571:pvrV1.26:rvnAcer:rnEA50_HB:rvrV1.26:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.version: V1.26 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815089] Re: 100% CPU / usr / lib / tracker / tracker-extract
[Expired for tracker (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tracker (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1815089 Title: 100% CPU / usr / lib / tracker / tracker-extract Status in tracker package in Ubuntu: Expired Bug description: The / usr / lib / tracker / tracker-extract is using almost 100% CPU resources see attached image After updates on today's date 07/02/2019 has improved the crashes, but the hunger for CPU continues. ** O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos da CPU vide imagem em anexo Após atualizações na data de hoje 07/02/2019 melhorou os travamentos, mas a fome por CPU continua. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1815089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824235] Re: nautilus package crashes on after power on.
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1824235 Title: nautilus package crashes on after power on. Status in nautilus package in Ubuntu: Expired Bug description: I am not sure if I am doing something specific that is invoking the crash. I see the crash report everytime ubuntu powers on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 13:33:23 2019 InstallationDate: Installed on 2016-04-27 (1078 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-08-15 (238 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1824235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832903] Re: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver
I was able to reproduce the problem with 4.15.0-51, but problem seems to be gone using the hwe kernel 4.18.0-21-generic. I'll do a kernel bisection and try to find the commit which fixes the situation. I'll also ask another impacted user to confirm if v4.18 works fine too, to double-check my testing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1832903 Title: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in wayland package in Ubuntu: New Bug description: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login screen doesn't work if 'Wayland' is in use (default) and if video kernel driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Access the machine via ssh or any other recovery approaches. - Force the login screen to use x11: File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [44] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: vmwgfx Kernel modules: vmwgfx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832875] Re: On-screen keyboard lacks several French layouts
** Changed in: gnome-shell Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832875 Title: On-screen keyboard lacks several French layouts Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Triaged Bug description: The on-screen keyboard in Gnome Shell is not localized (at least for some locales), and always displays a QWERTY keyboard, independently of the selected layout. See upstream issue https://gitlab.gnome.org/GNOME/gnome- shell/issues/997 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823857] Re: Backport to bionic a patch for improved fractional scaling
Hello Mitar, or anyone else affected, Accepted gnome-control-center into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-control-center/1:3.28.2-0ubuntu0.18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1823857 Title: Backport to bionic a patch for improved fractional scaling Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Bug description: * Impact In some cases after a configuration chang ethe "apply" button is not displayed * Test case On a multimonitor setup, go to settings -> display and change the monitors layout and zoom factor, following a change a "apply" button should be displayed * Regression potential The change is in the monitor configurations logic, just make sure that changing resolution/layouts work correctly and is restored are a logout/login cycle -- I have been debugging why I do not get "Apply" button in Displays view when my primary monitor is on the left of the external monitor, but it appears when it is on the right. I traced the problem down to this issue and patch: https://gitlab.gnome.org/GNOME/mutter/issues/412 https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346 Reading this issue tracker I see that some issues people are reporting my be connected to this problem. I would suggest, if possible, that this patch is backported to Bionic and its version of gnome-control- center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
Hello ethan.hsieh, or anyone else affected, Accepted gnome-control-center into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-control-center/1:3.28.2-0ubuntu0.18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: Fix Committed Status in OEM Priority Project bionic series: Fix Committed Status in OEM Priority Project xenial series: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Xenial: Fix Committed Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-control-center source package in Disco: Fix Released Bug description: [Impact] Fail to set delay time when the value is 90 minutes. In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 (90*60). When setting the delay time to 90 minutes, the UI will show "80 minutes" after reopening "All Settings". (Please refer to the photo in #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) Check if the value is 90 minutes. [Regression Potential] Low. The value of 90 minutes is wrong. Just correct the value to 5400. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
Hello ethan.hsieh, or anyone else affected, Accepted gnome-control-center into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-control-center/1:3.18.2-1ubuntu6.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- 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/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: Fix Committed Status in OEM Priority Project bionic series: Fix Committed Status in OEM Priority Project xenial series: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Xenial: Fix Committed Status in gnome-control-center source package in Disco: Fix Released Bug description: [Impact] Fail to set delay time when the value is 90 minutes. In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 (90*60). When setting the delay time to 90 minutes, the UI will show "80 minutes" after reopening "All Settings". (Please refer to the photo in #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) Check if the value is 90 minutes. [Regression Potential] Low. The value of 90 minutes is wrong. Just correct the value to 5400. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832913] [NEW] Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Public bug reported: I am getting this error in my log, Ubuntu 18.04: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1832913 Title: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in gnome-session package in Ubuntu: New Bug description: I am getting this error in my log, Ubuntu 18.04: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1832913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832903] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1832903 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1832903 Title: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in wayland package in Ubuntu: New Bug description: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login screen doesn't work if 'Wayland' is in use (default) and if video kernel driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Access the machine via ssh or any other recovery approaches. - Force the login screen to use x11: File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [44] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: vmwgfx Kernel modules: vmwgfx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832907] [NEW] Update to 67.0.2
Public bug reported: https://www.mozilla.org/en-US/firefox/67.0.2/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: Fix Released ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- 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/1832907 Title: Update to 67.0.2 Status in firefox package in Ubuntu: Fix Released Bug description: https://www.mozilla.org/en-US/firefox/67.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1832907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832903] [NEW] 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver
Public bug reported: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login screen doesn't work if 'Wayland' is in use (default) and if video kernel driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Access the machine via ssh or any other recovery approaches. - Force the login screen to use x11: File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [44] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: vmwgfx Kernel modules: vmwgfx ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Description changed: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login - screen doesn't work if it 'wayland' is in use (default) and if video - kernel driver inside is 'vgwfx'. + screen doesn't work if 'Wayland' is in use (default) and if video kernel + driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Force the login screen to use x11: + - Access the machine via ssh or any other recovery approaches. + - Force the login screen to use x11: - File: /etc/gdm3/custom.conf + File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false - I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. - So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. + I tried to reproduce the behaviour on my personal laptop, KVM guest, ... + without success. + So far it is only reproducible when the 'vgwfx' driver is in use in + combination with Wayland. + + lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) - Subsystem: VMware SVGA II Adapter [15ad:0405] - Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- - Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- - Capabilities: [44] PCI Advanced Features - AFCap: TP+ FLR+ - AFCtrl: FLR- - AFStatus: TP- - Kernel driver in use: vmwgfx - Kernel modules: vmwgfx + Subsystem: VMware SVGA II Adapter [15ad:0405] + Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- + Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- + Capabilities: [44] PCI Advanced Features + AFCap: TP+ FLR+ + AFCtrl: FLR- + AFStatus: TP- + Kernel driver in use: vmwgfx + Kernel modules: vmwgfx -- 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/1832903 Title: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login screen doesn't work if 'Wayland' is in use (default) and if video kernel driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Access the machine via ssh or any other recovery approaches. - Force the login screen to use x11: File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405]
[Desktop-packages] [Bug 1832656] Re: chromium-browser deb->snap transition breaks ubuntukylin image builds
This bug was fixed in the package ubuntukylin-meta - 0.37 --- ubuntukylin-meta (0.37) eoan; urgency=medium * Update update.cfg for eoan * disco->eoan * Refreshed dependencies * Removed chromium-browser from desktop-recommends. LP: #1832656. -- handsome_feng Fri, 14 Jun 2019 16:32:50 +0800 ** Changed in: ubuntukylin-meta (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1832656 Title: chromium-browser deb->snap transition breaks ubuntukylin image builds Status in chromium-browser package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Triaged Status in ubuntukylin-meta package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: New Status in livecd-rootfs source package in Eoan: Triaged Status in ubuntukylin-meta source package in Eoan: Fix Released Bug description: From https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881: Preparing to unpack .../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 It is possible that the flavors should switch to seeding the snap instead of the deb. However, it's unclear to me why the deb is failing to talk to the Snap Store, because seeding of snaps DOES work from within image builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832869] Re: gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows meta_workspace_list_windows
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 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/. + + https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58 + https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 + https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c + https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76 + https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680 -- 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/1832869 Title: gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows meta_workspace_list_windows Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 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/. https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58 https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76 https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832895] [NEW] /usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call
*** This bug is a duplicate of bug 1832869 *** https://bugs.launchpad.net/bugs/1832869 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1832895 Title: /usr/bin/gnome- shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832895] Re: /usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call
*** This bug is a duplicate of bug 1832869 *** https://bugs.launchpad.net/bugs/1832869 ** This bug has been marked a duplicate of bug 1832869 gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows meta_workspace_list_windows -- 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/1832895 Title: /usr/bin/gnome- shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832656] Re: chromium-browser deb->snap transition breaks ubuntukylin image builds
opening a task on livecd-rootfs about the question of injecting SNAPPY_STORE_NO_CDN=1 into the image build environment. ** Changed in: livecd-rootfs (Ubuntu Eoan) Importance: Undecided => High ** Changed in: livecd-rootfs (Ubuntu Eoan) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1832656 Title: chromium-browser deb->snap transition breaks ubuntukylin image builds Status in chromium-browser package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Triaged Status in ubuntukylin-meta package in Ubuntu: New Status in chromium-browser source package in Eoan: New Status in livecd-rootfs source package in Eoan: Triaged Status in ubuntukylin-meta source package in Eoan: New Bug description: From https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881: Preparing to unpack .../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 It is possible that the flavors should switch to seeding the snap instead of the deb. However, it's unclear to me why the deb is failing to talk to the Snap Store, because seeding of snaps DOES work from within image builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832656] Re: chromium-browser deb->snap transition breaks ubuntukylin image builds
The debdiff looks fine, sponsoring. Please note that there is a draft policy of the requirements around seeding of snaps on Ubuntu images, which applies to flavors as well https://wiki.ubuntu.com/UbuntuSeededSnaps The UbuntuKylin team should assure themselves that these requirements are met. Note in particular if the chromium snap does not have the set of channels required by this policy the image will still fail to build. ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1832656 Title: chromium-browser deb->snap transition breaks ubuntukylin image builds Status in chromium-browser package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Triaged Status in ubuntukylin-meta package in Ubuntu: New Status in chromium-browser source package in Eoan: New Status in livecd-rootfs source package in Eoan: Triaged Status in ubuntukylin-meta source package in Eoan: New Bug description: From https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881: Preparing to unpack .../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 It is possible that the flavors should switch to seeding the snap instead of the deb. However, it's unclear to me why the deb is failing to talk to the Snap Store, because seeding of snaps DOES work from within image builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832885] [NEW] package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1
Public bug reported: I tried to install vdr. lirc comes as a dependency... ProblemType: Package DistroRelease: Ubuntu 19.04 Package: lirc 0.10.1-5.2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 14 21:14:27 2019 ErrorMessage: installed lirc package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: lirc Title: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lirc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- 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/1832885 Title: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 Status in lirc package in Ubuntu: New Bug description: I tried to install vdr. lirc comes as a dependency... ProblemType: Package DistroRelease: Ubuntu 19.04 Package: lirc 0.10.1-5.2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 14 21:14:27 2019 ErrorMessage: installed lirc package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: lirc Title: package lirc 0.10.1-5.2 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1832885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress -- 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/1722886 Title: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data Status in gnome-shell package in Ubuntu: In Progress Bug description: When a bug is submitted to ubuntu about gnome-shell it would be convenient to have such settings. Monitors.xml is quite important to understand the configuration for mutter-related crashes, while other desktop settings (to be filtered- out) could be needed too. Ah, also the logs from journalctl /usr/bin/gnome-shell -b -o short-iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user
** Changed in: accountsservice Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1832865 Title: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user Status in accountsservice: New Status in accountsservice package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.1-1ubuntu1~19.04.1, the problem page at https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 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/accountsservice/+bug/1832865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.
I can confirm this is still happening in Ubuntu 19.04. -- 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/1723117 Title: Desktop icons goes under the Dock, if the Dock is set to auto-hide. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: This bug is found in Artful. Desktop icons goes under the Dock, if the Dock is set to auto-hide. Either the Dock should auto-hide on the Desktop as well, or the Desktop Icons should leave a margin with the same size of the Dock. This happen both horizontal and vertical Dock positions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1723117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832124] Re: Right-click file on desktop > Move to Trash frequently crashes gnome-shell
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Right-click file on desktop > Move to Trash frequently crashes gnome- shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: In 19.04 Disco fully up to date. Reproduced on two different machines: 1. Log into Wayland session (did not try with X) 2. touch ~/Desktop/testfile 3. Right-click testfile on Desktop > Move to Trash -> gnome-shell crashes in around 50% of instances in my case. I did not find out what's the difference. I do run a few other gnome-shell extensions, but all from the Ubuntu repos except for Remove Accessibility. There are quite some occurrences of org.gnome.Shell.desktop in journalctl, though I didn't correlate yet as the issues seems easy to repro. If you can't repro, pls let me know and I can look for clues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.3-1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 9 12:51:20 2019 InstallationDate: Installed on 2018-09-13 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-12 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832869] Re: gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows meta_workspace_list_windows
The crash is happening since gnome-shell/mutter 3.28.3+git20190124. I wasn't able to track-down the issue since we're missing Javascript stacktrace so, for people who can replicate this, we'd need to get a trace. You can have one following what said in https://is.gd/wiki_gnome_shell_crash_debug ** Summary changed: - /usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call + gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows meta_workspace_list_windows ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1832869 Title: gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows meta_workspace_list_windows Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832875] [NEW] On-screen keyboard lacks several French layouts
Public bug reported: The on-screen keyboard in Gnome Shell is not localized (at least for some locales), and always displays a QWERTY keyboard, independently of the selected layout. See upstream issue https://gitlab.gnome.org/GNOME/gnome-shell/issues/997 ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gnome-shell (Ubuntu Bionic) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Triaged ** Tags: fixed-in-3.32.0 fixed-upstream ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Bionic) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #997 https://gitlab.gnome.org/GNOME/gnome-shell/issues/997 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/997 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832875 Title: On-screen keyboard lacks several French layouts Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Triaged Bug description: The on-screen keyboard in Gnome Shell is not localized (at least for some locales), and always displays a QWERTY keyboard, independently of the selected layout. See upstream issue https://gitlab.gnome.org/GNOME/gnome- shell/issues/997 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832870] [NEW] /usr/bin/gnome-shell:11:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call:gjs_invoke_c_function
*** This bug is a duplicate of bug 1832869 *** https://bugs.launchpad.net/bugs/1832869 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1832870 Title: /usr/bin/gnome- shell:11:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call:gjs_invoke_c_function Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832871] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_is_a:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call
*** This bug is a duplicate of bug 1832869 *** https://bugs.launchpad.net/bugs/1832869 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1832871 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_a:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832872] [NEW] /usr/bin/gnome-shell:11:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call:gjs_invoke_c_function
*** This bug is a duplicate of bug 1832869 *** https://bugs.launchpad.net/bugs/1832869 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco eoan -- 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/1832872 Title: /usr/bin/gnome- shell:11:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call:gjs_invoke_c_function Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759008] Re: Revert automatic suspend by default for bionic?
Still broken with MATE desktop on Ubuntu 18.04.2 LTS. If I run mate- power-preferences and select ON AC Power - Put computer to sleep when inactive for: [never] the computer still automatically sleeps (enters S3) after 20 minutes. $ grep -C1 sleep-inactive-ac-timeout /usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override [org.gnome.settings-daemon.plugins.power] sleep-inactive-ac-timeout = 0 I've tried to manually run $ systemd-inhibit --mode=block sleep 2h but the system still enters S3 after 20 minutes unless I disable screen saver using mate-inhibit-applet. $ apt policy mate-desktop mate-desktop: Installed: 1.20.1-2ubuntu1 Candidate: 1.20.1-2ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1759008 Title: Revert automatic suspend by default for bionic? Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Bionic: Fix Released Bug description: GNOME 3.28 has turned Automatic Suspend on by default and set it to 20 minutes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/2fdb48fa I generally think this is a good thing. There are a few issues though. 1. The computer will still suspend even if there are remote users logged in or the computer is being used as a server for files, printers, etc. 2. Some software doesn't set inhibit correctly. ~ahasenack mentioned he was using the Spotify Snap and the computer suspend after 20 minutes. (Maybe Spotify needs to use the screen-inhibit-control snap interface.) 3. Even if it does set inhibit, there is a report that the computer will suspend as soon as the inhibit is removed if there is no other activity. (Imagine a movie playing. At the end of the movie, the computer goes to sleep immediately.) More details and proposed fix at https://bugzilla.gnome.org/show_bug.cgi?id=705942#c21 4. There is no GUI way to change this setting for the login screen yet. https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22 5. Some users think that desktop computers should be always running unless told otherwise. Personally, I don't give this argument much weight at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1759008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832872] Re: /usr/bin/gnome-shell:11:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call:gjs_invoke_c_function
*** This bug is a duplicate of bug 1832869 *** https://bugs.launchpad.net/bugs/1832869 ** This bug has been marked a duplicate of bug 1832869 /usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call -- 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/1832872 Title: /usr/bin/gnome- shell:11:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call:gjs_invoke_c_function Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832869] [NEW] /usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1832869 Title: /usr/bin/gnome- shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832870] Re: /usr/bin/gnome-shell:11:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call:gjs_invoke_c_function
*** This bug is a duplicate of bug 1832869 *** https://bugs.launchpad.net/bugs/1832869 ** This bug has been marked a duplicate of bug 1832869 /usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call -- 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/1832870 Title: /usr/bin/gnome- shell:11:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call:gjs_invoke_c_function Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832656] Re: chromium-browser deb->snap transition breaks ubuntukylin image builds
** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1832656 Title: chromium-browser deb->snap transition breaks ubuntukylin image builds Status in chromium-browser package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in chromium-browser source package in Eoan: New Status in ubuntukylin-meta source package in Eoan: New Bug description: From https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881: Preparing to unpack .../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 It is possible that the flavors should switch to seeding the snap instead of the deb. However, it's unclear to me why the deb is failing to talk to the Snap Store, because seeding of snaps DOES work from within image builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832871] Re: /usr/bin/gnome-shell:11:g_type_check_instance_is_a:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call
*** This bug is a duplicate of bug 1832869 *** https://bugs.launchpad.net/bugs/1832869 ** This bug has been marked a duplicate of bug 1832869 /usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call -- 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/1832871 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_a:meta_display_list_windows:meta_workspace_list_windows:ffi_call_unix64:ffi_call Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826918] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_
** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- 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/1826918 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_unref() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+git20190410-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/1a5d1f99fd9215f7a79b718d2e915c675ebcd69f 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/gnome-shell/+bug/1826918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Here you are, Till. Three sections, one for each NM version containing the two dig requests during the tests, plus one for a dig to contact the local DNS explicitly. nm-1.10.6: $ dig dnsmasq.local.org.com | grep -FA1 ';; ANSWER' # first attempt always fails ;; ANSWER SECTION: dnsmasq.local.org.com. 600 IN A 127.0.0.1 $ dig dnsmasq.local.org.com | grep -FA1 ';; ANSWER' # second onwards always works ;; ANSWER SECTION: dnsmasq.local.org.com. 600 IN A 172.22.0.2 nm-1.10.14: $ dig dnsmasq.local.org.com | grep -FA1 ';; ANSWER' ;; ANSWER SECTION: dnsmasq.local.org.com. 600 IN A 127.0.0.1 # first attempt always fails $ dig dnsmasq.local.org.com | grep -FA1 ';; ANSWER' ;; ANSWER SECTION: dnsmasq.local.org.com. 600 IN A 127.0.0.1 # all subsequent attempts fail too :( Direct dig example: $ dig dnsmasq.local.org.com @127.0.0.54 | grep -FA1 ';; ANSWER' # direct query to local dns specified in config (see main issue body) ;; ANSWER SECTION: dnsmasq.local.org.com. 600 IN A 172.22.0.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Bionic: Triaged Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1746656] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_display@1: error 1: invalid arguments for
** Tags added: eoan -- 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/1746656 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_display@1: error 1: invalid arguments for zwp_relative_pointer_manager_v1@15.get_relative_pointer\n"] Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.19.5-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/919f7b6d37f2b2e23bf18d4cc9fad6a6116edf82 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/xorg-server/+bug/1746656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user
Not a gnome-shell issue, but an accountsservice one. ** Summary changed: - /usr/bin/gnome-shell:11:g_str_hash:g_hash_table_hash_to_index:g_hash_table_lookup_node:g_hash_table_lookup:update_user + gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Changed in: accountsservice (Ubuntu) Status: New => In Progress ** Changed in: accountsservice (Ubuntu) Status: In Progress => Triaged ** Bug watch added: gitlab.freedesktop.org/accountsservice/accountsservice/issues #55 https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/55 ** Also affects: accountsservice via https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/55 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832865 Title: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user Status in accountsservice: Unknown Status in accountsservice package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.1-1ubuntu1~19.04.1, the problem page at https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 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/accountsservice/+bug/1832865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820859] Re: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb
Here is the Stacktrace from the Error Report:
#0 g_application_impl_get_dbus_object_path (impl=0x0) at
../../../gio/gapplicationimpl-dbus.c:855
No locals.
#1 0x7f1d99b3afa4 in g_application_get_dbus_object_path
(application=) at ../../../gio/gapplication.c:2108
__FUNCTION__ = "g_application_get_dbus_object_path"
#2 0x5618fcdb1b05 in update_dbus_opened_locations (self=0x5618fed38140) at
../src/nautilus-application.c:1407
priv = 0x5618fed38010
i =
l =
sl =
locations = 0x0
locations_size = 0
locations_array =
window =
location =
dbus_object_path = 0x0
windows_to_locations = 0x0
b = {u = {s = {partial_magic = 0, type = 0x5618ff89f620, y =
{94665366435361, 0, 0, 18446744073709551615, 94665365961056, 8, 0, 3,
1033660112, 0, 0, 0, 0, 0}}, x = {0, 94665366435360, 94665366435361, 0, 0,
18446744073709551615, 94665365961056, 8, 0, 3, 1033660112, 0, 0, 0, 0, 0}}}
wb = {u = {s = {partial_magic = 0, type = 0x7f1d80003980, y = {1, 32,
94665366770608, 9448834217829765632, 0, 94665354542176, 6, 0, 0,
94665354566224, 0, 139765121204133, 32, 94665365837920}}, x = {0,
139764678277504, 1, 32, 94665366770608, 9448834217829765632, 0, 94665354542176,
6, 0, 0, 94665354566224, 0, 139765121204133, 32, 94665365837920}}}
windows_to_locations_builder = {u = {s = {partial_magic =
94665365356048, type = 0x5618ff797e10, y = {0, 0, 4243608448, 94665354538272,
4, 8, 94665354567736, 0, 8, 139765121205065, 0, 139765121204849,
94665365356048, 4286152208}}, x = {94665365356048, 94665365356048, 0, 0,
4243608448, 94665354538272, 4, 8, 94665354567736, 0, 8, 139765121205065, 0,
139765121204849, 94665365356048, 4286152208}}}
__FUNCTION__ = "update_dbus_opened_locations"
#3 0x5618fcdb4d8d in bus_acquired_cb (conn=,
name=, user_data=0x5618ff794ac0) at
../src/nautilus-freedesktop-dbus.c:168
fdb = 0x5618ff794ac0
application =
__FUNCTION__ = "bus_acquired_cb"
#4 0x7f1d99b6fec4 in connection_get_cb (source_object=,
res=0x5618fed5c840, user_data=0x5618ff799ee0) at
../../../gio/gdbusnameowning.c:487
client = 0x5618ff799ee0
#5 0x7f1d99b0f059 in g_task_return_now (task=0x5618fed5c840) at
../../../gio/gtask.c:1209
No locals.
#6 0x7f1d99b0fb73 in g_task_return (task=0x5618fed5c840, type=) at ../../../gio/gtask.c:1278
source = 0x7f1d74001340
#7 0x7f1d99b620c2 in bus_get_async_initable_cb
(source_object=0x5618fed4e020, res=0x5618fed5c9c0,
user_data=user_data@entry=0x5618fed5c840) at ../../../gio/gdbusconnection.c:7346
task = 0x5618fed5c840
error = 0x0
__FUNCTION__ = "bus_get_async_initable_cb"
_g_boolean_var_ =
#8 0x7f1d99b0f059 in g_task_return_now (task=0x5618fed5c9c0) at
../../../gio/gtask.c:1209
No locals.
#9 0x7f1d99b0f099 in complete_in_idle_cb (task=0x5618fed5c9c0) at
../../../gio/gtask.c:1223
No locals.
#10 0x7f1d9a67e958 in ?? ()
No symbol table info available.
#11 0x5618fed4dc30 in ?? ()
No symbol table info available.
#12 0x7f1d in ?? ()
No symbol table info available.
#13 0x in ?? ()
No symbol table info available.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1820859
Title:
/usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb
Status in nautilus package in Ubuntu:
Triaged
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.31.90-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9
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/1820859/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832865] [NEW] gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.1-1ubuntu1~19.04.1, the problem page at https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 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: accountsservice Importance: Unknown Status: Unknown ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: Triaged ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Won't Fix ** Tags: disco -- 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/1832865 Title: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user Status in accountsservice: Unknown Status in accountsservice package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.1-1ubuntu1~19.04.1, the problem page at https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 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/accountsservice/+bug/1832865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832856] [NEW] Gnome-shell crashes frequently
Public bug reported: After the update to 3.32.1 gnome-shell crashes frequently. Before, on 3.32.0, I had no crashes and had a stable desktop. Now, I get 3-4 crashes a day, on average. Here is log snippet on the crash: Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: GNOME Shell crashed with signal 11 Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: == Stack trace for context 0x5602dcfe82c0 == Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #0 7ffe03deaae0 b resource:///org/gnome/shell/ui/workspaceSwitcherPopup.js:129 (7f2b39c37820 @ 351) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #1 7ffe03deab90 b /home/gjm/.local/share/gnome-shell/extensions/wsmat...@martin.zurowietz.de/IndicatorWsmatrixPopup.js:106 (7f2b38480790 @ 24) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #2 5602e16865c8 i resource:///org/gnome/shell/ui/workspaceSwitcherPopup.js:152 (7f2b39c37940 @ 43) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #3 5602e1686520 i /home/gjm/.local/share/gnome-shell/extensions/wsmat...@martin.zurowietz.de/BaseWorkspaceSwitcherPopup.js:13 (7f2b38480160 @ 24) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #4 5602e1686420 i /home/gjm/.local/share/gnome-shell/extensions/wsmat...@martin.zurowietz.de/WmOverride.js:332 (7f2b3847e4c0 @ 2358) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #5 7ffe03dec9c0 I self-hosted:981 (7f2b39e50940 @ 474) Jun 14 14:59:20 falcon gnome-session-binary[6929]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jun 14 14:59:20 falcon gnome-session[6929]: gnome-session-binary[6929]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 I talked to the maintainer of wsmatrix extension and, as he suggested, I disabled the extension and concluded that that the crashes are not the extension's fault. If there something I can do to help debug this issue I'll be glad to help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 15:00:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-14 (546 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-18 (56 days ago) mtime.conffile..etc.apport.crashdb.conf: 2018-11-21T09:13:30.219492 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832856 Title: Gnome-shell crashes frequently Status in gnome-shell package in Ubuntu: New Bug description: After the update to 3.32.1 gnome-shell crashes frequently. Before, on 3.32.0, I had no crashes and had a stable desktop. Now, I get 3-4 crashes a day, on average. Here is log snippet on the crash: Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: GNOME Shell crashed with signal 11 Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: == Stack trace for context 0x5602dcfe82c0 == Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #0 7ffe03deaae0 b resource:///org/gnome/shell/ui/workspaceSwitcherPopup.js:129 (7f2b39c37820 @ 351) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #1 7ffe03deab90 b /home/gjm/.local/share/gnome-shell/extensions/wsmat...@martin.zurowietz.de/IndicatorWsmatrixPopup.js:106 (7f2b38480790 @ 24) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #2 5602e16865c8 i resource:///org/gnome/shell/ui/workspaceSwitcherPopup.js:152 (7f2b39c37940 @ 43) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #3 5602e1686520 i /home/gjm/.local/share/gnome-shell/extensions/wsmat...@martin.zurowietz.de/BaseWorkspaceSwitcherPopup.js:13 (7f2b38480160 @ 24) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #4 5602e1686420 i /home/gjm/.local/share/gnome-shell/extensions/wsmat...@martin.zurowietz.de/WmOverride.js:332 (7f2b3847e4c0 @ 2358) Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: #5 7ffe03dec9c0 I self-hosted:981 (7f2b39e50940 @ 474) Jun 14 14:59:20 falcon gnome-session-binary[6929]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jun 14 14:59:20 falcon gnome-session[6929]: gnome-session-binary[6929]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 I talked to the maintainer of wsmatrix extension and, as he suggested, I disabled the extension and concluded that that the crashes are not the extension's fault. If there something I can do to help debug this issue I'll be glad to help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package:
[Desktop-packages] [Bug 1832426] Re: "Program" is not responding when debugging in gdb
The same problem. Ubuntu 18.04 QT Creator (gdb 8.2) gnome-shell 3.28.4 Repeatedly warning "MyApp is not responding" under debugging -- 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/1832426 Title: "Program" is not responding when debugging in gdb Status in gnome-shell package in Ubuntu: New Bug description: I believe this is a regression for bug 1740869: is not responding window is constantly showing when debugging a program I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint this window shows up and I can't get it to stop asking me to close the program. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 19.04 Release: 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.1-1ubuntu1~19.04.1 Candidate: 3.32.1-1ubuntu1~19.04.1 Version table: *** 3.32.1-1ubuntu1~19.04.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 3) What you expected to happen When I hit a breakpoint in gdb, the program should stop. 4) What happened instead The program stops and ubuntu asks me if i want to kill the program. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 22:03:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager
** Changed in: exo Status: Confirmed => Fix Released -- 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/1778069 Title: [xfce] nautilus don't open files if set as default file manager Status in Exo: Fix Released Status in exo package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in xubuntu-default-settings package in Ubuntu: Fix Released Status in nautilus package in Debian: New Bug description: If Nautilus is set as the preferred file manager with exo-preferred- applications, it no longer opens files. It opens only directories, .desktop files and executable files. Trying to open a file, be using Enter or with double mouse click, as a text file or a video makes Nautilus window blink for a instant and nothing happens. To be able to open the files, it's needed to choose to open with another application and then choose the application. Once Nautilus is unset as the default file manager (Thunar is chosen, for example), it starts to work fine again, opening files properly. Nautilus' Debian Sid version do not have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 Uname: Linux 4.17.2-041702-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 21 10:55:41 2018 InstallationDate: Installed on 2017-06-13 (372 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1778069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778069]
Resolved with the following commits: https://git.xfce.org/xfce/exo/commit/?id=404a7ef73246b73cb4cd2a4ab8cc10e1a02d6b74 Always terminates the mimetype associations with ";" https://git.xfce.org/xfce/exo/commit/?id=48e12f1d5f31e576f7017c50785032ef6d22cfd1 Removes bad entries that should no longer be used. https://git.xfce.org/xfce/exo/commit/?id=8bc59ad1c48df132e917337bd08211be58af5bb1 Possibly related, this synchronizes the preferences with gio-mime. Will be available with Exo 0.12.6, release shortly. -- 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/1778069 Title: [xfce] nautilus don't open files if set as default file manager Status in Exo: Fix Released Status in exo package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in xubuntu-default-settings package in Ubuntu: Fix Released Status in nautilus package in Debian: New Bug description: If Nautilus is set as the preferred file manager with exo-preferred- applications, it no longer opens files. It opens only directories, .desktop files and executable files. Trying to open a file, be using Enter or with double mouse click, as a text file or a video makes Nautilus window blink for a instant and nothing happens. To be able to open the files, it's needed to choose to open with another application and then choose the application. Once Nautilus is unset as the default file manager (Thunar is chosen, for example), it starts to work fine again, opening files properly. Nautilus' Debian Sid version do not have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 Uname: Linux 4.17.2-041702-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 21 10:55:41 2018 InstallationDate: Installed on 2017-06-13 (372 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1778069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829718] Re: Network printers (cups-browsed) disappear after each CUPS update on client side
Just a few more information about this issue. This is the cups-browsed's state just after a cups update... is dead... root@foo-ubuntu:/home/foo# service cups-browsed status ● cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: inactive (dead) since ven 2019-06-14 14:51:38 CEST; 2min 27s ago Main PID: 927 (code=exited, status=0/SUCCESS) jun 14 14:35:02 foo-ubuntu systemd[1]: Started Make remote CUPS printers available locally. jun 14 14:51:38 foo-ubuntu systemd[1]: Stopping Make remote CUPS printers available locally... jun 14 14:51:38 foo-ubuntu systemd[1]: Stopped Make remote CUPS printers available locally. And here the syslog just when update is applied... Jun 14 14:51:32 foo-ubuntu systemd[1]: Stopped Daily apt upgrade and clean activities. Jun 14 14:51:32 foo-ubuntu systemd[1]: Stopped Daily apt download activities. Jun 14 14:51:32 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:32 foo-ubuntu systemd[1]: Started CUPS Scheduler. Jun 14 14:51:32 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:34 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:34 foo-ubuntu systemd[1]: Started CUPS Scheduler. Jun 14 14:51:34 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:34 foo-ubuntu systemd[1]: Started Daily apt upgrade and clean activities. Jun 14 14:51:34 foo-ubuntu systemd[1]: Started Daily apt download activities. Jun 14 14:51:37 foo-ubuntu gnome-session[1647]: debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopped CUPS Scheduler. Jun 14 14:51:38 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:38 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopping Make remote CUPS printers available locally... Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopped Make remote CUPS printers available locally. Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopping CUPS Scheduler... Jun 14 14:51:38 foo-ubuntu systemd[1]: Stopped CUPS Scheduler. Jun 14 14:51:38 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:38 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:38 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:39 foo-ubuntu systemd[1]: Started ACPI event daemon. Jun 14 14:51:41 foo-ubuntu systemd[1]: Reloading. Jun 14 14:51:42 foo-ubuntu systemd[1]: Started ACPI event daemon. -- 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/1829718 Title: Network printers (cups-browsed) disappear after each CUPS update on client side Status in cups package in Ubuntu: New Bug description: Hi, We have a cups server (ubuntu) that centralize all our network printers. Each desktop users on Ubuntu (16.04, 18.04) are looking in that print server to retrieve those printers. It works fine but... # /etc/cups/cups-browsed.conf in a desktop user ... BrowseRemoteProtocols cups dnssd BrowsePoll 192.168.10.80:631 # CUPS server ... Each time that an CUPS update is applied on the client side all printers disappear from the listing and users are unable to print. So i have to connect to xxx computers in our company to restart the cups- browsed service... This problem exist from some years.. but still not resolved and i didn't found a way to fix it. Workaround: - sudo service cups-browsed restart OR reboot the computer Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831555] Re: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from clutter_actor_allocate_internal() from cl
Fixed with https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/576/ ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1831555 Title: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from clutter_actor_allocate_internal() from clutter_actor_allocate() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Bug description: This is a regression for GNOME Shell / mutter 3.32.1. Tracking upstream at https://gitlab.gnome.org/GNOME/gnome- shell/issues/1295 The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/7a0ffc1caa388737d61043fd4a0ee45677b63d71 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/. Similar stacktrace at https://errors.ubuntu.com/problem/66c2476d86f4d697ff373f99f20c6134c6b5fab3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1831555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1753884] Re: session logout after suspend
This happens to me periodically with Ubuntu 16.04.6 LTS, Kernel 4.14.114. External HDMI 1080p TV nVidia GTX 970M driven External HDMI 4K TV i915 Thunderbolt3 USB-C driven Internal Dell 1080p LCD i915 driven Method: 1) close laptop lid with power & systemd set to "do nothing" 2) external monitors will disconnect (no signal) and have to move mouse to reconnect. 3) select GUI suspend from external monitor 4) power off external screens after system suspends 5) power on external screens 6) open laptop lid to resume 7) about 20% of time login screen appears and all work is lost If fixed in 17.10 would be nice to see backported to 16.04 as current plans for upgrade aren't until 20.04. -- 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/1753884 Title: session logout after suspend Status in gnome-shell package in Ubuntu: Fix Released Bug description: Only when I have a second monitor plugged in, if I close the lid of my laptop, my session gets logged out. What I'm expecting is the lock screen comes up. Sometimes (but not always) the second monitor will flash the "logged out" screen for a second or two before going dim. I have "Suspend even if external monitor is plugged in" enabled in Tweak Tools. WORKAROUND: Suspend via the GUI with the lid open. WORKAROUND: Unplug the second monitor before closing the lid. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Mar 6 18:07:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-02-15 (19 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20AQ009HUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET78WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ009HUS 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ009HUS dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Some clarification: 1. dns-priority=-1 used to work (openvpn had highest DNS priority over other connections) before the regression happend. 2. I rebooted my system after changing config to dns-search=~ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Bionic: Triaged Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
Daniel After uncommenting the Wayland option the login appears, I can log in but the desktop refuses to resize. This was working previously. Entering full screen however works and doesn't crash the system. The crash with kernel option nomodeset when resizing or attempting fullscreen is probably a different bug as you said. -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it Status in mutter package in Ubuntu: Invalid Status in mutter source package in Bionic: Incomplete Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/mutter/+bug/1832138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
I have some extra information that might lead you into the right direction. I used the following extra line in my openvpn connection config file (/etc/NetworkManager/system-connections/vpn_connection_name): [ipv4] dns-priority=-1 After the update DNS received from OpenVPN connection was not respected anymore. Today I replaced that line with the following: [ipv4] dns-search=~ with following versions: network-manager: 1.10.14-0ubuntu2 systemd: 237-3ubuntu10.22 Now my DNS is correctly updated after connecting to OpenVPN. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Bionic: Triaged Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
For me the login screen hangs as the Ubuntu logo at the bottom of the screen fades in. The crashes are here https://errors.ubuntu.com/user/9918ca952fad5050e5d19cd326c70f270fae7631e330cf3c0c0ee4c728f149c2412b9c7bbdbfed5f6d72b3f62f187ada199b6d5ac8043b4329d0bbe352b51487 -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it Status in mutter package in Ubuntu: Invalid Status in mutter source package in Bionic: Incomplete Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/mutter/+bug/1832138/+subscriptions -- Mailing list: https://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 1832816] Re: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube
*** This bug is a duplicate of bug 1424201 *** https://bugs.launchpad.net/bugs/1424201 Thank you. I wish you make Ubuntu 19.10 and next LTS release the most stable and fast. I will continue test and find new bugs. -- 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/1832816 Title: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube Status in gnome-shell package in Ubuntu: New Bug description: Details in my video: https://photos.app.goo.gl/HeGFUeWzDeGmThYp8 Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card, 4 GB DDR3 RAM, 128 GB SSD Samsung. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:20:52 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
Looking at hungboot.txt I am starting to think maybe the login screen
('gnome-shell' process) is actually running in Wayland mode but failing
to display. That would explain a lot...
Pat, can you please reproduce the bug again and while it is happening:
1. SSH into the VM.
2. Run 'pidof gnome-shell' to find out the process ID of that process.
Tell us if you don't get a result.
3. If you do get a result from step 2 then using that PID run:
sudo kill -ABRT PID
where PID is the process ID number.
4. Wait 30 seconds.
5. Hopefully a crash report will have been generated so now follow:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
** Changed in: mutter (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but setting WaylandEnable=false
fixes it
Status in mutter package in Ubuntu:
Invalid
Status in mutter source package in Bionic:
Incomplete
Status in mutter source package in Eoan:
Invalid
Bug description:
I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
Macbook Pro.
I've been running this Ubuntu 18.04.2 VM without problem for many months
without problem.
Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the
system hangs immediately after displaying the splash screen. I never see a
login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.
I can SSH into the system however.
I've found that I can work around the hang/freeze if I uncomment the
following line in /etc/gdm3/custom.conf;
#WaylandEnable=false
After uncommenting the WaylandEnable=false line and rebooting, then I
see the login prompt as expected and I can then log in and use the
system normally again.
After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
as shown in this 'uname -a' output;
Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a output;
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Sun Jun 9 12:38:37 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2018-05-06 (399 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2018
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
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/mutter/+bug/1832138/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to :
Re: [Desktop-packages] [Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
Please, I shot this: https://photos.app.goo.gl/DHtcN9ZrHLVR8Ne98 пт, 14 июн. 2019 г. в 12:05, Daniel van Vugt : > Also, before locking the screen please open a Terminal window and run > 'top' then take a screenshot of the window and attach it to this bug. > > ** Changed in: gdm3 (Ubuntu) >Status: New => Incomplete > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1832812 > > Title: > Locking and unlocking the screen is slow and stuttery > > Status in gdm3 package in Ubuntu: > Incomplete > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gdm3 3.32.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 > Uname: Linux 5.0.0-16-generic x86_64 > ApportVersion: 2.20.11-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 14 10:10:38 2019 > InstallationDate: Installed on 2019-06-13 (0 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) > SourcePackage: gdm3 > UpgradeStatus: No upgrade log present (probably fresh install) > mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions > -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563350] Re: The cdio++ include directory is missing
3 years later and the C++ bindings are still not available. If anyone is interested, I've pushed libcdio v2.1 packages with C++ bindings to my testing ppa: https://launchpad.net/%7Ewsnipex/+archive/ubuntu/test/+packages?field.name_filter=cdio_filter=published_filter= -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1563350 Title: The cdio++ include directory is missing Status in libcdio package in Ubuntu: Confirmed Bug description: The directory include/cdio++ seems to be missing from the -dev package(s). There are hints of the existence of a libcdio++-dev package, but I can't find it anywhere. If possible, please also switch to a newer version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1563350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563350] Re: The cdio++ include directory is missing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libcdio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1563350 Title: The cdio++ include directory is missing Status in libcdio package in Ubuntu: Confirmed Bug description: The directory include/cdio++ seems to be missing from the -dev package(s). There are hints of the existence of a libcdio++-dev package, but I can't find it anywhere. If possible, please also switch to a newer version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1563350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
I have been trying to reproduce this bug in VMware but have not been able to. Ubuntu 18.04 always starts up with a login screen successfully for me. What it does not do successfully is offer the "Ubuntu on Wayland" option most of the time. So I expect that's the same root cause as this bug. Ordinarily if Wayland support is attempted and fails gracefully then your journalctl log should show something like: Jun 14 02:28:16 ubuntu gnome-shell[790]: Failed to create backend: Could not find a primary drm kms device If you don't see that message and still don't get Wayland support then it suggests mutter/gnome-shell is crashing during that attempt to try Wayland. In that case we would ask you to follow these instructions from within the virtual machine: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment I'll dig a bit deeper to try and find out why Wayland support seems to work so rarely, because that's the part of this bug I can reproduce. -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it Status in mutter package in Ubuntu: Invalid Status in mutter source package in Bionic: In Progress Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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
[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
Jussi, That sounds like maybe a different bug. Although "commenting out the Wayland" is also not what you need to do. You need to change: #WaylandEnable=false to: WaylandEnable=false If that doesn't fix the problem for you then you have a different bug. In that case please open a new bug by running: ubuntu-bug mutter from within the VM. -- 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it Status in mutter package in Ubuntu: Invalid Status in mutter source package in Bionic: In Progress Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/mutter/+bug/1832138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1655555] Re: Chromium aborts on SIGBUS every minute with vm.overcommit_memory=2
Hi, No, this does not go away. This problem still exists: Chromium 74.0.3729.169 Built on Ubuntu , running on Ubuntu 19.04 running kernel 5.0.0-16-generic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/165 Title: Chromium aborts on SIGBUS every minute with vm.overcommit_memory=2 Status in chromium-browser package in Ubuntu: New Bug description: The Linux kernel has a knob, vm.overcommit_memory, which switches how memory allocation requests are handled. What I'm reporting is that Chromium is basically unusable with a non-standard setting of that knob (which makes sense as a better default to me on my system). So, steps to reproduce: 1) install chromium-browser 2) sysctl vm.overcommit_memory=2 3) run chromium-browser Expected behavior: works normally. Actual behavior: crashes every minute or two. Console output: [1]7449 bus error (core dumped) chromium-browser I believe this is either a misconfigured build, or an upstream bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-LVDS-1: edid-base64: AP///wAw5IIDAAAWAQOAHxF4CrqFo1hUoScMUFQBAQEBAQEBAQEBAQEBAQEBMCpARGGEJDAwIDUANa4QAAAZ/gBMRyBEaXNwbGF5CiAg/gBMUDE0MFdEMi1UTEUyAFI= dpms: On modes: 1600x900 enabled: enabled status: connected DRM.card0-VGA-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected Date: Wed Jan 11 09:30:28 2017 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2013-07-12 (1278 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) Load-Avg-1min: 10.00 Load-Processes-Running-Percent: 0.5% MachineType: LENOVO 3444FHG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=0c3285b7-5de5-405d-8524-8396272551d7 ro quiet splash iwlwifi.power_save=1 iwlwifi.led_mode=1 i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to xenial on 2016-06-24 (200 days ago) dmi.bios.date: 02/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET93WW (2.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 3444FHG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG6ET93WW(2.53):bd02/04/2013:svnLENOVO:pn3444FHG:pvrThinkPadX1Carbon:rvnLENOVO:rn3444FHG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3444FHG dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832656] Re: chromium-browser deb->snap transition breaks ubuntukylin image builds
I have updated the ubuntukylin seeds, and made a debdiff of ubuntukylin- meta, could some help to upload it? Thanks! ** Patch added: "ubuntukylin-meta_0.37.debdiff" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832656/+attachment/5270760/+files/ubuntukylin-meta_0.37.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1832656 Title: chromium-browser deb->snap transition breaks ubuntukylin image builds Status in chromium-browser package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in chromium-browser source package in Eoan: New Status in ubuntukylin-meta source package in Eoan: New Bug description: From https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881: Preparing to unpack .../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 It is possible that the flavors should switch to seeding the snap instead of the deb. However, it's unclear to me why the deb is failing to talk to the Snap Store, because seeding of snaps DOES work from within image builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
Are you able to make another video without Firefox running? ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
Also, before locking the screen please open a Terminal window and run 'top' then take a screenshot of the window and attach it to this bug. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832816] Re: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube
*** This bug is a duplicate of bug 1424201 *** https://bugs.launchpad.net/bugs/1424201 > Shell works slowly with efforts also without Firefox launching. Yes, we know. But that's not an exact bug as much as an observation that performance is poor. For the type of issues you describe I have made a list of fixes we need, which is half done: https://trello.com/c/Q6JYXPPs -- 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/1832816 Title: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube Status in gnome-shell package in Ubuntu: New Bug description: Details in my video: https://photos.app.goo.gl/HeGFUeWzDeGmThYp8 Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card, 4 GB DDR3 RAM, 128 GB SSD Samsung. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:20:52 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions -- Mailing list: https://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 1832812] Re: Ubuntu 19.10 (alpha) lockscreen freezes
I don't use any Gnome Extensions. It's clear system after installation. If I switch button "Auto login" I don't see any changes with bug. пт, 14 июн. 2019 г., 11:20 Daniel van Vugt : > Also, does the bug still occur if you disable this? > > AutomaticLoginEnable=true > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1832812 > > Title: > Ubuntu 19.10 (alpha) lockscreen freezes > > Status in gdm3 package in Ubuntu: > Incomplete > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gdm3 3.32.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 > Uname: Linux 5.0.0-16-generic x86_64 > ApportVersion: 2.20.11-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 14 10:10:38 2019 > InstallationDate: Installed on 2019-06-13 (0 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) > SourcePackage: gdm3 > UpgradeStatus: No upgrade log present (probably fresh install) > mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions > -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions -- Mailing list: https://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 1832812] Re: Locking and unlocking the screen is slow and stuttery
It's not depend by Firefox пт, 14 июн. 2019 г., 11:40 Daniel van Vugt : > Also, does the bug still occur if you close Firefox before locking the > screen? > > If not then this may be related to bug 1832816. > > ** Summary changed: > > - Ubuntu 19.10 (alpha) lockscreen freezes > + Locking and unlocking the screen is slow and stuttery > > ** Tags added: performance > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1832812 > > Title: > Locking and unlocking the screen is slow and stuttery > > Status in gdm3 package in Ubuntu: > Incomplete > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gdm3 3.32.0-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 > Uname: Linux 5.0.0-16-generic x86_64 > ApportVersion: 2.20.11-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 14 10:10:38 2019 > InstallationDate: Installed on 2019-06-13 (0 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) > SourcePackage: gdm3 > UpgradeStatus: No upgrade log present (probably fresh install) > mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions > -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions -- Mailing list: https://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 1832816] Re: Ubuntu 19.10 Gnome Desktop works with freezes and efforts
*** This bug is a duplicate of bug 1424201 *** https://bugs.launchpad.net/bugs/1424201 Shell works slowly with efforts also without Firefox launching. пт, 14 июн. 2019 г., 11:30 Daniel van Vugt : > *** This bug is a duplicate of bug 1424201 *** > https://bugs.launchpad.net/bugs/1424201 > > It appears the problem is probably that your web browser is using all > the CPU power to display YouTube's auto-playing front page. Because our > web browsers don't support hardware video decoding (LP: #1424201). > > Your CPU is certainly new enough to do it. Your CPU is Apollo Lake > generation as shown in this picture: > > https://wiki.ubuntu.com/IntelQuickSyncVideo#YouTube > > So the only problem here is that Firefox would be stealing all your CPU > time, which then prevents gnome-shell from responding quickly. That > makes this a duplicate of bug 1424201. > > > ** This bug has been marked a duplicate of bug 1424201 >Web browsers lacking hardware-accelerated video decoding > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1832816 > > Title: > Gnome Shell is slow and stuttery while Firefox is loading/playing > YouTube > > Status in gnome-shell package in Ubuntu: > New > > Bug description: > Details in my video: https://photos.app.goo.gl/HeGFUeWzDeGmThYp8 > Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card, > 4 GB DDR3 RAM, 128 GB SSD Samsung. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gnome-shell 3.32.2-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 > Uname: Linux 5.0.0-16-generic x86_64 > ApportVersion: 2.20.11-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 14 10:20:52 2019 > DisplayManager: gdm3 > GsettingsChanges: >b'org.gnome.shell' b'command-history' redacted by apport >b'org.gnome.desktop.interface' b'gtk-im-module' > b"'gtk-im-context-simple'" > InstallationDate: Installed on 2019-06-13 (0 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions > -- 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/1832816 Title: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube Status in gnome-shell package in Ubuntu: New Bug description: Details in my video: https://photos.app.goo.gl/HeGFUeWzDeGmThYp8 Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card, 4 GB DDR3 RAM, 128 GB SSD Samsung. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:20:52 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
Also, does the bug still occur if you close Firefox before locking the screen? If not then this may be related to bug 1832816. ** Summary changed: - Ubuntu 19.10 (alpha) lockscreen freezes + Locking and unlocking the screen is slow and stuttery ** Tags added: performance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
** Changed in: mutter (Ubuntu Bionic) Status: Confirmed => 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/1832138 Title: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it Status in mutter package in Ubuntu: Invalid Status in mutter source package in Bionic: In Progress Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/mutter/+bug/1832138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832816] Re: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube
*** This bug is a duplicate of bug 1424201 *** https://bugs.launchpad.net/bugs/1424201 ** Summary changed: - Ubuntu 19.10 Gnome Desktop works with freezes and efforts + Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube -- 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/1832816 Title: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube Status in gnome-shell package in Ubuntu: New Bug description: Details in my video: https://photos.app.goo.gl/HeGFUeWzDeGmThYp8 Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card, 4 GB DDR3 RAM, 128 GB SSD Samsung. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:20:52 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832816] Re: Ubuntu 19.10 Gnome Desktop works with freezes and efforts
*** This bug is a duplicate of bug 1424201 *** https://bugs.launchpad.net/bugs/1424201 It appears the problem is probably that your web browser is using all the CPU power to display YouTube's auto-playing front page. Because our web browsers don't support hardware video decoding (LP: #1424201). Your CPU is certainly new enough to do it. Your CPU is Apollo Lake generation as shown in this picture: https://wiki.ubuntu.com/IntelQuickSyncVideo#YouTube So the only problem here is that Firefox would be stealing all your CPU time, which then prevents gnome-shell from responding quickly. That makes this a duplicate of bug 1424201. ** This bug has been marked a duplicate of bug 1424201 Web browsers lacking hardware-accelerated video decoding -- 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/1832816 Title: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube Status in gnome-shell package in Ubuntu: New Bug description: Details in my video: https://photos.app.goo.gl/HeGFUeWzDeGmThYp8 Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card, 4 GB DDR3 RAM, 128 GB SSD Samsung. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:20:52 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832812] Re: Ubuntu 19.10 (alpha) lockscreen freezes
Can you confirm you are not using any gnome-shell extensions? ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832812 Title: Ubuntu 19.10 (alpha) lockscreen freezes Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832812] Re: Ubuntu 19.10 (alpha) lockscreen freezes
Also, does the bug still occur if you disable this? AutomaticLoginEnable=true -- 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/1832812 Title: Ubuntu 19.10 (alpha) lockscreen freezes Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
The bug is marked as "fix released" so as far as we know the issue is closed. If you still experience problems then please open a new bug by running: ubuntu-bug gnome-shell and mention that it seems to be related to bug 1812266. -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
I have currently installed: gnome-shell 3.28.4-0ubuntu18.04.1. After more than five months, this bug is still in my installation of Ubuntu 18.04.2 LTS and annoys me every single day. I am really disappointed. Can somebody explain to me in simple language why the bug fix is still not released? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832816] [NEW] Ubuntu 19.10 Gnome Desktop works with freezes and efforts
Public bug reported: Details in my video: https://photos.app.goo.gl/HeGFUeWzDeGmThYp8 Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card, 4 GB DDR3 RAM, 128 GB SSD Samsung. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:20:52 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1832816 Title: Ubuntu 19.10 Gnome Desktop works with freezes and efforts Status in gnome-shell package in Ubuntu: New Bug description: Details in my video: https://photos.app.goo.gl/HeGFUeWzDeGmThYp8 Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card, 4 GB DDR3 RAM, 128 GB SSD Samsung. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:20:52 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832812] [NEW] Ubuntu 19.10 (alpha) lockscreen freezes
Public bug reported: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1832812 Title: Ubuntu 19.10 (alpha) lockscreen freezes Status in gdm3 package in Ubuntu: New Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820859] Re: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb
How to reproduce this ? Previously crash was in `nautilus_window_slot_get_location` which is now fixed upstream. With 3.32.1-1ubuntu1, I can't reproduce with G_MESSAGES_DEBUG=all /usr/bin/nautilus. Can you copy/paste error as I don't have access? But we don't really to update windows locations when org.freedesktop.FileManager1 is acquired or being acquired. If there is still a error I will open a merge. -- 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/1820859 Title: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb Status in nautilus package in Ubuntu: Triaged 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.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 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/1820859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826874]
Well, that patch doesn't apply to comm-esr60 at all. -- 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/1826874 Title: In Ubuntu's Thunderbird, Empty Deleted warns, Empty "Inbox"! Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Triaged Bug description: Issue: In Ubuntu desktop 18.10 and 19.04 (and perhaps years earlier?), when a Thunderbird user clicks on File>Empty Deleted, it warns that Empty "Inbox" will be done, instead! Ouch! (It does empty the correct folder anyway, but this should and does scare many users.) After a protracted dialog with the Mozilla Thunderbird support team, I've learned that Mozilla's own vanilla Thunderbird shows Empty "Trash", as it should. They say that the version of Thunderbird that comes bundled with Ubuntu is to blame - so please fix it. Note 1: Specifically, this wrong routine threatens to empty the active folder; commonly, that folder is "Inbox". Note 2: There's no prompt at all, if the "Trash" dialog box is suppressed. But default is (and should be) to have it enabled. Note 3: You can view the details of my Mozilla trouble-shooting (including my/Ubuntu's erroneous Thunderbird screen-print and Mozilla's correct one), here: https://support.mozilla.org/en-US/questions/1254659#answer-1216735 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1826874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
