[Desktop-packages] [Bug 2042859] Re: [snap] Firefox snap cannot use kerberos authentication
In bug #1970182 there is a workaround for the issue: adding something
similar to
default_ccache_name = FILE:/home/%{username}/krb5cc
under [libdefaults] will make the ticket store visible to firefox and,
thus, fix the authentication.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2042859
Title:
[snap] Firefox snap cannot use kerberos authentication
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Applies to Ubuntu 22.04 and any other versions where firefox runs as snap:
firefox:
Installed: 1:1snap1-0ubuntu2
Candidate: 1:1snap1-0ubuntu2
Version table:
*** 1:1snap1-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/statu
You can configure Firefox to use negotiate authentication with kerberos.
https://people.redhat.com/mikeb/negotiate/ on how to do this.
To use kerberos auth, Firefox needs to read kerberos ticket cache, default
to /tmp/krb5cc_${id -u}. Since Firefox runs as a snap in 22.04, and possibly
other versions, it cannot read this cache, and thus cannot use kerberized
authentication.
Firefox installed as native application works as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2042859/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908999] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
Not at the time. I found a way to have a proper apt package installed and I want to live without snaps as much as possible, so now I have $ apt policy chromium-browser chromium-browser: Installed: 87.0.4280.88-0ubuntu0.20.04.1.1~vaapi Candidate: 87.0.4280.88-0ubuntu0.20.04.1.1~vaapi Version table: 1:85.0.4183.83-0ubuntu0.20.04.2 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages *** 87.0.4280.88-0ubuntu0.20.04.1.1~vaapi 1337 1337 http://ppa.launchpad.net/xalt7x/chromium-deb-vaapi/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu focal/universe amd64 Packages instead of the fake package that installs a snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1908999 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I uninstalled the chromium snap because it was downloading an upgrade and failing daily. After I did it I tried to install it again (with apt) and it tried to install a snap and failed, sending me here. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 22 11:50:14 2020 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-11 (1106 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-10 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908999] [NEW] package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
Public bug reported: I uninstalled the chromium snap because it was downloading an upgrade and failing daily. After I did it I tried to install it again (with apt) and it tried to install a snap and failed, sending me here. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 22 11:50:14 2020 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-11 (1106 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-10 (72 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1908999 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: I uninstalled the chromium snap because it was downloading an upgrade and failing daily. After I did it I tried to install it again (with apt) and it tried to install a snap and failed, sending me here. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 22 11:50:14 2020 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-11 (1106 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-10 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894073] [NEW] Duplicity fails backups with message "SHA1 hash mismatch for file..." every single time
Public bug reported: Backup has been going on ok since some days ago. Then the backups started failing with message: Invalid data - SHA1 hash mismatch for file: duplicity-inc.20200828T014540Z.to.20200829T012824Z.vol1.difftar.gz Calculated hash: 06f2c3af5c64b989db2507d842a64e19d1cb7206 Manifest hash: 77788b1c0808968b82904e3b0f688143fbebe1d0 Without any way offered to take an action to proceed. ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Package changed: duplicity (Ubuntu) => deja-dup (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1894073 Title: Duplicity fails backups with message "SHA1 hash mismatch for file..." every single time Status in deja-dup package in Ubuntu: New Bug description: Backup has been going on ok since some days ago. Then the backups started failing with message: Invalid data - SHA1 hash mismatch for file: duplicity-inc.20200828T014540Z.to.20200829T012824Z.vol1.difftar.gz Calculated hash: 06f2c3af5c64b989db2507d842a64e19d1cb7206 Manifest hash: 77788b1c0808968b82904e3b0f688143fbebe1d0 Without any way offered to take an action to proceed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1894073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871757] Re: Duplicity fails backups at the end every time
apport information ** Tags added: apport-collected bionic ** Description changed: Backup seems to progress well (it takes a long time) and ends up with this error: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1472, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 728, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 764, in get_fileobj_iter backup_set.volume_name_dict[vol_num], KeyError: 8 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2017-12-11 (849 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + Package: duplicity 0.7.17-0ubuntu1.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 + Tags: bionic + Uname: Linux 5.3.0-42-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-06-05 (673 days ago) + UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1871757/+attachment/5350258/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1871757 Title: Duplicity fails backups at the end every time Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Backup seems to progress well (it takes a long time) and ends up with this error: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1472, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 728, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 764, in get_fileobj_iter backup_set.volume_name_dict[vol_num], KeyError: 8 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-11 (849 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: duplicity 0.7.17-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus:
[Desktop-packages] [Bug 1871757] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1871757/+attachment/5350260/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1871757 Title: Duplicity fails backups at the end every time Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Backup seems to progress well (it takes a long time) and ends up with this error: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1472, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 728, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 764, in get_fileobj_iter backup_set.volume_name_dict[vol_num], KeyError: 8 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-11 (849 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: duplicity 0.7.17-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-05 (673 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1871757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871757] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1871757/+attachment/5350259/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1871757 Title: Duplicity fails backups at the end every time Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Backup seems to progress well (it takes a long time) and ends up with this error: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1472, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 728, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 764, in get_fileobj_iter backup_set.volume_name_dict[vol_num], KeyError: 8 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-11 (849 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: duplicity 0.7.17-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-05 (673 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1871757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871757] [NEW] Duplicity fails backups at the end every time
Public bug reported: Backup seems to progress well (it takes a long time) and ends up with this error: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1472, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 728, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 764, in get_fileobj_iter backup_set.volume_name_dict[vol_num], KeyError: 8 ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1871757 Title: Duplicity fails backups at the end every time Status in duplicity package in Ubuntu: New Bug description: Backup seems to progress well (it takes a long time) and ends up with this error: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1472, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 728, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 764, in get_fileobj_iter backup_set.volume_name_dict[vol_num], KeyError: 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1871757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a fresh installation of 18.04. After entering the password and pressing enter, it takes 5 seconds for the lock screen to disappear. This problem didn't happen on the same machine with 16.04 or 14.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 15:31:48 2018 InstallationDate: Installed on 2018-05-04 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714180] [NEW] PCI/internal sound card disconnected is still selected and thus sound is missing
Public bug reported: After I connect the docking station and switch to it, everthing works ok with the HDMI device of my external monitor connected to it. But after disconnecting sound stops working until I open the sound preferences and select the only sound device, i.e. the HDMI sound remains selected after the device is no longer there. While I'm guessing it might be convenient, in the absence of an existing card, to keep it selected so that when I plug back the docking station the sound is restored, sound should keep playing when the selected device disappears. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.12.8-041208-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: sgala 3744 F...m pulseaudio /dev/snd/pcmC1D0p: sgala 3744 F...m pulseaudio /dev/snd/controlC1: sgala 3744 F pulseaudio /dev/snd/controlC0: sgala 3744 F pulseaudio CurrentDesktop: GNOME Date: Thu Aug 31 09:18:13 2017 InstallationDate: Installed on 2016-11-13 (290 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to zesty on 2017-04-23 (129 days ago) dmi.bios.date: 03/17/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.20 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z30-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.20:bd03/17/2016:svnTOSHIBA:pnPORTEGEZ30-B:pvrPT253E-01001MCE:rvnTOSHIBA:rnPORTEGEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: PORTEGE Z30-B dmi.product.version: PT253E-01001MCE dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1714180 Title: PCI/internal sound card disconnected is still selected and thus sound is missing Status in alsa-driver package in Ubuntu: New Bug description: After I connect the docking station and switch to it, everthing works ok with the HDMI device of my external monitor connected to it. But after disconnecting sound stops working until I open the sound preferences and select the only sound device, i.e. the HDMI sound remains selected after the device is no longer there. While I'm guessing it might be convenient, in the absence of an existing card, to keep it selected so that when I plug back the docking station the sound is restored, sound should keep playing when the selected device disappears. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.12.8-041208-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: sgala 3744 F...m pulseaudio /dev/snd/pcmC1D0p: sgala 3744 F...m pulseaudio /dev/snd/controlC1: sgala 3744 F pulseaudio /dev/snd/controlC0: sgala 3744 F pulseaudio CurrentDesktop: GNOME Date: Thu Aug 31 09:18:13 2017 InstallationDate: Installed on 2016-11-13 (290 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to zesty on 2017-04-23 (129 days ago) dmi.bios.date: 03/17/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.20 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z30-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.20:bd03/17/2016:svnTOSHIBA:pnPORTEGEZ30-B:pvrPT253E-01001MCE:rvnTOSHIBA:rnPORTEGEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: PORTEGE Z30-B dmi.product.version: PT253E-01001MCE dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1714180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697646] Re: Long-running ping command leads to 100% CPU usage
This happens (or used to happen) also in 16.04.2 (current). I paste here
a couple of evidences (17.04):
$ ps auxwww | grep ping
sgala12545 96.5 0.0 20592 1020 pts/2R+ 13:18 118:36 ping
192.168.25.96
(...)
$ sudo strace -p 12545
(...)
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
recvmsg(3, 0x7ffe0a5d0b00, MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLERR}], 1, 164) = 1 ([{fd=3, revents=POLLERR}])
(...)
The ping is taking 100% CPU. After I killed the process, one can see
that the command line was a plain "ping 192.168.25.96"
About ping version:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.04
DISTRIB_CODENAME=zesty
DISTRIB_DESCRIPTION="Ubuntu 17.04"
$ dpkg -l $(dpkg-query -S $(which ping) | awk -F: '{print $1}')
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-=-=-=-===
ii iputils-ping 3:20161105-1ubuntu2 amd64
Tools to test the reachability of network hosts
I have also seen this going on with Ubuntu 16.04.2 LTS fully patched. I
use something like ((ping -i 60 -B [address] >& /dev/null )&)& as a poor
man's keepalive, and it jumps systematically to 100% CPU after one or
two days.
Versions for 16.04.2:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
$ dpkg -l $(dpkg-query -S $(which ping) | awk -F: '{print $1}')
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-=-=-=-===
ii iputils-ping 3:20121221-5ubuntu2 amd64
Tools to test the reachability of network hosts
Note there has been some time since I last observed the bug in 16.04.2,
but I have just found my laptop spinning before I decided to look for
the bug and post here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1697646
Title:
Long-running ping command leads to 100% CPU usage
Status in iputils package in Ubuntu:
Confirmed
Bug description:
Since I've updated my laptop to Ubuntu MATE 17.04, I notice ping
sometimes gets into a runaway mode.
I'm on a shaky Wi-Fi so to monitor connectivity I usually have a long
running ping command against google's DNS server:
> ping -s16 8.8.4.4
Often, after leaving it for a while, I notice screaming vents and htop
then shows the ping process consuming 100% of one CPU. It will stay
like that until ping is killed.
I'm not sure how to troubleshoot this issue, can someone recommend a
protocol?
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: iputils-ping 3:20161105-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Tue Jun 13 11:11:26 2017
InstallationDate: Installed on 2017-04-05 (69 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications
[Desktop-packages] [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 Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1312780 Title: Floating menu mostly disappears in fullscreen mode Status in vinagre package in Ubuntu: Confirmed Status in vinagre package in Fedora: Unknown Bug description: When going into full screen mode on Ubuntu 14.04 (connecting to a Ubuntu 14.04 running Unity and x11vnc), the floating menu at the top of the screen is mostly inaccessible. I say mostly because you can wave your mouse around at the top center of the screen where the menu should appear and you will occasionally see something flash up for a split second. If you click continuously while waving the mouse around, you will occasionally hit a button. Here are some more details: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center vinagre: Installed: 3.10.2-0ubuntu1 Candidate: 3.10.2-0ubuntu1 Version table: *** 3.10.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Menu would appear at the top of the full screen window or at least when mouse hovers at top of full screen window. 4) What happened instead Occasional split second pop up of window and tool tips. Can also click buttons if you are lucky. Please let me know if there are logs I can pull. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1312780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1559601] [NEW] network manager rfkills unmanaged wireless devices when "Enabled Wifi" is set to disabled
Public bug reported: I needed to set network manager to avoid managing a given wireless interface, so that I can set it up with static IP + dhcpd + hostapd. When I disable Wireless the phy rfkill associated to it gets "softblocked" on boot, so I need to manually "rfkill unblock phy" and ifup, restart all services for the setup to work. When wifi is set to "Enable Wifi" it all works correctly. My guess is that network-manager rfkill even unmanaged devices when wifi is disabled, but I have not checked the source code. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1559601 Title: network manager rfkills unmanaged wireless devices when "Enabled Wifi" is set to disabled Status in network-manager package in Ubuntu: New Bug description: I needed to set network manager to avoid managing a given wireless interface, so that I can set it up with static IP + dhcpd + hostapd. When I disable Wireless the phy rfkill associated to it gets "softblocked" on boot, so I need to manually "rfkill unblock phy" and ifup, restart all services for the setup to work. When wifi is set to "Enable Wifi" it all works correctly. My guess is that network-manager rfkill even unmanaged devices when wifi is disabled, but I have not checked the source code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1559601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
I'm seeing this very same bug on a fresh install on a Asus A53J, quite similar hardware (Elantech, NVIDIA Corporation GF119M [GeForce GT 520M] (rev a1)) Any possibility to have it solved without loosing features? It is very annoying see the touchpad freeze every few minutes. Removing the option to deactivate while typing reduces the freeze frequency, but I NEED the two finger scrolling for productivity, and this one makes it freeze less often, but still enough... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: Using Asus N43SL laptop as an example, with nvidia-prime installed, so the dedicated NVIDIA graphics card (GT 540m) is in use, once in a while, my screen will freeze when I use my touchpad. WORKAROUND: Use USB mouse. WORKAROUND: Uninstall nvidia-prime and use integrated graphics. WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log The following upstream report has a patch that addresses this issue: https://bugs.freedesktop.org/show_bug.cgi?id=86288 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1315494] [NEW] package texlive-base 2013.20140215-1 failed to install/upgrade: intentando sobreescribir `/usr/share/texmf/web2c/texmf.cnf', que está también en el paquete tex-c
Public bug reported: no clue what happened ProblemType: Package DistroRelease: Ubuntu 14.04 Package: texlive-base 2013.20140215-1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 Date: Fri May 2 18:26:56 2014 DuplicateSignature: package:texlive-base:2013.20140215-1:intentando sobreescribir `/usr/share/texmf/web2c/texmf.cnf', que está también en el paquete tex-common 2.10 ErrorMessage: intentando sobreescribir `/usr/share/texmf/web2c/texmf.cnf', que está también en el paquete tex-common 2.10 InstallationDate: Installed on 2010-08-05 (1366 days ago) InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 (20100429.4) PackageArchitecture: all SourcePackage: texlive-base Title: package texlive-base 2013.20140215-1 failed to install/upgrade: intentando sobreescribir `/usr/share/texmf/web2c/texmf.cnf', que está también en el paquete tex-common 2.10 UpgradeStatus: Upgraded to trusty on 2014-05-01 (1 days ago) mtime.conffile..etc.texmf.dvipdfmx.dvipdfmx.cfg: 2014-05-02T18:26:58.474391 ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty ubuntu-une -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1315494 Title: package texlive-base 2013.20140215-1 failed to install/upgrade: intentando sobreescribir `/usr/share/texmf/web2c/texmf.cnf', que está también en el paquete tex-common 2.10 Status in “texlive-base” package in Ubuntu: New Bug description: no clue what happened ProblemType: Package DistroRelease: Ubuntu 14.04 Package: texlive-base 2013.20140215-1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 Date: Fri May 2 18:26:56 2014 DuplicateSignature: package:texlive-base:2013.20140215-1:intentando sobreescribir `/usr/share/texmf/web2c/texmf.cnf', que está también en el paquete tex-common 2.10 ErrorMessage: intentando sobreescribir `/usr/share/texmf/web2c/texmf.cnf', que está también en el paquete tex-common 2.10 InstallationDate: Installed on 2010-08-05 (1366 days ago) InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 (20100429.4) PackageArchitecture: all SourcePackage: texlive-base Title: package texlive-base 2013.20140215-1 failed to install/upgrade: intentando sobreescribir `/usr/share/texmf/web2c/texmf.cnf', que está también en el paquete tex-common 2.10 UpgradeStatus: Upgraded to trusty on 2014-05-01 (1 days ago) mtime.conffile..etc.texmf.dvipdfmx.dvipdfmx.cfg: 2014-05-02T18:26:58.474391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1315494/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to rhythmbox in Ubuntu. 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 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
[Desktop-packages] [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 Desktop Packages, which is subscribed to rhythmbox in Ubuntu. 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 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 To manage
Re: [Desktop-packages] [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: [Desktop-packages] [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: [Desktop-packages] [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
[Desktop-packages] [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 Desktop Packages, which is subscribed to rhythmbox in Ubuntu. 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 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 To manage notifications about this bug
[Desktop-packages] [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 Desktop Packages, which is subscribed to rhythmbox in Ubuntu. 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 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 To manage notifications about this bug go to:
[Desktop-packages] [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 Desktop Packages, which is subscribed to rhythmbox in Ubuntu. 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 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 To manage notifications about this bug go to:
[Desktop-packages] [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 Desktop Packages, which is subscribed to rhythmbox in Ubuntu. 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 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 To manage notifications about this bug go to:
[Desktop-packages] [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
[Desktop-packages] [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 Desktop Packages, 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 Status in “gdm” package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1251986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1247259 Title: rhythmbox unresponsive every few seconds Status in “rhythmbox” package in Ubuntu: New 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
[Desktop-packages] [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 Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1247259 Title: rhythmbox unresponsive every few seconds Status in “rhythmbox” package in Ubuntu: New 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 :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1247259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1100190] Re: I/O Error while opening file from WebDAV over GVFS from Nautilus
Note: I am seeing the same bug, but in a slightly different setup: * Ubuntu 13.04 up to date * The server is jackrabbit stable * If I mount it from nautilus with connect to server it fails most I/O operations with I/O Error, including things like 'ls -l', as stat of each node fails. * If I mount it as sudo mkdir /media/jackrepo; sudo mount -t davfs 'http://localhost:8080/repository/default' /media/jackrepo is works like a charm, including stat (ls -l) or opening fragments of a video So I don't think the bug is at Libreoffice, but at the gvfs layer instead -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1100190 Title: I/O Error while opening file from WebDAV over GVFS from Nautilus Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Problem description: Error when opening a file from Nautilus with LibreOffice when the file is WebDAV mounted with GVFS. The Same file can be opened from the same location from within LibreOffice, with the Open File Dialogue. Then you get asked for the Username and Password and Libreoffice seems to access the file directly over HTTP. Steps to reproduce: 1. Mount a DAV Folder with Nautilus. URL in my Case: dav://admin@10.1.10.58:8080/alfresco/webdav/Sites/puzzletest/documentLibrary/Alfresco%20WebDAV%20Test/ 2. Open a file with LibreOffice by doubleclick or context menu from Nautilus. 4. Error occurs. Exact message: (-) «General input/output error while accessing /home/pgassmann/.gvfs/WebDAV\ als\ admin\ auf\ 10.1.10.58%3A8080/Sites/puzzletest/documentLibrary/Alfresco\ WebDAV\ Test/Neu.odt.» [OK] Working Variant: 1. = 1. above 2. Start LibreOffice 3. Open File dialogue from LibreOffice 4. Select the same file and click Open. 5. LibreOffice Dialogue: Authentication Required, Enter user name and password for: Alfresco DAV Server on 10.1.10.58 6. Enter Username and password, click OK 7. File opens correctly LibreOffice Version: 3.5.2-2ubuntu1 Involved Software: LibreOffice, Nautilus, GVFS, Alfresco Current behavior: Opening file from Nautilus causes Error, Opening from LibreOffice Open File dialogue asks for credentials and works correctly Expected behavior: Opening from Nautilus works. Opening from Open File dialog works without asking for credentials. Attachment: strace log from following actions: LANG=C libreoffice --strace successfully Open File from LibreOffice dialogue. Trying to open file from Nautilus. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice 1:3.5.4-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Uname: Linux 3.2.0-36-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Jan 16 10:05:05 2013 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-05-22 (238 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1100190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 549904] Re: Help cannot be loaded: Error 500 Unable to compile class for JSP
I'm seeing this error in Raring (13.04). It is due to the following upstream bug: http://webcache.googleusercontent.com/search?q=cache:3zlSG6lQXTAJ:https://issues.apache.org/bugzilla/show_bug.cgi%3Fid%3D54440%26quot%3B%26gt%3Bissue+cd=1hl=esct=clnkgl=es -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/549904 Title: Help cannot be loaded: Error 500 Unable to compile class for JSP Status in “eclipse” package in Ubuntu: Fix Released Status in “eclipse” source package in Lucid: Confirmed Status in “eclipse” package in Debian: Fix Released Bug description: Binary package hint: eclipse Reliably reproducible. Steps to reproduce: 1) Open Eclipse 2) Go to Help - Help Contents Expected result: Help content is loaded Actual result: HTTP ERROR 500 Problem accessing /help/index.jsp. Reason: Unable to compile class for JSP: Used SW: Ubuntu 10.04, amd64 openjdk-6-jdk: 6b18~pre3-0ubuntu1 It's regression in Eclipse 3.5.2 (Ubuntu package). I didn't have this issue in 3.5.1 (neither in Karmic nor in Lucid). I also tested standalone package Eclipse 3.5.2 from http://www.eclipse.org/downloads/ and it works well too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/549904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 549904] Re: Help cannot be loaded: Error 500 Unable to compile class for JSP
I forgot to say this is happening to me with $ LC_ALL=C dpkg-query -l eclipse* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===-=== ii eclipse 3.8.1-1ubuntu1 all Extensible Tool Platform and Java IDE un eclipse-common-nlsnone (no description available) un eclipse-ecj none (no description available) ii eclipse-egit 2.1.0-1 all Eclipse Team provider for the Git version contr ii eclipse-jdt 3.8.1-1ubuntu1 all Eclipse Java Development Tools (JDT) un eclipse-jdt-gcj none (no description available) un eclipse-jgit none (no description available) ii eclipse-pde 3.8.1-1ubuntu1 amd64 Eclipse Plug-in Development Environment (PDE) un eclipse-pde-gcj none (no description available) ii eclipse-platform 3.8.1-1ubuntu1 amd64 Eclipse platform without development plug-ins un eclipse-platform-comm none (no description available) ii eclipse-platform-data 3.8.1-1ubuntu1 all Eclipse platform without development plug-ins ( un eclipse-platform-gcj none (no description available) un eclipse-platform-nls none (no description available) un eclipse-plugin-cvsnone (no description available) ii eclipse-rcp 3.8.1-1ubuntu1 amd64 Eclipse Rich Client Platform (RCP) un eclipse-rcp-gcj none (no description available) un eclipse-sourcenone (no description available) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/549904 Title: Help cannot be loaded: Error 500 Unable to compile class for JSP Status in “eclipse” package in Ubuntu: Fix Released Status in “eclipse” source package in Lucid: Confirmed Status in “eclipse” package in Debian: Fix Released Bug description: Binary package hint: eclipse Reliably reproducible. Steps to reproduce: 1) Open Eclipse 2) Go to Help - Help Contents Expected result: Help content is loaded Actual result: HTTP ERROR 500 Problem accessing /help/index.jsp. Reason: Unable to compile class for JSP: Used SW: Ubuntu 10.04, amd64 openjdk-6-jdk: 6b18~pre3-0ubuntu1 It's regression in Eclipse 3.5.2 (Ubuntu package). I didn't have this issue in 3.5.1 (neither in Karmic nor in Lucid). I also tested standalone package Eclipse 3.5.2 from http://www.eclipse.org/downloads/ and it works well too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/549904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in “gnome-control-center” package in Ubuntu: New Bug description: When I added a USB card that has a long name, the preferences window got unusable due to having no limit on the device list, on the left hand side, and the Configuration fof... pane on the right side. Overall I get a window that can't be resized and is ~1500 pixels wide, so diffult and tricky to use... :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
