[Bug 1834748] Re: shotwell crashed with SIGSEGV in library_window_switch_to_page

2019-06-29 Thread Prasanna V. Loganathar
** Summary changed:

- shotwell crash on startup
+ shotwell crashed with SIGSEGV in library_window_switch_to_page

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1834748

Title:
  shotwell crashed with SIGSEGV in library_window_switch_to_page

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1834748/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 460897] Re: Tracker not returning known results

2019-06-29 Thread Launchpad Bug Tracker
[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tracker (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/460897

Title:
  Tracker not returning known results

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/460897/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 402741] Re: Tracker not indexing all files it should

2019-06-29 Thread Launchpad Bug Tracker
[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tracker (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/402741

Title:
  Tracker not indexing all files it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/402741/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817620] Re: High cpu usage on alt-tab-ing

2019-06-29 Thread Launchpad Bug Tracker
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1817620

Title:
  High cpu usage on alt-tab-ing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1808775] Re: evolution does not reliably connect at system boot or resume

2019-06-29 Thread Launchpad Bug Tracker
[Expired for evolution (Ubuntu) because there has been no activity for
60 days.]

** Changed in: evolution (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1808775

Title:
  evolution does not reliably connect at system boot or resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1808775/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1796185] Re: Evolution terminates with SIGSEGV (Address boundary error)

2019-06-29 Thread Launchpad Bug Tracker
[Expired for evolution (Ubuntu) because there has been no activity for
60 days.]

** Changed in: evolution (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1796185

Title:
  Evolution terminates with SIGSEGV (Address boundary error)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1796185/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817620] Re: High cpu usage on alt-tab-ing

2019-06-29 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1817620

Title:
  High cpu usage on alt-tab-ing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1823576] Re: sigabrt in nautilus bookmark_connect_file

2019-06-29 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1823576

Title:
  sigabrt in nautilus bookmark_connect_file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1823576/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834762] Re: Screen locks after timeout with hidraw input

2019-06-29 Thread Luca Mastromatteo
** Description changed:

  As the title says, when using the hidraw as input method, used by game
  controllers in games in Steam big picture mode especially, is not being
  detected by the gnome desktop, and so if you are playing a game using
  hidraw only, the screen timeout will come out, and the session will be
  blocked
  
  Steps to reproduce:
  - Open a game
  - Play a game with a controller using hidraw as input, such as the RPCS3 
emulator
- - The gnome-screenshot timeout will kick in and lock the session even when 
actively playing, as long no mouse or keyboard is used
+ - The gnome-screensaver timeout will kick in and lock the session even when 
actively playing, as long no mouse or keyboard is used
  
  What should happen
  - Hidraw should be detected in the same way a mouse or keyboard does
  
  I have NOT tested with a game using native evdev
  
  My config is:
  Steam + steam-devices packages installed, the steam devices has some rules 
for hidraw to be correctly working with my controller.
  
  I own a PS4 controller connected via bluetooth, but the same should happen on 
USB as well
  I used the RPCS3 emulator, which so far supports only hidraw as input method.

** Description changed:

  As the title says, when using the hidraw as input method, used by game
  controllers in games in Steam big picture mode especially, is not being
  detected by the gnome desktop, and so if you are playing a game using
  hidraw only, the screen timeout will come out, and the session will be
  blocked
  
  Steps to reproduce:
  - Open a game
  - Play a game with a controller using hidraw as input, such as the RPCS3 
emulator
  - The gnome-screensaver timeout will kick in and lock the session even when 
actively playing, as long no mouse or keyboard is used
  
  What should happen
  - Hidraw should be detected in the same way a mouse or keyboard does
  
  I have NOT tested with a game using native evdev
  
  My config is:
- Steam + steam-devices packages installed, the steam devices has some rules 
for hidraw to be correctly working with my controller.
+ Steam + steam-devices packages installed, the steam-devices package has some 
udev rules for hidraw to be correctly working with this controller.
  
  I own a PS4 controller connected via bluetooth, but the same should happen on 
USB as well
  I used the RPCS3 emulator, which so far supports only hidraw as input method.

** Description changed:

- As the title says, when using the hidraw as input method, used by game
+ As the title says, when using hidraw as input method, used by game
  controllers in games in Steam big picture mode especially, is not being
  detected by the gnome desktop, and so if you are playing a game using
- hidraw only, the screen timeout will come out, and the session will be
- blocked
+ hidraw only, the blank screen and/or lock timeout will come out, and the
+ session will be blocked or the screen will become blank
  
  Steps to reproduce:
  - Open a game
  - Play a game with a controller using hidraw as input, such as the RPCS3 
emulator
  - The gnome-screensaver timeout will kick in and lock the session even when 
actively playing, as long no mouse or keyboard is used
  
  What should happen
  - Hidraw should be detected in the same way a mouse or keyboard does
  
  I have NOT tested with a game using native evdev
  
  My config is:
  Steam + steam-devices packages installed, the steam-devices package has some 
udev rules for hidraw to be correctly working with this controller.
  
  I own a PS4 controller connected via bluetooth, but the same should happen on 
USB as well
  I used the RPCS3 emulator, which so far supports only hidraw as input method.

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

Title:
  Screen locks after timeout with hidraw input

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1834762/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834762] [NEW] Screen locks after timeout with hidraw input

2019-06-29 Thread Luca Mastromatteo
Public bug reported:

As the title says, when using the hidraw as input method, used by game
controllers in games in Steam big picture mode especially, is not being
detected by the gnome desktop, and so if you are playing a game using
hidraw only, the screen timeout will come out, and the session will be
blocked

Steps to reproduce:
- Open a game
- Play a game with a controller using hidraw as input, such as the RPCS3 
emulator
- The gnome-screensaver timeout will kick in and lock the session even when 
actively playing, as long no mouse or keyboard is used

What should happen
- Hidraw should be detected in the same way a mouse or keyboard does

I have NOT tested with a game using native evdev

My config is:
Steam + steam-devices packages installed, the steam devices has some rules for 
hidraw to be correctly working with my controller.

I own a PS4 controller connected via bluetooth, but the same should happen on 
USB as well
I used the RPCS3 emulator, which so far supports only hidraw as input method.

** Affects: gnome-screensaver (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  As the title says, when using the hidraw as input method, used by game
- controllers in games like Steam especially, is not being detected by the
- gnome desktop, and so if you are playing a game using hidraw with the
- controller, the screen timeout will come out, and the session will be
+ controllers in games in Steam big picture mode especially, is not being
+ detected by the gnome desktop, and so if you are playing a game using
+ hidraw only, the screen timeout will come out, and the session will be
  blocked
  
  Steps to reproduce:
  - Open a game
  - Play a game with a controller using hidraw as input, such as the RPCS3 
emulator
  - The gnome-screenshot timeout will kick in and lock the session even when 
actively playing, as long no mouse or keyboard is used
  
  What should happen
  - Hidraw should be detected in the same way a mouse or keyboard does
  
  I have NOT tested with a game using native evdev
  
  My config is:
  Steam + steam-devices packages installed, the steam devices has some rules 
for hidraw to be correctly working with my controller.
  
  I own a PS4 controller connected via bluetooth, but the same should happen on 
USB as well
  I used the RPCS3 emulator, which so far supports only hidraw as input method.

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

Title:
  Screen locks after timeout with hidraw input

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1834762/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-06-29 Thread Evgeniy Check
Hello anybody. Yes a has same issue too - it happens because an of running 
application was hung up. System detect it and show pop - up message in the 
middle of screen about waiting or force closing hung application. More often it 
happens during debugging an application, when break point was raised and 
debugger waiting user action so system count this application as hang. Some 
times it happens so system detect hung application but some reason can't show 
popup message over hang application. It looks so like wrote on first post - 
blocking mouse input at any windows except application bar and gnome dashboard. 
In some application keyboard become locked too, for exaple in Eclipse.  Usually 
i switch to each application and try to interact with it by keyboard typing. If 
i suspect application hang, i run or switch to gnome-terminal and use command 
top to detect process id of hang application. Then i found it i use
 sudo kill 
As is hang application was closed - normal mouse input will restored.

But main question conclude to how to change reaction of system on hanged
application - turn off annoing modal dialog. This dialog so bore me a
lot. Each time when break point occur during debug process, Unubtu pop
up this modal dialog and lock all mouse input in other apps, include
debugger too. I need to switch debugging app and press "Wait" in this
popup message, some times it need to do more than once. Then I return to
debugger continue work.

Some one know how to turn off ubuntu hang application detection?

** Attachment added: "1561471346360.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666/+attachment/5274133/+files/1561471346360.jpg

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-06-29 Thread Evgeniy Check
-- 
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/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834748] Re: shotwell crash on startup

2019-06-29 Thread Prasanna V. Loganathar
Here's the gdb stack trace:

```
$ gdb /usr/bin/shotwell ./core.3036 
GNU gdb (Ubuntu 8.2.91.20190405-0ubuntu3) 8.2.91.20190405-git
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/shotwell...
Reading symbols from 
/usr/lib/debug/.build-id/de/5ef1027f855c42246be8090cc8484e5f2123ac.debug...
[New LWP 3036]
[New LWP 3051]
[New LWP 3088]
[New LWP 3084]
[New LWP 3085]
[New LWP 3087]
[New LWP 3134]
[New LWP 3089]
[New LWP 3086]
[New LWP 3049]
[New LWP 3093]
[New LWP 3094]
[New LWP 3091]
[New LWP 3090]
[New LWP 3110]
[New LWP 3095]
[New LWP 3092]
[New LWP 3074]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `shotwell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f306a883d40 in g_menu_model_get_n_items () from 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
[Current thread is 1 (Thread 0x7f3066bb1b00 (LWP 3036))]
(gdb) where
#0  0x7f306a883d40 in g_menu_model_get_n_items () at 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
#1  0x7f3069e60c31 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#2  0x7f3069e615ab in gtk_application_window_set_show_menubar () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#3  0x558796026d17 in library_window_switch_to_page 
(self=self@entry=0x558798503f70, page=page@entry=0x5587987ef8c0) at 
../src/library/LibraryWindow.vala:1310
#4  0x558796029065 in library_window_switch_to_import_queue_page 
(self=0x558798503f70) at ../src/library/LibraryWindow.vala:951
#5  0x5587960c42b6 in run_system_pictures_import 
(external_exclusion_manifest=) at ../src/main.vala:246
#6  0x5587960c42b6 in run_system_pictures_import 
(external_exclusion_manifest=) at main.c:1837
#7  0x5587960c4de7 in library_exec (mounts=, 
mounts_length1=) at ../src/main.vala:205
#8  0x5587960c5654 in _vala_main (args=, 
args_length1=) at ../src/main.vala:460
#9  0x558795fba3f0 in main (argc=, argv=) at 
../src/main.vala:347
(gdb) thread apply all bt

Thread 18 (Thread 0x7f3064a34700 (LWP 3074)):
#0  0x7f30692f8729 in __GI___poll (fds=0x5587981858f0, nfds=1, 
timeout=25000) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f306a678bf6 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f306a678d1c in g_main_context_iteration () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3064d35ffd in  () at 
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#4  0x7f306a6a187d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f30693db182 in start_thread (arg=) at 
pthread_create.c:486
#6  0x7f3069304b1f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7f30477fe700 (LWP 3092)):
#0  0x7f30692fe2e9 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f306a6c393f in g_cond_wait () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f306a64a0db in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f306a6a2217 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f306a6a187d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f30693db182 in start_thread (arg=) at 
pthread_create.c:486
#6  0x7f3069304b1f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7f3045ffb700 (LWP 3095)):
#0  0x7f30692fe2e9 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f306a6c393f in g_cond_wait () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f306a64a0db in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f306a6a2217 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f306a6a187d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f30693db182 in start_thread (arg=) at 
pthread_create.c:486
#6  0x7f3069304b1f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f300700 (LWP 3110)):
#0  0x7f30692f8729 in __GI___poll (fds=0x7f3004007030, nfds=3, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f304c0569f1 in  () at /lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f304c048260 in pa_mainloop_poll () at 
/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f304c0488ae in pa_mainloop_iterate () at 
/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f304c048960 in pa_mainloop_run () at 

[Bug 1834748] Re: shotwell crash on startup

2019-06-29 Thread Prasanna V. Loganathar
Ok, looks my core dump is corrupted. Marking as "incomplete", as there's
nothing actionable here without it.

** Changed in: shotwell (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1834748

Title:
  shotwell crash on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1834748/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834748] [NEW] shotwell crash on startup

2019-06-29 Thread Prasanna V. Loganathar
Public bug reported:

Random crash on startup

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: shotwell 0.30.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jun 29 22:37:24 2019
InstallationDate: Installed on 2019-06-23 (5 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shotwell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1834748

Title:
  shotwell crash on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1834748/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 783918] Re: Brasero ejects CD before burning audio CD

2019-06-29 Thread Michael McNally
Same problem, 18.04 with an external USB burner. Works with xfburn.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/783918

Title:
  Brasero ejects CD before burning audio CD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/783918/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1826918] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_unref()

2019-06-29 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1826918

Title:
  gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay()
  from detach_pixmap() from meta_surface_actor_x11_dispose() from
  g_object_unref() from g_object_unref()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1826918/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834733] [NEW] gimp can not use a ttf font then crash

2019-06-29 Thread tonton
Public bug reported:

install euphoria.ttf in $home/gimp-2.8/fonts/

open gimp
search for polices and try to use in image 

gimp crash

same as gimp 2.10.10 on snap packadge

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gimp 2.8.22-1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 29 11:15:55 2019
InstallationDate: Installed on 2018-10-24 (247 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gimp
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gimp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "one of police that not work correctly"
   
https://bugs.launchpad.net/bugs/1834733/+attachment/5274097/+files/euphoria.zip

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1834733

Title:
  gimp can not use a ttf font then crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1834733/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1740106] Re: Gnome terminal not starting, timeout reached (bionic)

2019-06-29 Thread Mariano Aquino
i have recently installed chrome remote desktop too, and nautilus and terminal 
stopped working.
running this solved the terminal issue for me, as suggested in this [0] 
duplicate question:

dbus-update-activation-environment --systemd --all

for some reason, terminal wouldnt launch, but i could use the terminal
embedded onto another application (vscode). I'm still looking for clues
for the other issue (nautilus)

[0]: https://bugs.launchpad.net/ubuntu/+source/gnome-
terminal/+bug/1772259/comments/9

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

Title:
  Gnome terminal not starting, timeout reached (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1740106/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs