[Desktop-packages] [Bug 2043507] Re: xdg-desktop-portal-gtk - asks two times "Select window to share with requesting application" when starting sharing a window in google meet
** Package changed: vino (Ubuntu) => xdg-desktop-portal-gtk (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2043507 Title: xdg-desktop-portal-gtk - asks two times "Select window to share with requesting application" when starting sharing a window in google meet Status in xdg-desktop-portal-gtk package in Ubuntu: New Bug description: Expected (initial) behavior in Google Meet was During the meeting: When I click "Present Now" Then popup: "Choose what to share with meet.google.com" When I click "Window" and select window to share and click OK Then the selected window is shared in the meet Observed behaviour: When I click "Present Now" Then Popup1: "Choose what to share with meet.google.com" When I click "Window" tab Then Popup2 "Select window to share with requesting application" - and Popup1 window list remains empty When I select a window and click Share Then Popup1 > Window shows a small image of the selected window When in Popup1 i click on the window image and Share Then Popup3: "Select window to share with requesting application" and a list of open windows When in Popup3 I select again the window to share and click Share Then the selected window is shared in the meet Based on the window title it seems that the extra popups (2/3 above) come from https://github.com/flatpak/xdg-desktop-portal-gtk/blob/1.14.0/src/screencastwidget.c release: Ubuntu 22.04.3 LTS xdg-desktop-portal-gtk/jammy,now 1.14.0-1build1 amd64 Google Chrome: Version 119.0.6045.123 (Official Build) (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2043507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043507] [NEW] xdg-desktop-portal-gtk - asks two times "Select window to share with requesting application" when starting sharing a window in google meet
Public bug reported: Expected (initial) behavior in Google Meet was During the meeting: When I click "Present Now" Then popup: "Choose what to share with meet.google.com" When I click "Window" and select window to share and click OK Then the selected window is shared in the meet Observed behaviour: When I click "Present Now" Then Popup1: "Choose what to share with meet.google.com" When I click "Window" tab Then Popup2 "Select window to share with requesting application" - and Popup1 window list remains empty When I select a window and click Share Then Popup1 > Window shows a small image of the selected window When in Popup1 i click on the window image and Share Then Popup3: "Select window to share with requesting application" and a list of open windows When in Popup3 I select again the window to share and click Share Then the selected window is shared in the meet Based on the window title it seems that the extra popups (2/3 above) come from https://github.com/flatpak/xdg-desktop-portal-gtk/blob/1.14.0/src/screencastwidget.c release: Ubuntu 22.04.3 LTS xdg-desktop-portal-gtk/jammy,now 1.14.0-1build1 amd64 Google Chrome: Version 119.0.6045.123 (Official Build) (64-bit) ** Affects: vino (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/2043507 Title: xdg-desktop-portal-gtk - asks two times "Select window to share with requesting application" when starting sharing a window in google meet Status in vino package in Ubuntu: New Bug description: Expected (initial) behavior in Google Meet was During the meeting: When I click "Present Now" Then popup: "Choose what to share with meet.google.com" When I click "Window" and select window to share and click OK Then the selected window is shared in the meet Observed behaviour: When I click "Present Now" Then Popup1: "Choose what to share with meet.google.com" When I click "Window" tab Then Popup2 "Select window to share with requesting application" - and Popup1 window list remains empty When I select a window and click Share Then Popup1 > Window shows a small image of the selected window When in Popup1 i click on the window image and Share Then Popup3: "Select window to share with requesting application" and a list of open windows When in Popup3 I select again the window to share and click Share Then the selected window is shared in the meet Based on the window title it seems that the extra popups (2/3 above) come from https://github.com/flatpak/xdg-desktop-portal-gtk/blob/1.14.0/src/screencastwidget.c release: Ubuntu 22.04.3 LTS xdg-desktop-portal-gtk/jammy,now 1.14.0-1build1 amd64 Google Chrome: Version 119.0.6045.123 (Official Build) (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/2043507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017841] Re: Firefox drag/drop url onto desktop crashes ubuntu login session
I have a similar situation. Firefox 112.0.2 When moving the mouse over thumbnails on the predominantly Youtube site, the browser closes spontaneously. Sometimes with exiting a Gnome desktop session. The reason is not clear. There is no such problem in the Chromium browser. Ubuntu 23.04, Wayland session, CPU AMD Ryzen 9 7900х ** Description changed: Situation - while browsing I want to save page's url to desktop (likely any folder). I drag the url (by padlock icon in the address bar) onto my desktop folder to save shortcut to the page (for later view, to share it etc). The ubuntu user session (Wayland) will lock up and crash (bringing me back to user login screen) the moment I move the mouse (dragging the url) to FF windows boundary. Sometimes I'll get as far hovering over open desktop area but it'll crash withing seconds from me starting the task. No shortcut is saved to the desktop. FireFox can't restore session when launched again after login to system (I tried even restarting the pc before attempts at launching FF again). All you get is black/blank FF window and spinning cursor. Initially, the only way to get FF working again appeared to be to kill open FF window, switch to in private mode - this one will start fine and the next time FF would start normally. The session from before the crash would be gone though, really annoying for anyone with multiple open tabs. I'm quite certain that this was the reason why I'd given up on FF snap in 22.04 (normal/legacy install did not have the problem) but the same (?) problem on 23.04 forced me to have a closer look at what's going on, recovery options and to sing up/report the bug. - What I've also noticed is that if following the crash I'd open in private FF windows 1st (instead of trying to open normal browser session only to have to terminate the browser showing blank window) and only then start normal FF session, FF would restore my tabs from before the crash. This is of little use now that I have to figure how to go back to my old session (I'll backtrack it somehow but this is pita). I'm tempted to pull the plug on snap FF again and move back to less fancy but more resilient setup (and with greater functionality). + What I've also noticed is that if following the crash I'd open in private FF windows 1st (instead of trying to open normal browser session only to have to terminate the browser showing blank window) and only then start normal FF session, FF would restore my tabs from before the crash. This is of little use now that I have to figure how to go back to my old session (I'll backtrack it somehow but this is pita). I'm tempted to pull the plug on snap FF again and move back to less fancy but more resilient setup (and with greater functionality). Btw, the same crash can be triggered when doing drag and drop from bookmark or history manager in FF. - Chromium snap install does not crash the login/Wayland session but url drag and drop attempt just does nothing anyway, no file is left on the desktop. Quite a basic functionality that works from any browser on Windows or macOS, seems like a great omission. An unfortunate choice if limited interactivity with user's own file system was just inherent to snap packaged software. I understand security but it's personal computer desktop environment 1st. + Chromium snap install does not crash the login/Wayland session but url drag and drop attempt just does nothing anyway, no file is left on the desktop. Quite a basic functionality that works from any browser on Windows or macOS, seems like a great omission. An unfortunate choice if limited interactivity with user's own file system was just inherent to snap packaged software. I understand security but it's personal computer desktop environment 1st. I'm not sure of any security impact but this surely does not look good and is definitely a risk of data/work lost (luckily I did not have whole lot of open windows besides terminal). -- 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/2017841 Title: Firefox drag/drop url onto desktop crashes ubuntu login session Status in firefox package in Ubuntu: Confirmed Bug description: Situation - while browsing I want to save page's url to desktop (likely any folder). I drag the url (by padlock icon in the address bar) onto my desktop folder to save shortcut to the page (for later view, to share it etc). The ubuntu user session (Wayland) will lock up and crash (bringing me back to user login screen) the moment I move the mouse (dragging the url) to FF windows boundary. Sometimes I'll get as far hovering over open desktop area but it'll crash withing seconds from me starting the task. No shortcut is saved to the desktop. FireFox can't restore session when launched again after login to system (I tried even restarting the pc before attempts at
[Desktop-packages] [Bug 1359715] Re: Ghostscript runaway memory consumption during font search
Marking as fixed according to the latest comments here ** Changed in: ghostscript (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1359715 Title: Ghostscript runaway memory consumption during font search Status in ghostscript package in Ubuntu: Fix Released Bug description: Linux Mint 17 (Qiana), Cinnamon 64-bit, kernel 3.13.0-24-generic #47-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux Ghostscript version 9.10 When Ghostscript searches for a specified font, if that font is not found in the Fontmap file, memory consumption shoots up, the system starts swapping and hangs. Tested on system (see above) with ~ 2GB memory. A simple way to reproduce, is to use the following procedure to attempt to display a font: 1) Invoke ghostscript on 'prfont.ps' $ gs /usr/share/ghostscript/9.10/lib/prfont.ps GPL Ghostscript 9.10 (2013-08-30) Copyright (C) 2013 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Loading NimbusRomNo9L-Regu font from /usr/share/fonts/type1/gsfonts/n021003l.pfb... 3896292 2355421 3853784 2540955 1 done. GS> 2) At Ghostscript prompt, specify a random fontname - which we know does not exist - to 'DoFont': GS>/Somefont DoFont Can't find (or can't open) font file /usr/share/ghostscript/9.10/Resource/Font/Somefont. Can't find (or can't open) font file Somefont. Querying operating system for font files... Result: memory usage maxes out, system swaps and hangs. I expected Ghostscript to conclude the font search (without exhausating system resources!) and to report failure to locate the specified font. This problem always occurs, and affects any other program which invokes ghostscript and triggers a font search. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1359715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1560722] Re: repositórios sumiram
** Changed in: glib2.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1560722 Title: repositórios sumiram Status in glib2.0 package in Ubuntu: Incomplete Bug description: repositórios sumiram não sei o que fiz de errado. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-notification-daemon 1.12.1-1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 22 19:41:03 2016 ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon InstallationDate: Installed on 2016-03-22 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon Signal: 5 SourcePackage: mate-notification-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so Title: mate-notification-daemon crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1560722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959027]
Not sure what the problem is, gtk apps refuse to use correct theme and font settings on wayland. As far as I know, it can be worked around by installing gtk xdg desktop portal. -- 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/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1360225] Re: gnome-mahjongg has outdated website link in the package description in Mint 17/Ubuntu 14.04
Fixed in version 1:3.14.1-1, according to git: https://salsa.debian.org/gnome-team/gnome- mahjongg/-/commit/04d2e96e8894b340e47b72e9f4bd29c0e2a32b72 ** Changed in: gnome-mahjongg (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/1360225 Title: gnome-mahjongg has outdated website link in the package description in Mint 17/Ubuntu 14.04 Status in gnome-mahjongg package in Ubuntu: Fix Released Bug description: The Software Manager (mintInstall 7.5.7) shows an outdated link for the gnome-mahjongg package. The link shown is https://live.gnome.org/Mahjongg but it should be https://wiki.gnome.org/Apps/Mahjongg Not the end of the world, I know, but still a bug. My system: Mint 17 64-bit XFCE, dist-upgraded to current. Cheers --Knut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/1360225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1549653] Re: Disks utility doesn't remove previous record in /etc/fstab
** Bug watch added: gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #43 https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/43 ** Changed in: gnome-disk-utility Importance: Medium => Unknown ** Changed in: gnome-disk-utility Status: Expired => Unknown ** Changed in: gnome-disk-utility Remote watch: GNOME Bug Tracker #762718 => gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #43 ** Bug watch removed: GNOME Bug Tracker #762718 https://gitlab.gnome.org/762718 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1549653 Title: Disks utility doesn't remove previous record in /etc/fstab Status in GNOME Disks: Unknown Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: How to reproduce: 1. delete an NTFS partition on secondary disk (rewrite with zeroes). 2. put there EXT4 partition instead. 3. reboot computer => ubuntu doesn't boot, allows only single-user mode. By checking system log, I found out system was trying to mount the old NTFS partition and hanged on it, even though that is not at all a necessary partition. Then I checked /etc/fstab and found out the GUI tool did NOT remove the original record, when it deleted the partition on the drive. By commenting it out I was able to get into the GUI again. Ubuntu 15.10 pkg: gnome-disk-utility 3.16.2-0ubuntu2 0 The original line, that was left behind: UUID=52D09468D09453D7 /backup ntfsdefaults,umask=007,gid=46 0 0 The new line that the tool created: /dev/disk/by-uuid/414e95a1-fb40-45a6-9b90-487a45337fdd /extdata auto nosuid,nodev,nofail,x-gvfs-show 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-disk-utility 3.16.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 25 08:34:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-02-24 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1549653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586716] Re: yelp crashed with SIGSEGV in g_str_equal()
** Bug watch added: gitlab.gnome.org/GNOME/yelp/-/issues #116 https://gitlab.gnome.org/GNOME/yelp/-/issues/116 ** Changed in: yelp Importance: Medium => Unknown ** Changed in: yelp Status: Expired => Unknown ** Changed in: yelp Remote watch: GNOME Bug Tracker #778553 => gitlab.gnome.org/GNOME/yelp/-/issues #116 ** Bug watch removed: GNOME Bug Tracker #778553 https://gitlab.gnome.org/778553 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1586716 Title: yelp crashed with SIGSEGV in g_str_equal() Status in Ubuntu GNOME: Triaged Status in Yelp: Unknown Status in yelp package in Ubuntu: Triaged Bug description: No idea, just saw the error. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: yelp 3.20.1-1ubuntu1~xenial1 [origin: LP-PPA-gnome3-team-gnome3-staging] Uname: Linux 4.6.0-040600-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Sun May 29 03:03:21 2016 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2014-02-04 (844 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140203) ProcCmdline: yelp file:///usr/share/doc/pspp/pspp.xml#ONEWAY SegvAnalysis: Segfault happened at: 0x7f497638eb5a <__strcmp_sse2_unaligned+26>: movdqu (%rdi),%xmm1 PC (0x7f497638eb5a) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: yelp StacktraceTop: g_str_equal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libyelp.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libyelp.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: yelp crashed with SIGSEGV in g_str_equal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers XsessionErrors: (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to create device: failed to obtain org.freedesktop.color-manager.create-device auth (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to obtain org.freedesktop.color-manager.create-profile auth (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to obtain org.freedesktop.color-manager.create-profile auth (cinnamon-settings-daemon:3255): color-plugin-WARNING **: could not find device: property match 'XRANDR_name'='eDP1' does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1586716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Hi! I had the same problem with JBL TUNE500BT Headphones on Ubuntu 20.04. I did a kernel update to 5.8.9-050809-generic version using ubuntu- mainline-kernel.sh script [1]. I also uninstalled ofono and ofono- phonesim which I installed earlier when trying to fix this problem and reverted any changes I did to the default.pa file. It seems to be working now, but audio quality is awful when using HSP/HFP, which is related to another bug [2]. I don't know if it's a good solution, but maybe it will help someone. [1]: https://raw.githubusercontent.com/pimlie/ubuntu-mainline-kernel.sh/master/ubuntu-mainline-kernel.sh [2]: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838151 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
Thank you for the fix! After having my mutter updated, I can finally watch the fullscreen videos while having the fractional scaling enabled However, there is one minor issue. Whenever I switch to the fullscreen mode, the scaling factor is changed from 150% to 200%, so all the widgets are unnecessarily large. This isn't a deal breaker for me, because I use the fullscreen mode only for watching the videos; I just wanted to confirm that it's the intended behavior -- 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/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) Status in mutter package in Ubuntu: Fix Released Bug description: When I play a video with mpv (or e.g. Firefox), it works just fine. When this video is fullscreened (e.g. in mpv by pressing f), the screen quickly turns off, and switches resolution modes in such a rate the screen is unusable. The native resolution of the screen is 1440p, but Xorg somehow increases the size to 3424x1926 for the fullscreen, then quickly switches back to 1440p, before increasing it again. As soon as the video is de-fullscreened (by pressing f again in mpv, or esc in Firefox), the funny resolution switching stops and the system is usable again. This also happens with the modesetting 2d-driver. This does not happen with Wayland. This can be seen in the Xorg-log: [20.215] (II) intel(0): EDID vendor "JDI", prod id 0 [20.215] (II) intel(0): Printing DDC gathered Modelines: [20.215] (II) intel(0): Modeline "2560x1440"x0.0 245.12 2560 2608 2640 2720 1440 1443 1449 1502 +hsync -vsync (90.1 kHz eP) [ 258.869] (II) intel(0): resizing framebuffer to 3424x1926 [ 258.905] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 268.955] (II) intel(0): resizing framebuffer to 2560x1440 [ 269.097] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 270.383] (II) intel(0): resizing framebuffer to 3424x1926 [ 270.400] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 271.852] (II) intel(0): resizing framebuffer to 2560x1440 [ 271.858] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 273.294] (II) intel(0): resizing framebuffer to 3424x1926 [ 273.314] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none When the resolution is increased, the Kernel complains about the framebuffer size: [ 269.830034] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 00:00:07 2020 DistUpgraded: 2020-02-05 22:21:13,002 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2259] MachineType: LENOVO 20LES01W00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=/dev/mapper/hostname-ubunturoot ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-02-05 (0 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET52W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LES01W00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET52W(1.38):bd11/27/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LES01W00 dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
@jonas-jelten I believe that should be it https://git.launchpad.net/ubuntu/+source/mutter/diff/debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch?id=3c4a6b2d7bcb210b3460f40587d4b14c19203c02 -- 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/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) Status in mutter package in Ubuntu: Fix Committed Bug description: When I play a video with mpv (or e.g. Firefox), it works just fine. When this video is fullscreened (e.g. in mpv by pressing f), the screen quickly turns off, and switches resolution modes in such a rate the screen is unusable. The native resolution of the screen is 1440p, but Xorg somehow increases the size to 3424x1926 for the fullscreen, then quickly switches back to 1440p, before increasing it again. As soon as the video is de-fullscreened (by pressing f again in mpv, or esc in Firefox), the funny resolution switching stops and the system is usable again. This also happens with the modesetting 2d-driver. This does not happen with Wayland. This can be seen in the Xorg-log: [20.215] (II) intel(0): EDID vendor "JDI", prod id 0 [20.215] (II) intel(0): Printing DDC gathered Modelines: [20.215] (II) intel(0): Modeline "2560x1440"x0.0 245.12 2560 2608 2640 2720 1440 1443 1449 1502 +hsync -vsync (90.1 kHz eP) [ 258.869] (II) intel(0): resizing framebuffer to 3424x1926 [ 258.905] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 268.955] (II) intel(0): resizing framebuffer to 2560x1440 [ 269.097] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 270.383] (II) intel(0): resizing framebuffer to 3424x1926 [ 270.400] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 271.852] (II) intel(0): resizing framebuffer to 2560x1440 [ 271.858] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 273.294] (II) intel(0): resizing framebuffer to 3424x1926 [ 273.314] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none When the resolution is increased, the Kernel complains about the framebuffer size: [ 269.830034] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 00:00:07 2020 DistUpgraded: 2020-02-05 22:21:13,002 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2259] MachineType: LENOVO 20LES01W00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=/dev/mapper/hostname-ubunturoot ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-02-05 (0 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET52W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LES01W00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET52W(1.38):bd11/27/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LES01W00 dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
[Desktop-packages] [Bug 1871068] [NEW] Gedit current line highlighting doesn't play well with Yaru-dark
Public bug reported: By default, gedit has "Highlight current line" option enabled. While that works great for Yaru and Adwaita, this is barely usable with Yaru- dark, because both background and foreground are just different shades of white. While this is a minor issue and can be easily fixed by adjusting gedit's color scheme, that might give not the best impression for a first-time Ubuntu user. apt policy gedit gedit: Installed: 3.36.1-1 Candidate: 3.36.1-1 Version table: *** 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status apt policy yaru-theme-gtk yaru-theme-gtk: Installed: 20.04.4 Candidate: 20.04.4 Version table: *** 20.04.4 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 11:43:32 2020 InstallationDate: Installed on 2019-11-07 (150 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2020-03-04 (32 days ago) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-04-06 11-42-38.png" https://bugs.launchpad.net/bugs/1871068/+attachment/5347648/+files/Screenshot%20from%202020-04-06%2011-42-38.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1871068 Title: Gedit current line highlighting doesn't play well with Yaru-dark Status in yaru-theme package in Ubuntu: New Bug description: By default, gedit has "Highlight current line" option enabled. While that works great for Yaru and Adwaita, this is barely usable with Yaru-dark, because both background and foreground are just different shades of white. While this is a minor issue and can be easily fixed by adjusting gedit's color scheme, that might give not the best impression for a first-time Ubuntu user. apt policy gedit gedit: Installed: 3.36.1-1 Candidate: 3.36.1-1 Version table: *** 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status apt policy yaru-theme-gtk yaru-theme-gtk: Installed: 20.04.4 Candidate: 20.04.4 Version table: *** 20.04.4 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 11:43:32 2020 InstallationDate: Installed on 2019-11-07 (150 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2020-03-04 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1871068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04
Thank you, removing both "xserver-xorg-video-intel" package and /etc/X11/xorg.conf.d/20-intel.conf file solved all the issues I had -- 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/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337888/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337907/+files/lspcik.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337906/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1867668/+attachment/5337877/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1867668/+attachment/5337880/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1867668/+attachment/5337879/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1867668/+attachment/5337876/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1867668/+attachment/5337878/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04
apport information ** Tags added: apport-collected third-party-packages ** Description changed: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user-specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu20 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-11-07 (130 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + Package: gnome-shell 3.35.91-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 + RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 + Tags: third-party-packages focal + Uname: Linux 5.4.0-14-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) + UserGroups: microk8s sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1867668/+attachment/5337875/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select
[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04
** Attachment added: "shell-example-1.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337649/+files/shell-example-1.png -- 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/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: New Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04
** Attachment added: "shell-example-4.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337651/+files/shell-example-4.png ** Description changed: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load - the system. The background image has some green/violet visual artifacts, - and the text elements in Gnome Shell incorrectly display some of the - symbol. Changing the background image removes the artifacts until the - next reboot (but if I select the previous one without rebooting, then I - still see the same artifacts, so it's probably cached somewhere). + the system. The background image has some green/violet/black visual + artifacts, and the text elements in Gnome Shell incorrectly display some + of the symbol. Changing the background image removes the artifacts until + the next reboot (but if I select the previous one without rebooting, + then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. - The issues are reproduced with and without extensions, with 1.0, 1.5 and - 2.0 display scaling factors applied, and they are not user-specific + The issues are reprodicable with and without extensions, with 1.0, 1.5 + and 2.0 display scaling factors applied, and they are not user-specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: - Installed: 3.35.91-1ubuntu2 - Candidate: 3.35.91-1ubuntu2 - Version table: - *** 3.35.91-1ubuntu2 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.35.91-1ubuntu2 + Candidate: 3.35.91-1ubuntu2 + Version table: + *** 3.35.91-1ubuntu2 500 + 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) - [Created at pci.386] - Unique ID: _Znp.pq3kk9M9L4C - SysFS ID: /devices/pci:00/:00:02.0 - SysFS BusID: :00:02.0 - Hardware Class: graphics card - Model: "Intel UHD Graphics 620" - Vendor: pci 0x8086 "Intel Corporation" - Device: pci 0x5917 "UHD Graphics 620" - SubVendor: pci 0x17aa "Lenovo" - SubDevice: pci 0x225c - Revision: 0x07 - Driver: "i915" - Driver Modules: "i915" - Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) - Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) - I/O Ports: 0xe000-0xe03f (rw) - Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) - IRQ: 161 (64308 events) - Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" - Driver Info #0: - Driver Status: i915 is active - Driver Activation Cmd: "modprobe i915" - Config Status: cfg=new, avail=yes, need=no, active=unknown + [Created at pci.386] + Unique ID: _Znp.pq3kk9M9L4C + SysFS ID: /devices/pci:00/:00:02.0 + SysFS BusID: :00:02.0 + Hardware Class: graphics card + Model: "Intel UHD Graphics 620" + Vendor: pci 0x8086 "Intel Corporation" + Device: pci 0x5917 "UHD Graphics 620" + SubVendor: pci 0x17aa "Lenovo" + SubDevice: pci 0x225c + Revision: 0x07 + Driver: "i915" + Driver Modules: "i915" + Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) + Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) + I/O Ports: 0xe000-0xe03f (rw) + Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) + IRQ: 161 (64308 events) + Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" + Driver Info #0: + Driver Status: i915 is active + Driver Activation Cmd: "modprobe i915" + Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor - [Created at monitor.125] - Unique ID: rdCR.R7Dpg_aaVOC - Parent ID: _Znp.pq3kk9M9L4C - Hardware Class: monitor - Model: "LG Display LCD Monitor" - Vendor: LGD "LG Display" - Device: eisa 0x058b - Resolution: 2560x1440@60Hz - Size: 309x174 mm - Year of Manufacture: 2016 - Week of Manufacture: 0 - Detailed Timings #0: - Resolution: 2560x1440 - Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync -
[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell after upgrading to 20.04
** Attachment added: "shell-example-3.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+attachment/5337650/+files/shell-example-3.png -- 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/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: New Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] [NEW] Visual artifacts in Gnome Shell after upgrading to 20.04
Public bug reported: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user-specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "shell-example-2.png" https://bugs.launchpad.net/bugs/1867668/+attachment/5337648/+files/shell-example-2.png -- 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/1867668 Title: Visual artifacts in Gnome Shell after upgrading to 20.04 Status in gnome-shell package in Ubuntu: New Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development
[Desktop-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
Same problem on Lenovo Ideapad 320-15IKB ** Changed in: alsa-driver (Ubuntu) Status: Expired => Confirmed -- 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/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) Status in alsa-driver package in Ubuntu: Confirmed Bug description: This is a metabug for all machines that are having phase inverted internal microphones. If your internal mic is either completely silent (no signal), or you can possibly pick a very small sound, with much background noise, even though you have set gain to maximum, there is something you could try. Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one. (If you're not running PulseAudio, you can try doing the same through AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try changing "Capture" level or "Internal Mic" or "Internal Mic Boost" using the Q,E,Z,C keys.) If so, please file a separate bug against the alsa-driver for your issue, make sure hardware info gets attached to it (either alsa-info as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones that follows when you do "ubuntu-bug alsa-driver" ), then write a comment in this bug, with your machine name and a pointer to the other bug. As time permits, I'll try to work on fixing them for the next Ubuntu release. Thanks! -- David Henningsson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Sorry, completely forgot about it... :-/ So bug 1828639 is now fixed. I guess no need to fix gconf triggers now? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846890] Re: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonload
** Attachment added: "Debdiff to fix Python 2 loader name" https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+attachment/5294753/+files/libpeas-debdiff-eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpeas in Ubuntu. https://bugs.launchpad.net/bugs/1846890 Title: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so Status in libpeas package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so ) but this file is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846890] Re: Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so
** Package changed: pluma (Ubuntu) => libpeas (Ubuntu) ** Summary changed: - Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so + Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpeas in Ubuntu. https://bugs.launchpad.net/bugs/1846890 Title: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so Status in libpeas package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so ) but this file is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
Cosmic is EOL since July 18, therefore the tag is removed https://lists.ubuntu.com/archives/ubuntu-security- announce/2019-July/004996.html -- 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/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835376] Re: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1828639 *** https://bugs.launchpad.net/bugs/1828639 ** This bug has been marked a duplicate of bug 1828639 Unlooping all the trigger loops! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1835376 Title: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned Status in gtk+2.0 package in Ubuntu: New Bug description: failed when i tried to do a partial upgrade because last upgrade already failed. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libvlc-bin:amd64 3.0.6-1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu Jul 4 10:16:45 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-04-06 (88 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: N/A SourcePackage: vlc Title: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1835376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836651] Re: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1828639 *** https://bugs.launchpad.net/bugs/1828639 ** This bug has been marked a duplicate of bug 1828639 Unlooping all the trigger loops! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1836651 Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned Status in texinfo package in Ubuntu: New Bug description: error during update ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 15 14:25:23 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-12-26 (201 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) 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: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1836651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761913] Re: gnome-software crashed with SIGABRT in g_assertion_message_error → ensure_surface_for_gicon → gtk_icon_helper_load_surface → gtk_icon_helper_ensure_surface → gtk_i
*** This bug is a duplicate of bug 1627564 *** https://bugs.launchpad.net/bugs/1627564 ** This bug has been marked a duplicate of bug 1627564 Crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1761913 Title: gnome-software crashed with SIGABRT in g_assertion_message_error → ensure_surface_for_gicon → gtk_icon_helper_load_surface → gtk_icon_helper_ensure_surface → gtk_icon_helper_ensure_surface → _gtk_icon_helper_get_size → gtk_image_get_content_size Status in gnome-software package in Ubuntu: New Bug description: testing ubuntu 18.04, this error popped up while NOT using gnome- software... ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 7 11:52:45 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-software StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_error () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-software crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1761913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819079] Re: /usr/lib/gcr/gcr-prompter:6:g_assertion_message:g_assertion_message_error:ensure_surface_for_gicon:gtk_icon_helper_load_surface:gtk_icon_helper_ensure_surface
*** This bug is a duplicate of bug 1627564 *** https://bugs.launchpad.net/bugs/1627564 ** This bug has been marked a duplicate of bug 1627564 Crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1819079 Title: /usr/lib/gcr/gcr- prompter:6:g_assertion_message:g_assertion_message_error:ensure_surface_for_gicon:gtk_icon_helper_load_surface:gtk_icon_helper_ensure_surface Status in gcr package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gcr. This problem was most recently seen with package version 3.28.0-1, the problem page at https://errors.ubuntu.com/problem/b7be50bc0b853f28c864412a51e9f75d60558e7d 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/gcr/+bug/1819079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1400036] Re: libvte9 shouldn't depend on libpango1.0-0 as it's a transitional package
** No longer affects: vte (Debian) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1400036 Title: libvte9 shouldn't depend on libpango1.0-0 as it's a transitional package Status in vte package in Ubuntu: Fix Released Bug description: libvte9 should depend on libpango-1.0-0 instead of libpango1.0-0 libpango1.0-0 is a transitional package. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvte9 1:0.28.2-5ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 7 02:39:58 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-11-01 (766 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: vte UpgradeStatus: Upgraded to trusty on 2014-09-04 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1400036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
Fixed in 2.56 ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in glib2.0 package in Ubuntu: Fix Released Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Oh, nice. Maybe then gconf patches won't be needed. (Still need to fix FTBFS in Bionic, bug 1834211.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1298534] Re: Mint 16 / 64-bit unable to mount via usb DROID Mini
Fixed in 1.1.7 upstream, so 1.1.10-2ubuntu1 in Ubuntu 16.04 has the fix. ** Project changed: linuxmint => libmtp (Ubuntu) ** Changed in: libmtp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1298534 Title: Mint 16 / 64-bit unable to mount via usb DROID Mini Status in libmtp package in Ubuntu: Fix Released Bug description: Installed 'mtp-tools' following instructions for "MTP' device recognition as listed on http://www.linuxmint.com/. Have created file 'etc/udev/rules.d/51-android.rules which contains: SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e67", MODE="0666" ownership is root:root and permissions 775 DROID mini still doesn't mount and am returned with: noname@nonameM-A:~ > mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=22b8 and PID=2e67) is UNKNOWN. ** Please report this VID/PID and the device model to the libmtp development team ** Found 1 device(s): 22b8:2e67 @ bus 1, dev 11 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device Android device detected, assigning default bug flags Error 1: Get Storage information failed. Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles. Error 2: Error 02fe: PTP: Protocol error, data expected USB low-level info: bcdUSB: 512 bDeviceClass: 0 bDeviceSubClass: 0 bDeviceProtocol: 0 idVendor: 22b8 idProduct: 2e67 IN endpoint maxpacket: 512 bytes OUT endpoint maxpacket: 512 bytes Raw device info: Bus location: 1 Device number: 11 Device entry info: Vendor: (null) Vendor id: 0x22b8 Product: (null) Vendor id: 0x2e67 Device flags: 0x08008106 Configuration 0, interface 0, altsetting 0: Interface description contains the string "MTP" Device recognized as MTP, no further probing. Device info: Manufacturer: motorola Model: XT1030 Device version: 1.0 Serial number: TA6260EEFY Vendor extension ID: 0x0006 Vendor extension description: microsoft.com: 1.0; android.com: 1.0; mot-mobility.com/DSU: 1.2 Detected object size: 64 bits Extensions: microsoft.com: 1.0 android.com: 1.0 Supported operations: 1001: get device info 1002: Open session 1003: Close session 1004: Get storage IDs 1005: Get storage info 1006: Get number of objects 1007: Get object handles 1008: Get object info 1009: Get object 100a: Get thumbnail 100b: Delete object 100c: Send object info 100d: Send object 1014: Get device property description 1015: Get device property value 1016: Set device property value 1017: Reset device property value 101b: Get partial object 9801: Get object properties supported 9802: Get object property description 9803: Get object property value 9804: Set object property value 9805: Get object property list 9810: Get object references 9811: Set object references 95c1: Get Partial Object (64bit Offset) 95c2: Send Partial Object 95c3: Truncate Object 95c4: Begin Edit Object 95c5: End Edit Object 9001: Unknown (9001) 9002: Unknown (9002) 9003: Unknown (9003) 9004: Unknown (9004) 9005: Unknown (9005) 9006: Unknown (9006) 9007: Unknown (9007) 9008: Unknown (9008) 9009: Unknown (9009) 900a: Unknown (900a) 900b: Unknown (900b) 900c: Unknown (900c) Events supported: 0x4002 0x4003 0x4004 0x4005 Device Properties Supported: 0xd401: Synchronization Partner 0xd402: Friendly Device Name 0x5003: Image Size Playable File (Object) Types and Object Properties Supported: 3000: Undefined Type dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY dc04: Object Size UINT64 data type READ ONLY dc07: Object File Name STRING data type GET/SET dc09: Date Modified STRING data type DATETIME FORM READ ONLY dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY dc44: Name STRING data type READ ONLY dc4e: Date Added STRING data type DATETIME FORM
[Desktop-packages] [Bug 1529999] Re: reporting per mtp-detect: droid razr hd not recognized
Fixed in Ubuntu 16.04 which has 1.1.10-2ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/152 Title: reporting per mtp-detect: droid razr hd not recognized Status in libmtp package in Ubuntu: Fix Released Bug description: On Ubuntu 12.04lts, mtp-detect reporst the following about a USB- connected Verizon DROID MAXX HD smartphone. Request that this be fixed. Device 0 (VID=22b8 and PID=2e62) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device libmtp version: 1.1.3 Listing raw device(s) Found 1 device(s): 22b8:2e62 @ bus 2, dev 10 Attempting to connect device(s) Android device detected, assigning default bug flags USB low-level info: Interface has a kernel driver attached. bcdUSB: 512 bDeviceClass: 0 bDeviceSubClass: 0 bDeviceProtocol: 0 idVendor: 22b8 idProduct: 2e62 IN endpoint maxpacket: 512 bytes OUT endpoint maxpacket: 512 bytes Raw device info: Bus location: 2 Device number: 10 Device entry info: Vendor: (null) Vendor id: 0x22b8 Product: (null) Vendor id: 0x2e62 Device flags: 0x08008106 Configuration 0, interface 0, altsetting 0: Interface description contains the string "MTP" Device recognized as MTP, no further probing. Device info: Manufacturer: motorola Model: DROID RAZR HD Device version: 1.0 Serial number: Vendor extension ID: 0x0006 Vendor extension description: microsoft.com: 1.0; android.com: 1.0; mot-mobility.com/DSU: 1.2 Detected object size: 64 bits Extensions: microsoft.com: 1.0 android.com: 1.0 Supported operations: 1001: get device info 1002: Open session 1003: Close session 1004: Get storage IDs 1005: Get storage info 1006: Get number of objects 1007: Get object handles 1008: Get object info 1009: Get object 100a: Get thumbnail 100b: Delete object 100c: Send object info 100d: Send object 1014: Get device property description 1015: Get device property value 1016: Set device property value 1017: Reset device property value 101b: Get partial object 9801: Get object properties supported 9802: Get object property description 9803: Get object property value 9804: Set object property value 9805: Get object property list 9810: Get object references 9811: Set object references 95c1: Unknown (95c1) 95c2: Unknown (95c2) 95c3: Unknown (95c3) 95c4: Unknown (95c4) 95c5: Unknown (95c5) 9001: Unknown (9001) 9002: Unknown (9002) 9003: Unknown (9003) 9004: Unknown (9004) 9005: Unknown (9005) 9006: Unknown (9006) 9007: Unknown (9007) 9008: Unknown (9008) 9009: Unknown (9009) 900a: Unknown (900a) 900b: Unknown (900b) 900c: Unknown (900c) Events supported: 0x4002 0x4003 0x4004 0x4005 Device Properties Supported: 0xd401: Synchronization Partner 0xd402: Friendly Device Name 0x5003: Image Size Playable File (Object) Types and Object Properties Supported: 3000: Undefined Type dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY dc04: Object Size UINT64 data type READ ONLY dc07: Object File Name STRING data type GET/SET dc09: Date Modified STRING data type DATETIME FORM READ ONLY dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY dc44: Name STRING data type READ ONLY dc4e: Date Added STRING data type DATETIME FORM READ ONLY 3001: Association/Directory dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY dc04: Object Size UINT64 data type READ ONLY dc07: Object File Name STRING data type GET/SET dc09: Date Modified STRING data type DATETIME FORM READ ONLY dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY dc44: Name STRING data type READ ONLY dc4e: Date Added STRING data type DATETIME FORM READ ONLY 3004: Text dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY dc02:
[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
It could be that Debian won't need this change. Looks like all the triggers are now processed near the end of upgrade, due to changes in dpkg itself. Possibly related entry from dpkg 1.19.3 changelog: * dpkg: Introduce a new dependency try level for trigger processing. This completely defers trigger processing until after the dependency cycle breaking level, so to avoid generating artificial trigger cycles, when we end up trying to process triggers with yet unsatisifiable dependencies. Closes: #810724, #854478, #911620 https://bugs.debian.org/810724 And from dpkg 1.19.7 changelog: * dpkg: Split the trigger dependtry into two, the second of which will be the one checking trigger cycles when deferring trigger processing due to unsatisfiable dependencies. Closes: #928429 https://bugs.debian.org/928429 ** Bug watch added: Debian Bug tracker #810724 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810724 ** Bug watch added: Debian Bug tracker #928429 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928429 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
No, Debian package doesn't have this change. As for the bug reports, I only found a mention of this issue in a report for dpkg: https://bugs.debian.org/774794 ** Bug watch added: Debian Bug tracker #774794 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774794 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Description changed: - When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. + [Impact] + + During system upgrades, triggers for gconf2 might activate too early, + while some of its dependencies aren't configured yet. This happens + several times in a loop and stops the upgrade in the end. + + The attached debdiffs fix this issue by changing interest to interest- + noawait in debian/gconf2.triggers file. The triggers will now activate + near the end of upgrade. + + In addition, the debdiff for Bionic also contains a fix for FTBFS (bug + 1834211). + + [Test Case] + + Triggers for gconf2 are usually activated on changes in + /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with + GNOME) is most suitable for reproducing the issue. To reproduce it, + install that edition, apply all updates, then try upgrading to the next + release. + + [Regression Potential] + + None, interest-noawait trigger is known to work well in other packages + (comment 31). + + [Other Info] + + Even if Cosmic goes EOL next month, the fix for it might be worth it for + release upgrades. + + [Original Description] + + When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: - dpkg 1.18.4ubuntu1 - apt 1.2.3 + dpkg 1.18.4ubuntu1 + apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) ** Summary changed: - package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed + [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** Tags added: bionic cosmic disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 1834211] Re: [SRU] gconf FTBFS in Bionic
These fixes are also added to combined debdiff in bug 1551623. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fix for 18.04 + build fix (bug 1834211) this can go into bionic-proposed in one diff ** Attachment added: "Debdiff with the fix for Bionic + build fix (bug 1834211)" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273780/+files/gconf-debdiff-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
For 18.04, a build fix is required first (bug 1834211). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fix for 18.10 ** Attachment added: "Debdiff with the fix for Cosmic" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273779/+files/gconf-debdiff-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fix for 19.04 ** Attachment added: "Debdiff with the fix for Disco" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273778/+files/gconf-debdiff-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
This is similar to what happened in the past with: - dbus (https://bugs.debian.org/771989) - cracklib-runtime (https://bugs.debian.org/854554) - shared-mime-info (https://bugs.debian.org/864953) It can be fixed the same way as those. I'll post the debdiffs with the fixes later. ** Bug watch added: Debian Bug tracker #771989 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771989 ** Bug watch added: Debian Bug tracker #854554 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854554 ** Bug watch added: Debian Bug tracker #864953 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864953 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733733] Re: portable apps crash while installing package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estad
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1733733 Title: portable apps crash while installing package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post- installation instalado retornou estado de saída de erro 128 Status in gconf package in Ubuntu: New Bug description: I installed orbital apps then it crashed, i changed to unity environment then tried to install again. I'm in need for portable apps for ubuntu. Description: Ubuntu 17.10 Release: 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: gconf2-common 3.2.6-4ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 21 21:44:08 2017 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 128 InstallationDate: Installed on 2017-09-05 (77 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: gconf Title: package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 128 UpgradeStatus: Upgraded to artful on 2017-11-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1733733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645384] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida d
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1645384 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 128 Status in gconf package in Ubuntu: Confirmed Bug description: el problema se genero cuando intentaba descargar unos programas, no se completo la descarga y la tuve que reiniciar y posterior al reinicio aparecio el mensaje de error. ProblemType: Package DistroRelease: elementary 0.4 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 28 09:10:05 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 128 InstallationDate: Installed on 2016-11-26 (1 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698612] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1698612 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett Status in gconf package in Ubuntu: New Bug description: this problem comes up after aech booting ProblemType: Package DistroRelease: elementary 0.4.1 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue May 23 18:21:04 2017 ErrorMessage: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett InstallationDate: Installed on 2017-05-22 (26 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711472] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sorti
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1711472 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128 Status in gconf package in Ubuntu: New Bug description: Hello, i want you say what this problem isn't today. I had this problem with ubuntu16.10 And today i have this problem with this new system based on ubuntu. I wish what you resolved this problem. Jo ProblemType: Package DistroRelease: elementary 0.4.1 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Aug 17 23:53:18 2017 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1711472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834211] Re: [SRU] gconf FTBFS in Bionic
** Attachment added: "Debdiff with the fix for Bionic" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+attachment/5273159/+files/gconf-debdiff-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834211] [NEW] [SRU] gconf FTBFS in Bionic
Public bug reported: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk-doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574029] Re: Upgrade failed
*** This bug is a duplicate of bug 1550292 *** https://bugs.launchpad.net/bugs/1550292 ** This bug has been marked a duplicate of bug 1550292 package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1574029 Title: Upgrade failed Status in shared-mime-info package in Ubuntu: New Bug description: At the end of the upgrade, a dialog box appeared "The upgrade has aborted. Your system could be in an unstable state. A recovery will run now (dpkg -configure - a). Nothing happened after closing the dialog box. After shutdown, boot up failed after grub tries to load something with this message "Starting up", then after 10 seconds this message "Gave up waiting for root device., common problems:.ALERT! UUID = 2476e..does not exist. The the boot process stopped at the initramfs prompt. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.5-2 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 17:34:29 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-11-12 (162 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1574029/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568572] Re: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fixed in Xenial on 2016-07-18 by using interest-noawait in debian/bamfdaemon.triggers file. More info at bug 1589097. ** Changed in: bamf (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1568572 Title: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in bamf package in Ubuntu: Fix Released Bug description: I submitted this bug report because Ubuntu advised me to do so during an upgrade to Xenial from Wily. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 Uname: Linux 4.0.3-bisect-test-01-0559366f72c86288c8d3dc5cae91dfc2f6e26ad9 x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 10 19:23:53 2016 DuplicateSignature: package:bamfdaemon:0.5.2~bzr0+15.10.20150627.1-0ubuntu1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: bamf Title: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1568572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574123] Re: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1568572 *** https://bugs.launchpad.net/bugs/1568572 ** This bug has been marked a duplicate of bug 1568572 package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1574123 Title: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in bamf package in Ubuntu: Confirmed Bug description: during upgrade bamfdaemon was noch possible to install. Now it seems to be missiong? how to install it now? via packet-installer or terminal? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Sat Apr 23 20:17:09 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-08-21 (246 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: bamf Title: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1574123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1599846] Re: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
*** This bug is a duplicate of bug 1568572 *** https://bugs.launchpad.net/bugs/1568572 ** This bug has been marked a duplicate of bug 1568572 package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1599846 Title: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet Status in bamf package in Ubuntu: New Bug description: Update failed while upgrading from xenial to yakkety. mahowi@T60:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 mahowi@T60:~$ apt-cache policy bamfdaemon bamfdaemon: Installiert: 0.5.3~bzr0+16.10.20160705-0ubuntu1 Installationskandidat: 0.5.3~bzr0+16.10.20160705-0ubuntu1 Versionstabelle: *** 0.5.3~bzr0+16.10.20160705-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 16.10 Package: bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 Date: Thu Jul 7 13:39:38 2016 ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet InstallationDate: Installed on 2016-07-06 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.9ubuntu1 apt 1.3~exp1 SourcePackage: bamf Title: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet UpgradeStatus: Upgraded to yakkety on 2016-07-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1599846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1615116] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1615116 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade Status in gconf package in Ubuntu: Confirmed Bug description: Error received when upgrading from 16.04 to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 19 18:49:10 2016 ErrorMessage: beroendeproblem - lämnar utlösare obehandlade InstallationDate: Installed on 2016-02-08 (193 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu2 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1615116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1669632] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1669632 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 2 20:56:22 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-04-10 (326 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-03-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1669632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1634151] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1634151 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld Status in gconf package in Ubuntu: New Bug description: Did an upgrade from Ubuntu 16.04 to 16.10, after rebooting the system the message occured ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Mon Oct 17 13:29:10 2016 ErrorMessage: vereistenproblemen - triggers blijven onbehandeld InstallationDate: Installed on 2016-05-04 (166 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1634151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681137] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1681137 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: while upgrading from 16.04 to 16.10, it gave me this bug.. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Apr 9 01:01:29 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-08-01 (250 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-04-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1681137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1632415] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1632415 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: error after updating from 16.04.1 to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 11 22:08:46 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-25 (78 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1632415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741658] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1741658 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: System upgrage to Ubuntu 16.04 failed. During upgrade many packets were not installed: I wrote down the Dutch remarks "Kan gconf2 niet installeren" and many others. Translated: Failed to install during the systemupgrade: == gconf2 (+ "gconf2 will possibly not work") gnupg-agent gnupg2 libgdata22 gvfs-backends adwaita-icon-theme-full libgail-3-0 gstreamer1.0-plugins-bad gstreamer0.10-plugins-good gstreamer1.10-plugins-good libgssdp-1.0-3 libupnp-1.0-4 libupnp-igd-1.0-4 libnice10 gstreamer1.0-nice libfarstream-0.2-5 libpurple0 gnome-keyring libgpgme11 libgmime-2.6-0 libwebkitgtk-3.0-0 geary gnome-icon-theme === Hope the list is complete :-)) Since then only logging-out is possible, but the menu items: "Close the system" ("Afsluiten" in Dutch) nor "Restart" gave any effect. Caption of this menu is: Lubuntu Session Zorin-OS-lite 16.04 Best regards! Dirk De Backer mailto:debacker.d...@worldonline.be ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Sat Jan 6 15:32:06 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-12-19 (748 days ago) InstallationMedia: Zorin 9 trusty - Release i386 (20140811) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2018-01-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1741658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636962] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1636962 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 26 23:42:05 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-04-27 (181 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1636962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1656553] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1645117 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1656553 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: Error during partial update from 16.04 LTS to 16.10. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic i686 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 Date: Sat Jan 14 15:46:26 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-12-14 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1656553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645117] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1645117 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: -- ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 Date: Sun Nov 27 21:29:34 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-09-03 (85 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1651222] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1651222 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: upgrade done with fail to install package gconf2 3.2.6ubuntu7 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Dec 19 13:13:09 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-11-19 (29 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1651222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698600] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1698600 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: upgrading from 16.04 to 17.04 failed to install ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 Date: Sat Jun 17 18:19:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-09-13 (277 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-06-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1701447] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1701447 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: The bugs being reported were generated automatically (without any of my input) when I allowed the system to upgrade itself from 16.04 to 16.10. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 Date: Thu Jun 29 21:58:13 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-11-27 (214 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-06-30 (0 days ago) mtime.conffile..etc.xdg.autostart.gsettings-data-convert.desktop: 2017-01-03T13:15:58.771330 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1701447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698478] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1698478 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: would load but with errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri Jun 16 17:22:13 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-06-16 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2017-06-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1618364] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1618364 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar Status in gconf package in Ubuntu: Confirmed Bug description: After upgrade from xenial to yakkety ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 09:34:31 2016 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2016-02-15 (196 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1618364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1610029] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1610029 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: when upgrading from 14.04 LTS to 16.04 LTS this error came up during the upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Aug 3 23:57:59 2016 ErrorMessage: dependency problems - leaving triggers unprocessed RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1610029/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1618492] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1618492 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati Status in gconf package in Ubuntu: Confirmed Bug description: crash ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 14:35:15 2016 ErrorMessage: problemi con le dipendenze - trigger non elaborati InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1618492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573662] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1573662 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet Status in gconf package in Ubuntu: Confirmed Bug description: error occured during regular "do-release-upgrade". System remains in unstable condition. dpkg --configure -a / apt-get -f install continues the process (still running). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Apr 22 17:05:44 2016 DuplicateSignature: package:gconf2:3.2.6-3ubuntu6:Abhängigkeitsprobleme - Trigger bleiben unverarbeitet ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet InstallationDate: Installed on 2016-03-17 (35 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1573662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576539] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1576539 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: bug happened while i'm upgrading ubuntu version from 15.10 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 29 08:16:36 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-03-05 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1576539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743975] Re: "Power Statistics" UI become grey and have no respond after launch it about 30 seconds
*** This bug is a duplicate of bug 1721282 *** https://bugs.launchpad.net/bugs/1721282 ** This bug has been marked a duplicate of bug 1721282 upowerd/gnome-power-statistics crash; high CPU, memory consumption -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1743975 Title: "Power Statistics" UI become grey and have no respond after launch it about 30 seconds Status in gnome-power-manager package in Ubuntu: New Bug description: Install Ubuntu 16.04 and launch Power Statistics, After the application launched for a while(about 30 sec), the UI become gray and has no response. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1743975/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796804] Re: webkit2gtk-4.0-dev 依赖关系不完整(dependence wrong)
*** This bug is a duplicate of bug 1795901 *** https://bugs.launchpad.net/bugs/1795901 ** This bug has been marked a duplicate of bug 1795901 libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1796804 Title: webkit2gtk-4.0-dev 依赖关系不完整(dependence wrong) Status in webkit2gtk package in Ubuntu: New Bug description: Proccess: apt install libwebkit2gtk-4.0-dev golang-go go get -v github.com/sourcegraph/go-webkit2/webkit2 Will report error: # github.com/sourcegraph/go-webkit2/webkit2 In file included from /usr/include/webkitgtk-4.0/webkit2/webkit2.h:54:0, from ../../github.com/sourcegraph/go-webkit2/webkit2/settings.go:3: /usr/include/webkitgtk-4.0/webkit2/WebKitJavascriptResult.h:28:10: fatal error: jsc/jsc.h: No such file or directory #include ^~~ compilation terminated. Because: there is no "jsc.h" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1796804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795901] Re: libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h
Thanks, Atril builds fine now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1795901 Title: libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h Status in WebKit: Unknown Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk source package in Bionic: Fix Released Status in webkit2gtk package in Debian: Unknown Bug description: 2.22.2-0ubuntu0.18.04.1, just like https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=906519 /usr/include/webkitgtk-4.0/webkit2/WebKitJavascriptResult.h:28:10: fatal error: jsc/jsc.h: No such file or directory #include ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/webkit-open-source/+bug/1795901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795901] Re: libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h
Also it's impossible to build Atril, MATE's document viewer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1795901 Title: libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h Status in webkit2gtk package in Ubuntu: Confirmed Status in webkit2gtk package in Debian: Unknown Bug description: 2.22.2-0ubuntu0.18.04.1, just like https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=906519 /usr/include/webkitgtk-4.0/webkit2/WebKitJavascriptResult.h:28:10: fatal error: jsc/jsc.h: No such file or directory #include ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1795901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Is this fix related to nvidia-390 only or will nvidia-396 from graphics- drivers/ppa benefit from it as well? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788036] Re: nautilus crashed with SIGSEGV in tcache_get()
*** This bug is a duplicate of bug 1786650 *** https://bugs.launchpad.net/bugs/1786650 ** This bug has been marked a duplicate of bug 1786650 nautilus crashed with SIGSEGV in tcache_get() -- 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/1788036 Title: nautilus crashed with SIGSEGV in tcache_get() Status in nautilus package in Ubuntu: Confirmed Bug description: nautilus closed all of a sudden ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 23:26:18 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'216' b'org.gnome.nautilus.window-state' b'geometry' b"'960x1011+960+27'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f7f019c1207 <__GI___libc_malloc+407>: mov (%rdx),%rdi PC (0x7f7f019c1207) ok source "(%rdx)" (0x6f73692e) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: tcache_get (tc_idx=0) at malloc.c:2943 __GI___libc_malloc (bytes=17) at malloc.c:3050 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strndup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strsplit () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGSEGV in tcache_get() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1788036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound
Same: ASUS Prime x470-pro, Ryzen 7 2700X, 4.18.0 kernel. Cracking sound on the mic/line-in on ALC1220. The only thing, that somewhat helped, is increasing the default-fragment-size-msec to 75+ at /etc/pulse/daemon.conf. But it is a workaround, and it doesn't remove the cracking fully. -- 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/1716654 Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Confirmed Bug description: Have checked under windows (same computer in dual-boot & same headset), and the sound is crystal clear, so 99% sure this is not a hardware problem. Motherboard is ASUS Crosshair Hero 6. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: paul 2587 F pulseaudio /dev/snd/controlC0: paul 2587 F pulseaudio /dev/snd/controlC1: paul 2587 F pulseaudio /dev/snd/controlC2: paul 2587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 11:48:05 2017 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic successful Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780390] Re: gedit - incorrect print preview - 2 pages per side
** Attachment added: "print preview" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1780390/+attachment/5160294/+files/Screenshot%20from%202018-07-06%2009-52-39.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1780390 Title: gedit - incorrect print preview - 2 pages per side Status in gedit package in Ubuntu: New Bug description: Steps: 1. open gedit with text file ( 145 lines - sample attached) 2. menu > print > page setup > pages per side=2; orientation=portrait > Preview Observed: Layout uses only left side of each sheet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1780390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780390] [NEW] gedit - incorrect print preview - 2 pages per side
Public bug reported: Steps: 1. open gedit with text file ( 145 lines - sample attached) 2. menu > print > page setup > pages per side=2; orientation=portrait > Preview Observed: Layout uses only left side of each sheet ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu-test-preview.txt" https://bugs.launchpad.net/bugs/1780390/+attachment/5160293/+files/ubuntu-test-preview.txt ** Package changed: splix (Ubuntu) => gedit (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/1780390 Title: gedit - incorrect print preview - 2 pages per side Status in gedit package in Ubuntu: New Bug description: Steps: 1. open gedit with text file ( 145 lines - sample attached) 2. menu > print > page setup > pages per side=2; orientation=portrait > Preview Observed: Layout uses only left side of each sheet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1780390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745666] Re: gsd-housekeeping leaks file descriptors
Same here, for Permission Denied, on Bionic. Occurs once every hour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Apparently a process called gsd-housekeeping is periodically invoked on my Ubuntu 17.10 system. It traverses my /var/tmp for some reason. Looks like it is leaking file descriptors while doing so. My syslogs are full of error messages like the following: Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h': Too many open files $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.26.2-0ubuntu0.1 Candidate: 3.26.2-0ubuntu0.1 Version table: *** 3.26.2-0ubuntu0.1 500 500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu5 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption
** Tags added: bionic xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1721282 Title: upowerd/gnome-power-statistics crash; high CPU, memory consumption Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: Not sure if necessary here since same bug is already on: https://bugzilla.redhat.com/show_bug.cgi?id=1427621 https://bugs.freedesktop.org/show_bug.cgi?id=100626 https://bugzilla.gnome.org/show_bug.cgi?id=781088 Tested on Ubuntu 16.04.3, 4.12.0-041200rc3-generic Steps to reproduce: 1. have a system with a recent kernel (4.10.x or later) 2. start gnome-power-statistics 3. go to Pprocessor tab 4. have a look at gnome-system-monitor or htop Result: - On Processor section, Wakeups tab: "Processor wakeups pers second: GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats." - High CPU usage of /usr/lib/upower/upowerd - Crash gnome-power-statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1721282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1421808] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter()
Hello, Reproduction steps: 1. connect an external monitor (I connect mine through mini-DisplayPort, and I use only the external monitor, I do NOT use both the laptop screen and the external monitor) 2. with the external monitor connected, suspend the computer (I do it by running xfce4-session-logout --suspend, I have a shortcut for this) 3. with the laptop suspended, disconnect the monitor 4. open the laptop, you'll be shown the Xdm login screen 5. log in 6. Xorg will crash, it will restart, and you'll see again the Xdm login screen What works (how to avoid the crash) 1. connect an external monitor 2. before suspending the laptop, disconnect the external monitor 3. suspend the laptop 4. open the laptop, everything will be ok -- 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/1421808 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter() Status in xorg-server package in Ubuntu: Confirmed Bug description: The error is reported on boot up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 8 12:36:52 2015 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2013-04-24 (660 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130403) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86VTEnter () WakeupHandler () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to vivid on 2015-01-30 (14 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1421808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1421808] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter()
Hello, For me this started to manifest in the last months; Xorg started crashing randomly after I resume from sleep. In the meantime, I've installed Xubuntu 18.04 from scratch (keeping only the /home partition) hoping that the problem would be gone. But it isn't. It seems to be related to the external monitor - ie when there is an external monitor plugged in and I suspend the computer, and when I resume there's only the laptop. But it doesn't always happen, so I don't have clear steps for reproducing. (My bug report was marked as duplicate of this bug, https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1774635) -- 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/1421808 Title: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter() Status in xorg-server package in Ubuntu: Confirmed Bug description: The error is reported on boot up. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 8 12:36:52 2015 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2013-04-24 (660 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130403) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86VTEnter () WakeupHandler () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to vivid on 2015-01-30 (14 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1421808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774635] Re: Xorg crashes - SIGABRT - after resuming from suspend
** Information type changed from Private to Public -- 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/1774635 Title: Xorg crashes - SIGABRT - after resuming from suspend Status in xorg-server package in Ubuntu: New Bug description: In the last months, Xorg started crashing randomly after I resume from sleep. I've installed Xubuntu 18.04 from scratch (keeping only the /home partition) hoping that the problem would be gone. But it isn't. It seems to be related to the external monitor - ie when there is an external monitor plugged in and I suspend the computer, and when I resume there's only the laptop. But it doesn't always happen, so I don't have clear steps for reproducing. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Thu May 31 18:01:17 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1523633505 GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e3] InstallationDate: Installed on 2018-05-22 (10 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 12-9Q33 ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcCwd: / ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=0da52507-c787-46d7-9266-d53448c18283 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86VTEnter () WakeupHandler () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.asset.tag: 0 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1774635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765230] Re: Immediate logout when using Chrome (and not only it)
The bug was in the Amdgpu-pro drivers. Uninstalled them, and the problem disappeared. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765230 Title: Immediate logout when using Chrome (and not only it) Status in xorg package in Ubuntu: New Bug description: Sometimes when I open a new tab or start downloading a file with the Chrome browser, the system logs me out. Then this problem persists so that I'm logged out very fast, and only reboot helps. Starting Firefox after the first crash also leads to logout. What exact information can I provide (some logs etc)? Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Apr 19 01:56:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.40-492261: added virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3418] InstallationDate: Installed on 2018-04-11 (7 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765230] Re: Immediate logout when using Chrome (and not only it)
Here are the main syslog lines when it happens: Apr 19 22:52:00 vladiat0r dbus-daemon[929]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.97' (uid=1000 pid=2112 comm="/opt/google/chrome/chrome " label="unconfined") Apr 19 22:52:00 vladiat0r systemd[1]: Starting Hostname Service... Apr 19 22:52:00 vladiat0r org.a11y.Bus[1158]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Apr 19 22:52:00 vladiat0r org.a11y.Bus[1158]: after 6865 requests (6865 known processed) with 0 events remaining. Apr 19 22:52:00 vladiat0r org.kde.kuiserver[1158]: kuiserver: Fatal IO error: client killed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765230 Title: Immediate logout when using Chrome (and not only it) Status in xorg package in Ubuntu: New Bug description: Sometimes when I open a new tab or start downloading a file with the Chrome browser, the system logs me out. Then this problem persists so that I'm logged out very fast, and only reboot helps. Starting Firefox after the first crash also leads to logout. What exact information can I provide (some logs etc)? Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Apr 19 01:56:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.40-492261: added virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3418] InstallationDate: Installed on 2018-04-11 (7 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765230] [NEW] Immediate logout when using Chrome (and not only it)
Public bug reported: Sometimes when I open a new tab or start downloading a file with the Chrome browser, the system logs me out. Then this problem persists so that I'm logged out very fast, and only reboot helps. Starting Firefox after the first crash also leads to logout. What exact information can I provide (some logs etc)? Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Apr 19 01:56:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.40-492261: added virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3418] InstallationDate: Installed on 2018-04-11 (7 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic kubuntu performance ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765230 Title: Immediate logout when using Chrome (and not only it) Status in xorg package in Ubuntu: New Bug description: Sometimes when I open a new tab or start downloading a file with the Chrome browser, the system logs me out. Then this problem persists so that I'm logged out very fast, and only reboot helps. Starting Firefox after the first crash also leads to logout. What exact information can I provide (some logs etc)? Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Apr 19 01:56:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.40-492261: added virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3418] InstallationDate: Installed on 2018-04-11 (7 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No
[Desktop-packages] [Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)
** Package changed: mate-desktop (Ubuntu) => ubuntu-mate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1754458 Title: nm-applet symbol not displayed on mate (18.04) Status in ubuntu-mate: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 18.04, the network manager applet symbol isn't displayed any longer. The other functionality (asking for credentials) is working. I also see other symbols. aptitude show network-manager-gnome Paket: network-manager-gnome Version: 1.8.10-2ubuntu1 Neu: ja Zustand: Installiert stdout/stderr: Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module" ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab information for modem at /org/freedesktop/ModemManager1/Modem/6: No ModemManager support (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is not available for modem at /org/freedesktop/ModemManager1/Modem/6 (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on widget which has a parent ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: MATE Date: Thu Mar 8 21:27:56 2018 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) WpaSupplicantLog: nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1754458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755555] Re: nautilus crashed with SIGSEGV while trying to install Budgie Desktop applet
** Information type changed from Private to Public -- 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/175 Title: nautilus crashed with SIGSEGV while trying to install Budgie Desktop applet Status in nautilus package in Ubuntu: New Bug description: This problem happens on Ubuntu Budgie 18.04 when first time in session I try to install applet using Budgie Desktop Applets. Seems like it only happens when installing Global menu applet (budgie-appmenu- applet) which afterwards also does not show up in applet list, though apt says it installed. But Pixel Saver applet (budgie-pixel-saver- applet) which has similar functionality installs without any problems and works fine. Release: 18.04 Description: Ubuntu Bionic Beaver (development branch) budgie-appmenu-applet: Installed: 0.6.92+repack1-3ubuntu1 budgie-pixel-saver-applet: Installed: 4.0+git20171102.30c1f94-0ubuntu1~bionic nautilus: Installed: 1:3.26.2-0ubuntu3.1 I should also mention that I could not login and got freezes after installation without nomodeset because of Nvidia drivers. I installed nvidia-384 driver and deleted xserver-xorg-video-nvidia-390 to fix these freezes and be able to login to desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 13 19:11:31 2018 Disassembly: No registers. ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+108+80'" b'org.gnome.nautilus.desktop' b'network-icon-visible' b'true' b'org.gnome.nautilus.desktop' b'volumes-visible' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-03-12 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180312) ProcCmdline: /usr/bin/nautilus --gapplication-service Registers: The program has no registers now. SegvAnalysis: Failure: invalid literal for int() with base 16: 'program' Signal: 11 SourcePackage: nautilus Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1613363] Re: /usr/bin/engrampa:11:g_type_check_instance_is_fundamentally_a:g_object_get_qdata:detach_from_style:clear_cache:ensure_cache_up_to_date
** Package changed: engrampa (Ubuntu) => gtk+2.0 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1613363 Title: /usr/bin/engrampa:11:g_type_check_instance_is_fundamentally_a:g_object_get_qdata:detach_from_style:clear_cache:ensure_cache_up_to_date Status in gtk+2.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding engrampa. This problem was most recently seen with version 1.12.0-2, the problem page at https://errors.ubuntu.com/problem/2f8bf782a90fe3ab90595f0ab71cdafa82f08b7f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1613363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569068] Re: /usr/bin/mate-settings-daemon:ERROR:pulse/glib-mainloop.c:407:glib_defer_free: assertion failed: (!e->dead)
** Package changed: mate-settings-daemon (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1569068 Title: /usr/bin/mate-settings-daemon:ERROR:pulse/glib- mainloop.c:407:glib_defer_free: assertion failed: (!e->dead) Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with version 1.12.1-2build1, the problem page at https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1569068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 580958] Re: nautilus crashed with signal 7
** Package changed: nautilus (Ubuntu) => gvfs (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/580958 Title: nautilus crashed with signal 7 Status in Nautilus: Expired Status in gvfs package in Ubuntu: Triaged Bug description: Binary package hint: nautilus Nautilus crashes if it has not been used for some time (I don't now the exact time but maybe 15 minutes). If it is already started it crashes and if I start it it crashes. But it works if I start it a second time, but crashes again when it has been idle for 15 minutes. ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: openafs nvidia Architecture: i386 CrashCounter: 1 Date: Sat May 15 15:15:29 2010 ExecutablePath: /usr/bin/nautilus ProcCmdline: nautilus ProcEnviron: LANGUAGE=sv_SE:sv:en_GB:en PATH=(custom, no user) LANG=sv_SE.utf8 SHELL=/bin/bash Signal: 7 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/gio/modules/libgvfsdbus.so ?? () from /usr/lib/gio/modules/libgvfsdbus.so ?? () from /usr/lib/gio/modules/libgvfsdbus.so ?? () from /usr/lib/gio/modules/libgvfsdbus.so ?? () from /usr/lib/gio/modules/libgvfsdbus.so Title: nautilus crashed with signal 7 UserGroups: admin audio plugdev pulse To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/580958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp