[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
This bug affects me on 24.04 noble too. It did not on 23.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019498] Re: Unable to connect to Google in GCC
Here is the output: $ journalctl -f May 19 21:05:13 nitro gnome-control-c[5879]: Error showing account: Child process exited with code 1 May 19 21:06:07 nitro org.gnome.Settings.desktop[5921]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialogue was dismissed May 19 21:06:07 nitro xdg-desktop-por[2266]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info May 19 21:06:19 nitro kernel: WebKitWebProces[6157]: segfault at 5564481e0ac8 ip 5564481e0ac8 sp 7ffc22016728 error 14 likely on CPU 2 (core 1, socket 0) May 19 21:06:19 nitro kernel: Code: Unable to access opcode bytes at 0x5564481e0a9e. May 19 21:07:39 nitro systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... May 19 21:07:39 nitro systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. May 19 21:07:39 nitro systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. May 19 21:07:39 nitro systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. May 19 21:07:41 nitro gnome-control-c[5879]: Error showing account: Child process exited with code 1 May 19 21:07:49 nitro org.gnome.Settings.desktop[6127]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialogue was dismissed May 19 21:07:50 nitro xdg-desktop-por[2266]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info May 19 21:08:01 nitro kernel: WebKitWebProces[6296]: segfault at 55ce66a0a8da ip 55ce66a0a8da sp 7ffce52facf8 error 14 likely on CPU 0 (core 0, socket 0) May 19 21:08:01 nitro kernel: Code: Unable to access opcode bytes at 0x55ce66a0a8b0. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2019498 Title: Unable to connect to Google in GCC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2019498] Re: Unable to connect to Google in GCC
Hi, I'm away with work for the rest of this week, so I'll do this on Saturday for you. On Tue, 16 May 2023 at 10:59, Sebastien Bacher <2019...@bugs.launchpad.net> wrote: > Thank you for your bug report. Could you do > $ journalctl -f > then trigger the bug and see if any error is printed in the journal log? > > ** Changed in: gnome-control-center (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2019498 > > Title: > Unable to connect to Google in GCC > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > At installation of Ubuntu 23.04, and subsequently, when trying to use > Gnome Control Center to connect my Google account in Online Accounts, > I am able to enter my email address, but then the screen freezes in > the transition to the screen where I'd enter my password. > > This happens every time. > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: gnome-control-center 1:44.0-1ubuntu5 > ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 > Uname: Linux 6.2.0-20-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.26.1-0ubuntu2 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Sun May 14 12:44:51 2023 > InstallationDate: Installed on 2023-05-14 (0 days ago) > InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 > (20230417) > SourcePackage: gnome-control-center > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center; > component=main; status=Incomplete; importance=Undecided; assignee=None; > Launchpad-Bug-Tags: amd64 apport-bug lunar > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: juglugs1974 seb128 > Launchpad-Bug-Reporter: Mark Smith (juglugs1974) > Launchpad-Bug-Modifier: Sebastien Bacher (seb128) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: juglugs1974 > > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2019498 Title: Unable to connect to Google in GCC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2019498] [NEW] Unable to connect to Google in GCC
Public bug reported: At installation of Ubuntu 23.04, and subsequently, when trying to use Gnome Control Center to connect my Google account in Online Accounts, I am able to enter my email address, but then the screen freezes in the transition to the screen where I'd enter my password. This happens every time. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 14 12:44:51 2023 InstallationDate: Installed on 2023-05-14 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "Screenshot of frozen online accounts screen" https://bugs.launchpad.net/bugs/2019498/+attachment/5672961/+files/20230514OnlineAccountsBug.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2019498 Title: Unable to connect to Google in GCC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2011313] Re: gnome-control-center crashes after launch
I can confirm that this issue is now resolved On Thu, 16 Mar 2023 at 12:15, Mark Smith <2011...@bugs.launchpad.net> wrote: > Awesome! Thank you for your help on this. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2011313 > > Title: > gnome-control-center crashes after launch > > Status in gnome-control-center package in Ubuntu: > Fix Released > > Bug description: > I had successfully opened settings and used it to change some of the > desktop options (size of the docker icons, etc.). > Then I clicked on "Users" and ubuntu-settings crashed. > Since then, I am unable to open ubuntu-settings - it will open and flash > up on the screen before crashing. > This has continued even after restarting the machine a few times. > > ubuntu-settings version: 23.04.2 500 > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: ubuntu-settings 23.04.2 > ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 > Uname: Linux 6.1.0-16-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.26.0-0ubuntu2 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Sat Mar 11 18:33:16 2023 > InstallationDate: Installed on 2023-03-11 (0 days ago) > InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) > PackageArchitecture: all > ProcEnviron: >LANG=en_US.UTF-8 >PATH=(custom, no user) >SHELL=/bin/bash >TERM=xterm-256color >XDG_RUNTIME_DIR= > SourcePackage: ubuntu-settings > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center; > component=main; status=Fix Released; importance=High; assignee= > jeremy.bi...@canonical.com; > Launchpad-Bug-Tags: amd64 apport-bug lunar > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: fthx gunnarhj juglugs1974 starkus > Launchpad-Bug-Reporter: Mark Smith (juglugs1974) > Launchpad-Bug-Modifier: Mark Smith (juglugs1974) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: juglugs1974 > > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
Awesome! Thank you for your help on this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
Ahaha so ubuntu-settings was rolled out into Lunar overnight NOT gnome-control-settings. I had forgotten that I had originally tagged the wrong app - in fact, I'm not going to have to go and look up the difference between them :) So - false alarm - It's not ready yet :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2011313] Re: gnome-control-center crashes after launch
Yeah, I think that it's not worth fixing in the alpha version. Do you know when 1:44~rc will be merged? Thank you for your help with this bug! It is much appreciated :) On Sun, 12 Mar 2023 at 22:00, Gunnar Hjalmarsson <2011...@bugs.launchpad.net> wrote: > Yeah.. That "Couldn't get locale for language: (null)" warning comes > from a patch which I wrote initially, and first I feared that the > segfault is related to that. But it's not. I committed a fix which will > get rid of the warning in this situation: > > https://salsa.debian.org/gnome-team/gnome-control- > center/-/commit/53e9a9a2 > > But it still segfaults. For some reason it fails to fetch the user data > properly. > > My thought is that since the problem seems to be gone in g-c-c 1:44~rc, > it's not worth it to figure out why exactly the alpha version crashes. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2011313 > > Title: > gnome-control-center crashes after launch > > Status in gnome-control-center package in Ubuntu: > In Progress > > Bug description: > I had successfully opened settings and used it to change some of the > desktop options (size of the docker icons, etc.). > Then I clicked on "Users" and ubuntu-settings crashed. > Since then, I am unable to open ubuntu-settings - it will open and flash > up on the screen before crashing. > This has continued even after restarting the machine a few times. > > ubuntu-settings version: 23.04.2 500 > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: ubuntu-settings 23.04.2 > ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 > Uname: Linux 6.1.0-16-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.26.0-0ubuntu2 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Sat Mar 11 18:33:16 2023 > InstallationDate: Installed on 2023-03-11 (0 days ago) > InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230310) > PackageArchitecture: all > ProcEnviron: >LANG=en_US.UTF-8 >PATH=(custom, no user) >SHELL=/bin/bash >TERM=xterm-256color >XDG_RUNTIME_DIR= > SourcePackage: ubuntu-settings > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center; > component=main; status=In Progress; importance=High; assignee= > jeremy.bi...@canonical.com; > Launchpad-Bug-Tags: amd64 apport-bug lunar > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: gunnarhj juglugs1974 starkus > Launchpad-Bug-Reporter: Mark Smith (juglugs1974) > Launchpad-Bug-Modifier: Gunnar Hjalmarsson (gunnarhj) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: juglugs1974 > > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
That command: gsettings reset org.gnome.ControlCenter last-panel Doesn't work for me - I get: No such schema “org.gnome.ControlCenter” -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
And thanks for the tip ref running it without going to "Users" :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011313] Re: gnome-control-center crashes after launch
As a data point, when I run gnome-control-center from the terminal I get a "Segmentation Error" and core dump. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011313 Title: gnome-control-center crashes after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976498] Re: nautilus causes gvfsd-trash 'Too many files open' error and fills syslog
Not sure this was actually a bug. I reinstalled my system anyway so the issue went away. Now marked as invalid ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1976498 Title: nautilus causes gvfsd-trash 'Too many files open' error and fills syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1976498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976498] Re: DING causes gvfsd 'Too many files open' error and fills syslog
Changed from ding to nautilus after reading about nautilus gvfsd-trash bug ** Package changed: ding (Ubuntu) => nautilus (Ubuntu) ** Summary changed: - DING causes gvfsd 'Too many files open' error and fills syslog + nautilus causes gvfsd-trash 'Too many files open' error and fills syslog ** Description changed: - My syslog is filled (to >30GB) regularly with these messages. I seem to - have this thing called DING going on, which maybe causing it? + My syslog is filled (to >30GB) regularly with these messages. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: (org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer connection failed: Unable to create socket: Too many open files. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server at address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create socket: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1 Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:
[Bug 1967883] Re: Application Icons missing from "Show Applications" screen
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577339/+files/Screenshot%20from%202022-04-05%2014-48-11.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967883 Title: Application Icons missing from "Show Applications" screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967883] [NEW] Application Icons missing from "Show Applications" screen
Public bug reported: From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox (nightly) from Ubuntu Software (as snaps). Neither of the two icons/graphics show up in the show applications window - either in the thumbnails of the groups I have created, or the expanded windows (see screenshots). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 14:49:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-04-05 14-47-30.png" https://bugs.launchpad.net/bugs/1967883/+attachment/5577331/+files/Screenshot%20from%202022-04-05%2014-47-30.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967883 Title: Application Icons missing from "Show Applications" screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967883] Re: Application Icons missing from "Show Applications" screen
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577338/+files/Screenshot%20from%202022-04-05%2014-48-11.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967883 Title: Application Icons missing from "Show Applications" screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1952515] Re: QA Test Ubuntu 22.04 Gnome-shell Crashed
Unable to reproduce in VB environment -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1952515 Title: QA Test Ubuntu 22.04 Gnome-shell Crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952515/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881712] Re: gnome-software says connection is metered while is not
Same issue on 21.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1881712 Title: gnome-software says connection is metered while is not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1881712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
ID = #3026 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3026 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870748] Re: Authentication Window Stays Open
Sorry, I should add that the pop-up window remained on top of all the others, so it wasn't hidden behind anything else before I went to bed. And although it was at the top, when I entered my password and the field went grey, the window remained visible, but if I clicked anywhere in the window, I actually clicked whatever was behind it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870748 Title: Authentication Window Stays Open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870748] Re: Authentication Window Stays Open
Not at that time - I had just gone to bed. I had changed them earlier that day, and the error triggered. So I rebooted. This time the error came about without me touching it. Journal output attached. The bug doesn't appear to be triggered by any steps in Software-Updater ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870748/+attachment/5347706/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870748 Title: Authentication Window Stays Open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 318300] Re: no commas in gcalctool
I am affected by the missing comma problem. I am running gcalctool 6.4.1.1 (as reported with gcalctool --version) and 6.4.1.1-0ubuntu3 (as reported by dpkg-query -l gcalctool) on Ubuntu 12.04.3 LTS which is up to date as of today. When I run gcalctool from a terminal, it outputs the following at exactly the time it should be outputting a comma (e.g. i type in 1000 into the gcalctool): (gcalctool:8733): Gtk-WARNING **: Invalid text buffer iterator: either the iterator is uninitialized, or the characters/pixbufs/widgets in the buffer have been modified since the iterator was created. You must use marks, character numbers, or line numbers to preserve a position across buffer modifications. You can apply tags and insert marks without invalidating your iterators, but any mutation that affects 'indexable' buffer contents (contents that can be referred to by character offset) will invalidate all outstanding iterators I am using English, but there may be something set for NZ somewhere hidden. When I examine my environment, there are no LC variables set: $ env | grep LC when i run gcalctool as follows it displays a comma, yet still outputs the same Gtk-WARNING as above: LC_ALL=en_NZ.UTF-8 gcalctool -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/318300 Title: no commas in gcalctool To manage notifications about this bug go to: https://bugs.launchpad.net/gcalctool/+bug/318300/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
It's a bit more complicated than that, but not much: Sudo stores the SID in the authentication file. However, setsid is installed by default, so you can just launch processes with new SIDs until you get a match. You can either run setsid and sudo a bunch and hope that you match up, or you can look up the SID (also found in auth.log) and match that without running sudo. It's not trivial, but it's certainly doable. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
Todd C Miller is working on it from the sudo side upstream, potentially using CLOCK_MONOTONIC. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
Michael: But again, this totally ignores the question: Why on earth do we need that? How many times per day are you changing your clock that this is necessary?! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
** Bug watch added: Sudo Bugzilla #616 http://www.sudo.ws/bugs/show_bug.cgi?id=616 ** Changed in: sudo Importance: Undecided => Unknown ** Changed in: sudo Status: New => Unknown ** Changed in: sudo Remote watch: None => Sudo Bugzilla #616 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
** Also affects: sudo Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
> There's a fine balance between security and usability, and not everyone is comfortable with the same level of security. As I've mentioned before, it is trivial to modify the defaults to achieve the level of security that is appropriate for your environment. If that's the case, why are you defaulting to a level that Debian, Fedora, Mint, and Windows all feel is too lax? Why not let the very few users who need this, change it to be less secure? Based on my discussions, it seems that this is actually a *sudo* bug, since it uses the non-monotonic clock, rather than using other system features. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
A somewhat sensible workaround I can find at the moment is to force re- authentication every time you type sudo. The way to do this is by adding: Defaults timestamp_timeout=0 to the Defaults section of your /etc/sudoers This will work on Ubuntu, OS X, and other variants. Details can be found in http://www.sudo.ws/sudoers.man.html We really shouldn't be trusting the clock to being with. The fact that Ubuntu developers have seen fit to add "convenience features" to bypass security rather proves the point. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
>This allows administrative users travelling with laptops to change the timezone without getting an authentication prompt. Why is saving the traveling admin from typing their password a couple of times a day worth compromising security for everyone else? No, seriously. Why? >Your attack vector assumes that an administrative user is going to leave an >open session unattended. Yes, my assumption is that users will forget to lock their machines, because it happens all the time. This is especially true if it's a personal machine, and they are the ONLY user. >If that is the case, there are a whole slew of attacks that are possible, and >don't require changing the date. For example, creating scripts in ~/bin that >are higher in the path then system binaries. Even if that number is high, that's no excuse. Is your stance really "Well, they could compromise security 100 ways, so what's one more?" Plus, how many of those attacks require 0 external resources, and creating 0 additional files on the system, and would leave little trace beyond a hiccup in the time/date? >Since your local security policy is different than what is shipped in a >general purpose operating system... Wanting a slightly more secure system is more of an edge case than changing the time zone repeatedly? REALLY? Does Windows 8 count as general purpose to you? It requires escalation to change the date and time. Maybe their escalation system isn't very good, but it's still better than blithely letting admins change the system time without so much as a prompt. Also, their security system doesn't rely on file timestamps, so it's less likely to grant someone root access. > 1- Requiring your administrative users to lock their workstation when they > are left unattended. People make mistakes. Are you telling me you've NEVER forgotten to lock your workstation? You've NEVER seen another admin forget to lock theirs? > 2- Requiring your administrative users to use "sudo -k" to forcibly > invalidate cached credentials. That only works on a per pty/tty basis on ubuntu. It only "invalidates" one of the sessions, and it "invalidates" it by changing the timestamp to a date to Dec. 31, 1969 or Jan. 1, 1970. You could try "sudo -K", which deletes the file, but again only on a per pty/tty basis. > 3- Removing the policykit-desktop-privileges package, or overriding the > policy with a local one. Oh good, more administrative work, all to save typing a password! Pity about all the users who don't know what policykit-desktop-privileges is or does though... > 4- Disabling ntp, or setting up ntp authentication. Disabling ntp wouldn't help, since the whole point is that the user can change the time to anything manually anyhow. > 5- Setting a firmware password on local machines. This doesn't help if they walked away and forgot to lock their machines. I especially love how #2 requires the user to remember to execute a command before they close their terminal, and adds an extra 7 keystrokes PER TTY/PTY. All this to save a hypothetical traveling admin from having to type his password once when he moves to a different timezone. If they want to save themselves a few keystrokes to change the timezone, let /them/ change policy kit. Don't stick every unsuspecting user with a security hole. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
Are you really sure users are supposed to be able to bypass sudo like that? ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
This is by DESIGN? Your design is that any user can change the time, and therefore bypass the security of sudo? What's the justification for not having the user enter a password to change the time? Convenience? Marc, with all due respect, did you even read the bug? "If you disable the sudo password for your account, you will seriously compromise the security of your computer. Anyone sitting at your unattended, logged in account will have complete Root access, and remote exploits become much easier for malicious crackers." This policy kit change adds a single condition: That the user has used sudo to escalate at some point, and it creates /exactly/ the same conditions. I'm going to re-open this just to be sure. It seems incredible that Ubuntu would intentionally let people bypass security like that. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls skips Levels.
Just popped in to check on this bug. I don't have the hardware I filed this against anymore, and I'm still happy on OS X and my Macbook Air, but I feel a responsibility to the users still stuck with this problem. Why are you guys marking the g-p-m bug invalid? The switch to g-s-d doesn't invalidate the original bug, which was logged against a still- supported LTS version. 10.04 still uses g-p-m. By all means, open a new bug for the new g-s-d incarnation of the bug, but please don't hose the LTS users... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 839281] Re: Double brightness events after logging in.
I think I have found a workaround, for those running across this. I posted some info here, in this similar bug. https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157 The practical upshot of all this is that adding the kernel parameter acpi_backlight="vendor" seems to give me proper brightness levels across the board. There were some side effects, namely my screen would go to sleep (due to the power manager timer) and not wake up. I'd suggest setting your screen to never go to sleep unless you close the lid. This "fixed" the comatose screen issue for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/839281 Title: Double brightness events after logging in. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/839281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls skips Levels.
Happy Birthday Bug 527157! Gee, has it been two years already? It feels like just yesterday I was wondering why I couldn't get more than 5-7 brightness levels! Three Ubuntu releases later, and I've had to find two different solutions to the same problem. Maybe it's a g-p-m bug! Maybe it's a kernel bug! I've heard claims that the kernel is reporting xrandr brightness change failures even though the change actually succeeded. Who knows?! For those of you who are tired of patching Gnome-Power-Manager, or trying unsuccesfully to patch the new version in the Gnome 3 branches, I may have found a solution less likely to get clobbered by system updates. The fix worked for this bug on my next laptop, an Alienware M11x r2. I've since moved on to OS X on a Macbook Air, but my hope is that it will help other poor souls just trying to get a comfortable brightness level. Add the following options to your kernel boot parameters: acpi_backlight=vendor I can't guarantee this will work on your laptop. It gave me 15 brightness levels on the Alienware (instead of the default 9 in windows or 4.5 in unmodified ubuntu). An unpleasant side effect was that the screen would go to sleep and not wake up, even though the system was still accessible via ssh. No amount of hand waving or xrandr prodding managed to fix this, or revive the comatose screen. I "solved" this by setting my display to never turn off unless I closed the screen. Despite my snark, I am appreciative of the work put in by people to fix this bug. I would like to thank everyone who helped out on this bug with your comments and testing. I would like to give special thanks to Darwin Bautista and Konstantin Lavrov for working so diligently on the original patch. Your work let me use my machine with the proper brightness levels right up until the 3.x tree of GPM. Without you guys (and especially Darwin's ppa), I would've never had proper screen brightness, and would've never known where to look when resolving this issue in the next version of GPM. >From the bottom of my heart, thank you all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls skips Levels.
This bug is still a problem in Oneric.The version of Gnome Power Manager is completely different (3.1.3). Is there a fix possible for this? The bug is exactly the same. Two brightness levels when only one is needed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls skips Levels.
Tested Konstantin Lavrov's patch (Comment #15) in Natty (11.04). worked like a charm. With the patch, double brightness events are now gone in my Alienware M11xR2 as well. Please commit ASAP! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls skips Levels.
I tested this in Arch, and it affects Arch's current version as well. Every version of GPM I've seen seems to have this issue. Kubuntu's power manager does not have this problem. I looked into the code for GPM, and noticed that xrandr is used to adjust the brightness. The HAL code has an option to check an fdi for brightness_in_hardware, but the xrandr code does not have any similar option. My C kung-fu is not sufficient to fix this problem on my own at this time, but I will continue to work at it. \ I don't think we want to disable xrandr entirely for this model, since this would likely break stuff like "dim after a few minutes" or dim on battery. Instead, I think there should be an option to disable brightness up and down events being controlled by xrander, based on gconf or a setting in GPM. -- Brightness controls skips Levels. https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls skips Levels.
** Also affects: gnome-power-manager (Arch Linux) Importance: Undecided Status: New -- Brightness controls skips Levels. https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 522901] Re: DVD video playback pauses after ~1s, audio continues [lucid regression]
Ditto here. same platform. ** Changed in: gstreamer0.10 (Ubuntu) Status: New => Confirmed -- DVD video playback pauses after ~1s, audio continues [lucid regression] https://bugs.launchpad.net/bugs/522901 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls skips Levels.
Is there any other information that I can provide to help out? I understand this is low priority, but I'm hoping someone will have a "Eureka!" moment and find a workaround/fix. -- Brightness controls skips Levels. https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls create triple brightness changes on Dell Mini 1012
uname per https://wiki.ubuntu.com/DebuggingACPI ** Attachment added: "uname.txt" http://launchpadlibrarian.net/39745596/uname.txt -- Brightness controls create triple brightness changes on Dell Mini 1012 https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls create triple brightness changes on Dell Mini 1012
lspci as per https://wiki.ubuntu.com/DebuggingACPI ** Attachment added: "lspci.txt" http://launchpadlibrarian.net/39745575/lspci.txt -- Brightness controls create triple brightness changes on Dell Mini 1012 https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls create triple brightness changes on Dell Mini 1012
dmidecode log per https://wiki.ubuntu.com/DebuggingACPI ** Attachment added: "dmidecode.txt" http://launchpadlibrarian.net/39744516/dmidecode.txt -- Brightness controls create triple brightness changes on Dell Mini 1012 https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls create triple brightness changes on Dell Mini 1012
output of /usr/share/gnome-power-manager/gnome-power-bugreport ** Attachment added: "bugreport.txt" http://launchpadlibrarian.net/39744291/bugreport.txt -- Brightness controls create triple brightness changes on Dell Mini 1012 https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls create triple brightness changes on Dell Mini 1012
I'd love to run apport-collect, but it crashes and won't send the bug report :) I did forget to mention that I'm on x86_64. -- Brightness controls create triple brightness changes on Dell Mini 1012 https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls create triple brightness changes on Dell Mini 1012
** Tags added: apport-collected -- Brightness controls create triple brightness changes on Dell Mini 1012 https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] Re: Brightness controls create triple brightness changes on Dell Mini 1012
** Description changed: Binary package hint: gnome-power-manager - When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. + Expected: + Hitting brightness up key or brightness down key changes brightness by one level out of 15. + + Actual: + Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. + + + When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. - when hitting brightness up/down with gnome-power-manager, udevmonitor shows + when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) + with gnome-power-manager not running, it shows no events. + + Before: + cat /proc/acpi/video/IGD0/LCD/brightness + levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 + current: 25 + + Brightness up pressed: + cat /proc/acpi/video/IGD0/LCD/brightness + levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 + current: 40 + + With options video brightness_switch_enabled = 0: + cat /proc/acpi/video/IGD0/LCD/brightness + levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 + current: 25 + + Brightness up pressed: + cat /proc/acpi/video/IGD0/LCD/brightness + levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 + current: 35 + + With brightness_switch_enabled=0 and gnome-power-manager not running: + cat /proc/acpi/video/IGD0/LCD/brightness + levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 + current: 25 + + Brightness up pressed: + cat /proc/acpi/video/IGD0/LCD/brightness + levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 + current: 30 + + Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: - Installed: 2:2.9.1-1ubuntu1 - Candidate: 2:2.9.1-1ubuntu1 - Version table: - *** 2:2.9.1-1ubuntu1 0 - 500 http://archive.linux.duke.edu lucid/main Packages - 100 /var/lib/dpkg/status + Installed: 2:2.9.1-1ubuntu1 + Candidate: 2:2.9.1-1ubuntu1 + Version table: + *** 2:2.9.1-1ubuntu1 0 + 500 http://archive.linux.duke.edu lucid/main Packages + 100 /var/lib/dpkg/status gnome-power-manager: - Installed: 2.29.1-0ubuntu2 - Candidate: 2.29.1-0ubuntu2 - Version table: - *** 2.29.1-0ubuntu2 0 - 500 http://archive.linux.duke.edu lucid/main Packages - 100 /var/lib/dpkg/status + Installed: 2.29.1-0ubuntu2 + Candidate: 2.29.1-0ubuntu2 + Version table: + *** 2.29.1-0ubuntu2 0 + 500 http://archive.linux.duke.edu lucid/main Packages + 100 /var/lib/dpkg/status -- Brightness controls create triple brightness changes on Dell Mini 1012 https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 527157] [NEW] Brightness controls create triple brightness changes on Dell Mini 1012
Public bug reported: Binary package hint: gnome-power-manager When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Description:Ubuntu lucid (development branch) Release:10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- Brightness controls create triple brightness changes on Dell Mini 1012 https://bugs.launchpad.net/bugs/527157 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343067] Re: Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played.
It HAS been sent upstream to GNOME. The claim is that it is due to the fact that libarchive in ubuntu 9.04 is out of date. I disagreed with this assessment since the version they tested ships with Fedora 11, and the same issue is there, but have seen no further updates, and have nothing else to add other than "It's still broken." at this time. -- Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played. https://bugs.launchpad.net/bugs/343067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343067] Re: Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played.
Filed upstream. Refined as it is likely a problem with gvfs-archive. I set the status to "confirmed" before because I was told to do so in #ubuntu+1 (before the jaunty release date) by one of the devs in the channel, who along with another user, did indeed confirm the bug. I will leave it as "new" for now, and ask them to set it to confirmed themselves in the future. ** Also affects: gvfs (Fedora) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #580916 http://bugzilla.gnome.org/show_bug.cgi?id=580916 ** Also affects: gvfs via http://bugzilla.gnome.org/show_bug.cgi?id=580916 Importance: Unknown Status: Unknown -- Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played. https://bugs.launchpad.net/bugs/343067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343067] Re: Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played.
This appears to be related to gvfsd-archive behavior, as that is what mounts the iso. What controls which files gvfsd attempts to mount? -- Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played. https://bugs.launchpad.net/bugs/343067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343067] Re: Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played.
This behaviour also appears if you attempt to import the file into rythmbox. The iso is mounted, but no content is played. VLC, Disc Burner, and archive manager are able to open the files normally, and do not mount the isos. It appears that Totem and Rythmbox attempt to mount the ISO then read the content somehow. -- Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played. https://bugs.launchpad.net/bugs/343067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343067] Re: Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played.
** Changed in: totem (Ubuntu) Status: Incomplete => Confirmed -- Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played. https://bugs.launchpad.net/bugs/343067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343067] Re: Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played.
Where is "here"? Ubuntu 8.10? What works fine? Right clicking an .iso of a DVD and opening with movie player? Going to File->Open and picking the ISO? Clicking and dragging the ISO to a playlist? None of these works fine for me on two separate machines installed with Jaunty Jackalope, but all of them work fine in 8.10 (thus the idea that it is a regression). Instead, the disc is mounted, and the files inside show up as .;1, for example VIDEO_TS.VOB;1 rather than the proper VIDEO_TS.VOB (possibly related to another bug I saw, am not able to find at the moment). Does playing it from the command line work for you in totem-gstreamer? Totem-xine? -- Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played. https://bugs.launchpad.net/bugs/343067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343067] Re: Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played.
No, if you go to File->Open it still mounts the ISO and does not play. I was able to get it working by playing it from command line via totem dvd:// in totem-xine. With totem-gstreamer dvd://, I get ** Message: Missing plugin: gstreamer|0.10|totem|DVD source|urisource-dvd (DVD source) ** Message: No installation candidate for missing plugins found. ** Message: Error: A DVD source plugin is required to play this stream, but not installed. gstplaybasebin.c(1673): gen_source_element (): /GstPlayBin:play: No URI handler for dvd ** Message: Missing plugin: gstreamer|0.10|totem|DVD source|urisource-dvd (ignoring) ** Message: All missing plugins are blacklisted, doing nothing I think this is unrelated however, since with totem-xine I get fine playback using the above dvd:// method. Going to file->open, however, always mounts the DVD iso and does not play it. -- Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played. https://bugs.launchpad.net/bugs/343067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343067] Re: Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played.
Sorry, my initial workaround is incomplete, and as a result launches whatever is in your dvd drive. I made this mistake because I had the original DVD and the iso I was trying to mount in my DVD drive. -- Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played. https://bugs.launchpad.net/bugs/343067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 343067] [NEW] Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played.
Public bug reported: Binary package hint: totem Description:Ubuntu jaunty (development branch) Release:9.04 Regression In 9.04 (Jaunty): When using totem-xine, totem-gstreamer, etc to open an iso, it mounts the iso to .gvfs, and then doesn't play it. The files contained in the mounted folder are the AUDIO_TS and VIDEO_TS folders, and none of the files contained in them play. Right clicking an ISO and opening it with totem (Movie Player menu option) used to play the ISO if it was a DVD in Intrepid Ibex / 8.10. This is quite important for people who are using netbooks and cannot watch DVDs via an internal drive. In the case of ALIEN.iso (Or JURASSIC169.ISO or APOLLO69.ISO or any other backup of a DVD) Expected: Right click on ALIEN.iso, navigate to "Open With > Open with "Movie Player", DVD playback begins. Actual: Right click on ALIEN.iso, navigate to "Open With" > Open with "Movie Player", DVD is mounted to .gvfs, appears on desktop. totem doesn't play any files or add ALIEN.iso to playlist. Reproducible: Always. Other Notes: Physical DVDs are unaffected, and play normally (mounted on /media/cdrom0, but playback from /dev/sr0) totem: Installed: 2.25.92-0ubuntu2 Candidate: 2.25.92-0ubuntu2 Version table: *** 2.25.92-0ubuntu2 0 500 http://us.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status Temporary workaround: Install totem-xine using your package manager. Create a custom command launcher. Right click an ISO, click properties, click the "Open With" tab, click Add, click the Use a custom command arrow, and set the command to totem-xine dvd:// ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- Playing a DVD iso in totem causes the iso to be mounted in .gvfs and not played. https://bugs.launchpad.net/bugs/343067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 103228] Re: [apport] totem-plugin-viewer crashed with SIGSEGV in g_signal_emit()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7154308/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7154309/Dependencies.txt ** Attachment added: "Disassembly.txt" http://librarian.launchpad.net/7154310/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7154311/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7154312/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7154313/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/7154314/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/7154315/ThreadStacktrace.txt -- [apport] totem-plugin-viewer crashed with SIGSEGV in g_signal_emit() https://bugs.launchpad.net/bugs/103228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 103228] [apport] totem-plugin-viewer crashed with SIGSEGV in g_signal_emit()
Public bug reported: Binary package hint: totem Source mp4 was "Media Type mp4" on http://www.linspire.com/file_types/filetypes.php ProblemType: Crash Architecture: i386 Date: Thu Apr 5 09:36:35 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/lib/totem/totem-plugin-viewer Package: totem-gstreamer 2.18.0-0ubuntu3 PackageArchitecture: i386 ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type narrowspace --user-agent Mozilla/5.0\ (X11;\ U;\ Linux\ i686;\ en-US;\ rv:1.8.1.3)\ Gecko/20061201\ Firefox/2.0.0.3\ (Ubuntu-feisty) --mimetype video/mp4 ProcCwd: /home/marks ProcEnviron: SHELL=/bin/bash PATH=/home/marks/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/gstreamer-0.10/libgstqtdemux.so ?? () ?? () ?? () g_signal_emit () from /usr/lib/libgobject-2.0.so.0 Uname: Linux map0474 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video ** Affects: totem (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] totem-plugin-viewer crashed with SIGSEGV in g_signal_emit() https://bugs.launchpad.net/bugs/103228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 44196] Re: gnome-cups-icon uses 100% CPU
Hi, I've attached an strace snippet from my machine, which is exhibiting the same behaviour. Cheers Mark ** Attachment added: "Strace of 100% usage" http://librarian.launchpad.net/2757843/gnome-cups-icon-100pc-strace -- gnome-cups-icon uses 100% CPU https://launchpad.net/bugs/44196 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
