Re: [Bug 1943406] Re: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_winsys() from radeon_bo

Updated and tested. There is no crash at logout or restart Den tis 5 okt. 2021 kl 17:05 skrev Launchpad Bug Tracker < 1943...@bugs.launchpad.net>: > This bug was fixed in the package gnome-shell - 40.5-1ubuntu2 > > --- > gnome-shell (40.5-1ubuntu2) impish; urgency=medium > > [

[Bug 1943406] Re: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_winsys() from radeon_bo_ref

Now I get a problem that cannot be reported ** Attachment added: "Screenshot from 2021-09-28 16-27-45.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943406/+attachment/5528718/+files/Screenshot%20from%202021-09-28%2016-27-45.png -- You received this bug notification

[Bug 1923335] Re: At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works)

My Impish installation don't behave like that. At restart I see the spinner for about 4 sec, then black screen for about 12 sec until I see the "Asus logo" and a second later the grub menu. The only customization is some extensions: ArcMenu Just Perfection to move the panel to bottom of the

Re: [Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status

krev Brian Murray <1921...@bugs.launchpad.net >: > Hello Per-Inge, or anyone else affected, > > Accepted systemd into focal-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.7 in a few > hours, an

Re: [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path

Don't get the crash any longer. Den tors 22 apr. 2021 kl 16:41 skrev Launchpad Bug Tracker < 1820...@bugs.launchpad.net>: > This bug was fixed in the package nautilus - 1:3.38.2-1ubuntu2 > > --- > nautilus (1:3.38.2-1ubuntu2) hirsute; urgency=medium > > *

[Bug 1925464] [NEW] Cannot open /boot/efi

Public bug reported: Get this error message when trying to open /boot/efi "gdbus error freedesktop policykit1 error failed unix process subject does not have uuid set" ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu

[Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status

Didn't get the log message about rfkill after boot this morning. After update today I have systemd 247.3-3ubuntu3 installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921696 Title: Failed to

[Bug 1922234] [NEW] Grub doesn't update kernel version

Public bug reported: You have a dual boot with two Ubuntu versions installed, e.g lts version and development version. The kernel in the development version is updated. At reboot the development version will boot with the old kernel. To boot with the new kernel you first have to boot with the

[Bug 1921696] [NEW] Failed to start Load/Save RF Kill Switch Status

Public bug reported: When I boot the system I get these lög messages - Failed to start Load/Save RF Kill Switch Statu - A start job for unit systemd-rfkill.service has failed and with sender systemd-rfkil Read event structure of invalid size Also happens on an Ubuntu system on the same computer.

[Bug 1906294] Re: systemd-journal hang after chromium is closed

Has been fixed after updates. Probably one of these Start-Date: 2020-12-01 19:43:08 Commandline: aptdaemon role='role-commit-packages' sender=':1.241' Upgrade: xserver-common:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1), xserver-xorg-core:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1),

[Bug 1905946] Re: Mouse stop moving after few seconds. restart at click

I installed all the updates in proposed (main repository) and now have libfprint-2-2 1:1.90.3tod1-0ubuntu3 installed This fixed the problem on my computer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1906294] [NEW] systemd-journal hang after chromium is closed

Public bug reported: CPU usage after close of Chromium is 98,7% by systemd-jounal after these updates Start-Date: 2020-11-30 18:39:16 Commandline: packagekit role='update-packages' Upgrade: gir1.2-mutter-7:amd64 (3.38.1-1ubuntu1, 3.38.1-2ubuntu1), snapd:amd64 (2.47.1+20.10.1, 2.48+20.10),

[Bug 1905946] Re: Mouse stop moving after few seconds. restart at click

Same problem mouse is Steeleries Rival 110 My configuration is p-i@pi-TUF-Gaming-B550M:~$ inxi -Fz System:Kernel: 5.8.0-25-generic x86_64 bits: 64 Desktop: GNOME 3.38.1 Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: Mobo:

[Bug 1904382] Re: Always crash when opened

Fixed in this update Start-Date: 2020-11-22 09:54:35 Commandline: apt upgrade Requested-By: p-i (1000) Upgrade: libc-ares2:amd64 (1.16.1-1ubuntu1, 1.17.1-1), libkrb5-3:amd64 (1.17-10, 1.17-10ubuntu1), libgssapi-krb5-2:amd64 (1.17-10, 1.17-10ubuntu1), mscompress:amd64 (0.4-7, 0.4-8),

[Bug 1904878] Re: update-manager crashed with dbus.exceptions.DBusException in update(): org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1

Fixed in this update Start-Date: 2020-11-22 09:54:35 Commandline: apt upgrade Requested-By: p-i (1000) Upgrade: libc-ares2:amd64 (1.16.1-1ubuntu1, 1.17.1-1), libkrb5-3:amd64 (1.17-10, 1.17-10ubuntu1), libgssapi-krb5-2:amd64 (1.17-10, 1.17-10ubuntu1), mscompress:amd64 (0.4-7, 0.4-8),

[Bug 1904878] Re: update-manager crashed with dbus.exceptions.DBusException in update(): org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904878 Title: update-manager crashed with dbus.exceptions.DBusException in update():

[Bug 1904866] Re: Software updater fails to update with errors

I got the bug on Ubuntu with the ubuntu-desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904866 Title: Software updater fails to update with errors To manage notifications about this bug go

Re: [Bug 1904382] Re: Always crash when opened

I think the bug is reported in https://bugs.launchpad.net/bugs/1904217 When I tried to report the crash I got the message that it already is reported, but I don't have permission to open the bug. Den mån 16 nov. 2020 kl 10:56 skrev Julian Andres Klode < 1904...@bugs.launchpad.net>: > Thanks for

[Bug 1904382] [NEW] Always crash when opened

Public bug reported: Crash when opened on a new hirsute installation. sudo apt update and sudo apt upgrade work OK ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: update-manager 1:20.10.1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64

Re: [Bug 1900998] Re: ubiquity graphic problems

Installed the 20201022 ISO. This worked better and the 2:nd time the installation worked without graphic issues The 1:st time I got a system hang, when I used the mouse to scroll down to find the keyboard layout. Had to do a hard reset of the computer. Den tors 22 okt. 2020 kl 15:38 skrev Per

Re: [Bug 1900998] Re: ubiquity graphic problems

A screenshot looks OK. But this time I got a gnome-shell crash and I uploaded this. Probably it's a gnome-shell problem and not ubiquity. Den tors 22 okt. 2020 kl 14:01 skrev Jean-Baptiste Lallement < 1900...@bugs.launchpad.net>: > Thanks for your report. Can you please attach a screenshot of

[Bug 1900998] [NEW] ubiquity graphic problems

Public bug reported: USB booted OK, graphic problem started when selecting keyboard and continued during the installation with unreadable text and slide show with graphic problems. Hard to select keyboard, had to guess the right keyboard was selected. Installation is OK with Nvidia driver. UEFI

Re: [Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist(

I don't have problems with suspend any longer. I think this bug is fixed. However I'm not using the standard kernel. I'm using Kernel: 5.7.7-050707-generic x86_64. I had a problem with Chrome freezing the computer and this kernel fixed that problem. Den tis 14 juli 2020 kl 16:01 skrev Martin

[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda

Made an USB boot disk with mkusb and tested the Groovy Ubuntu Desktop amd64 version 20200709. Worked with MBR/BIOS mode on a desktop computer with an AMD Bulldozer CPU and Nvidia 1660 GPU. There were however some peculiar things - Graphical artifacts during the installation. Perhaps "Safe

[Bug 1885414] Re: ubiquity: bootloader failed on /dev/vda

Tested installation in VirtualBox of Ubuntu desktop amd64 version 20200707.1 in both MBR and EFI mode. Both worked OK. Tested to install from USB in MBR mode on a computer with Nvidia GPU. Doesn't work. get an error message about /DEV/SR0 No media found Tested on another computer in EFI mode.

Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

p-i@asus-b450-f:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.36.3-1ubuntu1~20.04.2 Candidate: 3.36.3-1ubuntu1~20.04.2 Version table: *** 3.36.3-1ubuntu1~20.04.2 500 500 http://se.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 500

Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

No, this is noy groovy. I have downloaded Focal Daily from http://iso.qa.ubuntu.com/qatracker/milestones/408/builds some days ago and updates regularly and I think the developer option is set. After an update today the Gnome version is " Desktop: Gnome 3.36.3". I have made a couple of suspends and

Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

I'm now using the development version of 20.04.1. Will this fix be included? Den fre 19 juni 2020 kl 07:55 skrev Timo Aaltonen < 1877...@bugs.launchpad.net>: > Hello Per-Inge, or anyone else affected, > > Accepted gnome-shell into focal-proposed. The package will build now and

Re: [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() when using dash-to-panel

Started Groovy Gorilla today and update. Suspend don't crash gnome-shell. Perhaps "gnome-shell-extension-desktop-icons:amd64 (20.04.0-1, 20.04.0-2)" fixed the problem. Den ons 20 maj 2020 kl 19:30 skrev Per-Inge <1877...@bugs.launchpad.net>: > Used apport-cli to report and

[Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() when using dash-to-panel

Used apport-cli to report and that worked. Marked the report as bug 184. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/184 Title: gnome-shell crashed with SIGSEGV in

Re: [Bug 1879043] Re: gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

*** This bug is a duplicate of bug 184 *** https://bugs.launchpad.net/bugs/184 OK, when I send the crash report launchpad isn't opened. Might be because the crash file _usr_bin_gnome.shell.1000.crash is 45 MB, the file _usr_bin_gnome.shell.1000.upload is 0 bytes and the

Re: [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()

I reinstalled and got a crash after suspend. It might be bug 184, but I made a new one. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879043 Den fre 15 maj 2020 kl 22:41 skrev Marco Trevisan (Treviño) : > No error reported for the SRU or groovy version for this crash at >

[Bug 1879043] [NEW] gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

Public bug reported: It might be bug 184. This is a new installation. During the installation After each change I made Suspend and restarted the computer and checked if gnome-shell had crashed. Installed: Printer, Flatpaks, Sensory Perceptions, AlternateTab, Applications Menu, OpenWeather

[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()

I don't know if this is related. It seems I always get a crash either when I start suspend or when I return from suspend. When I send the crash report launchpad don't open. The crash is in gnome-shell and the crash message is "gnome-shell crashed with SIGSEGV

Re: [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()

happen often, but I will use this configuration for some time. Alternatively I also use a system on other hardware with Groovy Gorilla. This system don't have any kernel or graphic driver changes. Den tis 12 maj 2020 kl 22:21 skrev Brian Murray : > Hello Per-Inge, or anyone else affec

Re: [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()

I don't have a standard installation of Ubuntu 20.04 any longer. It's now updated with kernel 5.6.7-050607-generic x86_64 and I'm also using the oibaf-ppa. I tried clicking multiple times in appindicators in the system tray, but I didn't get any error. I run Fedora 32 on this computer too and I

[Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

No, I'm not using gTile. To Lock the screen and log in also works OK. My gnome-shell crashes don't happen that often and I haven't found a way to reproduce the crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1835660] Re: initramfs unpacking failed

I added the fix in comment #33 on two computers and this fixed the initramfs problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage

[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()

Thought this was fixed with gnome 3.36, but I got it when I 1:st closed Gmail and then Chrome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868660 Title: gnome-shell crashed with SIGSEGV in

[Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

Happened again, but now it refers to icon instead of font. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868440 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() To

Re: [Bug 1862792] Re: gnome-shell always crash after boot

This is the result: Error reports sent from this system Occurred Received Problem Type Program 2020-02-11 19:02 2020-02-11 18:02 UTC Crash gnome-shell 2020-02-11 06:02 2020-02-11 05:02 UTC Crash gnome-shell 2020-02-10 11:02 2020-02-10 11:02 UTC Crash gnome-shell 2020-02-09 12:02 2020-02-09 12:02

[Bug 1862792] [NEW] gnome-shell always crash after boot

Public bug reported: gnome-shell always crash after boot with an UnreportableReason. This is in a Wayland session. There are no stability issues after boot. I get this information in the terminal after the command ubuntu-bug p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell

[Bug 1835660] Re: initramfs unpacking failed

I get different behavior depending on how I boot the computer using the BIOS boot menu - When I select sda with Ubuntu 20.04, I don't get the error message - When I select sdc with Fedora 31 and select Ubuntu from Fedora's boot menu I get the error message -- You received this bug notification

[Bug 1835660] Re: initramfs unpacking failed

Added Fedora 31 and made a triple boot system with Ubuntu 20.04, Windows 10 and Fedora 31. Fedora stored the boot record in /dev/sdc1 and I had to change boot disk to sdc in BIOS. Fedora provides a boot menu with Fedora Ubuntu Windows When I start Ubuntu via the Fedora boot menu I get this error

[Bug 1848771] Re: Reboot after resume from suspend (deep)

I don't know if this is related but it fixed my problem with wake up from suspend. This is on a desktop with an Asus Rog Strix B450-F Gaming motherboard and Focal Fossa. I have changed these settings in BIOS - Used DOCP settings on the memory - USB power delivery in SoftOff is set to Disable -

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

On computers with HDA or SDA drives it is possible to disconnect all drives except the installation drive to install grub on the wanted drive. This is however not a practical solution with NVme drives. As I want to use the development version of Ubuntu early this is normally the last

[Bug 1846318] [NEW] Placement set to Left

Public bug reported: When Placement in Windows Titlebars is set to Left, gnome-tweaks opens in a too small window and the menu to select view isn't shown. Test case: Set placement to Left Open gnome-tweaks Enlarge the window and the menu is shown. ProblemType: Bug DistroRelease: Ubuntu 19.10

Re: [Bug 1842022] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

I haven't seen this bug for some time and the test case: log in, start Gnome Gmail open a mail and click a link that opens Chrome works fine. This is on ibus 1.5.19-4ubuntu2. Den tis 17 sep. 2019 kl 21:50 skrev Gunnar Hjalmarsson < 1842...@bugs.launchpad.net>: > IBus has just been updated in

Re: [Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

Test case Start Text Editor, Minimize and right click Text Editor in the Dock works fine. Den mån 16 sep. 2019 kl 17:50 skrev Launchpad Bug Tracker < 1843...@bugs.launchpad.net>: > This bug was fixed in the package gnome-shell-extension-ubuntu-dock - > 66ubuntu19.10.2 > > --- >

[Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

One more problem. After Log Out and Log In, Windows Titlebars are move from Left to Right. It is not possible to change them back to Left in Tweaks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

This also happens in this usecase. Open an application for example text editor Minimize the application Right click the application in Ubuntu Dock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843520

[Bug 1834957] [NEW] Automatic generated printer in CUPS

Public bug reported: The automatic generated printer don't work. It is possible to use Settings and add the printer. It is possible to delete the faulty printer in Setting, but every time the printer is turned on the faulty printer is generated again. It is also possible to use Settings to

[Bug 1809936] Re: Installing GNOME shell extensions

In a new installation of EOAN it's not possible to install gnome extensions in Chromium. You get this error message "Although GNOME Shell integration extension is running, native host connector is not detected." Refer documentation for instructions about installing connector." The method

Re: [Bug 1821435] [NEW] nautilus crashed with SIGABRT in g_assertion_message()

. Restarted Nautilus, but this didn't help. Logged out and logged in again. Open Documents and starred the file again. This time the file showed up in Starred. Did the same in Eoan with the same result. Den lör 23 mars 2019 kl 08:15 skrev Per-Inge : > Private bug reported: > > Copied a

Re: [Bug 1821435] Re: nautilus crashed with SIGABRT in g_assertion_message()

Will test om thursday Den mån 20 maj 2019 16:30Łukasz Zemczak <1821...@bugs.launchpad.net> skrev: > Hello Per-Inge, or anyone else affected, > > Accepted nautilus into disco-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+sou

[Bug 1723760] Re: No restart after installation

I haven't seen this when I have followed the 18.10 and 19.04 development. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723760 Title: No restart after installation To manage notifications about

Re: [Bug 1793249] Re: nautilus crashed with SIGABRT in g_assertion_message()

I don't get that crash any longer. I'm using Nautilus 3.26.4. Den tis 15 jan. 2019 kl 18:35 skrev Sebastien Bacher : > The error tracker has a few report for that issue on > https://errors.ubuntu.com/problem/82ca773a06c225419be734599e500c5f4b2100ac > > ** Information type changed from Private to

[Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

Thanks a lot. This worked OK. I used kernel 4.19.1, but now I have removed it and I have also removed the "proposed package" setting. The power draw from the wall outlet at idle is now back to the normal 63W-65W. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

This kernel update didn't fix the the high power consumption on my Radeon RX580 GPU. Start-Date: 2018-11-14 06:51:30 Commandline: /usr/bin/unattended-upgrade Install: linux-headers-4.18.0-11:amd64 (4.18.0-11.12, automatic), linux-image-4.18.0-11-generic:amd64 (4.18.0-11.12, automatic),

Re: [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

I followed the [Test Case] and got the expected result "Please note that the upstream fix reverts a new behaviour and as a result, when opening again gnome-software at step 6, the application opens on the home screen instead of resuming the last open page." These are the updates I installed:

Re: [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

To get the new version of ubuntu/gnome-software you have to enable "Pre-released updates" in "Developer Options" and allow all updates of ubuntu-software. Den ons 24 okt. 2018 kl 20:50 skrev Edson José dos Santos < 1798...@bugs.launchpad.net>: > Se abrir a loja novamente volta para mesma tela e

Re: [Bug 1798053] Re: [SRU] Click on the back icon in gnome-software doesn't work

Tested and behaves as expected. When gnome-software is started again the home screen is shown. Den ons 24 okt. 2018 kl 00:41 skrev Brian Murray : > Hello Per-Inge, or anyone else affected, > > Accepted gnome-software into cosmic-proposed. The package will build now > and be availa

[Bug 1798053] [NEW] Click on the back icon in gnome-software don't work

Public bug reported: Searched for Chromium, installed Chromium (snap version), clicked Launched and used chromium. Went back to gnome-software and clicked the back button. Nothing happened. Restarted gnome-software and clicked the back button. Nothing happened. ProblemType: Bug DistroRelease:

[Bug 1798050] [NEW] Installation crashed after Continue clicked after presentation of the time Zone

Public bug reported: Followed the test case Install (auto-resize) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity 18.10.10 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

[Bug 1797198] Re: [nvidia] After login the screen goes black

This bug was fixed in the http://cdimage.ubuntu.com/daily- live/20181013.1/cosmic-desktop-amd64.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797198 Title: [nvidia] After login the screen goes

[Bug 1797198] [NEW] Oct 10 18:22:28 pi-GA-990FXA-UD3 /usr/lib/gdm3/gdm-x-session[1676]: Fatal server error:

Public bug reported: When I boot Cosmic, grub is working OK and login screen is presented OK, but after login the screen goes black. When I boot in Recovery Mode" and "Resume" all is working OK and Nvidia driver 390 is used. These bugs my be related

[Bug 1794923] Re: Corrupt sreen in CIV VI

Tested. Works OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794923 Title: Corrupt sreen in CIV VI To manage notifications about this bug go to:

[Bug 1795210] [NEW] nautilus crashed with SIGABRT in g_assertion_message_expr()

Public bug reported: Search in Computer with åäö. Nautilus kept searching. Canceled the search, which worked OK. Edited the search with backspace. Removed ö and removed ä. Nautilus crashed when å was the only character in the search field. I suppose this is related to bug#1795136. ProblemType:

[Bug 1794923] [NEW] Corrupt sreen in CIV VI

Public bug reported: After the upgrade of MESA to 18.2.1, CIV VI has corrupt picture elements in full screen mode, e.g the buttons to the right in the upper panel are corrupt. The intro picture when starting a game is not displayed correctly. See the attached screenshot. ProblemType: Bug

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

Still not fixed in the ISO from 8/9 Not able to run gnome-calculator. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps To manage

[Bug 1759591] Re: gnome-control-center assert failure: corrupted size vs. prev_size

This is on "Ubuntu 18.10" with 4.17.0-041700rc6. Opened settings/device/printers clicked on the cog, selected Printing Options and clicked Test Page. The page was printed, but I wasn't able to close the window and settings crashed. -- You received this bug notification because you are a member

Re: [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

Yes every time. I changed method and used Power/Automatic suspend instead, which actually is more convenient. 2018-04-24 23:12 GMT+02:00 Marco Trevisan (Treviño) : > Great to hear, were you getting this regularly? > > -- > You received this bug notification because you are

Re: [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

I checked and I don't get this bug any longer 2018-04-18 23:41 GMT+02:00 Launchpad Bug Tracker <1724...@bugs.launchpad.net >: > This bug was fixed in the package mutter - 3.28.1-1 > > --- > mutter (3.28.1-1) unstable; urgency=medium > > [ Jeremy Bicha ] > * New upstream release >

[Bug 1765593] [NEW] Cannot start synaptic from Ubuntu-dock

Public bug reported: To reproduce the bug: - click the Synaptic icon in Ubuntu-dock - when Synaptic starts click cancel - click the Synaptic icon in Ubuntu-dock Synaptic will not start It's possible to start Synaptic from the terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package:

[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 g_log() from

I always get this bug when I start with an Xorg session. I started with a Wayland session and didn't get the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748450 Title: gnome-shell crashed

[Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

I have earlier reported a private bug #1761149 and bug #1761973 According to information it is a duplicate this bug. When I'm asked to report the bug, this bug number or my earlier reported bugs isn't among the suggested bugs. I am used to turn of the monitor, when I'm not going to use the

Re: [Bug 1761149] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

*** This bug is a duplicate of bug 1724439 *** https://bugs.launchpad.net/bugs/1724439 It's a little better now. There is no crash, but Ubuntu dock isn't working. To see the favorite applications you have to click activities. 2018-04-04 14:43 GMT+02:00 Apport retracing service <

Re: [Bug 897842] Re: The alternative Try Ubuntu failed

You may clear this bug. It's not happening any longer. 2018-04-03 2:32 GMT+02:00 Simon Quigley : > Thank you for taking the time to report this bug and helping to make > Ubuntu better. We are sorry that we do not always have the capacity to look > at all reported bugs in a

Re: [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 g_log() from

I also get this in Xorg. My duplicate is #Bug 1760448 2018-04-03 5:40 GMT+02:00 swadesh Parasher <1748...@bugs.launchpad.net>: > Yes, at least the bug I reported was from Ubuntu 18.04 which doesn't use > Wayland by default. > > -- > You received this bug notification because you are subscribed

[Bug 1752950] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Have crashed a couple of times. Updated Bionic Beaver with oibaf ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752950 Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow() To

[Bug 1630218] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

I suppose it's this bug even if I'm on Ubuntu 18.04 with kernel 4.15-RC3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630218 Title: gnome-shell crashed with signal 5 in g_log_default_handler()

[Bug 1738749] Re: vlc 3 fails to start under wayland: vlc crashed with SIGABRT in qt_message_fatal()

VLC is working on my system after today's updates, but I had to change Video Settings/Output from "Automatic" to "OpenGL video output". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738749 Title:

[Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

Installed "Bionic Beaver" from 2017-11-09. Used "Install Ubuntu", which worked OK Used "Try Ubuntu", made the installation, got the error message and not the expected "Remove the installation Media and press Return". Used Ctrl+C to stop the script and the system restarted. The Installation

[Bug 1723760] [NEW] No restart after installation

Public bug reported: New installation of Ubuntu 17.10 with ISO from 20171015. After the message that ends with Restart Now. There is a system hang after this information: 7.616392 sd 3:0:0:0:0 [sdd] No cashing mode page found 7.616393 sd 3:0:0:0:0 [sdd] Assuming cash: write through When Ctrl+C

Re: [Bug 1502978] Re: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build against kernel 4.3 [firegl_public.c:... error: void value not ignored as it ought to be ... seq_printf]

This is a very old bug. As far as I know support of fglrx is cancelled and replaced with amdgpu-pro. I'm using amdgpu now and have no problems. Additional drivers don't offers on the Ubuntu 17.10 beta I'm using now. 2017-10-01 21:44 GMT+02:00 Launchpad Bug Tracker <1502...@bugs.launchpad.net >:

Re: [Bug 1720510] Re: No results after search

No I don't get any errors. Tested again.on two installations on the same hardware. - Restarted the the computer. - Started Ubuntu Software from the doc - Search for "soft" and the result was presented - Closed Ubuntu Software - Started Ubuntu Software from the doc - Search for "soft" and the

[Bug 1720510] [NEW] No results after search

Public bug reported: Test case: Open a new version of gnome-software/Ubuntu Software Search for soft No results are shown Do something outside the gnome-software window, e.g mouse click or focus on another window, and the results are shown. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package:

[Bug 1702078] Re: Boot to blank screen

Installed the Daily Build from 2917-09-27. This version works OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702078 Title: Boot to blank screen To manage notifications about this bug go to:

Re: [Bug 1713249] Re: gnome-software don't install e.g gnome-tweak tool

I get the problem after a new install. I have my configurations file in Dropbox and my bookmarks in Chrome/Chromium. It's essential to me that it's easy to install these packages. Today I used the 2/9 daily and Software provided this message both at installation of Dropbox and Chromium. "Enable

[Bug 1713249] [NEW] gnome-software don't install e.g gnome-tweak tool

Public bug reported: When installing gnome-tweak-tool and also chromium, gnome-tweak-tool provides the error message "Enable Third-party Software Source? GNOME Tweaks is provided by "ubuntu-artful-universe". This software source must be enabled to continue installation. Cancel Enable to continue

Re: [Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]

I get the bug notification directly after boot, but only after an upgrade. It's strange that there is No reference to the known bug. I am useing the Ubuntu login. Regards Per-inge Den 26 juli 2017 9:25 fm skrev "Daniel van Vugt" < daniel.van.v...@canonical.com>: > Weirdly th

[Bug 1702077] [NEW] Boot to blank screen

Public bug reported: Made the test case Install (entire disk) in Ubuntu Desktop amd64 in Artful Daily Installation went OK. At boot the grub menu is shown. After selection of Ubuntu the screen gets blank. The plymouth screen isn't shown. When I press Ctrl repeatedly the plymouth screen is shown

[Bug 1702078] [NEW] Boot to blank screen

Public bug reported: Made the test case Install (entire disk) in Ubuntu Desktop amd64 in Artful Daily Installation went OK. At boot the grub menu is shown. After selection of Ubuntu the screen gets blank. The plymouth screen isn't shown. When I press Ctrl repeatedly the plymouth screen is shown

[Bug 1695600] [NEW] package grub-efi-amd64-signed 1.83+2.02~beta3-4ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Public bug reported: The computer has 3 boot-disks sda with Ubuntu artful efi boot sdb with W10 non efi boot sdc with Ubuntu artful non efi boot Problems earlier with grub on sda as sudo update-grub don't find the W10 installation. ProblemType: Package DistroRelease: Ubuntu 17.10 Package:

[Bug 1693101] [NEW] gnome-shell crashed with signal 5 in _XIOError()

Public bug reported: Happened directly after boot. No usability issue. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture:

[Bug 1692309] [NEW] nautilus crashed with SIGSEGV

Public bug reported: Happened directly after boot. The only activities was a bug report about plymouth and start of Chrome. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.24.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic

[Bug 1692293] [NEW] gnome-shell crashed with signal 5 in _XIOError()

*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 Public bug reported: Happend directly after boot. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux

[Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 ***

Happend on a new install of Artful after installation of gnome-shell and ubuntu-gnome-desktop, logout and login. Crashed during "Welcome to Gnome" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616651

[Bug 1442728] Re: Chromium fullscreen should be unredirected by default

The suggestion in post #6 fixed the issue on my system, when playing a C More Channel in Chrome Version 47.0.2526.111 (64-bit). Ubuntu Xenial Xerus Radeon R9 380 AMD FX -8120 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1504989] Re: package libunity9 7.1.4+15.10.20151002-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other instances of pa

After an update of Wily before 14/12 Unity Tweak Tool didn't start, but after installation of these packages Unity Tweak Tool started OK. Installed the following packages: libunity-webapps0 (2.5.0~+15.10.20151002-0ubuntu1) qtdeclarative5-ubuntu-web-plugin (0.23+16.04.20151204-0ubuntu1)

  1   2   3   >