[Bug 1309605] Re: OSD (skip, pause) take full window (and fullscreen) height
Let me be a bit more precise (no pun intended). In Window mode, it I resize the window while the OSD is shown, it is rescaled to the window size. When switching to full screen while an OSD is there, it is also resized. So a temporary workaround is to resize the window to a minimal size while forcing an OSD and then never again resize when an OSD is shown. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1309605 Title: OSD (skip, pause) take full window (and fullscreen) height To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1309605/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1309605] [NEW] OSD (skip, pause) take full window (and fullscreen) height
Public bug reported: The OSD icons for forward/backward skip and pause have the wrong heigt. They take the full (sometimes even more) height on the player window and also full height in fullscreen mode. This appeared after the upgrade to trusty (totem 3.10.1) ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1309605 Title: OSD (skip, pause) take full window (and fullscreen) height To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1309605/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 448234] Re: epiphany-browser assert failure: epiphany-browser: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed.
still not fixed, is it? Even if it's some kind of annoying flash-issue, there should be at least some kind of more specific error message and epiphany should not crash at all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/448234 Title: epiphany-browser assert failure: epiphany-browser: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/epiphany-browser/+bug/448234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 448234] Re: epiphany-browser assert failure: epiphany-browser: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed.
Got the same bug on my machine with epiphany (but not firefox). This showed up only recently, but it might be it's because I usually don't use flash websites. See crash log attached. Using epiphany 2.30.2 on ubuntu maverick ** Attachment added: "Crash log of epiphany" https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/448234/+attachment/2145040/+files/crash.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/448234 Title: epiphany-browser assert failure: epiphany-browser: /build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject: Assertion `npobj != ((void *)0)' failed. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 666846] Re: Keyring unlock asks for password twice despite auto-unlock via pam_gnome_keyring
Found that the libpam-gnome-keyring only unlocks the "login" keyring on purpuse. http://live.gnome.org/GnomeKeyring/Pam So this is not really a bug-report but more a feature-request/wishlist thing. ** Changed in: gnome-keyring (Ubuntu) Status: New => Opinion -- Keyring unlock asks for password twice despite auto-unlock via pam_gnome_keyring https://bugs.launchpad.net/bugs/666846 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 666846] [NEW] Keyring unlock asks for password twice despite auto-unlock via pam_gnome_keyring
Public bug reported: Binary package hint: gnome-keyring I'm running ubuntu 10.10, with all updates as of today, especially gnome-keyring 2.92.92.is.2.31.91-0ubuntu4 I have two keyrings: default and login, which were automatically created and filled with passwords by applications (empathy, networkmanager, etc). After changing my password some time ago, I had the problem that the keyring passwords were not changed, so I did that manually to make sure they are the same as the login password. When I now login using gdm, the "login" keyring gets unlocked, but the "default" keyring does not. I'm asked twice to enter it's password, before networkmanager is able to use it. I tried apt-get install --reinstall --purge gnome-keyring libpam-gnome-keyring, but didn't solve it. Because it worked in the past I assumed that the auto-unlock should try unlocking all keyrings. - If it should unlock all keyrings: Why does it not? Which logs should I attach? - If it's only supposed so unlock the "login" keyring: Can this be changed? Why then do programs use two different keyrings at all? Thanks a lot ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- Keyring unlock asks for password twice despite auto-unlock via pam_gnome_keyring https://bugs.launchpad.net/bugs/666846 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
The problem is only partially solved by making "Disk Utility" close the luks device. In fact all other situations in which a device is not closed correctly also lead to this error. I use an encrypted external harddrive. Whenever I shutdown the drive before unmounting or suspend the pc, then disconnect the drive and resume the pc, the luks device is not closed cleanly. Such situations can happen and should be handeled correctly, by making nautilus (or the gvfs backend, I'm not an expert here) close a luks drive automatically, when it is no longer accessible. Steps to reproduce: 1) mount an luks-encrypted external harddrive 2) suspend the system 3) disconnect the drive 4) resume the system 5) connect the drive 6) try to mount the encryptet partition (happens automatically by default when inserted) I would be happy to give further details when helpful and will test a patch if available. -- Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists https://bugs.launchpad.net/bugs/484429 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
