[Desktop-packages] [Bug 1987556] [NEW] Add a short alias (eg "gted") for gnome-text-editor
Public bug reported: Unix pro users on the terminal emulator probably use vi, emacs or nano to edit plain text files. Those have all short binary names because it is a practical common UNIX practice to use short binary names for common usage. With Ubuntu 22.10 gnome-text-editor is the new default text editor instead of gedit. I used gedit quite often for editing files and "gedit" was like "vi" or "nano" easy to type. gnome-text-editor is not certainly not written for being invoked from the terminal but like gedit before it will be used by Linux beginners for it's ease of use (like notepad on Windows). Having a short alias like e.g. "gted" by default would make it easy to invoke gnome-text-editor for those who don't know how to set aliases or edit the .bashrc. And having it set by default would help having seeing it used in Ubuntu tutorials. Upstream is not willing to discuss the clunky binary Name thus this would be a non intrusive downstream workaround. As Debian is more of a power user distribution and Ubuntu more beginner- centric, I decided to file the bug for Ubuntu only. 1) System: Ubuntu 22.10 2) Package: gnome-text-editor 42.2 3) What I expected to happen: a fast way to open the text editor that I am used to in gnome-terminal 4) what happened instead: "gnome-text-editor filename" ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1987556 Title: Add a short alias (eg "gted") for gnome-text-editor Status in gnome-text-editor package in Ubuntu: New Bug description: Unix pro users on the terminal emulator probably use vi, emacs or nano to edit plain text files. Those have all short binary names because it is a practical common UNIX practice to use short binary names for common usage. With Ubuntu 22.10 gnome-text-editor is the new default text editor instead of gedit. I used gedit quite often for editing files and "gedit" was like "vi" or "nano" easy to type. gnome-text-editor is not certainly not written for being invoked from the terminal but like gedit before it will be used by Linux beginners for it's ease of use (like notepad on Windows). Having a short alias like e.g. "gted" by default would make it easy to invoke gnome-text-editor for those who don't know how to set aliases or edit the .bashrc. And having it set by default would help having seeing it used in Ubuntu tutorials. Upstream is not willing to discuss the clunky binary Name thus this would be a non intrusive downstream workaround. As Debian is more of a power user distribution and Ubuntu more beginner-centric, I decided to file the bug for Ubuntu only. 1) System: Ubuntu 22.10 2) Package: gnome-text-editor 42.2 3) What I expected to happen: a fast way to open the text editor that I am used to in gnome-terminal 4) what happened instead: "gnome-text-editor filename" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1987556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963241] Re: [FFe] evince 42
The new libarchive should increase increase the compatibility with zip and RAR files. Certainly not an essential boost in functionality but on the other hand certainly welcome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1963241 Title: [FFe] evince 42 Status in evince package in Ubuntu: Fix Released Bug description: Why Needed -- The Ubuntu Desktop had a goal of including as much of GNOME 42 as possible in Ubuntu 22.04 LTS. (One major exception was where apps had switched to GTK4). The evince document viewer (PDFs and more) did not have earlier releases in the 42 cycle and its Beta wasn't released until March 3, a week after Feature Freeze. The Ubuntu Desktop Team commits to packaging the final evince 42 stable release and working to fix any regressions introduced in the update. We do have the ability to use a "really" version number in case we decide we need to go back to the 41 version. What Changed https://gitlab.gnome.org/GNOME/evince/-/blob/42.beta/NEWS https://gitlab.gnome.org/GNOME/evince/-/compare/41.3...42.beta For this release I have reverted 2 commits that required a new version of libarchive since that wasn't included in 22.04 LTS yet. Build Test -- Builds successfully Install Test $ sudo apt install ./../build-area/*ev*.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'evince' instead of './../build-area/evince_42~beta-1_amd64.deb' Note, selecting 'evince-common' instead of './../build-area/evince-common_42~beta-1_all.deb' Note, selecting 'gir1.2-evince-3.0' instead of './../build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb' Note, selecting 'libevdocument3-4' instead of './../build-area/libevdocument3-4_42~beta-1_amd64.deb' Note, selecting 'libevview3-3' instead of './../build-area/libevview3-3_42~beta-1_amd64.deb' The following packages were automatically installed and are no longer required: libabsl20200923 libicu67 libpoppler115 Use 'sudo apt autoremove' to remove them. Suggested packages: unrar The following packages will be upgraded: evince evince-common gir1.2-evince-3.0 libevdocument3-4 libevview3-3 5 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Need to get 0 B/821 kB of archives. After this operation, 803 kB disk space will be freed. Get:1 /home/jeremy/devel/pkg-gnome/build-area/evince-common_42~beta-1_all.deb evince-common all 42~beta-1 [132 kB] Get:2 /home/jeremy/devel/pkg-gnome/build-area/evince_42~beta-1_amd64.deb evince amd64 42~beta-1 [306 kB] Get:3 /home/jeremy/devel/pkg-gnome/build-area/libevdocument3-4_42~beta-1_amd64.deb libevdocument3-4 amd64 42~beta-1 [204 kB] Get:4 /home/jeremy/devel/pkg-gnome/build-area/libevview3-3_42~beta-1_amd64.deb libevview3-3 amd64 42~beta-1 [148 kB] Get:5 /home/jeremy/devel/pkg-gnome/build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb gir1.2-evince-3.0 amd64 42~beta-1 [31.1 kB] (Reading database ... 207369 files and directories currently installed.) Preparing to unpack .../evince-common_42~beta-1_all.deb ... Unpacking evince-common (42~beta-1) over (41.3-3) ... Preparing to unpack .../evince_42~beta-1_amd64.deb ... Unpacking evince (42~beta-1) over (41.3-3) ... Preparing to unpack .../libevdocument3-4_42~beta-1_amd64.deb ... Unpacking libevdocument3-4:amd64 (42~beta-1) over (41.3-3) ... Preparing to unpack .../libevview3-3_42~beta-1_amd64.deb ... Unpacking libevview3-3:amd64 (42~beta-1) over (41.3-3) ... Preparing to unpack .../gir1.2-evince-3.0_42~beta-1_amd64.deb ... Unpacking gir1.2-evince-3.0:amd64 (42~beta-1) over (41.3-3) ... Setting up evince-common (42~beta-1) ... Setting up libevdocument3-4:amd64 (42~beta-1) ... Setting up libevview3-3:amd64 (42~beta-1) ... Setting up evince (42~beta-1) ... Setting up gir1.2-evince-3.0:amd64 (42~beta-1) ... Processing triggers for desktop-file-utils (0.26-1ubuntu2) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1ubuntu2) ... Processing triggers for libglib2.0-0:amd64 (2.71.2-1) ... Processing triggers for libc-bin (2.35-0ubuntu1) ... Processing triggers for man-db (2.10.1-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... N: Download is performed unsandboxed as root as file '/home/jeremy/devel/pkg-gnome/build-area/evince-common_42~beta-1_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) $ evince (runs ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1943083] Re: screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen
** Description changed: - I reported that against mutter, but it can be gnome-shell as well. Or - Intel driver/Kernel related. It happens since I switched to Impish, - never saw that before. + I reported that against mutter, but it can be gnome-shell as well, or + even Intel driver/kernel related. It happens since my switch to Impish, + I have never seen that issue before. - Intel HD graphics 400 onboard. + Integrated Intel HD graphics 400 onboard. + STEPS to reproduce: + 1) Move the mouse pointer to the left edge of the screen + 2) See that everything works as expected + 3) Open an app so that the window comes up, eg. "Files" + 4) Move the mouse pointer to the left edge again. + 5) See that the screen goes black for a second, but the mouse pointer stays visible. - STEPS to reproduce: - 1) Move Mouse pointer to the left edge of the screen - 2) See that everything works as expected - 3) Start an app so that the window comes up, eg. "Files" - 4) Move the Mouse pointer to the left edge again. - 5) See that the Screen goes black for a second, but the mouse pointer stays visible. + Observation 1: At first I thought that it was related to dash-to-dock + because moving the mouse to the area where I used to have the dock + exhibits the flicker (I moved it to bottom for GNOME 40). But it turns + out that it doesn't matter: I can turn off the extension completely or + move it back to the left and the flicker always occurs. - Observation 1: At first I thought that it was related to dash-to dock - since moving the mouse to the area where I used to have the dock - exhibits the flicker (I had moved it to bottom for GNOME 40). But it - turns out that it doesn't matter: I can turn off the extension - completely or move it back to the left and the flicker always occurs. - - Observation 2: I doesn't happen without any window onscreen. Having a + Observation 2: It doesn't happen without any window onscreen. Having a program minimized to the dock doesn't suffice to exhibit the bug. I have - to bring up the window and then it shows. Fun Fact 1: "Files" exhibits - it more "aggresive" than "Terminal". + to bring up the window and then the bug shows up. Fun Fact 1: "Files" + exhibits it more "aggresively" than "Terminal". It is easier to trigger. + With gnome-terminal I sometimes can hit the edge with the pointer + without triggering the glitch. Observation 3: I cannot record the issue: Recording a screencast via - "Ctrl-Alt-Shift-R" doesn't work. When recording the screencast the issue - doesn't happen. + "Ctrl-Alt-Shift-R" doesn't work. Well, the screencasting itself does + work, but when recording the screencast the glitch simply doesn't + happen. - I am a bit lost further debugging this, any help is highly welcome. + I am a bit lost further debugging this, any help is highly welcome. I + guess that my observations rather hint at mutter being to blame. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mutter 40.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 23:03:53 2021 InstallationDate: Installed on 2018-02-23 (1293 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1943083 Title: screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen Status in mutter package in Ubuntu: New Bug description: I reported that against mutter, but it can be gnome-shell as well, or even Intel driver/kernel related. It happens since my switch to Impish, I have never seen that issue before. Integrated Intel HD graphics 400 onboard. STEPS to reproduce: 1) Move the mouse pointer to the left edge of the screen 2) See that everything works as expected 3) Open an app so that the window comes up, eg. "Files" 4) Move the mouse pointer to the left edge again. 5) See that the screen goes black for a second, but the mouse pointer stays visible. Observation 1: At first I thought that it was related to dash-to-dock because moving the mouse to the area where I used to have the dock exhibits the flicker (I moved it to bottom for GNOME 40). But it turns out that it doesn't matter: I can turn off the extension completely or move it back to the left and the flicker always occurs. Observation 2: It doesn't happen without any window onscreen. Having a program minimized to the dock doesn't suffice to exhibit the bug. I have to bring up the window and then the bug shows up. Fun Fact 1: "Files" exhibits it more "aggresively" than "Terminal". It
[Desktop-packages] [Bug 1943083] [NEW] screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen
Public bug reported: I reported that against mutter, but it can be gnome-shell as well. Or Intel driver/Kernel related. It happens since I switched to Impish, never saw that before. Intel HD graphics 400 onboard. STEPS to reproduce: 1) Move Mouse pointer to the left edge of the screen 2) See that everything works as expected 3) Start an app so that the window comes up, eg. "Files" 4) Move the Mouse pointer to the left edge again. 5) See that the Screen goes black for a second, but the mouse pointer stays visible. Observation 1: At first I thought that it was related to dash-to dock since moving the mouse to the area where I used to have the dock exhibits the flicker (I had moved it to bottom for GNOME 40). But it turns out that it doesn't matter: I can turn off the extension completely or move it back to the left and the flicker always occurs. Observation 2: I doesn't happen without any window onscreen. Having a program minimized to the dock doesn't suffice to exhibit the bug. I have to bring up the window and then it shows. Fun Fact 1: "Files" exhibits it more "aggresive" than "Terminal". Observation 3: I cannot record the issue: Recording a screencast via "Ctrl-Alt-Shift-R" doesn't work. When recording the screencast the issue doesn't happen. I am a bit lost further debugging this, any help is highly welcome. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mutter 40.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 23:03:53 2021 InstallationDate: Installed on 2018-02-23 (1293 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1943083 Title: screen flashes black (mouse pointer stays visible) when moving mouse pointer to the left edge of the screen Status in mutter package in Ubuntu: New Bug description: I reported that against mutter, but it can be gnome-shell as well. Or Intel driver/Kernel related. It happens since I switched to Impish, never saw that before. Intel HD graphics 400 onboard. STEPS to reproduce: 1) Move Mouse pointer to the left edge of the screen 2) See that everything works as expected 3) Start an app so that the window comes up, eg. "Files" 4) Move the Mouse pointer to the left edge again. 5) See that the Screen goes black for a second, but the mouse pointer stays visible. Observation 1: At first I thought that it was related to dash-to dock since moving the mouse to the area where I used to have the dock exhibits the flicker (I had moved it to bottom for GNOME 40). But it turns out that it doesn't matter: I can turn off the extension completely or move it back to the left and the flicker always occurs. Observation 2: I doesn't happen without any window onscreen. Having a program minimized to the dock doesn't suffice to exhibit the bug. I have to bring up the window and then it shows. Fun Fact 1: "Files" exhibits it more "aggresive" than "Terminal". Observation 3: I cannot record the issue: Recording a screencast via "Ctrl-Alt-Shift-R" doesn't work. When recording the screencast the issue doesn't happen. I am a bit lost further debugging this, any help is highly welcome. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mutter 40.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 23:03:53 2021 InstallationDate: Installed on 2018-02-23 (1293 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1943083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918874] Re: [regression] Application windows appear over the icon grid when Ubuntu Dock or Dash To Dock is loaded
I think the input thread code is more worthwhile than keeping the self- proclaimed "kinda hackish" code untouched. -- 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/1918874 Title: [regression] Application windows appear over the icon grid when Ubuntu Dock or Dash To Dock is loaded Status in mutter package in Ubuntu: In Progress Bug description: Click on 'Show Applications' the icons of the applications appear but the windows of the applications does not disappear so the icons are hidden. problem happens with both sessions Xorg and Wayland after last updates see attached picture ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 12 07:36:41 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1288, 663)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-02-28 (11 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920973] Re: open windows show in app grid
** Description changed: Showing the app grid doesn't overlay any open app window. So the window stays visible even if it should be hidden. - Hirsute, updated on March 23rd. + Hirsute, up to date (March 23rd). + + Steps to reproduce: + *Start gnome-terminal + *Click on the 9-Dot icon in the bottom left corner + *See the app grid coming app + *Notice that the gnome-terminal window stays visible, when it should be overlaid by the app grid. + + I think that happens since the latest gnome-shell update. It was fine + before that. ** Description changed: Showing the app grid doesn't overlay any open app window. So the window stays visible even if it should be hidden. Hirsute, up to date (March 23rd). Steps to reproduce: *Start gnome-terminal *Click on the 9-Dot icon in the bottom left corner - *See the app grid coming app + *See the app grid coming up *Notice that the gnome-terminal window stays visible, when it should be overlaid by the app grid. I think that happens since the latest gnome-shell update. It was fine before that. -- 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/1920973 Title: open windows show in app grid Status in gnome-shell package in Ubuntu: New Bug description: Showing the app grid doesn't overlay any open app window. So the window stays visible even if it should be hidden. Hirsute, up to date (March 23rd). Steps to reproduce: *Start gnome-terminal *Click on the 9-Dot icon in the bottom left corner *See the app grid coming up *Notice that the gnome-terminal window stays visible, when it should be overlaid by the app grid. I think that happens since the latest gnome-shell update. It was fine before that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920973] [NEW] open windows show in app grid
Public bug reported: Showing the app grid doesn't overlay any open app window. So the window stays visible even if it should be hidden. Hirsute, up to date (March 23rd). Steps to reproduce: *Start gnome-terminal *Click on the 9-Dot icon in the bottom left corner *See the app grid coming app *Notice that the gnome-terminal window stays visible, when it should be overlaid by the app grid. I think that happens since the latest gnome-shell update. It was fine before that. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1920973 Title: open windows show in app grid Status in gnome-shell package in Ubuntu: New Bug description: Showing the app grid doesn't overlay any open app window. So the window stays visible even if it should be hidden. Hirsute, up to date (March 23rd). Steps to reproduce: *Start gnome-terminal *Click on the 9-Dot icon in the bottom left corner *See the app grid coming app *Notice that the gnome-terminal window stays visible, when it should be overlaid by the app grid. I think that happens since the latest gnome-shell update. It was fine before that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
Why can't you just move on? What is your stupid agenda? -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819779] Re: Stick to the 3.30 serie still?
Is there a bug for the Debian side of things? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1819779 Title: Stick to the 3.30 serie still? Status in gnome-software package in Ubuntu: Triaged Bug description: The new serie/version is having stability issues (see bug #1817223 for example, which means we got no testing of the refactoring at this point) and we don't have the resources to deal with the fallout. There are also no change in the NEWS that we consider essential to get this cycle (backporting the new icon/appmenu change might be worth doing though) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1819779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842910] Re: Desktop right click menu appears in the wrong place if a Terminal window is open
Hmm. At least in the Ubuntu-wayland session I cannot reproduce that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1842910 Title: Desktop right click menu appears in the wrong place if a Terminal window is open Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Status in gnome-shell source package in Eoan: New Status in gnome-shell-extension-desktop-icons source package in Eoan: New Bug description: Desktop right click menu appears in the wrong place if a Terminal window is open. 1. Open a Terminal 2. Right click on the desktop. Expected: The menu appears where you click. Observed: The menu appears near the Terminal window instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.3+git20190814.1-1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Thu Sep 5 18:26:24 2019 InstallationDate: Installed on 2019-05-02 (126 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1842910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme
Hmm. Personally I prefer Colibre as I find it to be the most professional icon theme for LibreOffice. But if the Yaru team feels that Breeze fits Yaru better, then go for it. And please test the themes with the shiny new tabbed layout interface because that will be the one people will switch to over time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1827948 Title: Use libreoffice-style-breeze as the default icon theme Status in libreoffice package in Ubuntu: New Bug description: The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. So do the breeze icons for libreoffice. All in all does the breeze icon set for libre office fit very good to the look of the Yaru icons. https://i.imgur.com/tgioycv.png https://i.imgur.com/WwKvjMh.png Thus I would suggest to use it as the default icon set in Ubuntu to guarantee a consistent look and feel across the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
Adwaita? What about Yaru? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install
As Sebastien Bacher pointed out, ImageMagick can be removed for good now as CUPS does no longer depend on it in Disco. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819503] Re: Drop imagemagick-display from the default install [disco regression]
** Description changed: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 - Since the update to Disco the unprofessional and childish ImageMagick - icon is back. It was removed in Artful, Bionic and Cosmic for the - following reasons, perfectly summed up by Jeremy Bicha (a copy and paste - from Bug #171951): + Since the update to Disco the unprofessional ImageMagick icon is back. + It was removed in Artful, Bionic and Cosmic for the following reasons, + perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): + + I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session + and it it returned in all three instances. Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) ** Description changed: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 - Since the update to Disco the unprofessional ImageMagick icon is back. - It was removed in Artful, Bionic and Cosmic for the following reasons, - perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): - I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session - and it it returned in all three instances. + I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session and the bug is visible in all three instances. + + Since the update to Disco the rather unprofessional ImageMagick icon is + back. It was removed in Artful, Bionic and Cosmic for the following + reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug + #171951): + Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1819503 Title: Drop imagemagick-display from the default install [disco regression] Status in ubuntu-settings package in Ubuntu: New Bug description: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session and the bug is visible in all three instances. Since the update to Disco the rather unprofessional ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual,
[Desktop-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install
Filed https://bugs.launchpad.net/ubuntu/+source/ubuntu- settings/+bug/1819503 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819503] Re: Drop imagemagick-display from the default install [disco regression]
** Summary changed: - Drop imagemagick-display from the default install [regression] + Drop imagemagick-display from the default install [disco regression] ** Description changed: - This is actually a regression from - https://bugs.launchpad.net/bugs/1717951 + This is actually a regression in Disco from Artful, Bionic and Cosmic, + where this was fixed in https://bugs.launchpad.net/bugs/1717951 Since the update to Disco the unprofessional and childish ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1819503 Title: Drop imagemagick-display from the default install [disco regression] Status in ubuntu-settings package in Ubuntu: New Bug description: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session and the bug is visible in all three instances. Since the update to Disco the rather unprofessional ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1819503/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819503] [NEW] Drop imagemagick-display from the default install [disco regression]
Public bug reported: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 Since the update to Disco the unprofessional and childish ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1819503 Title: Drop imagemagick-display from the default install [disco regression] Status in ubuntu-settings package in Ubuntu: New Bug description: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 Since the update to Disco the unprofessional and childish ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1819503/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install
Hmm. I upgraded to Disco today and the icon is back. Is that expected? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796548] Re: [regression] New windows are all centred
I really liked the previous behavior. I think that this was changed by did rocks and suugested by me. What makes it "annoying"? I find th upstream behavior annoying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1796548 Title: [regression] New windows are all centred Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: In a fresh cosmic installation new windows all appear in the same place; the middle of the screen. This makes opening multiple windows annoying. WORKAROUND: Gnome Tweaks > Windows > Center New Windows = OFF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1796548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from
Benjamin, out of interest: Do you see the crash with both sessions? X and waylan? -- 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/1748450 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in mutter source package in Bionic: Fix Released Bug description: [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive after Xwayland has reset itself. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence the Xwayland bugs are irrelevant. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. Just don't mark them as duplicates of each other because they are all still collecting duplicates of their own. - *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from
Wayland of course. Just suggesting that switching to Wayland might fix your problem. -- 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/1748450 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in mutter source package in Bionic: Fix Released Bug description: [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive after Xwayland has reset itself. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence the Xwayland bugs are irrelevant. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. Just don't mark them as duplicates of each other because they are all still collecting duplicates of their own. - *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799222] Re: libreoffice crashes reliably on startup (and the recovery window comes up)
As a workaround: The current stable snap is on 6.1.2.1 and works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1799222 Title: libreoffice crashes reliably on startup (and the recovery window comes up) Status in libreoffice package in Ubuntu: New Bug description: My ubuntu is pretty stock. I recently upgraded to nautilus 3.30 from the GNOME3 Staging PPA and installed the Dektop Icons extension but that seems rather unprobable to be related. A few days ago (maybe two weeks) LibreOffice worked as expected. But that could have been version 6.1.1, I don't know for sure if 6.1.2 ever worked for me. To get the crash errors below I had to set the --norestore flag, otherwise an endless chain of file recovery windows are shown Purging all libreoffice debs and re-installing the libreoffice metapackage wasn't successful, the crash remained. amano@amano-desktop:~$ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3cfb3)[0x7f0a82c03fb3] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d1c3)[0x7f0a82c041c3] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f0a829fe100] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f0a829fe077] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f0a829df535] /usr/lib/libreoffice/program/libmergedlo.so(+0x11ee372)[0x7f0a83e12372] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0x90)[0x7f0a85a5cfe0] /usr/lib/libreoffice/program/libmergedlo.so(+0x1efdc57)[0x7f0a84b21c57] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3e59b)[0x7f0a85a6259b] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x17202)[0x7f0a82bde202] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d08f)[0x7f0a82c0408f] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f0a829fe100] /lib/x86_64-linux-gnu/libc.so.6(+0xad116)[0x7f0a82a6a116] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f0a817c55a4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2eb899f)[0x7f0a85adc99f] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9996)[0x7f0a817ba996] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9ba8)[0x7f0a817baba8] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f0a81780203] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8fad6)[0x7f0a81780ad6] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc1812)[0x7f0a817b2812] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f0a81780203] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f239)[0x7f0a81780239] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f0a815cdae8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ded8)[0x7f0a815cded8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f0a815cdf6c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x89973)[0x7f0a769a8973] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f0a85a5d4be] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f0a85a5ec35] /usr/lib/libreoffice/program/libmergedlo.so(+0x1f035b6)[0x7f0a84b275b6] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3fd26)[0x7f0a85a63d26] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f0a85a63e20] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7f0a84b43c61] /usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x55a4c0b8e07b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f0a829e109b] /usr/lib/libreoffice/program/soffice.bin(+0x10ba)[0x55a4c0b8e0ba] ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice 1:6.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 15:18:05 2018 InstallationDate: Installed on 2018-02-23 (240 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: libreoffice UpgradeStatus: Upgraded to cosmic on 2018-09-02 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799222] Re: libreoffice crashes reliably on startup (and the recovery window comes up)
** Summary changed: - libreoffice crashes reliably on startup (and the recovery console comes up) + libreoffice crashes reliably on startup (and the recovery window comes up) ** Description changed: - My ubuntu is pretty stock. I recently upgraded to nautilus 3.30 from the + My ubuntu is pretty stock. It crashes reliably wihtin the X session and + the Wayland session. I recently upgraded to nautilus 3.30 from the GNOME3 Staging PPA and installed the Dektop Icons extension but that - seems rather unprobably as the root case. + seems rather unprobable as the root case. A few days ago (maybe two weeks) LibreOffice worked as expected. - Now there is this crash (I have to use the --norestore flag, otherwise - an endless chain of file recovery windows are shown): + For that crash I have to set the --norestore flag, otherwise an endless + chain of file recovery windows are shown and I get no output amano@amano-desktop:~$ libreoffice --norestore Application Error - Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3cfb3)[0x7f0a82c03fb3] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d1c3)[0x7f0a82c041c3] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f0a829fe100] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f0a829fe077] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f0a829df535] /usr/lib/libreoffice/program/libmergedlo.so(+0x11ee372)[0x7f0a83e12372] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0x90)[0x7f0a85a5cfe0] /usr/lib/libreoffice/program/libmergedlo.so(+0x1efdc57)[0x7f0a84b21c57] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3e59b)[0x7f0a85a6259b] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x17202)[0x7f0a82bde202] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d08f)[0x7f0a82c0408f] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f0a829fe100] /lib/x86_64-linux-gnu/libc.so.6(+0xad116)[0x7f0a82a6a116] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f0a817c55a4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2eb899f)[0x7f0a85adc99f] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9996)[0x7f0a817ba996] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9ba8)[0x7f0a817baba8] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f0a81780203] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8fad6)[0x7f0a81780ad6] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc1812)[0x7f0a817b2812] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f0a81780203] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f239)[0x7f0a81780239] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f0a815cdae8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ded8)[0x7f0a815cded8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f0a815cdf6c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x89973)[0x7f0a769a8973] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f0a85a5d4be] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f0a85a5ec35] /usr/lib/libreoffice/program/libmergedlo.so(+0x1f035b6)[0x7f0a84b275b6] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3fd26)[0x7f0a85a63d26] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f0a85a63e20] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7f0a84b43c61] /usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x55a4c0b8e07b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f0a829e109b] /usr/lib/libreoffice/program/soffice.bin(+0x10ba)[0x55a4c0b8e0ba] ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice 1:6.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 15:18:05 2018 InstallationDate: Installed on 2018-02-23 (240 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: libreoffice UpgradeStatus: Upgraded to cosmic on 2018-09-02 (49 days ago) ** Description changed: - My ubuntu is pretty stock. It crashes reliably wihtin the X session and - the Wayland session. I recently upgraded to nautilus 3.30 from the + My ubuntu is pretty stock. I recently upgraded to nautilus 3.30 from the GNOME3 Staging PPA and installed the Dektop Icons extension but that - seems rather unprobable as the root case. + seems rather unprobable to be related. - A few days ago (maybe two weeks) LibreOffice worked as expected. + A few days ago (maybe two weeks) LibreOffice worked as expected. But + that could have been version 6.1.1, I don't know for sure if 6.1.2 ever + worked for me. - For that crash I have to set the --norestore flag, otherwise an endless - chain of file recovery windows are shown and I get no outpu
[Desktop-packages] [Bug 1799222] [NEW] libreoffice crashes reliably on startup (and the recovery console comes up)
Public bug reported: My ubuntu is pretty stock. I recently upgraded to nautilus 3.30 from the GNOME3 Staging PPA and installed the Dektop Icons extension but that seems rather unprobably as the root case. A few days ago (maybe two weeks) LibreOffice worked as expected. Now there is this crash (I have to use the --norestore flag, otherwise an endless chain of file recovery windows are shown): amano@amano-desktop:~$ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3cfb3)[0x7f0a82c03fb3] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d1c3)[0x7f0a82c041c3] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f0a829fe100] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f0a829fe077] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f0a829df535] /usr/lib/libreoffice/program/libmergedlo.so(+0x11ee372)[0x7f0a83e12372] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0x90)[0x7f0a85a5cfe0] /usr/lib/libreoffice/program/libmergedlo.so(+0x1efdc57)[0x7f0a84b21c57] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3e59b)[0x7f0a85a6259b] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x17202)[0x7f0a82bde202] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d08f)[0x7f0a82c0408f] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f0a829fe100] /lib/x86_64-linux-gnu/libc.so.6(+0xad116)[0x7f0a82a6a116] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f0a817c55a4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2eb899f)[0x7f0a85adc99f] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9996)[0x7f0a817ba996] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9ba8)[0x7f0a817baba8] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f0a81780203] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8fad6)[0x7f0a81780ad6] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc1812)[0x7f0a817b2812] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f0a81780203] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f239)[0x7f0a81780239] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f0a815cdae8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ded8)[0x7f0a815cded8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f0a815cdf6c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x89973)[0x7f0a769a8973] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f0a85a5d4be] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f0a85a5ec35] /usr/lib/libreoffice/program/libmergedlo.so(+0x1f035b6)[0x7f0a84b275b6] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3fd26)[0x7f0a85a63d26] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f0a85a63e20] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7f0a84b43c61] /usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x55a4c0b8e07b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f0a829e109b] /usr/lib/libreoffice/program/soffice.bin(+0x10ba)[0x55a4c0b8e0ba] ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice 1:6.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 15:18:05 2018 InstallationDate: Installed on 2018-02-23 (240 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: libreoffice UpgradeStatus: Upgraded to cosmic on 2018-09-02 (49 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1799222 Title: libreoffice crashes reliably on startup (and the recovery console comes up) Status in libreoffice package in Ubuntu: New Bug description: My ubuntu is pretty stock. I recently upgraded to nautilus 3.30 from the GNOME3 Staging PPA and installed the Dektop Icons extension but that seems rather unprobably as the root case. A few days ago (maybe two weeks) LibreOffice worked as expected. Now there is this crash (I have to use the --norestore flag, otherwise an endless chain of file recovery windows are shown): amano@amano-desktop:~$ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3cfb3)[0x7f0a82c03fb3] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d1c3)[0x7f0a82c041c3] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f0a829fe100] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f0a829fe077] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f0a829df535] /usr/lib/libreoffice/program/libmergedlo.so(+0x11ee372)[0x7f0a83e12372] /usr/lib/libreoffice/program/libm
[Desktop-packages] [Bug 1792356] Re: [ffe] Update to 1.4.3
https://ubuntuforums.org/showthread.php?t=2400138 Some experienced users from the Ubuntu forums see that journalctl collects plenty of colord entries garbage with colord 1.3.3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1792356 Title: [ffe] Update to 1.4.3 Status in colord package in Ubuntu: Triaged Bug description: Debian got the new version, it would be nice to have in cosmic now. Although the upgrade from our current 1.3.3 to 1.4.3 might seem a big jump, colord upstream does not see a lot of development activity; most changes here are bug fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1792356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
Nope. Not completely sure, sorry. I didn't compile GNOME apps before, so that would probably be a rather heavy task for me ;) I had a quick look at the 3.30.0 source but couldn't even find out which lines were changed by the Debian patch. Aren't the patches included within the source tar? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
https://4.bp.blogspot.com/-CKw5ikw4WNo/WWo7WrezseI/KC4/CPbs48OQj0A2hMNY5_Ivu6iTaRzClDYMQCLcBGAs/s1600/07%2BGNOME%2BTerminal.jpg This is a gnome-terminal screenshot from Fedora 26. There everything seems ok. Can we drop the Debian patch above to see if that fixes the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
Is this an upstream issue (does Fedora show that behavior as well?) or the outcome of a Debian patch? There is at least one which is scrollbar related: + Add scrollbar-background-theming.patch: - Draw background under the scrollbar that matches the actual terminal background color. This allows proper theming. https://lists.canonical.com/archives/cosmic- changes/2018-September/009594.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754169] Re: [Bionic] [wayland] many gnome applications exit or crash when a file is opened
Is that a Mutter or Gnome-shell regression? Is it going to be fixed upstream? It seems that some (XDG?-) handover between some gnome apps doesn't work as expected and both apps have to exit. ** Summary changed: - [Bionic] [wayland] many gnome applications exit or crash when a file is opened + [Bionic] [wayland] many gnome applications exit or crash when a file is opened from within ** Description changed: See title. Make sure that your are on the ubuntu-wayland session. ==Steps to reproduce for Nautilus== 0) From the log in screen, click your name, then click the gear button and select Ubuntu on Wayland. Log in. 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile or an archive (eg. /home/user/.thunderbird ) 3) Right click a textfile or an archive (eg. profiles.ini) 4) Choose gedit or File Roller from the list, click ok. 5) Nautilus crashes, gedit or File Roller don't come up Another observation: This problem is not limited to Nautilus. Thus going back to Nautilus 3.26.0 will not help. ==Steps to reproduce for other apps (via opening yelp files)== 1) Open nautilus 2) click on the nautilus entry in the top bar (left of "activities". 3) Select "Help" 4) nautilus exits, yelp doesn't come up 5) open polari 6) click on the "Polari" entry in the top bar (left of acitivies. 7) Select "Help" 8) See polari crash 9) Open gnome-control-center 10) See that gnome-control-center will exit/crash, see that yelp doesn't come up + ==Affected applications== Not all applications crash. Most applications don't offer the possibility to open yelp from the top bar. So those are not mentioned in the list below: - 1) Deja Dup, Gnome control center, Nautilus, Polari, Gnome-Disks, Gnome-Photos, gEdit and gnome-logs will crash - 2) Gnome Terminal, Rhythmbox, Gnome-Sudoku, Cheese, Gthumb, Gnome-Mahjongg, Gnome-Mines, Simple-Scan, Gnome-Calculator and Gnome-Clocks, File Roller, gnome-screenshot, baobab, gnome-system-monitor and Totem will not. + + * Deja Dup, Gnome control center, Nautilus, Polari, Gnome-Disks, Gnome- + Photos, gEdit and gnome-logs will crash + + * Gnome Terminal, Rhythmbox, Gnome-Sudoku, Cheese, Gthumb, Gnome- + Mahjongg, Gnome-Mines, Simple-Scan, Gnome-Calculator and Gnome-Clocks, + File Roller, gnome-screenshot, baobab, gnome-system-monitor and Totem + will not. ==Expected result== The gnome app doesn't crash, gEdit, Yelp or File Roller come up and let you view the file ==The reason I initially thought it was a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ==The reason I initially thought it was a nautilus regression== Not only opening gedit causes a crash but also opening an archive with File Roller. ==Conclusion= Is that a Mutter or Gnome-shell regression? Is it going to be fixed upstream? It seems that some (XDG?-) handover between some gnome apps doesn't work as expected and both apps have to exit. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Also affects: polari (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-logs (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-photos (Ubuntu) Importance: Undecided Status: New ** Description changed: See title. Make sure that your are on the ubuntu-wayland session. ==Steps to reproduce for Nautilus== 0) From the log in screen, click your name, then click the gear button and select Ubuntu on Wayland. Log in. 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile or an archive (eg. /home/user/.thunderbird ) 3) Right click a textfile or an archive (eg. profiles.ini) 4) Choose gedit or File Roller from the list, click ok. 5) Nautilus crashes, gedit or File Roller don't come up Another observation: This problem is not limited to Nautilus. Thus going back to Nautilus 3.26.0 will not help. ==Steps to reproduce for other apps (via opening yelp files)== 1) Open nautilus - 2) click on the nautilus entry in the top bar (left of "activities". + 2) click on the nautilus entry in the top bar (right of "Activities". 3) Select "Help" 4) nautilus exits, yelp doesn't come up 5) open polari - 6) click
[Desktop-packages] [Bug 1754169] Re: [Bionic] [wayland] Nautilus crashes when a file is opened
Another observation: This problem is not limited to Nautilus. Thus going back to Nautilus 3.26.0 will not help. ==Steps to reproduce for other apps== 1) Open nautilus 2) click on the nautilus entry in the top bar (left of "activities". 3) Select "Help" 4) nautilus exits, yelp doesn't come up 5) open polari 6) click on the "Polari" entry in the top bar (left of acitivies. 7) Select "Help" 8) See polari crash 9) Open gnome-control-center 10) See that gnome-control-center will exit/crash, see that yelp doesn't come up Not all applications crash. Most applications don't offer the possibility to open yelp from the top bar. So those are not mentioned in the list below: 1) Deja Dup, Gnome control center, Nautilus, Polari, Gnome-Disks, Gnome-Photos, gEdit and gnome-logs will crash 2) Gnome Terminal, Rhythmbox, Gnome-Sudoku, Cheese, Gthumb, Gnome-Mahjongg, Gnome-Mines, Simple-Scan, Gnome-Calculator and Gnome-Clocks, File Roller, gnome-screenshot, baobab, gnome-system-monitor and Totem will not. ** Description changed: - See title. + See title. Make sure that your are on the ubuntu-wayland session. - ==Steps to reproduce== + ==Steps to reproduce for Nautilus== 0) From the log in screen, click your name, then click the gear button and select Ubuntu on Wayland. Log in. 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile or an archive (eg. /home/user/.thunderbird ) 3) Right click a textfile or an archive (eg. profiles.ini) 4) Choose gedit or File Roller from the list, click ok. 5) Nautilus crashes, gedit or File Roller don't come up + Another observation: This problem is not limited to Nautilus. Thus going + back to Nautilus 3.26.0 will not help. + + ==Steps to reproduce for other apps== + + 1) Open nautilus + 2) click on the nautilus entry in the top bar (left of "activities". + 3) Select "Help" + 4) nautilus exits, yelp doesn't come up + 5) open polari + 6) click on the "Polari" entry in the top bar (left of acitivies. + 7) Select "Help" + 8) See polari crash + 9) Open gnome-control-center + 10) See that gnome-control-center will exit/crash, see that yelp doesn't come up + + Not all applications crash. Most applications don't offer the possibility to open yelp from the top bar. So those are not mentioned in the list below: + 1) Deja Dup, Gnome control center, Nautilus, Polari, Gnome-Disks, Gnome-Photos, gEdit and gnome-logs will crash + 2) Gnome Terminal, Rhythmbox, Gnome-Sudoku, Cheese, Gthumb, Gnome-Mahjongg, Gnome-Mines, Simple-Scan, Gnome-Calculator and Gnome-Clocks, File Roller, gnome-screenshot, baobab, gnome-system-monitor and Totem will not. + ==Expected result== - Nautilus doesn't crash, gedit or File Roller come up and let you view the file + The gnome app doesn't crash, gEdit, Yelp or File Roller come up and let you view the file ==The reason I initially thought it was a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ==Why certainly a Nautilus regression== Not only opening gedit causes a crash but also opening an archive with File Roller. - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: See title. Make sure that your are on the ubuntu-wayland session. ==Steps to reproduce for Nautilus== 0) From the log in screen, click your name, then click the gear button and select Ubuntu on Wayland. Log in. 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile or an archive (eg. /home/user/.thunderbird ) 3) Right click a textfile or an archive (eg. profiles.ini) 4) Choose gedit or File Roller from the list, click ok. 5) Nautilus crashes, gedit or File Roller don't come up Another observation: This problem is not limited to Nautilus. Thus going back to Nautilus 3.26.0 will not help. - ==Steps to reproduce for other apps== - + ==Steps to reproduce for other apps (via opening yelp files)== 1) Open nautilus 2) click on the nautilus entry in the top bar (left of "activities". 3) Select "Help" 4) nautilus exits, yelp doesn't come up 5) open polari 6) click on the "Polari" entry in the top bar (left of acitivies. 7) Select "Help" 8) See polari crash 9) Open gnome-control-center 10) See that gnome-control-center will exit/crash, see that yelp doesn't come up Not all applications crash. Most applications don't offer the possibility to open yelp from the top bar. So those are
[Desktop-packages] [Bug 1754169] Re: [Bionic] [wayland] Nautilus crashes when a file is opened
Even opening archives with File Roller makes Nautilus 3.26.2 crash. So it cannot be a gedit problem. I edited the title to reflect that. So all gnome apps make Nautilus crash (in fact opening the file makes Nautilus and the other program crash) while LibreOffice obviously doensn't. What makes opening a file with LibreOffice different. I wonder if reverting to 3.26.0 would be a good idea? It potentially resolves the problem and the stable branch doesn't add anything too interesting to Nautilus 3.26. If the problem persists another package update probably causes the problem. So we know at least... -- 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/1754169 Title: [Bionic] [wayland] Nautilus crashes when a file is opened Status in gedit package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: See title. ==Steps to reproduce== 0) From the log in screen, click your name, then click the gear button and select Ubuntu on Wayland. Log in. 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile or an archive (eg. /home/user/.thunderbird ) 3) Right click a textfile or an archive (eg. profiles.ini) 4) Choose gedit or File Roller from the list, click ok. 5) Nautilus crashes, gedit or File Roller don't come up ==Expected result== Nautilus doesn't crash, gedit or File Roller come up and let you view the file ==The reason I initially thought it was a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ==Why certainly a Nautilus regression== Not only opening gedit causes a crash but also opening an archive with File Roller. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754169] Re: [Bionic] [wayland] Nautilus crashes when a file is opened
** Summary changed: - [Bionic] [wayland] Nautilus crashes when a file is opened with gedit + [Bionic] [wayland] Nautilus crashes when a file is opened ** Description changed: See title. ==Steps to reproduce== 0) From the log in screen, click your name, then click the gear button and select Ubuntu on Wayland. Log in. 1) Open nautilus (currently 3.26.2 in bionic) - 2) Browse to a location with a textfile (eg. /home/user/.thunderbird ) - 3) Right click a textfile (eg. profiles.ini) - 4) Choose gedit from the list (probably default), click ok. - 5) Nautilus crashes, gedit doesn't come up + 2) Browse to a location with a textfile or an archive (eg. /home/user/.thunderbird ) + 3) Right click a textfile or an archive (eg. profiles.ini) + 4) Choose gedit or File Roller from the list, click ok. + 5) Nautilus crashes, gedit or File Roller don't come up ==Expected result== - Nautilus doesn't crash, gedit comes up and lets you edit the file + Nautilus doesn't crash, gedit or File Roller come up and let you view the file - ==Why (probably) a gedit regression== + ==The reason I initially thought it was a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. + + ==Why certainly a Nautilus regression== + Not only opening gedit causes a crash but also opening an archive with File Roller. + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1754169 Title: [Bionic] [wayland] Nautilus crashes when a file is opened Status in gedit package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: See title. ==Steps to reproduce== 0) From the log in screen, click your name, then click the gear button and select Ubuntu on Wayland. Log in. 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile or an archive (eg. /home/user/.thunderbird ) 3) Right click a textfile or an archive (eg. profiles.ini) 4) Choose gedit or File Roller from the list, click ok. 5) Nautilus crashes, gedit or File Roller don't come up ==Expected result== Nautilus doesn't crash, gedit or File Roller come up and let you view the file ==The reason I initially thought it was a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ==Why certainly a Nautilus regression== Not only opening gedit causes a crash but also opening an archive with File Roller. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754169] Re: [Bionic] [wayland] Nautilus crashes when a file is opened with gedit
It just happens in the Ubuntu-Wayland session. It doesn't happen in the default Ubuntu session. Added the wayland tag. -- 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/1754169 Title: [Bionic] [wayland] Nautilus crashes when a file is opened with gedit Status in gedit package in Ubuntu: Invalid Status in nautilus package in Ubuntu: New Bug description: See title. ==Steps to reproduce== 0) From the log in screen, click your name, then click the gear button and select Ubuntu on Wayland. Log in. 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile (eg. /home/user/.thunderbird ) 3) Right click a textfile (eg. profiles.ini) 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754169] Re: [Bionic] Nautilus crashes when a file is opened with gedit
** Description changed: See title. ==Steps to reproduce== 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile (eg. /home/user/.thunderbird ) - 3) Right click a textfile (eg. profiles.ini + 3) Right click a textfile (eg. profiles.ini) 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1754169 Title: [Bionic] Nautilus crashes when a file is opened with gedit Status in gedit package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: See title. ==Steps to reproduce== 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile (eg. /home/user/.thunderbird ) 3) Right click a textfile (eg. profiles.ini) 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754169] [NEW] [Bionic] Nautilus crashes when a file is opened with gedit
Public bug reported: See title. ==Steps to reproduce== 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile (eg. /home/user/.thunderbird ) 3) Right click a textfile (eg. profiles.ini) 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session ** Summary changed: - Nautilus crashes when a file is being opened with gedit when right-clicking it + [Bionic] Nautilus 3.27.92 crashes when a file is being opened with gedit when right-clicking it ** Summary changed: - [Bionic] Nautilus 3.27.92 crashes when a file is being opened with gedit when right-clicking it + [Bionic] Nautilus 3.27.92 crashes when a file is opened with gedit by right-clicking it ** Description changed: See title. ==Steps to reproduce== - 1) Open nautilus + 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse a location with a textfile (eg. /home/user/.thunderbird 3) Right click a textfile (eg. profiles.ini 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: See title. ==Steps to reproduce== 1) Open nautilus (currently 3.26.2 in bionic) - 2) Browse a location with a textfile (eg. /home/user/.thunderbird + 2) Browse a location with a textfile (eg. /home/user/.thunderbird ) 3) Right click a textfile (eg. profiles.ini 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: See title. ==Steps to reproduce== 1) Open nautilus (currently 3.26.2 in bionic) - 2) Browse a location with a textfile (eg. /home/user/.thunderbird ) + 2) Browse to a location with a textfile (eg. /home/user/.thunderbird ) 3) Right click a textfile (eg. profiles.ini 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 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: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago)
[Desktop-packages] [Bug 1740743] Re: Hide imagemagick's Display app from GNOME software
** Summary changed: - * Hide imagemagick's Display app from GNOME software + Hide imagemagick's Display app from GNOME software ** Summary changed: - Hide imagemagick's Display app from GNOME software + Hide Imagemagick's Display app from GNOME software -- 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/1740743 Title: Hide Imagemagick's Display app from GNOME software Status in gnome-software package in Ubuntu: New Bug description: In bug #1717951 Imagemagick was already removed from being displayed in GNOME-Shell. It is still listed in GNOME-Software which causes some (potential) usability issues: Users can still test the "imagemagick" app from within Ubuntu Software and decide to remove it from there. Because that app looks dated, ugly and out of place in a modern desktop environment. Removing Imagemagick has the bad side-effect of removing printing support while user won't even realize that Imagemagick was printing related at all. Thus I propose to remove the app from being listed as installed in Ubuntu Software at all. Or to be moved to the "System Apps" section to prevent users from removing it manually (and unvoluntarily CUPS with it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1740743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740743] [NEW] Hide Imagemagick's Display app from GNOME software
Public bug reported: In bug #1717951 Imagemagick was already removed from being displayed in GNOME-Shell. It is still listed in GNOME-Software which causes some (potential) usability issues: Users can still test the "imagemagick" app from within Ubuntu Software and decide to remove it from there. Because that app looks dated, ugly and out of place in a modern desktop environment. Removing Imagemagick has the bad side-effect of removing printing support while user won't even realize that Imagemagick was printing related at all. Thus I propose to remove the app from being listed as installed in Ubuntu Software at all. Or to be moved to the "System Apps" section to prevent users from removing it manually (and unvoluntarily CUPS with it). ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1740743 Title: Hide Imagemagick's Display app from GNOME software Status in gnome-software package in Ubuntu: New Bug description: In bug #1717951 Imagemagick was already removed from being displayed in GNOME-Shell. It is still listed in GNOME-Software which causes some (potential) usability issues: Users can still test the "imagemagick" app from within Ubuntu Software and decide to remove it from there. Because that app looks dated, ugly and out of place in a modern desktop environment. Removing Imagemagick has the bad side-effect of removing printing support while user won't even realize that Imagemagick was printing related at all. Thus I propose to remove the app from being listed as installed in Ubuntu Software at all. Or to be moved to the "System Apps" section to prevent users from removing it manually (and unvoluntarily CUPS with it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1740743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740741] [NEW] * Hide imagemagick's Display app from the Ubuntu GNOME session as well
Public bug reported: Imagemagick's Display app was hidden from the default Ubuntu session for Artful (LP: #1717951), but was still visible if you chose the GNOME session instead. I propose to apply the same fix (for the same reasons given in Bug 1717951) to the GNOME session in Bionic. Link to bug 1717951: https://bugs.launchpad.net/ubuntu/+source/ubuntu- settings/+bug/1717951 ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1740741 Title: * Hide imagemagick's Display app from the Ubuntu GNOME session as well Status in ubuntu-settings package in Ubuntu: New Bug description: Imagemagick's Display app was hidden from the default Ubuntu session for Artful (LP: #1717951), but was still visible if you chose the GNOME session instead. I propose to apply the same fix (for the same reasons given in Bug 1717951) to the GNOME session in Bionic. Link to bug 1717951: https://bugs.launchpad.net/ubuntu/+source/ubuntu- settings/+bug/1717951 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1740741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723577] Re: No login screen (mutter silently goes headless) on some AMD GPUs
The nvidia user (me) can happily confirm that this bug is fixed now :) What a nastie: A mutter crash that leads to the startup of the X.org fallback session which can't be displayed due to a gnome-shell regression. Wow. No wonder that this was so hard to diagnose. And timely cropping up just before final freeze to keep the fun alive. -- 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/1723577 Title: No login screen (mutter silently goes headless) on some AMD GPUs Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)
So with this gnome-shell downgrade you can get past Plymouth into GDM reliably? I will try at home as well... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)
So with this gnome-shell downgrade you can get past Plymouth into GDM reliably? I will try at home as well... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723619 is (sadly) not my issue. It took again 4 tries to have GDM appearing :( Having me regress at the same time as the many ATI users seems too much of an incident. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)
amano@amano-desktop:~$ uname -r 4.14.0-rc5-lp1723619+revert So the revert there in the patched 4.14 kernel doesn't affect me :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artful won't start with Wayland activated (AMD?) Status in gdm3 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Incomplete Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723577] Re: Artfull won't start with wayland activated
Rather a GDM bug. I it doesn't get stuck on Plymouth, it starts up the “Ubuntu“ gnome-shell session reliably for me. ** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1723577 Title: Artfull won't start with wayland activated Status in gdm3 package in Ubuntu: Confirmed Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723577] Re: Artfull won't start with wayland activated
If I get past Plymouth and into GDM (I have to try 4 times to succeed), I can log into the “Ubuntu“ session reliably. So I think that this bug is rather a GDM one than a gnome-shell one. -- 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/1723577 Title: Artfull won't start with wayland activated Status in gdm3 package in Ubuntu: Confirmed Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723577] Re: Artfull won't start with wayland activated
For me it worked reliably the whole development cycle until the week leading up to the 7th of October. It is borked just for about a week now. On the 5th of October I remember it being fine, it was borked when starting Ubuntu up on the morning of October 7th. Now it seems like a dealbreaker worth debugging (if I knew where to start). -- 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/1723577 Title: Artfull won't start with wayland activated Status in gnome-shell package in Ubuntu: Confirmed Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723577] Re: Artfull won't start with wayland activated
Even after the updates of today (with the new kernel and the gnome-shell crash fix) the boot splash is getting stuck most of the time (certainly 3 out of 4 tries). Only switching to the nvidia 340 blob fixes that (then it boots reliably, not showing Plymouth at all). I don't think that it is a Plymouth bug, but GDM crashing when trying to bring up Wayland. Since it crashes that early I don't think that it is related to mutter or gnome-shell at all. Or does GDM use mutter these days? [S]Does apport leave a crash log in /var/crash/ with Ubuntu freezing or crashing that early?[/S] EDIT: Nope, no crash log in /var/crash/ at all :( A regression in X? In Mesa? -- 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/1723577 Title: Artfull won't start with wayland activated Status in gnome-shell package in Ubuntu: Confirmed Bug description: On a fresch install, ubuntu stop and freeze before gdm is opened With no splah i have "started user manager for uid 121" and then it freeze need to uncomment WaylandEnable=false in custom.conf to start ubuntu so with xorg. lspci -nn | grep VGA return 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 07:36:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install
While the visual side of this bug is fixed now (the ugly wizard-icon is gone from the launcher), the usability side is still alive: You can still test the "imagemagick" app from within Ubuntu Software and decide to remove it from there. With the ugly side-effect of removing printing support without even realizing that this is printing related at all. Jeremy, Ian, can you remove the app from being listed in Ubuntu Software as well? Or at least move it to the "System Apps" section to prevent useres to unvoluntarily remove CUPS? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714654] Re: random blackscreen of death when switching tabs in firefox
** Tags added: wayland -- 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/1714654 Title: random blackscreen of death when switching tabs in firefox Status in gnome-shell package in Ubuntu: New Bug description: full update. screen will suddenly blackout for a few seconds when switching tabs in firefox. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 2 05:30:59 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'com.canonical.launcher.amazon.desktop', 'gnome-control-center.desktop', 'htop.desktop', 'etr.desktop', 'org.gnome.Screenshot.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-06-13 (80 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170611) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712800] Re: FFe: gnome-shell 3.26
At least the first one should already be fixed with https://github.com/GNOME/mutter/commit/06d09890147b48bfa23f122ff86cf7fc43ff84f2 which made it to the master branch two days after 3.25.91. -- 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/1712800 Title: FFe: gnome-shell 3.26 Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Desktop Team wants to ship gnome-shell/mutter 3.26 with Ubuntu 17.10. The new version appears to improve responsiveness and has quite a few other improvements and tweaks. https://git.gnome.org/browse/gnome-shell/tree/NEWS https://git.gnome.org/browse/mutter/tree/NEWS armhf issue === The major blocker now is that gjs 1.49/mozjs52 is not working on armhf. See https://bugzilla.gnome.org/786578 If we can't find a fix to this problem, we may need to remove gjs (and rdpends) binaries from armhf. We didn't want to rush into doing this but discuss this more as a team first. One other option is to temporarily remove gjs 1.49 (and gnome-shell, gnome-sushi, polari) from artful-proposed. But since we do want to target mozjs52 for Ubuntu 17.10 for security support reasons, that's only a partial help. Mutter transition = mutter 3.26 has a soname bump but the only other rdepend, Budgie, is already confirmed as working with the new version. Packaging is available in the GNOME3 Staging PPA or https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2916/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1712800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712986] Re: clutter apps (e.g. totem, gnome-maps, pinpoint) colours are wrong (red/blue swapped) in Gnome Shell 3.25 Wayland
Probably fixed by https://github.com/GNOME/mutter/commit/06d09890147b48bfa23f122ff86cf7fc43ff84f2 which made it to the master branch two days after 3.25.91. -- 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/1712986 Title: clutter apps (e.g. totem, gnome-maps, pinpoint) colours are wrong (red/blue swapped) in Gnome Shell 3.25 Wayland Status in Clutter: Confirmed Status in clutter package in Ubuntu: New Status in clutter-gst-3.0 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: clutterautovideosink (e.g. totem) colours are wrong (red/blue swapped) in Gnome Shell 3.25 Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/clutter/+bug/1712986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1708569] Re: Installer on latest image fails to create a complete $HOME directory
** Tags added: wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1708569 Title: Installer on latest image fails to create a complete $HOME directory Status in gnome-session package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Test case: Use latest image (august 2 here Install, reboot Check contents of home folder Seen here: $ ls Desktop examples.desktop ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 3 22:07:38 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- InstallationDate: Installed on 2017-08-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170802) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1708569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705188] Re: GIMP color picker does not work in Wayland
The upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=780375 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1705188 Title: GIMP color picker does not work in Wayland Status in The Gimp: Confirmed Status in gimp package in Ubuntu: Confirmed Bug description: GIMP color picker does not work in Wayland, it returns just black. It seems a common problem for 'pick' function in Wayland: https://bugs.launchpad.net/ubuntu/+source/gpick/+bug/1704808 To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/1705188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650395] Re: Large grey border around gnome-terminal shadows when transparency is enabled (wayland)
Can someone confirm that this is fixed with the latest gnome-terminal update in artful? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1650395 Title: Large grey border around gnome-terminal shadows when transparency is enabled (wayland) Status in Ubuntu GNOME: Triaged Status in gnome-terminal package in Ubuntu: Triaged Bug description: I have found that after switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22, that there is a large strange grey border around the window: - Fullscreen_gnome-terminal_in_AO_no_strange_border.png - Fullscreen_gnome-terminal_window.png - gnome-terminal_in_AO_strange_border.png - gnome-terminal_window_strange_border.png But this only occurs when the window is not fullscreen, and when transparency is enabled. Turning transparency off immediately fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: LP-PPA-gnome3-team-gnome3-staging] 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 CurrentDesktop: GNOME Date: Thu Dec 15 21:29:17 2016 InstallationDate: Installed on 2016-05-15 (214 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-19 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296334] Re: Update to bug-fix release 3.0.2 in Trusty
Removing a song from the Play Queue removes it from the Library That sounds like a bummer. I think that 3.02 should go into the LTS, if possible, as it is a pure bugfix release Subscribing Sebastian Bacher, in case he doesn't know already about the minor release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1296334 Title: Update to bug-fix release 3.0.2 in Trusty Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Upstream has released 3.0.2 of Rhythmbox. This is just a bug-fix release - see the NEWS for the release. - https://github.com/GNOME/rhythmbox/commit/72b998294cba6af6d6a1b8077482a9df1c787ac4 Overview of changes in Rhythmbox 3.0.2 == * Assorted bug fixes Bugs fixed: 678938 - Selectable text for playing song interferes with dragging by toolbar 692485 - application hangs clicking on devices with undefined playlist_path 701598 - rhythmbox seems to always be compiled with --enable-uninstalled-build 705105 - Rhythmbox while playing disables automatic screen lock 707144 - Rhythmbox doesn't support itmss:// links 707525 - Last.fm radio stations can't be properly deleted 707618 - Trying to play a file missing on disk crashes rhythmbox in rb-player-gst.c:516 708084 - podcast: Local file name is not escaped 708201 - Core dumped when running on Wayland 708341 - Transfer to mass storage player hangs after last song 710493 - Gdk assertion failed: invalid cairo image surface format 710832 - Removing a song from the Play Queue removes it from the Library 711285 - Cannot play remote files (sftp/gvfs) in library 712237 - Rhythmbox segfaults on broken cover images 712699 - Take into account the size of header button for column width 715177 - running rhythmbox-client --play-uri file:///path/to/song with rhythmbox closed only starts the app, not the song 719514 - cairo crash on playback whenever coverart search plugin is enabled 719777 - data: Add audio/mp4 as a supported mime-type 720116 - app menu: standardize Help/About/Quit 720217 - If transfer to device fails with non-sanitized filename, try with sanitized one 720819 - header: vertically centralize the Not playing label 721550 - License text contains obsolete FSF postal address 721758 - Please add search by genre 722069 - Incorrect links to the website 722782 - link to Rhythmbox Home Page is invalid 723839 - audioscrobbler: Invalid path passed to g_settings_new_with_path() 724931 - rhythmbox crashed with SIGSEGV in rb_list_model_find() 725625 - Absolute Radio Stations Should No Longer Be Included as Default (not streaming outside of UK) 726167 - .linked class is set on toolbar buttons instead of their container Translation updates: - cs, courtesy of Marek Černocký - de, courtesy of Christian Kirbach - es, courtesy of Daniel Mustieles - fr, courtesy of Claude Paroz - gl, courtesy of Fran Dieguez - hu, courtesy of Gabor Kelemen - it, courtesy of Milo Casagrande - lt, courtesy of Aurimas Černius - pl, courtesy of Piotr Drąg - pt_BR, courtesy of Rafael Ferreira - pt, courtesy of Tiago S. - ru, courtesy of Yuri Myasoedov - sl, courtesy of Matej Urbančič - sr, courtesy of Мирослав Николић - sr@latin, courtesy of Miroslav Nikolić - zh_CN, courtesy of YunQiang Su As such, it is a perfect candidate to allow this in for an exception for Trusty given that we are still over a month away from release. I've confirmed that all current git patches included in Rhythmbox v3.0.1 in Trusty are included in this v3.0.2 release. Also I've confirmed that the Ubuntu specific patch work also works in v3.0.2 that is as follows: The debian/series file needs only contain the following entries - everything else in the v3.0.1 version can be removed from this file and the associated patches folder: 02_use_escaped_podcast_uri.patch 03_magnatune_partner.patch 05_hide_on_quit.patch 07_quicklists.patch 10_encoding_use_ubuntu_profiles.patch make-shuffle-repeat-proper-toggle-actions.patch restore-traditional-menubar.patch ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 16:54:24 2014 InstallationDate: Installed on 2014-02-22 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140220.1) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1296334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1296334] Re: Update to bug-fix release 3.0.2 in Trusty
If you are at it, you could consider if you want to update VLC as well. There has been an update to 2.1.3 at the end of February (Trusty ships 2.1.2): http://www.videolan.org/developers/vlc-branch/NEWS * Fix a crash with the simple volume widget * Fix a crash in the audio menu building * Fix encrypted DVD playback Those fixes sound like we would like to have them in the LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1296334 Title: Update to bug-fix release 3.0.2 in Trusty Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Upstream has released 3.0.2 of Rhythmbox. This is just a bug-fix release - see the NEWS for the release. - https://github.com/GNOME/rhythmbox/commit/72b998294cba6af6d6a1b8077482a9df1c787ac4 Overview of changes in Rhythmbox 3.0.2 == * Assorted bug fixes Bugs fixed: 678938 - Selectable text for playing song interferes with dragging by toolbar 692485 - application hangs clicking on devices with undefined playlist_path 701598 - rhythmbox seems to always be compiled with --enable-uninstalled-build 705105 - Rhythmbox while playing disables automatic screen lock 707144 - Rhythmbox doesn't support itmss:// links 707525 - Last.fm radio stations can't be properly deleted 707618 - Trying to play a file missing on disk crashes rhythmbox in rb-player-gst.c:516 708084 - podcast: Local file name is not escaped 708201 - Core dumped when running on Wayland 708341 - Transfer to mass storage player hangs after last song 710493 - Gdk assertion failed: invalid cairo image surface format 710832 - Removing a song from the Play Queue removes it from the Library 711285 - Cannot play remote files (sftp/gvfs) in library 712237 - Rhythmbox segfaults on broken cover images 712699 - Take into account the size of header button for column width 715177 - running rhythmbox-client --play-uri file:///path/to/song with rhythmbox closed only starts the app, not the song 719514 - cairo crash on playback whenever coverart search plugin is enabled 719777 - data: Add audio/mp4 as a supported mime-type 720116 - app menu: standardize Help/About/Quit 720217 - If transfer to device fails with non-sanitized filename, try with sanitized one 720819 - header: vertically centralize the Not playing label 721550 - License text contains obsolete FSF postal address 721758 - Please add search by genre 722069 - Incorrect links to the website 722782 - link to Rhythmbox Home Page is invalid 723839 - audioscrobbler: Invalid path passed to g_settings_new_with_path() 724931 - rhythmbox crashed with SIGSEGV in rb_list_model_find() 725625 - Absolute Radio Stations Should No Longer Be Included as Default (not streaming outside of UK) 726167 - .linked class is set on toolbar buttons instead of their container Translation updates: - cs, courtesy of Marek Černocký - de, courtesy of Christian Kirbach - es, courtesy of Daniel Mustieles - fr, courtesy of Claude Paroz - gl, courtesy of Fran Dieguez - hu, courtesy of Gabor Kelemen - it, courtesy of Milo Casagrande - lt, courtesy of Aurimas Černius - pl, courtesy of Piotr Drąg - pt_BR, courtesy of Rafael Ferreira - pt, courtesy of Tiago S. - ru, courtesy of Yuri Myasoedov - sl, courtesy of Matej Urbančič - sr, courtesy of Мирослав Николић - sr@latin, courtesy of Miroslav Nikolić - zh_CN, courtesy of YunQiang Su As such, it is a perfect candidate to allow this in for an exception for Trusty given that we are still over a month away from release. I've confirmed that all current git patches included in Rhythmbox v3.0.1 in Trusty are included in this v3.0.2 release. Also I've confirmed that the Ubuntu specific patch work also works in v3.0.2 that is as follows: The debian/series file needs only contain the following entries - everything else in the v3.0.1 version can be removed from this file and the associated patches folder: 02_use_escaped_podcast_uri.patch 03_magnatune_partner.patch 05_hide_on_quit.patch 07_quicklists.patch 10_encoding_use_ubuntu_profiles.patch make-shuffle-repeat-proper-toggle-actions.patch restore-traditional-menubar.patch ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 16:54:24 2014 InstallationDate: Installed on 2014-02-22 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140220.1) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 290150] Re: does not support lame mp3 gapless tag
I changed the package from gstreamer0.10 to gstreamer1.0 since 0.10 isn't getting developed anymore. I don't know if the combinantion of Rhythmbox 3.01 with gstreamer1.0 in Trusty will yield better results than the combination in Saucy since I haven't upgraded yet. ** Package changed: gstreamer0.10 (Ubuntu) = gstreamer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/290150 Title: does not support lame mp3 gapless tag Status in The GStreamer Multimedia Framework: Triaged Status in The Rhythmbox Music Management Application: New Bug description: Binary package hint: rhythmbox Rhythmbox claims to support gapless playback. It does for the most part, but on mp3's, it doesn't. This is due to the design of mp3 frames. Each frame is a predetermined length of time, and the last frame is no exception, which causes a small silence at the end of each song. LAME has a workaround for this: embed a tag that tells a decoder exactly how long the song should be. iTunes, iPod, and libgpod support this. Rhythmbox neither makes use of this tag in its normal playback, nor for syncing songs to an iPod. The bug is present in all versions of Rhythmbox, in all versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/290150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 862161] Re: check_gl_texture_size crashed with SIGSEGV in __libc_start_main()
Affects unity3D as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/862161 Title: check_gl_texture_size crashed with SIGSEGV in __libc_start_main() Status in “gnome-desktop3” package in Ubuntu: Confirmed Bug description: Bug occurs in Unity2D session.. no more information . last update/upgrade 20110929 at 11.00 am ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: libgnome-desktop-3-2 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Thu Sep 29 10:59:46 2011 ExecutablePath: /usr/lib/gnome-desktop3/check_gl_texture_size InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110808) ProcCmdline: /usr/lib/gnome-desktop3/check_gl_texture_size ProcEnviron: SegvAnalysis: Segfault happened at: 0x400872: mov0xe0(%rax),%esi PC (0x00400872) ok source 0xe0(%rax) (0x00e0) not located in a known VMA region (needed readable region)! destination %esi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-desktop3 StacktraceTop: ?? () __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () ?? () Title: check_gl_texture_size crashed with SIGSEGV in __libc_start_main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/862161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
