[Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
/metoo App indicators visible: * accessibility * skype (quitting skype does not make any difference) * remmina (quitting remmina does not make any difference) * input languages * standard "network-volume-battery" one I used to have the indicator-multiload too, but I removed it due to heavy log spam and unreadable display. BTW, how can one remove the accessibility or keyboard indicators? I can no longer find where or how to remove them both, as the only functionality I need (switch keyboard layouts) is available via key combo. -- 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/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1698734] [NEW] systemd-resolved spams syslog whenever I'm disconnected
Public bug reported:
Every time I suspend my laptop and resume in a situation where I don't have
connectivity
I get big syslog spam from systemd-resolved. See for instance yesterday when I
went out:
Jun 18 18:48:16 chiron systemd[1]: Starting Suspend...
Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server
8.8.8.8.
Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server
8.8.4.4.
Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server
2001:4860:4860::.
Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server
2001:4860:4860::8844.
...
And the last messages of the "episode":
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server
8.8.8.8.
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server
8.8.4.4.
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server
2001:4860:4860::.
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server
2001:4860:4860::8844.
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server
8.8.8.8.
Jun 18 20:13:28 chiron NetworkManager[30674]: [1497809608.0889] device
(wlp2s0): supplicant interface state: associ
ated -> 4-way handshake
So this correspond to roughly 85 minutes of disconnection, during which
I got...
$ grep "fallback DNS" /var/log/syslog.1 | wc -l
444066
This correspond to 5224 messages/minute, 87 messages/second
I had a few other episodes in the last week, including a 4h train
roundtrip:
$ zgrep "fallback DNS" /var/log/syslog* | wc -l
1964217
I noticed the bug during the trip, when the SSD activity was slowing my
machine in a clearly noticeable way.
I'm running:
$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04
$ apt-cache policy $(dpkg-query -S $(which systemd-resolve ) | awk '{print $1}')
systemd:
Installed: 232-21ubuntu3
Candidate: 232-21ubuntu3
Version table:
*** 232-21ubuntu3 500
500 http://es.archive.ubuntu.com/ubuntu zesty-updates/main amd64
Packages
100 /var/lib/dpkg/status
232-21ubuntu2 500
500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1698734
Title:
systemd-resolved spams syslog whenever I'm disconnected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698734/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1312780] Re: Floating menu mostly disappears in fullscreen mode
The problem is still there in Ubuntu 16.04.1 The workarounds work too -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1312780 Title: Floating menu mostly disappears in fullscreen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1312780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247259] Re: rhythmbox unresponsive every few seconds
How many songs do you have in the collection? I have something like 20.000, and it used to be very smooth before, with the same number. Also, this machine has a SSD card instead of HD. Not sure what goes on. If I use ptrace I can only see brk increasing memory slowly ( 0x1000 on each call ) and some FUTEX_WAIT from time to time. My guess is that the amount of memory per song jumped sharply up (either on its own or due to UI constraints (each song is an item in a list)... -- 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/1247259 Title: rhythmbox unresponsive every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1247259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247259] Re: rhythmbox unresponsive every few seconds
I just tried rhythmbox 3.0.1, from ppa:jacob/media, on top of 13.10, and it fails exactly the same. I'm not sure if any of the changes in 14.04 will fix it, but I highly doubt it -- 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/1247259 Title: rhythmbox unresponsive every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1247259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1247259] Re: rhythmbox unresponsive every few seconds
On Mon, Apr 7, 2014 at 10:02 AM, Walter Garcia-Fontes walter.gar...@upf.edu wrote: Thanks Santiago for your input. Are you still seeing this issue in a currently supported fully updated Ubuntu system? Can you test if the issue exists in the development version 14.04? (You can try it with a life CD or USB). The problem has not changed at all in 13.10: 100% CPU during a couple of minutes with the UI unresponsive every time the list pane gets focus. WRT 14.04, we will switch to it soon for development, and I will probably be able to test. But I don't expect any improvement. I think rhythmbox is dead, which is a real pity because all alternatives are not good. I'm using audacious currently, but its db capabilities are much worse :( Regards Santiago -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1247259 Title: rhythmbox unresponsive every few seconds Status in “rhythmbox” package in Ubuntu: Incomplete Bug description: Since I updated to 13.10, rhythmbox is not usable. After it starts, it freezes on every mouse click on different panes, sometimes it recovers, sometimes it stays apparently forever gray, and the dialog to wait or kill appears. When I arrive to the point where I can play, it remains unresponsive and I cannot stop playing or switch songs. This was not happening since I upgraded from 13.04 last week. Example output when I start it from command line: $ rhythmbox (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped at this stage it has remained gray and unresponsive for more than 2 minutes and I don't know how to play music. I have a big collection (almost 2 songs), and rhythmbox has remained my player of choice for its ability to handle this, but it is slowly changing (in 13.04 it was very slow when it loosed and regained focus, like 10 seconds at 100% CPU every time. Now it seems to last forever with 100% CPU... I can help with debugging, I'm a software developer. The machine where I run it right now is an i7 with 4 cores, 8GB RAM and a fast SSD, so performance should not be an issue. The same music collection was way faster in 12.04 or 12.10... In 13.04 rhythmbox also stopped showing the performance year, which is still there in the metadata. This is a separate bug that has not been
Re: [Bug 1247259] Re: rhythmbox unresponsive every few seconds
Debug symbols are completely useless, as the problem I'd about unusable performance (minutes with the ui locked) but no crash. Generic messages don't really help me El 07/04/2014 10:51, Walter Garcia-Fontes walter.gar...@upf.edu escribió: Thanks again, since rhythmbox is the default player not only for Ubuntu but for all the Gnome family, upstream is expected to keep improving it, not all hopes are lost. If you can reproduce the issue in 14.04, it would be helpful to produce a stacktrace and file a bug upstream. If you want to do that first make sure you have the debugging symbols installed: sudo apt-get install rhythmbox-dbg and then follow the instructions at: https://wiki.ubuntu.com/Backtrace -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1247259 Title: rhythmbox unresponsive every few seconds Status in “rhythmbox” package in Ubuntu: Incomplete Bug description: Since I updated to 13.10, rhythmbox is not usable. After it starts, it freezes on every mouse click on different panes, sometimes it recovers, sometimes it stays apparently forever gray, and the dialog to wait or kill appears. When I arrive to the point where I can play, it remains unresponsive and I cannot stop playing or switch songs. This was not happening since I upgraded from 13.04 last week. Example output when I start it from command line: $ rhythmbox (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped at this stage it has remained gray and unresponsive for more than 2 minutes and I don't know how to play music. I have a big collection (almost 2 songs), and rhythmbox has remained my player of choice for its ability to handle this, but it is slowly changing (in 13.04 it was very slow when it loosed and regained focus, like 10 seconds at 100% CPU every time. Now it seems to last forever with 100% CPU... I can help with debugging, I'm a software developer. The machine where I run it right now is an i7 with 4 cores, 8GB RAM and a fast SSD, so performance should not be an issue. The same music collection was way faster in 12.04 or 12.10... In 13.04 rhythmbox also stopped showing the performance year, which is still there in the metadata. This is a separate bug that has not been fixed in 13.10 :( --- ApportVersion:
Re: [Bug 1247259] Re: rhythmbox unresponsive every few seconds
On Mon, Apr 7, 2014 at 11:10 AM, Walter Garcia-Fontes walter.gar...@upf.edu wrote: Sorry, this was not a generic message. I'm a user as yourself, and Sorry, I'm tired of seeing bugs closed without any action on every new release. I thought it was such an effort. upstream they don't even open the bug report if there is not a stacktrace to check. This is the reason why they will never fix it, and the reason why I'm actively looking for alternatives. A lot of time ago I stopped thinking that rhythmbox would ever get fixed. No stacktrace here, just 2 minutes unresponsive on every focus change on a Core I7. Regards Santiago -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1247259 Title: rhythmbox unresponsive every few seconds Status in “rhythmbox” package in Ubuntu: Incomplete Bug description: Since I updated to 13.10, rhythmbox is not usable. After it starts, it freezes on every mouse click on different panes, sometimes it recovers, sometimes it stays apparently forever gray, and the dialog to wait or kill appears. When I arrive to the point where I can play, it remains unresponsive and I cannot stop playing or switch songs. This was not happening since I upgraded from 13.04 last week. Example output when I start it from command line: $ rhythmbox (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped at this stage it has remained gray and unresponsive for more than 2 minutes and I don't know how to play music. I have a big collection (almost 2 songs), and rhythmbox has remained my player of choice for its ability to handle this, but it is slowly changing (in 13.04 it was very slow when it loosed and regained focus, like 10 seconds at 100% CPU every time. Now it seems to last forever with 100% CPU... I can help with debugging, I'm a software developer. The machine where I run it right now is an i7 with 4 cores, 8GB RAM and a fast SSD, so performance should not be an issue. The same music collection was way faster in 12.04 or 12.10... In 13.04 rhythmbox also stopped showing the performance year, which is still there in the metadata. This is a separate bug that has not been fixed in 13.10 :( --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10
[Bug 1247259] LogAlsaMixer.txt
apport information ** Attachment added: LogAlsaMixer.txt https://bugs.launchpad.net/bugs/1247259/+attachment/4068809/+files/LogAlsaMixer.txt -- 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/1247259 Title: rhythmbox unresponsive every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1247259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247259] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1247259/+attachment/4068811/+files/XorgLog.txt -- 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/1247259 Title: rhythmbox unresponsive every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1247259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247259] Re: rhythmbox unresponsive every few seconds
apport information ** Tags added: apport-collected saucy third-party-packages ** Description changed: Since I updated to 13.10, rhythmbox is not usable. After it starts, it freezes on every mouse click on different panes, sometimes it recovers, sometimes it stays apparently forever gray, and the dialog to wait or kill appears. When I arrive to the point where I can play, it remains unresponsive and I cannot stop playing or switch songs. This was not happening since I upgraded from 13.04 last week. Example output when I start it from command line: $ rhythmbox (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped at this stage it has remained gray and unresponsive for more than 2 minutes and I don't know how to play music. I have a big collection (almost 2 songs), and rhythmbox has remained my player of choice for its ability to handle this, but it is slowly changing (in 13.04 it was very slow when it loosed and regained focus, like 10 seconds at 100% CPU every time. Now it seems to last forever with 100% CPU... I can help with debugging, I'm a software developer. The machine where I run it right now is an i7 with 4 cores, 8GB RAM and a fast SSD, so performance should not be an issue. The same music collection was way faster in 12.04 or 12.10... - In 13.04 rhythmbox also stopped showing the performance year, which is - still there in the metadata. This is a separate bug that has not been - fixed in 13.10 :( + In 13.04 rhythmbox also stopped showing the performance year, which is still there in the metadata. This is a separate bug that has not been fixed in 13.10 :( + --- + ApportVersion: 2.12.5-0ubuntu2.2 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + InstallationDate: Installed on 2013-07-23 (256 days ago) + InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) + MarkForUpload: True + Package: rhythmbox 2.99.1-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 + Tags: third-party-packages saucy + Uname: Linux 3.11.0-19-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-10-29 (158 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1247259/+attachment/4068807/+files/Dependencies.txt -- You received this bug
[Bug 1247259] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1247259/+attachment/4068810/+files/ProcEnviron.txt -- 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/1247259 Title: rhythmbox unresponsive every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1247259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247259] GstreamerVersions.txt
apport information ** Attachment added: GstreamerVersions.txt https://bugs.launchpad.net/bugs/1247259/+attachment/4068808/+files/GstreamerVersions.txt -- 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/1247259 Title: rhythmbox unresponsive every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1247259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251986] [NEW] package gdm 3.8.4-0ubuntu2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 128
Public bug reported: No clue, sessions stopped working after a reboot following an update, with lots of errors that I guess are those reported now. After login I got black screen with a white mouse and nothing else. Sometimes errors (Cancel Report bug) windows without decoration... It started working again after I updated, dist-upgrades installed lxde and chose it as a session. Bad breakin completely X sessions, I had no way to get network access or research/report the errors ProblemType: Package DistroRelease: Ubuntu 13.10 Package: gdm 3.8.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 AptOrdering: gnome: Purge gnome-core: Purge gdm: Purge Architecture: amd64 Date: Sat Nov 16 16:53:07 2013 DuplicateSignature: package:gdm:3.8.4-0ubuntu2:subprocess installed post-removal script returned error exit status 128 ErrorMessage: subprocess installed post-removal script returned error exit status 128 InstallationDate: Installed on 2013-07-23 (117 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gdm Title: package gdm 3.8.4-0ubuntu2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 128 UpgradeStatus: Upgraded to saucy on 2013-10-29 (18 days ago) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1251986 Title: package gdm 3.8.4-0ubuntu2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1251986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247259] [NEW] rhythmbox unresponsive every few seconds
Public bug reported: Since I updated to 13.10, rhythmbox is not usable. After it starts, it freezes on every mouse click on different panes, sometimes it recovers, sometimes it stays apparently forever gray, and the dialog to wait or kill appears. When I arrive to the point where I can play, it remains unresponsive and I cannot stop playing or switch songs. This was not happening since I upgraded from 13.04 last week. Example output when I start it from command line: $ rhythmbox (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652b00 is mapped but visible child GtkScrollbar 0x1786220 is not mapped (rhythmbox:12664): Gtk-WARNING **: RBPropertyView 0x1652ce0 is mapped but visible child GtkScrollbar 0x17865c0 is not mapped at this stage it has remained gray and unresponsive for more than 2 minutes and I don't know how to play music. I have a big collection (almost 2 songs), and rhythmbox has remained my player of choice for its ability to handle this, but it is slowly changing (in 13.04 it was very slow when it loosed and regained focus, like 10 seconds at 100% CPU every time. Now it seems to last forever with 100% CPU... I can help with debugging, I'm a software developer. The machine where I run it right now is an i7 with 4 cores, 8GB RAM and a fast SSD, so performance should not be an issue. The same music collection was way faster in 12.04 or 12.10... In 13.04 rhythmbox also stopped showing the performance year, which is still there in the metadata. This is a separate bug that has not been fixed in 13.10 :( ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- 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/1247259 Title: rhythmbox unresponsive every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1247259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247259] Re: rhythmbox unresponsive every few seconds
The run I'm describing eventually ungrayed itself, after about 5 minutes. I then pressed play, and I was unable to stop or change tracks. I had to mute the sound and wait, as it was still playing. After several minutes with the UI frozen I press the window close button, and the Force close window appeared. I force-closed it and it just printed: Killed as additional output. Completely unusable. Is there another music player that will take .m3u lists? I need it real soon, or I'll be forced to DJ with my android phone :( -- 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/1247259 Title: rhythmbox unresponsive every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1247259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1070766] Re: Sound preferences have unbounded width and get unusable with long-named sound cards
I think it is gnome-control-center, but I'm really not sure which component it is... ** Package changed: ubuntu = gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1070766 Title: Sound preferences have unbounded width and get unusable with long- named sound cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
