[Bug 1757280] Re: Night Light only works on one Monitor

2020-07-27 Thread fermulator
similar issue in 18.04.4, `gnome-shell 3.28.4`

$ xrandr | grep " connected"
eDP-1 connected (normal left inverted right x axis y axis)
DP-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
521mm x 293mm
DP-1-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 521mm x 293mm

eDP-1 is the built-in laptop monitor; (lid is closed) [1st]
DP-1-X are the external monitors over display port; (in active use, dual 
monitor) [2nd,3rd]

primary display is 2nd, secondary display is 3rd

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

Title:
  Night Light only works on one Monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1757280/+subscriptions

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

[Bug 1721833] Re: Can't type numbers in the evolution search box

2018-02-23 Thread fermulator
@jbicha; how can we get this fix delivered into Ubuntu Artful stable? -
this has been fixed since Nov2017, and still yet delivered into Ubuntu
17.10

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

Title:
  Can't type numbers in the evolution search box

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

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

[Bug 1542471] Re: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer.

2018-02-20 Thread fermulator
(had this tab open in a really old browser session ... doing some clean
up ...)

retested on Fedora 26, it works! (bug no longer present)

{{{
$ sudo zfs list | grep music
zstorage/music 7.40G  84.9G  7.40G  /zstorage/music
}}}

rhythmbox opens, music library on that pool, music plays

{{{
4.14.14-200.fc26.x86_64, zfs-0.7.5-1.fc26.x86_64, rhythmbox-3.4.1-3.fc26.x86_64
}}}

** Attachment added: "rbox_zfs_pool_source.png"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+attachment/5059243/+files/rbox_zfs_pool_source.png

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

Title:
  Playing mp3 files causes: Problem occurred without error being set.
  This is a bug in Rhythmbox or GStreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+subscriptions

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

[Bug 1741511] Re: GDM3 display manager: logon constantly trying to "press enter" - unable to login using PTY

2018-02-02 Thread fermulator
Reporting back, not experiencing the bug anymore.
How can this be closed as "obsolete"?

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

Title:
  GDM3 display manager: logon constantly trying to "press enter" -
  unable to login using PTY

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

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

[Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

2018-01-23 Thread fermulator
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

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

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

[Bug 1744849] Re: gnome-shell segfault in libgobject-2.0 g_type_check_instance_cast

2018-01-23 Thread fermulator
*** This bug is a duplicate of bug 1714989 ***
https://bugs.launchpad.net/bugs/1714989

*accepted* - huh; not sure why that didn't turn up in my search results
before submitting

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

Title:
  gnome-shell segfault in libgobject-2.0 g_type_check_instance_cast

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

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

[Bug 1744849] Re: gnome-shell segfault in libgobject-2.0 g_type_check_instance_cast

2018-01-22 Thread fermulator
Got 2x instances (1 from each unique user today)
, here's one online ubuntu-bug report:

https://errors.ubuntu.com/oops/a12896a4-fff3-11e7-b78e-fa163ef911dc

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

Title:
  gnome-shell segfault in libgobject-2.0 g_type_check_instance_cast

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

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

[Bug 1744849] Re: gnome-shell segfault in libgobject-2.0 g_type_check_instance_cast

2018-01-22 Thread fermulator
(ran ubuntu-bug on the core file, awaiting UUID to show up in the
system, will post here once it's available)

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

Title:
  gnome-shell segfault in libgobject-2.0 g_type_check_instance_cast

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

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

[Bug 1744849] [NEW] gnome-shell segfault in libgobject-2.0 g_type_check_instance_cast

2018-01-22 Thread fermulator
Public bug reported:

{{{
[13704.632087] gnome-shell[9051]: segfault at 82 ip 7f3e7e900de2 sp 
7fff6078c200 error 4 in libgobject-2.0.so.0.5400.1[7f3e7e8cb000+52000]
}}}

Stack trace is roughly:
 * g_type_check_instance_cast() at libgobject-2.0.so.0
 * st_label_set_text() at libst-1.0.so
 ...

My setup:
 * dual monitors
 * multiple local users
 * often 2x users logged in at same time
 * flip between them using PTY (CTRL+ALT+ F2, F3, etc.)
 * CTRL+ALT+F1 gets us to the gdm login screen (user selection)

What happens:
 * eventually either by timeout (or after suspend), or manual lock screen
 * user hits CTRL+ALT+F2,3,X, to access their PTY
 * screen may or may not be locked; (user logs in)
 * user hits "ALT+F2", and types "r" +  (gnome-shell --replace)

Reproducibility:
 * happened a few times since upgrade to Ubuntu 17.10
 * happened immediately after running "r"

Issue Analysis:
 * none - need guidance on how to debug/isolate next time it happens

---

System Information:

$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

$ uname -a
Linux fermmy 4.13.0-31-generic #34-Ubuntu SMP Fri Jan 19 16:34:46 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ apt-cache policy gdm3
gdm3:
  Installed: 3.26.1-3ubuntu3
  Candidate: 3.26.1-3ubuntu3
  Version table:
 *** 3.26.1-3ubuntu3 500
500 http://ca.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.26.1-3ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages


$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.24.2-0ubuntu0.1
  Candidate: 3.24.2-0ubuntu0.1
  Version table:
 *** 3.24.2-0ubuntu0.1 500
500 http://ca.archive.ubuntu.com/ubuntu zesty-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.24.0-0ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages

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

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

Title:
  gnome-shell segfault in libgobject-2.0 g_type_check_instance_cast

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

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

[Bug 1741511] Re: GDM3 display manager: logon constantly trying to "press enter" - unable to login using PTY

2018-01-22 Thread fermulator
over the next few days/weeks, since upgrading to Ubuntu 17.10 (gnome-
shell 3.26.2), will monitor for this issue to reproduce

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

Title:
  GDM3 display manager: logon constantly trying to "press enter" -
  unable to login using PTY

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

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

[Bug 1741511] Re: GDM3 display manager: logon constantly trying to "press enter" - unable to login using PTY

2018-01-22 Thread fermulator
fun

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

Title:
  GDM3 display manager: logon constantly trying to "press enter" -
  unable to login using PTY

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-09 Thread fermulator
since upgrading to Ubuntu 17.04, I'm unable to reproduce the crash any
longer FYI.

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1741511] Re: GDM3 display manager: logon constantly trying to "press enter" - unable to login using PTY

2018-01-08 Thread fermulator
Ha; selected LOCK SCREEN just now, and rolled up the GDM login, boom
reproduced.

SUSPECT:
, in order to reproduce 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739525, at the 
start of ever session, I've been restarting gnome-shell through gpb with:
```
gdb --args gnome-shell --replace
```

This could be relevant here.

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

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

Title:
  GDM3 display manager: logon constantly trying to "press enter" -
  unable to login using PTY

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

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

[Bug 1741511] Re: GDM3 display manager: logon constantly trying to "press enter" - unable to login using PTY

2018-01-08 Thread fermulator
If it were a physical key stuck issue, the login screen would be
attempting login much faster (there is a key repeat frequency for held
down keys).

I did confirm by "smushing" the keys.

Also, if the user goes to a non-graphical PTY terminal, there are NO
symptoms of "stuck keys".

So it's definitely not a hardware/keyboard problem.

--
However, as suggested, it _could_ be a soft-issue within GDM3. Next time the 
situation occurs, is there any other debug information to gather other than 
"try to tap some keys"?

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

Title:
  GDM3 display manager: logon constantly trying to "press enter" -
  unable to login using PTY

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

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

[Bug 1741511] [NEW] GDM3 display manager: logon constantly trying to "press enter" - unable to login using PTY

2018-01-05 Thread fermulator
Public bug reported:

I've seen this on Fedora (GDM+gnome-shell) in the past (can't remember
how I fixed it, or if it just went away one day with an OS upgrade).
Recently upgraded from Ubuntu 16.04.4 to 17.04, and this issue is
present here now as well.

My setup:
 * dual monitors
 * multiple local users
 * often 2x users logged in at same time
 * flip between them using PTY (CTRL+ALT+ F2, F3, etc.)
 * CTRL+ALT+F1 gets us to the gdm login screen (user selection)

What happens:
 * eventually either by timeout (or after suspend), or manual lock screen
 * user hits CTRL+ALT+F2,3,X, to access their PTY
 * screen is locked
 * login screen is presented with user, password entry and cancel/unlock
 * the screen is _already_ saying "Authentication Failed" over and over and 
over (orange text)
 * if the user tries to enter their password, it "cuts them off" too fast, and 
they can't even complete entry! - my password is in fact so long >16chars, it's 
seemingly not humanly possible to enter it within the short ~500ms window 
between resets...

Reproducibility:
 * uncertain exactly how/when it starts
 * after multiple PTY switches maybe
 * perhaps related to sending the system into sleep S3 and resuming
 * sometimes I use the proper gnome-shell "switch user" functionality

Issue Analysis:
 * none - need guidance on how to debug/isolate next time it happens


---

System Information:

$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

$ uname -a
Linux fermmy 4.10.0-42-generic #46-Ubuntu SMP Mon Dec 4 14:38:01 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux


$ apt-cache policy gdm3
gdm3:
  Installed: 3.24.1-0ubuntu0.2
  Candidate: 3.24.1-0ubuntu0.2
  Version table:
 *** 3.24.1-0ubuntu0.2 500
500 http://ca.archive.ubuntu.com/ubuntu zesty-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu zesty-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.24.0-0ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.24.2-0ubuntu0.1
  Candidate: 3.24.2-0ubuntu0.1
  Version table:
 *** 3.24.2-0ubuntu0.1 500
500 http://ca.archive.ubuntu.com/ubuntu zesty-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.24.0-0ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gdm3 3.24.1-0ubuntu0.2
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.10
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jan  5 12:24:06 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-05-11 (1700 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
SourcePackage: gdm3
UpgradeStatus: Upgraded to zesty on 2017-12-30 (6 days ago)
mtime.conffile..etc.gdm3.custom.conf: 2018-01-02T23:13:17.149142

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


** Tags: amd64 apport-bug third-party-packages zesty

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

Title:
  GDM3 display manager: logon constantly trying to "press enter" -
  unable to login using PTY

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-04 Thread fermulator
Bah; after sleep + resume, my GDM login had the dreaded "constantly
trying to press enter" problem on it ... (had this in Fedora long time
ago ... can't remember how I fixed it) - anyway - had to
CTRL+ALT+BACKSPACE to kill the gnome-shell and login again ... re-
initiating gdb run

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-02 Thread fermulator
Just installed libwxgtk3.0-0v5-dbg. re-running gnome-shell in gdb again
... will see ...

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-02 Thread fermulator
now i'm getting something
{{{
$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash 
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
}}}

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-02 Thread fermulator
When I run it, it opens the "report" thing, (sorry, Ubuntu 170.4 has 
experienced an internal error);
same as before, I click "Continue" and it just disappears (nothing output on 
the terminal either) 

In analyzing the thread manually, this most recent one appears to be
irrelevant to this report actually ... it is in libnspr4.so now ...

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Dependencies.txt

2018-01-02 Thread fermulator
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5030309/+files/Dependencies.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-02 Thread fermulator
PS: the annoyance of initially running ubuntu-bug didn't tell me how to
go "-u" ...
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1740967

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] ProcEnviron.txt

2018-01-02 Thread fermulator
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5030313/+files/ProcEnviron.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-02 Thread fermulator
On the weekend I upgraded to Ubuntu 17.10;
Amazingly, it crashed again :)

This time, apport is working, AND I get goodies in /var/crash.
{{{
fermulator@fermmy:~$ ll /var/crash
total 120364
drwxrwsrwt  2 root   whoopsie 4096 Jan  2 19:45 ./
drwxr-xr-x 17 root   root 4096 Dec 29 13:23 ../
(snip)
-rw-r-  1 fermulator whoopsie 49774498 Jan  2 10:10 
_usr_bin_gnome-shell.1000.crash
(snip)
}}}

I ran this ... but I don't know where it went!
{{{
ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
}}}

** Tags added: zesty

** Description changed:

  As requested by vanvugt in #1580605, submitting a crash unique to my
  user.
  
  This isn't fun, several times per day a crash:
  {{{
  $ dmesg -T | grep seg
  [Thu Nov 9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip 
7fd954f6d6a2 sp 7ffe04425eb8 error 4 in 
libgdk-3.so.0.1800.9[7fd954f3+d4000]
  [Thu Nov 9 10:11:16 2017] dota2[22006]: segfault at 0 ip 7fef2866683a sp 
7fff560539a0 error 6 in libtier0.so[7fef2863+8]
  [Thu Nov 9 13:04:18 2017] gnome-shell[1356]: segfault at e8 ip 
7f15ccddd6a2 sp 7fff9ecf47f8 error 4 in 
libgdk-3.so.0.1800.9[7f15ccda+d4000]
  [Thu Nov 9 17:16:45 2017] gnome-shell[14440]: segfault at e8 ip 
7f196afdd6a2 sp 7ffea13b5948 error 4 in 
libgdk-3.so.0.1800.9[7f196afa+d4000]
  [Thu Nov 9 17:16:52 2017] dconf worker[18015]: segfault at 52c ip 
004a133c sp 7f351f7e6170 error 4 in perl[40+1cf000]
  [Thu Nov 9 20:35:24 2017] gnome-shell[32271]: segfault at e8 ip 
7fd6ef0256a2 sp 7ffebb0d3608 error 4 in 
libgdk-3.so.0.1800.9[7fd6eefe8000+d4000]
  [Thu Nov 9 20:42:09 2017] gnome-shell[11070]: segfault at 23 ip 
7fc2bd8687bf sp 7fffcc3bc680 error 4 in 
libgnome-desktop-3.so.12.0.0[7fc2bd848000+39000]
  [Thu Nov 9 23:13:09 2017] gnome-shell[24832]: segfault at 6 ip 
7fb95e624818 sp 7ffc656ced30 error 4 in 
libgio-2.0.so.0.4800.2[7fb95e56+18]
  [Thu Nov 9 23:51:17 2017] gnome-shell[3253]: segfault at e8 ip 
7f2d1f4756a2 sp 7fff455b3128 error 4 in 
libgdk-3.so.0.1800.9[7f2d1f438000+d4000]
  [Fri Nov 10 01:09:27 2017] gnome-shell[31134]: segfault at e8 ip 
7f3b923756a2 sp 7fff91dea558 error 4 in 
libgdk-3.so.0.1800.9[7f3b92338000+d4000]
  [Fri Nov 10 01:12:43 2017] gnome-shell[9188]: segfault at e8 ip 
7f683370d6a2 sp 7ca20198 error 4 in 
libgdk-3.so.0.1800.9[7f68336d+d4000]
  [Fri Nov 10 03:40:54 2017] gnome-shell[25978]: segfault at e8 ip 
7f8af06ed6a2 sp 7ffdf3c5cfc8 error 4 in 
libgdk-3.so.0.1800.9[7f8af06b+d4000]
  [Sat Nov 11 00:49:59 2017] gnome-shell[31566]: segfault at e8 ip 
7ffab7ae56a2 sp 7fff76561338 error 4 in 
libgdk-3.so.0.1800.9[7ffab7aa8000+d4000]
  [Sat Nov 11 20:01:10 2017] gnome-shell[23459]: segfault at e8 ip 
7f6a4c1dd6a2 sp 7ffdfcd62008 error 4 in 
libgdk-3.so.0.1800.9[7f6a4c1a+d4000]
  [Sat Nov 11 21:05:36 2017] gnome-shell[28874]: segfault at e8 ip 
7f48523d56a2 sp 7ffd15fbc738 error 4 in 
libgdk-3.so.0.1800.9[7f4852398000+d4000]
  }}}
  
  My setup:
   * Dual monitors
   * OFTEN switch between users
  a) using the GDM3 "switch user" GUI
  b) using CTRL+ALT+FXX quick flips
   * Daily I suspend the system and resume (Power Management)
  
  Versions
  {{{
  $ cat /etc/issue
  Ubuntu 16.04.3 LTS \n \l
  
  $ uname -a
  Linux  4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  
  
  $ dpkg --list | grep gnome-shell
  ii  chrome-gnome-shell  
9-0ubuntu1~ubuntu16.04.3 all  GNOME Shell 
extensions integration for web browsers
  ii  gnome-shell 
3.18.5-0ubuntu0.3amd64graphical shell for 
the GNOME desktop
  ii  gnome-shell-common  
3.18.5-0ubuntu0.3all  common files for the 
GNOME graphical shell
  ii  gnome-shell-timer   
0.3.12+20140924-3all  GNOME Shell extension 
providing a countdown timer in the top panel
  
  $ dpkg --list | grep libgdk
  ii  libgdk-pixbuf2.0-0:amd64
2.32.2-1ubuntu1.3amd64GDK Pixbuf library
  ii  libgdk-pixbuf2.0-0:i386 
2.32.2-1ubuntu1.3i386 GDK Pixbuf library
  ii  libgdk-pixbuf2.0-common 
2.32.2-1ubuntu1.3all  GDK Pixbuf library - 
data files
  ii  libgdk-pixbuf2.0-dev
2.32.2-1ubuntu1.3amd64GDK Pixbuf library 
(development files)
  }}}
  
  Some random snippet:
  {{{
   Dec 6 21:47:44 fermmy gnome-session[9885]: (gnome-shell:

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-02 Thread fermulator
PS: Don't see the stacktrace auto-uploaded .. hmmm. (in the GUI, I saw
it; but couldn't copy it ;/)

PPS: 
https://errors.ubuntu.com/user/1e1145eaed4889fbf4b9b34afdec32bef59b5445c5b86e87b5a55d713b285c7f490cd65ed98cd622a50b4e395de9a91482820e11dada93321d414a30066cc930
 (do not yet see my most recent uploads from 2018 ... might take time to update)

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] ProcCpuinfoMinimal.txt

2018-01-02 Thread fermulator
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5030312/+files/ProcCpuinfoMinimal.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] GsettingsChanges.txt

2018-01-02 Thread fermulator
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5030310/+files/GsettingsChanges.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] JournalErrors.txt

2018-01-02 Thread fermulator
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5030311/+files/JournalErrors.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-22 Thread fermulator
$ ll /var/crash
total 8
drwxrwsrwt  2 root whoopsie 4096 Sep  4 12:12 ./
drwxr-xr-x 18 root root 4096 Feb 11  2017 ../


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

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-22 Thread fermulator
Not sure what to do, apport is running for sure, but still no gnome-
shell crash files are being generated.

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-22 Thread fermulator
RE 1)

Yes I have PPAs in use: (hopefully it's not a crime ;o) - but, please do let me 
know how to isolate one as providing "bad" or perhaps an "old" library?
{{{
/etc/apt/sources.list.d$ find . | egrep "list$"
./wire-desktop.list
./google-earth.list
./webupd8team-ubuntu-atom-xenial.list
./steam.list
./webupd8team-java.list
./private-ppa.launchpad.net_commercial-ppa-uploaders_brightness-controller_ubuntu.list
./i3wm.list
./mystic-mirage-ubuntu-pycharm-xenial.list
./videolan-stable-daily.list
./virtualbox.list
./slack.list
./gnumdk-ubuntu-lollypop-xenial.list
./dropbox.list
./shiki-mediainfo-precise.list
./google-talkplugin.list
./webupd8team-tor.list
./strukturag-libde265-trusty.list
./shutter-ppa.list
./ring-nightly-man.list
./google-chrome.list
./webupd8team-ubuntu-java-xenial.list
./wine-ubuntu-wine-builds-xenial.list
./skype-unstable.list
./svn-ppa-precise.list
./tualatrix-ppa-precise.list
./skype-stable.list
./team-xbmc-ubuntu-xbmc-nightly-xenial.list
./maarten-baert-ubuntu-simplescreenrecorder-xenial.list
./gnome3-team-gnome3-trusty.list
./phablet-team-tools-precise.list
./ne0sight-ubuntu-chrome-gnome-shell-xenial.list
./ubuntu-wine-ubuntu-ppa-xenial.list
}}}

RE libcogl20; (what is "suspicious" about it?)
{{{
$ apt-cache search libcogl20
libcogl20 - Object oriented GL/GLES Abstraction/Utility Layer
libcogl20-dbg - Object oriented GL/GLES Abstraction/Utility Layer (debug files)

$ apt-cache show libcogl20
Package: libcogl20
Priority: optional
Section: libs
Installed-Size: 817
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian GNOME Maintainers 

Architecture: amd64
Source: cogl
Version: 1.22.0-2
Depends: libc6 (>= 2.17), libcairo2 (>= 1.10), libdrm2 (>= 2.4.17), 
libegl1-mesa (>= 7.8.1) | libegl1-x11, libgbm1 (>= 8.1~0), libgdk-pixbuf2.0-0 
(>= 2.22.0), libglib2.0-0 (>= 2.32.0), libwayland-client0 (>= 1.3.92), 
libwayland-egl1-mesa (>= 10.0.2) | libwayland-egl1, libwayland-server0 (>= 
1.2.0), libx11-6, libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxrandr2 (>= 
2:1.2.0), libgl1-mesa-glx
Recommends: libcogl-common
Suggests: libgles2-mesa | libgles2
Breaks: libclutter-1.0-0 (<< 1.17), libcogl11, libcogl12, libcogl15, libcogl9
Filename: pool/main/c/cogl/libcogl20_1.22.0-2_amd64.deb
Size: 283916
MD5sum: 5cebf6546cc68d93c484ab5902bdb7f8
SHA1: 8c53e01546d50cfd830e09eaf40e4776f5324af4
SHA256: 7301ea606ae65e9c5f03531f83bb33b6f5400954dea9587079420e979a7923a8
Description-en: Object oriented GL/GLES Abstraction/Utility Layer
 Cogl is a small open source library for using 3D graphics hardware to draw
 pretty pictures. The API departs from the flat state machine style of
 OpenGL and is designed to make it easy to write orthogonal components that
 can render without stepping on each others toes.
Description-md5: 8c0fee75492f726194fa0be454f54661
Multi-Arch: same
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Supported: 5y
Task: ubuntu-desktop, ubuntu-usb, edubuntu-desktop, edubuntu-usb, 
xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop, ubuntu-gnome-desktop, 
ubuntukylin-desktop, ubuntu-mate-desktop
}}}

RE 2)
, again, I never have any crash files in /var/crash. Not sure why.

{{{
$ sudo systemctl status apport.service
● apport.service - LSB: automatic crash report generation
   Loaded: loaded (/etc/init.d/apport; bad; vendor preset: enabled)
   Active: active (exited) since Fri 2017-12-15 13:19:31 EST; 6 days ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2733 ExecStart=/etc/init.d/apport start (code=exited, 
status=0/SUCCESS)
Tasks: 0
   Memory: 0B
  CPU: 0
}}}

, it looks like however it was marked as disabled in
`/etc/default/apport` ; (I clearly disabled it ~2years ago because
things kept crashing and I wasn't in the position to deal with it... I
recall a time when colord was crashing all the time; couldn't live my
life! ;o)

SO; RE #2, I've re-enabled that, so -hopefully- I get a proper core file
next gnome-shell crash.

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] ProcEnviron.txt

2017-12-21 Thread fermulator
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5025855/+files/ProcEnviron.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] GsettingsChanges.txt

2017-12-21 Thread fermulator
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5025852/+files/GsettingsChanges.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-21 Thread fermulator
dmesg full output from most recent crash

** Attachment added: "dmesg_full.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739525/+attachment/5025857/+files/dmesg_full.txt

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

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] ProcCpuinfoMinimal.txt

2017-12-21 Thread fermulator
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5025854/+files/ProcCpuinfoMinimal.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-21 Thread fermulator
here's the full "journalctl -xe" output from a most recent crash

** Attachment added: "journalctl_full.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739525/+attachment/5025856/+files/journalctl_full.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-21 Thread fermulator
apport information

** Description changed:

  As requested by vanvugt in #1580605, submitting a crash unique to my
  user.
  
  This isn't fun, several times per day a crash:
  {{{
  $ dmesg -T | grep seg
  [Thu Nov 9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip 
7fd954f6d6a2 sp 7ffe04425eb8 error 4 in 
libgdk-3.so.0.1800.9[7fd954f3+d4000]
  [Thu Nov 9 10:11:16 2017] dota2[22006]: segfault at 0 ip 7fef2866683a sp 
7fff560539a0 error 6 in libtier0.so[7fef2863+8]
  [Thu Nov 9 13:04:18 2017] gnome-shell[1356]: segfault at e8 ip 
7f15ccddd6a2 sp 7fff9ecf47f8 error 4 in 
libgdk-3.so.0.1800.9[7f15ccda+d4000]
  [Thu Nov 9 17:16:45 2017] gnome-shell[14440]: segfault at e8 ip 
7f196afdd6a2 sp 7ffea13b5948 error 4 in 
libgdk-3.so.0.1800.9[7f196afa+d4000]
  [Thu Nov 9 17:16:52 2017] dconf worker[18015]: segfault at 52c ip 
004a133c sp 7f351f7e6170 error 4 in perl[40+1cf000]
  [Thu Nov 9 20:35:24 2017] gnome-shell[32271]: segfault at e8 ip 
7fd6ef0256a2 sp 7ffebb0d3608 error 4 in 
libgdk-3.so.0.1800.9[7fd6eefe8000+d4000]
  [Thu Nov 9 20:42:09 2017] gnome-shell[11070]: segfault at 23 ip 
7fc2bd8687bf sp 7fffcc3bc680 error 4 in 
libgnome-desktop-3.so.12.0.0[7fc2bd848000+39000]
  [Thu Nov 9 23:13:09 2017] gnome-shell[24832]: segfault at 6 ip 
7fb95e624818 sp 7ffc656ced30 error 4 in 
libgio-2.0.so.0.4800.2[7fb95e56+18]
  [Thu Nov 9 23:51:17 2017] gnome-shell[3253]: segfault at e8 ip 
7f2d1f4756a2 sp 7fff455b3128 error 4 in 
libgdk-3.so.0.1800.9[7f2d1f438000+d4000]
  [Fri Nov 10 01:09:27 2017] gnome-shell[31134]: segfault at e8 ip 
7f3b923756a2 sp 7fff91dea558 error 4 in 
libgdk-3.so.0.1800.9[7f3b92338000+d4000]
  [Fri Nov 10 01:12:43 2017] gnome-shell[9188]: segfault at e8 ip 
7f683370d6a2 sp 7ca20198 error 4 in 
libgdk-3.so.0.1800.9[7f68336d+d4000]
  [Fri Nov 10 03:40:54 2017] gnome-shell[25978]: segfault at e8 ip 
7f8af06ed6a2 sp 7ffdf3c5cfc8 error 4 in 
libgdk-3.so.0.1800.9[7f8af06b+d4000]
  [Sat Nov 11 00:49:59 2017] gnome-shell[31566]: segfault at e8 ip 
7ffab7ae56a2 sp 7fff76561338 error 4 in 
libgdk-3.so.0.1800.9[7ffab7aa8000+d4000]
  [Sat Nov 11 20:01:10 2017] gnome-shell[23459]: segfault at e8 ip 
7f6a4c1dd6a2 sp 7ffdfcd62008 error 4 in 
libgdk-3.so.0.1800.9[7f6a4c1a+d4000]
  [Sat Nov 11 21:05:36 2017] gnome-shell[28874]: segfault at e8 ip 
7f48523d56a2 sp 7ffd15fbc738 error 4 in 
libgdk-3.so.0.1800.9[7f4852398000+d4000]
  }}}
  
  My setup:
   * Dual monitors
   * OFTEN switch between users
  a) using the GDM3 "switch user" GUI
  b) using CTRL+ALT+FXX quick flips
   * Daily I suspend the system and resume (Power Management)
  
  Versions
  {{{
  $ cat /etc/issue
  Ubuntu 16.04.3 LTS \n \l
  
  $ uname -a
  Linux  4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  
  
  $ dpkg --list | grep gnome-shell
  ii  chrome-gnome-shell  
9-0ubuntu1~ubuntu16.04.3 all  GNOME Shell 
extensions integration for web browsers
  ii  gnome-shell 
3.18.5-0ubuntu0.3amd64graphical shell for 
the GNOME desktop
  ii  gnome-shell-common  
3.18.5-0ubuntu0.3all  common files for the 
GNOME graphical shell
  ii  gnome-shell-timer   
0.3.12+20140924-3all  GNOME Shell extension 
providing a countdown timer in the top panel
  
  $ dpkg --list | grep libgdk
  ii  libgdk-pixbuf2.0-0:amd64
2.32.2-1ubuntu1.3amd64GDK Pixbuf library
  ii  libgdk-pixbuf2.0-0:i386 
2.32.2-1ubuntu1.3i386 GDK Pixbuf library
  ii  libgdk-pixbuf2.0-common 
2.32.2-1ubuntu1.3all  GDK Pixbuf library - 
data files
  ii  libgdk-pixbuf2.0-dev
2.32.2-1ubuntu1.3amd64GDK Pixbuf library 
(development files)
  }}}
  
  Some random snippet:
  {{{
   Dec 6 21:47:44 fermmy gnome-session[9885]: (gnome-shell:10011): Gtk-CRITICAL 
**: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed
  Dec 6 21:47:44 fermmy kernel: [225347.940591] gnome-shell[10011]: segfault at 
e8 ip 7f6d239876a2 sp 7ffcebaa54b8 error 4 in 
libgdk-3.so.0.1800.9[7f6d2394a000+d4000]
  }}}
  
  Running gnome-shell from a terminal, in hopes of acquiring a stack trace on 
crash:
  {{{
   (gnome-shell:13599): Gtk-CRITICAL **: gtk_widget_get_window: assertion 
'GTK_IS_WIDGET (widget)' failed
  Segmentation fault
  }}}
  ; useless
  
  
  Ran it through gdb once:
  {{{
  $ gdb --args gnome-

[Bug 1739525] JournalErrors.txt

2017-12-21 Thread fermulator
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5025853/+files/JournalErrors.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-21 Thread fermulator
(I think I may have disabled auto-apport reports long ago because of the
constant annoyance) - no reports since `2015-12-15 18:12`

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-20 Thread fermulator
(retracted that categorization as it significantly reduces potential
participants - i self-audited the content and nothing drastic is
revealed; although I filed apport bugs to address it in the future
#1739531 and #1739532)

** Information type changed from Private Security to Public

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] ProcEnviron.txt

2017-12-20 Thread fermulator
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5025446/+files/ProcEnviron.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] GsettingsChanges.txt

2017-12-20 Thread fermulator
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5025443/+files/GsettingsChanges.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-20 Thread fermulator
apport information

** Tags added: apport-collected third-party-packages xenial

** Description changed:

  As requested by vanvugt in #1580605, submitting a crash unique to my
  user.
  
  This isn't fun, several times per day a crash:
  {{{
  $ dmesg -T | grep seg
  [Thu Nov 9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip 
7fd954f6d6a2 sp 7ffe04425eb8 error 4 in 
libgdk-3.so.0.1800.9[7fd954f3+d4000]
  [Thu Nov 9 10:11:16 2017] dota2[22006]: segfault at 0 ip 7fef2866683a sp 
7fff560539a0 error 6 in libtier0.so[7fef2863+8]
  [Thu Nov 9 13:04:18 2017] gnome-shell[1356]: segfault at e8 ip 
7f15ccddd6a2 sp 7fff9ecf47f8 error 4 in 
libgdk-3.so.0.1800.9[7f15ccda+d4000]
  [Thu Nov 9 17:16:45 2017] gnome-shell[14440]: segfault at e8 ip 
7f196afdd6a2 sp 7ffea13b5948 error 4 in 
libgdk-3.so.0.1800.9[7f196afa+d4000]
  [Thu Nov 9 17:16:52 2017] dconf worker[18015]: segfault at 52c ip 
004a133c sp 7f351f7e6170 error 4 in perl[40+1cf000]
  [Thu Nov 9 20:35:24 2017] gnome-shell[32271]: segfault at e8 ip 
7fd6ef0256a2 sp 7ffebb0d3608 error 4 in 
libgdk-3.so.0.1800.9[7fd6eefe8000+d4000]
  [Thu Nov 9 20:42:09 2017] gnome-shell[11070]: segfault at 23 ip 
7fc2bd8687bf sp 7fffcc3bc680 error 4 in 
libgnome-desktop-3.so.12.0.0[7fc2bd848000+39000]
  [Thu Nov 9 23:13:09 2017] gnome-shell[24832]: segfault at 6 ip 
7fb95e624818 sp 7ffc656ced30 error 4 in 
libgio-2.0.so.0.4800.2[7fb95e56+18]
  [Thu Nov 9 23:51:17 2017] gnome-shell[3253]: segfault at e8 ip 
7f2d1f4756a2 sp 7fff455b3128 error 4 in 
libgdk-3.so.0.1800.9[7f2d1f438000+d4000]
  [Fri Nov 10 01:09:27 2017] gnome-shell[31134]: segfault at e8 ip 
7f3b923756a2 sp 7fff91dea558 error 4 in 
libgdk-3.so.0.1800.9[7f3b92338000+d4000]
  [Fri Nov 10 01:12:43 2017] gnome-shell[9188]: segfault at e8 ip 
7f683370d6a2 sp 7ca20198 error 4 in 
libgdk-3.so.0.1800.9[7f68336d+d4000]
  [Fri Nov 10 03:40:54 2017] gnome-shell[25978]: segfault at e8 ip 
7f8af06ed6a2 sp 7ffdf3c5cfc8 error 4 in 
libgdk-3.so.0.1800.9[7f8af06b+d4000]
  [Sat Nov 11 00:49:59 2017] gnome-shell[31566]: segfault at e8 ip 
7ffab7ae56a2 sp 7fff76561338 error 4 in 
libgdk-3.so.0.1800.9[7ffab7aa8000+d4000]
  [Sat Nov 11 20:01:10 2017] gnome-shell[23459]: segfault at e8 ip 
7f6a4c1dd6a2 sp 7ffdfcd62008 error 4 in 
libgdk-3.so.0.1800.9[7f6a4c1a+d4000]
  [Sat Nov 11 21:05:36 2017] gnome-shell[28874]: segfault at e8 ip 
7f48523d56a2 sp 7ffd15fbc738 error 4 in 
libgdk-3.so.0.1800.9[7f4852398000+d4000]
  }}}
  
  My setup:
   * Dual monitors
   * OFTEN switch between users
  a) using the GDM3 "switch user" GUI
  b) using CTRL+ALT+FXX quick flips
   * Daily I suspend the system and resume (Power Management)
  
  Versions
  {{{
  $ cat /etc/issue
  Ubuntu 16.04.3 LTS \n \l
  
  $ uname -a
  Linux  4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  
  
  $ dpkg --list | grep gnome-shell
  ii  chrome-gnome-shell  
9-0ubuntu1~ubuntu16.04.3 all  GNOME Shell 
extensions integration for web browsers
  ii  gnome-shell 
3.18.5-0ubuntu0.3amd64graphical shell for 
the GNOME desktop
  ii  gnome-shell-common  
3.18.5-0ubuntu0.3all  common files for the 
GNOME graphical shell
  ii  gnome-shell-timer   
0.3.12+20140924-3all  GNOME Shell extension 
providing a countdown timer in the top panel
  
  $ dpkg --list | grep libgdk
  ii  libgdk-pixbuf2.0-0:amd64
2.32.2-1ubuntu1.3amd64GDK Pixbuf library
  ii  libgdk-pixbuf2.0-0:i386 
2.32.2-1ubuntu1.3i386 GDK Pixbuf library
  ii  libgdk-pixbuf2.0-common 
2.32.2-1ubuntu1.3all  GDK Pixbuf library - 
data files
  ii  libgdk-pixbuf2.0-dev
2.32.2-1ubuntu1.3amd64GDK Pixbuf library 
(development files)
  }}}
  
  Some random snippet:
  {{{
   Dec 6 21:47:44 fermmy gnome-session[9885]: (gnome-shell:10011): Gtk-CRITICAL 
**: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed
  Dec 6 21:47:44 fermmy kernel: [225347.940591] gnome-shell[10011]: segfault at 
e8 ip 7f6d239876a2 sp 7ffcebaa54b8 error 4 in 
libgdk-3.so.0.1800.9[7f6d2394a000+d4000]
  }}}
  
  Running gnome-shell from a terminal, in hopes of acquiring a stack trace on 
crash:
  {{{
   (gnome-shell:13599): Gtk-CRITICAL **: gtk_widget_get_window: assertion 
'GTK_IS_WIDGET (widget)' failed
  Segmentation fault
  }}}
  ; useless

[Bug 1739525] ProcCpuinfoMinimal.txt

2017-12-20 Thread fermulator
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5025445/+files/ProcCpuinfoMinimal.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] JournalErrors.txt

2017-12-20 Thread fermulator
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1739525/+attachment/5025444/+files/JournalErrors.txt

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-20 Thread fermulator
PS: the latest logs/reports will indicate that I"m running an `nvidia`
GPU w/ nouveau (previously however I was running Radeon R9 290X w/ open
source Radeon drivers) - so it's not graphics hardware related.

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

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1739525] [NEW] gnome-shell segfault at e8 in libgdk-3.so.0

2017-12-20 Thread fermulator
Public bug reported:

As requested by vanvugt in #1580605, submitting a crash unique to my
user.

This isn't fun, several times per day a crash:
{{{
$ dmesg -T | grep seg
[Thu Nov 9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip 
7fd954f6d6a2 sp 7ffe04425eb8 error 4 in 
libgdk-3.so.0.1800.9[7fd954f3+d4000]
[Thu Nov 9 10:11:16 2017] dota2[22006]: segfault at 0 ip 7fef2866683a sp 
7fff560539a0 error 6 in libtier0.so[7fef2863+8]
[Thu Nov 9 13:04:18 2017] gnome-shell[1356]: segfault at e8 ip 7f15ccddd6a2 
sp 7fff9ecf47f8 error 4 in libgdk-3.so.0.1800.9[7f15ccda+d4000]
[Thu Nov 9 17:16:45 2017] gnome-shell[14440]: segfault at e8 ip 
7f196afdd6a2 sp 7ffea13b5948 error 4 in 
libgdk-3.so.0.1800.9[7f196afa+d4000]
[Thu Nov 9 17:16:52 2017] dconf worker[18015]: segfault at 52c ip 
004a133c sp 7f351f7e6170 error 4 in perl[40+1cf000]
[Thu Nov 9 20:35:24 2017] gnome-shell[32271]: segfault at e8 ip 
7fd6ef0256a2 sp 7ffebb0d3608 error 4 in 
libgdk-3.so.0.1800.9[7fd6eefe8000+d4000]
[Thu Nov 9 20:42:09 2017] gnome-shell[11070]: segfault at 23 ip 
7fc2bd8687bf sp 7fffcc3bc680 error 4 in 
libgnome-desktop-3.so.12.0.0[7fc2bd848000+39000]
[Thu Nov 9 23:13:09 2017] gnome-shell[24832]: segfault at 6 ip 7fb95e624818 
sp 7ffc656ced30 error 4 in libgio-2.0.so.0.4800.2[7fb95e56+18]
[Thu Nov 9 23:51:17 2017] gnome-shell[3253]: segfault at e8 ip 7f2d1f4756a2 
sp 7fff455b3128 error 4 in libgdk-3.so.0.1800.9[7f2d1f438000+d4000]
[Fri Nov 10 01:09:27 2017] gnome-shell[31134]: segfault at e8 ip 
7f3b923756a2 sp 7fff91dea558 error 4 in 
libgdk-3.so.0.1800.9[7f3b92338000+d4000]
[Fri Nov 10 01:12:43 2017] gnome-shell[9188]: segfault at e8 ip 
7f683370d6a2 sp 7ca20198 error 4 in 
libgdk-3.so.0.1800.9[7f68336d+d4000]
[Fri Nov 10 03:40:54 2017] gnome-shell[25978]: segfault at e8 ip 
7f8af06ed6a2 sp 7ffdf3c5cfc8 error 4 in 
libgdk-3.so.0.1800.9[7f8af06b+d4000]
[Sat Nov 11 00:49:59 2017] gnome-shell[31566]: segfault at e8 ip 
7ffab7ae56a2 sp 7fff76561338 error 4 in 
libgdk-3.so.0.1800.9[7ffab7aa8000+d4000]
[Sat Nov 11 20:01:10 2017] gnome-shell[23459]: segfault at e8 ip 
7f6a4c1dd6a2 sp 7ffdfcd62008 error 4 in 
libgdk-3.so.0.1800.9[7f6a4c1a+d4000]
[Sat Nov 11 21:05:36 2017] gnome-shell[28874]: segfault at e8 ip 
7f48523d56a2 sp 7ffd15fbc738 error 4 in 
libgdk-3.so.0.1800.9[7f4852398000+d4000]
}}}

My setup:
 * Dual monitors
 * OFTEN switch between users
a) using the GDM3 "switch user" GUI
b) using CTRL+ALT+FXX quick flips
 * Daily I suspend the system and resume (Power Management)

Versions
{{{
$ cat /etc/issue
Ubuntu 16.04.3 LTS \n \l

$ uname -a
Linux  4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux


$ dpkg --list | grep gnome-shell
ii  chrome-gnome-shell  
9-0ubuntu1~ubuntu16.04.3 all  GNOME Shell 
extensions integration for web browsers
ii  gnome-shell 
3.18.5-0ubuntu0.3amd64graphical shell for 
the GNOME desktop
ii  gnome-shell-common  
3.18.5-0ubuntu0.3all  common files for the 
GNOME graphical shell
ii  gnome-shell-timer   
0.3.12+20140924-3all  GNOME Shell extension 
providing a countdown timer in the top panel

$ dpkg --list | grep libgdk
ii  libgdk-pixbuf2.0-0:amd64
2.32.2-1ubuntu1.3amd64GDK Pixbuf library
ii  libgdk-pixbuf2.0-0:i386 
2.32.2-1ubuntu1.3i386 GDK Pixbuf library
ii  libgdk-pixbuf2.0-common 
2.32.2-1ubuntu1.3all  GDK Pixbuf library - 
data files
ii  libgdk-pixbuf2.0-dev
2.32.2-1ubuntu1.3amd64GDK Pixbuf library 
(development files)
}}}

Some random snippet:
{{{
 Dec 6 21:47:44 fermmy gnome-session[9885]: (gnome-shell:10011): Gtk-CRITICAL 
**: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed
Dec 6 21:47:44 fermmy kernel: [225347.940591] gnome-shell[10011]: segfault at 
e8 ip 7f6d239876a2 sp 7ffcebaa54b8 error 4 in 
libgdk-3.so.0.1800.9[7f6d2394a000+d4000]
}}}

Running gnome-shell from a terminal, in hopes of acquiring a stack trace on 
crash:
{{{
 (gnome-shell:13599): Gtk-CRITICAL **: gtk_widget_get_window: assertion 
'GTK_IS_WIDGET (widget)' failed
Segmentation fault
}}}
; useless


Ran it through gdb once:
{{{
$ gdb --args gnome-shell --replace
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

[Bug 1739525] Re: gnome-shell segfault in libgdk-3.so.0

2017-12-20 Thread fermulator
As per:
https://wiki.ubuntu.com/DebuggingProgramCrash

The following NEW packages will be installed:
  gnome-shell-dbg mutter-dbg

(no instructions on what to do with that)

Nothing in /var/log/Xorg.0.log either

** Summary changed:

- gnome-shell segfault in libgdk-3.so.0
+ gnome-shell segfault at e8 in libgdk-3.so.0

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

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

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

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

[Bug 1580605] Re: gnome-shell crashes often

2017-12-20 Thread fermulator
Submitted my own in #1739525

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

Title:
  gnome-shell crashes often

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

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

[Bug 1580605] Re: gnome-shell crashes often

2017-12-20 Thread fermulator
In an attempt to acquire more detailed debug...
```

$ gdb --args gnome-shell --replace
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 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 gnome-shell...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/gnome-shell --replace
[Thread debugging using libthread_db enabled]


(SNIP) - bunch of debug/info logs

# then it borked


(gnome-shell:5119): Clutter-WARNING **: Failed to set the markup of the actor 
'ClutterText': Error on line 1: Entity did not end with a semicolon; most 
likely you used an ampersand character without intending to start an entity - 
escape ampersand as &

(gnome-shell:5119): Gtk-CRITICAL **: gtk_widget_get_window: assertion
'GTK_IS_WIDGET (widget)' failed

Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x71c4c6a2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
(gdb) 
(gdb) 
(gdb) 
(gdb) 
(gdb) Exception ignored in: 
Traceback (most recent call last):
  File "/usr/share/gdb/python/gdb/__init__.py", line 43, in flush
def flush(self):
KeyboardInterrupt


```

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

Title:
  gnome-shell crashes often

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

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

[Bug 1580605] Re: gnome-shell crashes often

2017-12-07 Thread fermulator
bah, useless, this is all i got:
```
(gnome-shell:13599): Gtk-CRITICAL **: gtk_widget_get_window: assertion 
'GTK_IS_WIDGET (widget)' failed
Segmentation fault
```

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

Title:
  gnome-shell crashes often

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

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

[Bug 1580605] Re: gnome-shell crashes often

2017-12-06 Thread fermulator
Similar outputs, although of note my libgdk is older than yours
```
$ sudo find /usr/ -iname 'libgdk-3.so*' -exec dpkg -S '{}' \;
libgtk-3-dev:amd64: /usr/lib/x86_64-linux-gnu/libgdk-3.so
libgtk-3-0:amd64: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
libgtk-3-0:amd64: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0.1800.9
libgtk-3-0:i386: /usr/lib/i386-linux-gnu/libgdk-3.so.0
libgtk-3-0:i386: /usr/lib/i386-linux-gnu/libgdk-3.so.0.1800.9
```

I've just restarted gnome-shell from a terminal, so next time it crashes
I'll hopefully have more logs.

One additional bit of information:
```
Dec  6 21:47:44 fermmy gnome-session[9885]: (gnome-shell:10011): Gtk-CRITICAL 
**: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed
Dec  6 21:47:44 fermmy kernel: [225347.940591] gnome-shell[10011]: segfault at 
e8 ip 7f6d239876a2 sp 7ffcebaa54b8 error 4 in 
libgdk-3.so.0.1800.9[7f6d2394a000+d4000]
```
, the last time it crashed today, syslog shows a Gtk-CRITICAL failure just 
prior to the segfault.

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

Title:
  gnome-shell crashes often

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

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

[Bug 1580605] Re: gnome-shell crashes often

2017-12-04 Thread fermulator
@James your stack trace and issue (bug/911591) appear to be different
from this.

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

Title:
  gnome-shell crashes often

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

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

[Bug 1580605] Re: gnome-shell crashes often

2017-12-01 Thread fermulator
Isn't it weird that my stack trace is for "libgdk-3.so" ... and not
"libgtk"? (g vs. t)

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

Title:
  gnome-shell crashes often

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

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

[Bug 1580605] Re: gnome-shell crashes often

2017-11-14 Thread fermulator
I do not know why this was changed to invalid. This is a critical issue
that has clearly introduced a regression set of crashes.

(there MAY be confusing reports from other users for other issues, but I
can confirm the originally submitted report)

This isn't fun, several times per day a crash:
{{{
$ dmesg -T | grep seg
[Thu Nov  9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip 
7fd954f6d6a2 sp 7ffe04425eb8 error 4 in 
libgdk-3.so.0.1800.9[7fd954f3+d4000]
[Thu Nov  9 10:11:16 2017] dota2[22006]: segfault at 0 ip 7fef2866683a sp 
7fff560539a0 error 6 in libtier0.so[7fef2863+8]
[Thu Nov  9 13:04:18 2017] gnome-shell[1356]: segfault at e8 ip 
7f15ccddd6a2 sp 7fff9ecf47f8 error 4 in 
libgdk-3.so.0.1800.9[7f15ccda+d4000]
[Thu Nov  9 17:16:45 2017] gnome-shell[14440]: segfault at e8 ip 
7f196afdd6a2 sp 7ffea13b5948 error 4 in 
libgdk-3.so.0.1800.9[7f196afa+d4000]
[Thu Nov  9 17:16:52 2017] dconf worker[18015]: segfault at 52c ip 
004a133c sp 7f351f7e6170 error 4 in perl[40+1cf000]
[Thu Nov  9 20:35:24 2017] gnome-shell[32271]: segfault at e8 ip 
7fd6ef0256a2 sp 7ffebb0d3608 error 4 in 
libgdk-3.so.0.1800.9[7fd6eefe8000+d4000]
[Thu Nov  9 20:42:09 2017] gnome-shell[11070]: segfault at 23 ip 
7fc2bd8687bf sp 7fffcc3bc680 error 4 in 
libgnome-desktop-3.so.12.0.0[7fc2bd848000+39000]
[Thu Nov  9 23:13:09 2017] gnome-shell[24832]: segfault at 6 ip 
7fb95e624818 sp 7ffc656ced30 error 4 in 
libgio-2.0.so.0.4800.2[7fb95e56+18]
[Thu Nov  9 23:51:17 2017] gnome-shell[3253]: segfault at e8 ip 
7f2d1f4756a2 sp 7fff455b3128 error 4 in 
libgdk-3.so.0.1800.9[7f2d1f438000+d4000]
[Fri Nov 10 01:09:27 2017] gnome-shell[31134]: segfault at e8 ip 
7f3b923756a2 sp 7fff91dea558 error 4 in 
libgdk-3.so.0.1800.9[7f3b92338000+d4000]
[Fri Nov 10 01:12:43 2017] gnome-shell[9188]: segfault at e8 ip 
7f683370d6a2 sp 7ca20198 error 4 in 
libgdk-3.so.0.1800.9[7f68336d+d4000]
[Fri Nov 10 03:40:54 2017] gnome-shell[25978]: segfault at e8 ip 
7f8af06ed6a2 sp 7ffdf3c5cfc8 error 4 in 
libgdk-3.so.0.1800.9[7f8af06b+d4000]
[Sat Nov 11 00:49:59 2017] gnome-shell[31566]: segfault at e8 ip 
7ffab7ae56a2 sp 7fff76561338 error 4 in 
libgdk-3.so.0.1800.9[7ffab7aa8000+d4000]
[Sat Nov 11 20:01:10 2017] gnome-shell[23459]: segfault at e8 ip 
7f6a4c1dd6a2 sp 7ffdfcd62008 error 4 in 
libgdk-3.so.0.1800.9[7f6a4c1a+d4000]
[Sat Nov 11 21:05:36 2017] gnome-shell[28874]: segfault at e8 ip 
7f48523d56a2 sp 7ffd15fbc738 error 4 in 
libgdk-3.so.0.1800.9[7f4852398000+d4000]
}}}

My setup:
 * Dual monitors
 * OFTEN switch between users
a) using the GDM3 "switch user" GUI
b) using CTRL+ALT+FXX quick flips
 * Daily I suspend the system and resume (Power Management)

Versions
{{{
$ cat /etc/issue
Ubuntu 16.04.3 LTS \n \l

$ uname -a
Linux  4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

$ dpkg --list | grep gnome-shell
ii  chrome-gnome-shell  
9-0ubuntu1~ubuntu16.04.3 all  GNOME Shell 
extensions integration for web browsers
ii  gnome-shell 
3.18.5-0ubuntu0.3amd64graphical shell for 
the GNOME desktop
ii  gnome-shell-common  
3.18.5-0ubuntu0.3all  common files for the 
GNOME graphical shell
ii  gnome-shell-timer   
0.3.12+20140924-3all  GNOME Shell extension 
providing a countdown timer in the top panel

$ dpkg --list | grep libgdk
ii  libgdk-pixbuf2.0-0:amd64
2.32.2-1ubuntu1.3amd64GDK Pixbuf library
ii  libgdk-pixbuf2.0-0:i386 
2.32.2-1ubuntu1.3i386 GDK Pixbuf library
ii  libgdk-pixbuf2.0-common 
2.32.2-1ubuntu1.3all  GDK Pixbuf library - 
data files
ii  libgdk-pixbuf2.0-dev
2.32.2-1ubuntu1.3amd64GDK Pixbuf library 
(development files)

}}}

** Changed in: gnome-shell (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  gnome-shell crashes often

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

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

[Bug 1542471] Re: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer.

2016-07-20 Thread fermulator
Same issue here on Fedora22. The "touch trick" did not work for me.

 can't play MP3 files via Rhythmbox when the file source is a ZFS pool
:( -- it works fine from a non-ZFS storage device.  (Fedora 22,
4.4.13-200.fc22.x86_64, zfs = 0.6.5.7-1.fc22, rhythmbox = 3.2.1-1.fc22)
-- anyone know of this issue?

 I'm wondering if there's some sort of "setting" which needs to applied
to the pool. It's definitely a "rhythmbox integration" issue of some
sort ... as playing through standard gnome-player works regardless of
storage source.

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

Title:
  Playing mp3 files causes: Problem occurred without error being set.
  This is a bug in Rhythmbox or GStreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+subscriptions

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


[Bug 160311] Re: Resizing windows by grabbing window borders is difficult [please no more comments; patches welcome]

2010-10-18 Thread fermulator
John, this is why we test the solution.  Should someone implement a fix,
I will volunteer for testing.

We need to ensure that this fix works across the board for compiz,
metacity, popular default themes, etc.  single monitor, dual monitor.
ATI/nvidia/Intel graphics (if that matters).

This needs to be scoped ASAP for 10.04+.

-- 
Resizing windows by grabbing window borders is difficult [please no more 
comments; patches welcome]
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 440865] Re: Visual notification for/correct user response to incoming voice calls and subscription requests not obvious

2010-10-17 Thread fermulator
Ah;  So while the workaround didn't work, when I click on the "mail
icon" in the applet, I was able to control the request.  Shouldn't this
functionality be available in Empathy itself? (rather than using the
applet?)

-- 
Visual notification for/correct user response to incoming voice calls and 
subscription requests not obvious
https://bugs.launchpad.net/bugs/440865
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.

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


[Bug 440865] Re: Visual notification for/correct user response to incoming voice calls and subscription requests not obvious

2010-10-17 Thread fermulator
Same problem in Empathy 2.30.2.

 * Ubuntu 10.04 LTS
 * Empathy 2.30.2
 * 2.6.32-23-generic

Under preferences, Notifications tab, I unchecked everything, and then
the notification just doesn't happen.

-- 
Visual notification for/correct user response to incoming voice calls and 
subscription requests not obvious
https://bugs.launchpad.net/bugs/440865
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.

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


[Bug 160311] Re: Resizing windows by grabbing window borders is difficult

2010-09-05 Thread fermulator
[QUOTE]
Think about it... if the window is maximized, this region lies outside the 
window and is unreachable.
[/QUOTE]

Doug,

A great idea, but how would this work with dual/milti monitors?  Or,
even, with the "grid" plugin from compiz, (allows you to square off
windows with relative ease CTRL+ALT+NUMPAD1 = bottom left,
CTRL+ALT+NUMPAD3 = bottom right, etc.).

Certainly an "outside" invisible area would overlap windows, and would
have to be considered in implementation.

-- 
Resizing windows by grabbing window borders is difficult
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 160311] Re: Resizing windows by grabbing window borders is difficult

2010-09-05 Thread fermulator
[QUOTE]
It would be helpful to know what is wrong with the current approach, which has 
changed considerably from two years ago. The default themes now have a 
_considerably large_ hotspot for resizing on all four corners of every window. 
From my perspective, this problem feels like it's solved (though there is a 
slight learning curve for those coming from Windows).

So, why is that solution insufficient?
[/QUOTE]

Hey Dylan,

I just tried using: 
 * Ubuntu 10.04
 * Theme: Ambiance
 * terminal window and nautilus window

The corner hotspots are certainly helpful, however, I wouldn't call them
"hotspots".  With the ambiance theme, it looks like they tried to make
things a little easier by increasing the BOTTOM BORDER width to ~5px(?).
This gives the illusion of a hotspot, but if you try to increase the
height of the window by using the bottom border, you'll realize that
those "hotspots" are simply a byproduct of the thicker bottom border.

As everyone has already mentioned numerous times, this bug is a terrible
UI bug.  It shouldn't be "hard" to maneuver your mouse cursor over that
tini tiny right/left border of 1px.

It's been a while since I've used Windows, so I fired up my Virtual
WinXP.  It would appear that they've simply opted for the "5px(?)"
border size all around to ensure users can easily resize.  (I don't feel
like rebooting into Win7 to see how it is with the latest Windows)

Perhaps, the solution for Ubuntu Linux, would be to force all themes to
have a 5px theme (by default).  If the user is a aesthetic/power user,
then they can change the border size themselves, then suffer through
difficulty of resizing (or they'll know to use ALT+resize -- although
that in itself has issues).

I truly believe that the default needs to be "user friendly" (i.e. an
easy to use UI in this case), rather than an "aesthetically pleasing 1px
border".

-- 
Resizing windows by grabbing window borders is difficult
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 160311] Re: Resizing windows by grabbing window borders is difficult

2010-07-06 Thread fermulator
Interesting, it didn't work for me at all.  The window would basically
get "sent to background" behind other windows.

I had to apply the patch in
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/207065.  Now,
Alt+MiddleClick resize works on any window, and if I so choose,
Alt+RightClick resize works on any window.

-- 
Resizing windows by grabbing window borders is difficult
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 160311] Re: Resizing windows by grabbing window borders is difficult

2010-07-06 Thread fermulator
@ David Siegel,
[QUOTE]
We will be discussing this bug and a solution for it at Ubuntu
Developer Summit next week. Please save your breath, we know it's high
priority and we are going to fix it!
[/QUOTE]

Indeed, a good question.  Was there any verdict/action from the
discussion?  (willing to help test and such if needed)

-- 
Resizing windows by grabbing window borders is difficult
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 160311] Re: Resizing windows by grabbing window borders is difficult

2010-07-06 Thread fermulator
@ Melroy van den Berg
[QUOTE]
Clem has a good alternative in the mainwhile:
press "Alt" on the keyboard while pressing the middle click on the mouse to 
resize the window
[/QUOTE]

This workaround doesn't work on terminal windows (or anything that
happens to have an editable text field if you're mouse is over it it
wants to quickpaste text instead of resize. heh.)

-- 
Resizing windows by grabbing window borders is difficult
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 312632] Re: wish : no compulsory extension

2010-04-11 Thread fermulator
I changed the status to "incomplete".

Just tried with EyeOfGnome (eog) 2.26.1, and the problem still exists.
I personally tested with Ubuntu Jaunty 9.04, and I had someone else test
in Ubuntu Karmic 9.10.

Steps to reproduce.

 1) Open any image with EyeOfGnome (Image Viewer) in Ubuntu.
 2) File --> "Save As"
 3) Now, we're prompted with a "Name".  Call it "my picture I am saving"
 4) Click "Save"

ERROR: File format is unknown or unsupported - Eye of GNOME could not
determine a supported writable file format based on the filename.
Please try a different file extension like .png or .jpg.

OK, look at this, there's a "File type" drop down menu, currently said "All 
Images".
Try changing this to "JPEG" or "PNG", try again, same error.

There are two options here:
 A) [RECOMMENDED] When the user choses the filetype, it should automatically 
suffix the "Name" entry with that chosen filetype.
 B) eog shouldn't care if an extension exists (I don't think this is good 
though -- it is preferred to suffix images with the proper extension for its 
type)

Here's my version on 9.04:
$ dpkg --list | grep eog
ii  eog2.26.1-0ubuntu1  
 Eye of GNOME graphics viewer program


** Changed in: eog (Ubuntu)
   Status: Fix Released => Confirmed

-- 
wish : no compulsory extension
https://bugs.launchpad.net/bugs/312632
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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


[Bug 327793] Re: Window decorations in title bar missing with compiz enabled

2010-03-20 Thread fermulator
w4w4n  wrote on 2010-01-20:

CONFIRMED.  Applying those options to the Device section in xorg.conf
restores window decorations in compiz.

-- 
Window decorations in title bar missing with compiz enabled
https://bugs.launchpad.net/bugs/327793
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 354995] Re: Brasero Checksum Error

2009-12-19 Thread fermulator
If Brasero 2.28.2 works, can we allow the latest Brasero for Ubuntu 9.04
then?

-- 
Brasero Checksum Error
https://bugs.launchpad.net/bugs/354995
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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


[Bug 307939] Re: Brasero fails to burn any kind of DVD

2009-12-19 Thread fermulator
[QUOTE]
DervishD  wrote on 2009-06-25:#10

Exactly the same happened to me on my Jaunty when writing an ISO image
into a DVD-R.

I'm using brasero 2.26.1-0ubuntu1 on AMD64 arch.
[/QUOTE]

Dervish, did you report another bug?  I'm getting th same thing on
Ubuntu 9.10 x86.

-- 
Brasero fails to burn any kind of DVD
https://bugs.launchpad.net/bugs/307939
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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


[Bug 428884] Re: gnome-screensaver-command --poke no longer inhibits screensaver

2009-12-14 Thread fermulator
I'd like to comment on perspective here.

Ubuntu is supposed to be "Linux for Humans".  Something as stupid as
"breaking the inhibit" functionality of the screensaver shouldn't take
this long to fix.  Since Ubuntu is very popular amongst multimedia
centres, this is a pretty crucial feature for people.

Suggestion:
 1. Temporarily fix the bug NOW, (remove regression), and allow the patch to 
flow to Karmic users so that functionality returns.  (i..e they shouldn't have 
to "patch" anything -- this should come upstream via apt)
 2. Spend the time to figure out the "right" solution BEFORE breaking it.  Once 
it's been agreed on the right solution, implement it, test it, and release it.

Users don't care if gnome-screensaver wants to use a new API and media
players aren't catching up.  We can't expect people to actually adopt
this OS if we're squabbling over stupid stuff like this.  As soon as
this bug was realised, the regression should have been removed, and once
functionality was restored (the old way), then we can take the time to
discuss the "right way" to fix it.  I'm all for "doing things right",
but not at the expense of having a feature (that used to work) disappear
from a new release for months...  completely unacceptable.

-- 
gnome-screensaver-command --poke no longer inhibits screensaver
https://bugs.launchpad.net/bugs/428884
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.

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


[Bug 160311] Re: Resizing windows by grabbing window borders is difficult

2009-08-11 Thread fermulator
Interesting idea Martin.

This is just IMHO, but personally I don't see much value in a "resize"
(or HDV) button.  The same "Resize" (R) button is in the "top left hand
corner" button (i don't' know what it's called) on most windows.  Also,
the usability of the "Resize" in that menu is functional at best ...
it's not very intuitive for me.

I guess I don't really think it addresses the problem at hand -- it just
makes the existing "Resize" feature one less click away.

-- 
Resizing windows by grabbing window borders is difficult
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 160311] Re: Resizing windows by grabbing window borders is difficult

2009-08-09 Thread fermulator
So there are two separate issues here now:
 1. Border thickness (Thomas' patch)
--- This introduction of a slider is a great idea.  It gives the user some 
GUI control of his/her theme in GNOME.  I think it's certainly a nice perk, and 
is yet another form of control given to the user via the GUI instead of 
modifying the XML file.  This inadvertently provides an easier workaround for 
window resizing, but does not solve the underlying problem.
 2. Border resize can be difficult with a "thin" border
--- So here we have the scenario that if a user wants thin borders (or has 
chosen a theme with thin borders) for aesthetic reasons, then resizing his/her 
windows can be difficult.  The difficulty to grab 1px of the screen is linearly 
proportional to the ever increasing resolution sizes on desktop monitors.  Two 
ideas/solutions have been proposed:
A) Virtual Border -- This would have to be user controllable, float.  If 
the user is using a thick border, they probably would want to disable this, but 
if the user is using a thin border (1px for example), then they should be able 
to control the percentage of "virtual border area" +/- around the borders.  As 
I stated previously 
(https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/160311/comments/82), a 
good default is 0.15% for this value.
   B) Snap to Border -- This would also have to be user controllable, boolean.  
Disable/Enable.  As some users have pointed out, some people will hate this 
behaviour, while others might find it useful.  Snap to Border would be mutually 
exclusive to Virtual Border, but follow a similar implementation.  If the user 
is within said 0.15% (user configurable), the cursor would "snap" to the actual 
border.

-- 
Resizing windows by grabbing window borders is difficult
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 160311] Re: Window Resize Difficult (Window Border Thickness)

2009-07-25 Thread fermulator
NOTE:  We must ensure the calculation of 0.15% is of the xrandr output,
NOT the Virtual desktop size!

-- 
Window Resize Difficult (Window Border Thickness)
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 160311] Re: Window Resize Difficult (Window Border Thickness)

2009-07-25 Thread fermulator
So are we getting any closer to deciding an action to solve this
problem?...

What daniel wrote on 2009-06-22 seems like a very good compromise.  But,
it's more of a "workaround" than a solution.  If theme writers don't
employ the "thick bottom border", then users still have to muck with it
themselves.

An accessibility option sounds like a very good idea.  Where if the user
moves the mouse cursor +/- 0.15% of the border, the cursor would either
"snap to border" or be "virtual border" allowing the user to click and
then snap to border.

0.15% Because:
 * 1024x768 --> +/- 2 & 1 pixels
 * 1280x1024 --> +/- 2 & 2 pixels
 * 1680x1050 --> +/- 3 & 2 pixels

Right now I have my borders sized to "5 pixel" thickness on a 1680x1050
resolution.  This is a good size IMO to easily grab the border when you
need to, and it doesn't look too thick.

This allows a decent (but small enough to not be intrusive) desktop real
estate area to be used for border catching.  As resolution sizes
increase, the number of pixels will also increase, scaling properly with
the ever increasing resolution sizes.

Of course, this option in accessibility options should be enabled by
default, but anyone who finds it "annoying" can disable it if they like.
The reason it should be enabled by default is for the obvious reason
that "normal" users won't know to go there to enable it.  This is a
"helpful" default behaviour to make window management easier.

-- 
Window Resize Difficult (Window Border Thickness)
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 126618] Re: gnome-system-monitor does not display hd reads to fake-raid

2009-06-24 Thread fermulator
To all who have confirmed this bug, please re-confirm at
http://bugzilla.gnome.org/show_bug.cgi?id=586853.  I've submitted this
bug to the gnome developers.

** Bug watch added: GNOME Bug Tracker #586853
   http://bugzilla.gnome.org/show_bug.cgi?id=586853

-- 
gnome-system-monitor does not display hd reads to fake-raid
https://bugs.launchpad.net/bugs/126618
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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


[Bug 137606] Re: an icon view for the fileselectors would be useful

2009-06-19 Thread fermulator
This is still present in Ubuntu 9.04 Jaunty...

"File Chooser" should have image preview!

-- 
an icon view for the fileselectors would be useful
https://bugs.launchpad.net/bugs/137606
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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


[Bug 126618] Re: gnome-system-monitor does not display hd reads to fake-raid

2009-06-11 Thread fermulator
NOTE:  As per http://ubuntuforums.org/showthread.php?p=7401844, can
anyone confirm that this bug also applies to mdadm RAID devices?
(/dev/md###)

-- 
gnome-system-monitor does not display hd reads to fake-raid
https://bugs.launchpad.net/bugs/126618
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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


[Bug 126618] Re: gnome-system-monitor does not display hd reads to fake-raid

2009-06-11 Thread fermulator
I can confirm this bug still exists on Ubuntu Jaunty, 9.04.  Here are
some filtered results from "mount":

~$: mount
/dev/sdc6 on /home type ext3 (rw,relatime,errors=remount-ro,acl)
/dev/mapper/isw_dihagdeiig_RAID03 on / type ext3 (rw,relatime,errors=remount-ro)
/dev/mapper/isw_dihagdeiig_RAID07 on /mnt/storage type ext3 
(rw,relatime,errors=remount-ro,acl)
/dev/mapper/isw_dihagdeiig_RAID01 on /mnt/windows_vista type fuseblk 
(rw,nosuid,nodev,allow_other,default_permission,blksize=4096)



Basically the gnome-system-monitor applet can monitor hard disk
activity.  It monitors /dev/hd#, /dev/sd# (IDE & SATA drives, USB
Sticks, etc.) just fine.  However, devices which exist in /dev/mapper
(from the dmraid configuration) are not monitored for disk I/O activity,
and they should be.

In my particular example, the only disk which shows disk I/O in the
applet is activity against my /home drive.  The root filesystem resides
on /dev/mapper/isw_dihagdeiig_RAID03, and it never shows I/O.

If you require any additional information, I'd be more than pleased to
provide.

** Changed in: gnome-system-monitor (Ubuntu)
   Status: Invalid => Confirmed

-- 
gnome-system-monitor does not display hd reads to fake-raid
https://bugs.launchpad.net/bugs/126618
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

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


[Bug 160311] Re: Window Resize Difficult (Window Border Thickness)

2009-06-11 Thread fermulator
NOTE:  This bug also applies to compiz, would a fix to metacity transfer
to compiz?

-- 
Window Resize Difficult (Window Border Thickness)
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 160311] Re: Window Resize Difficult (Window Border Thickness)

2009-06-11 Thread fermulator
I concur with Jared.

Also running Jaunty and I've tried various themes for Gnome including
"Human", "New Wave", "Dust", etc.

All of these themes have different border sizes, and for aesthetics,
many themes have a very thin border (1 pix).  When the border is so
thin, it's extremely difficult to "naturally" move your mouse cursor
over that 1 pixel thickness.

As per some discussion in the "New Wave" Gnome theme 
(https://bugs.launchpad.net/bugs/371833), you can customize the border width as 
follows:
I've edited my metacity-theme-1.xml (found in /usr/share/themes/New 
Wave/metacity-1) as follows:



Again though, forcing users to have a thicker border to make resizing
windows natural isn't the correct solution.  Having an "invisible"
thicker resize area would work, or perhaps a "snap to" border edge when
you're within 5 or 10 pixels of the border.

-- 
Window Resize Difficult (Window Border Thickness)
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in ubuntu.

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


[Bug 15442] Re: panels change their position between logins

2009-05-07 Thread fermulator
NOTE:  The script supplied by Nagel no longer works in Jaunty.
(https://bugs.launchpad.net/gnome-panel/+bug/15442/comments/15)

It LOOKS like it works when it's run (it properly moves the panels
around in the right manour), but when you log out and log back in, the
panels are back to the old 'wrong order'.

-- 
panels change their position between logins
https://bugs.launchpad.net/bugs/15442
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.

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


[Bug 15442] Re: panels change their position between logins

2009-05-07 Thread fermulator
Same issue in Jaunty 32-bit.

-- 
panels change their position between logins
https://bugs.launchpad.net/bugs/15442
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.

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


[Bug 30942] Re: Request to add option to disable 'Recent Documents' lists.

2009-05-06 Thread fermulator
+1

-- 
Request to add option to disable 'Recent Documents' lists.
https://bugs.launchpad.net/bugs/30942
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.

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