** Changed in: rhythmbox (Ubuntu)
Status: Triaged => In Progress
** Changed in: rhythmbox (Ubuntu)
Assignee: (unassigned) => James Cuzella (trinitronx)
** Changed in: hundredpapercuts
Assignee: (unassigned) => James Cuzella (trinitronx)
** Changed in: hundred
** Branch linked: lp:~trinitronx/rhythmbox/fix-party-mode-docs
--
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/329389
Title:
"Party mode" ununderstandable and undocumented
To
Attaching upstream patch with fixed conflicts & updated date
** Patch added: "Upstream Patch from
https://gitlab.gnome.org/GNOME/rhythmbox/-/merge_requests/59;
I was able to find that this was documented upstream in patch for Gnome
bug #572651
Source: https://bugzilla.gnome.org/show_bug.cgi?id=572651
I've applied the patch, fixed the failing patch hunks and created a
merge request (GitLab's version of pull request) here:
@fermulator: It looks like it's likely to be
https://en.wikipedia.org/wiki/GDK
$ 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:
So due to differing stacktrace here, I think #911591 is likely a
different issue than this one. Different stack library means different
codepath.
@fermulator: Does seem a bit odd at first glance... does gnome-shell
use .NET or C# (gdk-sharp)?
libgdk3.0 is a valid package name in Ubuntu, but
@dino99
Happy to open a new bug report on this, as it still appears to be an
issue in latest Ubuntu 17.10. Usually when reporting bugs, I opt to
prefer adding information to an existing bug report that I have high
confidence describes the problem I am seeing. I believe this helps to
reduce
At first glance, bug may be related to this upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=768204
** Bug watch added: GNOME Bug Tracker #768204
https://bugzilla.gnome.org/show_bug.cgi?id=768204
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I've added more details for the crash I am seeing in this bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Adding journalctl logs for gnome-shell crash. After segfault line,
gnome-shell crashes and I'm returned to gdm login screen. Once I login,
everything works again until next crash, usually caused by OpenGL window
resizing or xrandr resolution changes.
** Attachment added: "gnome-shell-crash.log"
Bug seems to be reported also elsewhere:
- ArchLinux: https://bbs.archlinux.org/viewtopic.php?id=231158
- RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1250128
The RHEL bug report mentions that they have Xorg configured without
RandR support. I do see a message in my logs that says gdm
As original reporter stated, it usually appears related to OpenGL window
resize events. I have also noted that xrandr display resolution changes
can trigger the crash.
I see errors in dmesg that mention libmutter:
[15040.472843] gnome-shell[32127]: segfault at 8 ip 7f327f29d5d0 sp
I am seeing gnome-shell crashes also. However, it usually appears
related to OpenGL window resize events as well as xrandr display
resolution changes.
Errors in dmesg mention libmutter:
[15040.472843] gnome-shell[32127]: segfault at 8 ip 7f327f29d5d0 sp
7ffeccf94a38 error 4 in
I can confirm this bug is still happening on:
Ubuntu 17.10 (Artful Aardvark)
gnome-shell 3.26.1-0ubuntu5
** 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
*** This bug is a duplicate of bug 1200950 ***
https://bugs.launchpad.net/bugs/1200950
I'm seeing this too upon upgrade to 16.04.3 LTS with Unity. This
appears to have been reported many times and marked as duplicate of
#1200950 by the Apport Launchpad bot.
I'm marking this one also as dupe
Complaints show fear, anger ungratefulness while calm feature requests
show peace, gratefulness understanding of a problem.
Community giving of FOSS shows kindness compassion, while taking
complaining shows an unsatisfied desire for control.
True control lies in harmonising with the
This bug does *not* seem fixed for me. I'm running:
google-chrome-stable - 11.0.696.68-r84545
xdg-utils - 1.1.0~rc1-2ubuntu3
Ubuntu 11.04 natty
Setting via chrome's internal Make Google Chrome my default browser button
does *not* work.
Setting via sudo update-alternatives --config
17 matches
Mail list logo
