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

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 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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[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:

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

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 Desktop Bugs, which is subscribed to gnome-shell in 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 Desktop Bugs, which is subscribed to gnome-shell in

[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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868660 Title: gnome-shell

[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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868440 Title: gnome-shell crashed with SIGSEGV in

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 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

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

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 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 Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1797198 Title: [nvidia] After login

[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 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 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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1748450 Title:

[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 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 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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1630218 Title: gnome-shell crashed with signal 5 in

[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

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:

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 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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1376609] [NEW] nautilus crashed with SIGSEGV in bacon_video_widget_properties_set_has_type()

Public bug reported: I think this bug is related to https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1212601 The bug happened when I copied a media file with strange Audio/Video properties in Utopic. The Audio/Video properties are shown OK in Ubuntu 14.04. ProblemType: Crash DistroRelease:

[Bug 1371885] Re: nautilus crashed with SIGSEGV in ffi_call_unix64()

Seems to always happen after a check of video properties when Totem cannot read the video properties. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1371885 Title: nautilus crashed

[Bug 1371885] [NEW] nautilus crashed with SIGSEGV in ffi_call_unix64()

Public bug reported: Right clicked a video in Nautilus. Selected to play with Totem. The video is stored on my NAS. Before that, looked at the file properties. The Audio/Video tab in 14.10 is different compared to 14.04. In 14.10 the Basic tab shows type: Matroska video, but the Audio/Video

[Bug 1098284] [NEW] gedit crashed with signal 5 in _XReply()

Public bug reported: The crash happend when I used this search string gcc -I /usr/include/python2.7 -c ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic x86_64 NonfreeKernelModules:

[Bug 1063734] Re: nautilus crashed with SIGSEGV

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1063734 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to:

[Bug 1063340] Re: evolution-calendar-factory crashed with SIGABRT

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1063340 Title: evolution-calendar-factory crashed with SIGABRT To manage

[Bug 1054596] Re: nautilus crashed with SIGSEGV in g_type_check_instance_cast()

*** This bug is a duplicate of bug 1053670 *** https://bugs.launchpad.net/bugs/1053670 ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1054596

[Bug 918040] Re: nautilus crashed with SIGSEGV in g_closure_invoke()

*** This bug is a duplicate of bug 917979 *** https://bugs.launchpad.net/bugs/917979 ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/918040

[Bug 910810] Re: gnome-terminal crashed with SIGABRT in raise()

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/910810 Title: gnome-terminal crashed with SIGABRT in raise() To manage notifications about

[Bug 901101] Re: rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/901101 Title: rhythmbox-metadata crashed with SIGSEGV in g_type_check_value() To manage

[Bug 750379] Re: gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion()

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/750379 Title: gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion()

[Bug 741059] Re: gsettings-data-convert crashed with SIGABRT

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/741059 Title: gsettings-data-convert crashed with SIGABRT -- desktop-bugs mailing list