[Bug 2051450] [NEW] n/a
Public bug reported: n/a ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 28 09:29:28 2024 ExecutablePath: /usr/libexec/gnome-session-binary InstallationDate: Installed on 2023-12-27 (31 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2051450 Title: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2051450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967812] Re: ubuntu 22.04 beta crash regarding gnome-shell and several others also...
** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1967812 Title: ubuntu 22.04 beta crash regarding gnome-shell and several others also... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967812/+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]
It is happening in 20.04 after an update earlier in the week for me. -- 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/gnome-shell/+bug/1824874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1908801] Re: Acer laptop internal keyboard & touchpad not working
** Description changed: A fresh install of 20.04 from the live USB doesn't see internal keyboard or touchpad input on my Acer Aspire E15 E5-511-POBM. After much private investigation to no avail (https://askubuntu.com/questions/1275809/ubuntu-20-04-lts-laptop- internal-keyboard-and-touchpad-no-longer-work), I am prepared to assert this as a bug. I'll restate the relevant info here, but see the link for a more chronological account. And I guess, for what it's worth, I would also assert that this is reproducible by installing 20.04 on my specific laptop model. So, I boot up the laptop. I'm presented with GRUB boot menu. At this point the keyboard works, and if I choose advanced options and boot into a root shell I can type commands and do things that way as a last resort. However, all the problems seem to begin right from the start of the graphical session, even the login screen. This, in accordance with the instruction of https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, is why I've filed this as a bug in gdm3. As I couldn't run the graphical bug program in Ubuntu, I ran the CLI in the root shell and attached the apport file here. I've tried to follow the relevant steps, but this is my first bug report so apologies if something is wrong. I first noticed this problem a few weeks after upgrading 18.04 to 20.04. Yes, for the first few weeks of using 20.04, there were no problems. And then, one day, I booted up and the keyboard and touchpad spontaneously stopped working. This was mysterious because to my memory I hadn't done any major upgrade or change to any part of the system the previous day. When the system is asleep / suspended, pressing a key or the touchpad easily wakes it up -- after which, they refuse to work again. The brightness key combos (Fn+←/→) and one that turns off the screen (Fn+F6) do work, but others such as volume (Fn+↑/↓) do not work. I see all expected key output when I run `sudo libinput debug-events --device /dev/input/event4 --show-keycodes` and type keys. When I plug in an external USB keyboard and mouse, they work correctly while the internal keyboard and touchpad remain the same. Outside of those specific situations, absolutely no internal keyboard input -- not even Ctrl+Alt+Del or Ctrl+Alt+F2 VT switching, let alone ordinary typing -- has any effect, and same with the touchpad. When I haven't had an external keyboard available I've used the on- screen keyboard to painstakingly run terminal commands by clicking each letter. However, sometimes the on-screen keyboard also stops sending keystrokes. The only concrete situation I can report is what I saw after resuming the system from sleep by opening the lid: at the login prompt on the lock screen, the onscreen keyboard came up, but didn't do anything when keys were clicked, forcing me to reboot. I had the following message in my `journalctl -b` logs: ``` The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Warning: Unsupported maximum keycode 569, clipping. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > X11 cannot support keycodes above 255. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Internal error: Could not resolve keysym Invalid Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: Errors from xkbcomp are not fatal to the X server ``` This looks like it should have something to do with the keyboard issue. If it doesn't, then what is its significance? - When I investigated, I was on kernel 5.0.47. When I selected 4.15.0-112 - in the boot menu, everything was fine again; keyboard and touchpad - working. I also found everything working fine on the install USB demo. - Yet when I did a fresh reinstall of Ubuntu from the USB, the keyboard - and touchpad did not work. + When I first investigated, I was on kernel 5.0.47. When I selected + 4.15.0-112 in the boot menu, everything was fine again; keyboard and + touchpad working. I also found everything working fine on the install + USB demo. Yet when I did a fresh reinstall of Ubuntu from the USB, the + keyboard and touchpad did not work. This was now kernel 5.4.0-54. + + Fortunately, switching down to 5.4.0-42 fixes my keyboard and touchpad + problems, but I've no idea how long this will last (whether the problem + is intermittent or can be relied upon to stay this way). Also, this was + after my reinstall -- I did try this kernel on my previous install, and + back then it only fixed the keyboard without the touchpad! + + After installing lightdm alongside gdm, I see that lightdm actually sees + my touchpad on 5.4.0-54, but still not my keyboard. How can it be OK in the Live USB Demo but not the OS it installs? And - why did switching down to that old kernel version fix my problem if the - problems only happened i
[Bug 1908801] Re: Acer laptop internal keyboard & touchpad not working
** Description changed: A fresh install of 20.04 from the live USB doesn't see internal keyboard or touchpad input on my Acer Aspire E15 E5-511-POBM. After much private investigation to no avail (https://askubuntu.com/questions/1275809/ubuntu-20-04-lts-laptop- internal-keyboard-and-touchpad-no-longer-work), I am prepared to assert this as a bug. I'll restate the relevant info here, but see the link for a more chronological account. And I guess, for what it's worth, I would also assert that this is reproducible by installing 20.04 on my specific laptop model. So, I boot up the laptop. I'm presented with GRUB boot menu. At this point the keyboard works, and if I choose advanced options and boot into a root shell I can type commands and do things that way as a last resort. However, all the problems seem to begin right from the start of the graphical session, even the login screen. This, in accordance with the instruction of https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, is why I've filed this as a bug in gdm3. As I couldn't run the graphical bug program in Ubuntu, I ran the CLI in the root shell and attached the apport file here. I've tried to follow the relevant steps, but this is my first bug report so apologies if something is wrong. I first noticed this problem a few weeks after upgrading 18.04 to 20.04. Yes, for the first few weeks of using 20.04, there were no problems. And then, one day, I booted up and the keyboard and touchpad spontaneously stopped working. This was mysterious because to my memory I hadn't done any major upgrade or change to any part of the system the previous day. When the system is asleep / suspended, pressing a key or the touchpad easily wakes it up -- after which, they refuse to work again. The brightness key combos (Fn+←/→) and one that turns off the screen (Fn+F6) do work, but others such as volume (Fn+↑/↓) do not work. I see all expected key output when I run `sudo libinput debug-events --device /dev/input/event4 --show-keycodes` and type keys. When I plug in an external USB keyboard and mouse, they work correctly while the internal keyboard and touchpad remain the same. Outside of those specific situations, absolutely no internal keyboard input -- not even Ctrl+Alt+Del or Ctrl+Alt+F2 VT switching, let alone ordinary typing -- has any effect, and same with the touchpad. When I haven't had an external keyboard available I've used the on- screen keyboard to painstakingly run terminal commands by clicking each letter. However, sometimes the on-screen keyboard also stops sending keystrokes. The only concrete situation I can report is what I saw after resuming the system from sleep by opening the lid: at the login prompt on the lock screen, the onscreen keyboard came up, but didn't do anything when keys were clicked, forcing me to reboot. I had the following message in my `journalctl -b` logs: ``` The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Warning: Unsupported maximum keycode 569, clipping. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > X11 cannot support keycodes above 255. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Internal error: Could not resolve keysym Invalid Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: Errors from xkbcomp are not fatal to the X server ``` This looks like it should have something to do with the keyboard issue. If it doesn't, then what is its significance? When I investigated, I was on kernel 5.0.47. When I selected 4.15.0-112 in the boot menu, everything was fine again; keyboard and touchpad working. I also found everything working fine on the install USB demo. Yet when I did a fresh reinstall of Ubuntu from the USB, the keyboard and touchpad did not work. How can it be OK in the Live USB Demo but not the OS it installs? And why did switching down to that old kernel version fix my problem if the problems only happened in the GUI and not the root console? What on earth is the connection between the kernel and GNOME's input handling ... on top of an apparently working libinput?? Ideally I'd want to know the different stages in the lifecycle of a keystroke (post-libinput) and to find out at which stage the key event is getting discarded. I literally went digging through the source code of various GNOME packages and programs, xkb tools, etc. I got as far as vaguely learning about Mutter or Clutter or something before deciding I had better things to do with my evenings. I am lost and I need someone who knows more about this. One person on Ask Ubuntu gave some pessimistic sympathy, describing the issue as "just a thing we have to live with" on this particular laptop model. This is unacceptable, and I am able and wi
[Bug 1908801] Re: Acer laptop internal keyboard & touchpad not working
** Description changed: A fresh install of 20.04 from the live USB doesn't see internal keyboard or touchpad input on my Acer Aspire E15 E5-511-POBM. After much private investigation to no avail (https://askubuntu.com/questions/1275809/ubuntu-20-04-lts-laptop- internal-keyboard-and-touchpad-no-longer-work), I am prepared to assert this as a bug. I'll restate the relevant info here, but see the link for a more chronological account. And I guess, for what it's worth, I would also assert that this is reproducible by installing 20.04 on my specific laptop model. So, I boot up the laptop. I'm presented with GRUB boot menu. At this point the keyboard works, and if I choose advanced options and boot into a root shell I can type commands and do things that way as a last resort. However, all the problems seem to begin right from the start of the graphical session, even the login screen. This, in accordance with the instruction of https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, is why I've filed this as a bug in gdm3. As I couldn't run the graphical bug program in Ubuntu, I ran the CLI in the root shell and attached the apport file here. I've tried to follow the relevant steps, but this is my first bug report so apologies if something is wrong. I first noticed this problem a few weeks after upgrading 18.04 to 20.04. Yes, for the first few weeks of using 20.04, there were no problems. And then, one day, I booted up and the keyboard and touchpad spontaneously stopped working. This was mysterious because to my memory I hadn't done any major upgrade or change to any part of the system the previous day. When the system is asleep / suspended, pressing a key or the touchpad easily wakes it up -- after which, they refuse to work again. The brightness key combos (Fn+←/→) and one that turns off the screen (Fn+F6) do work, but others such as volume (Fn+↑/↓) do not work. I see all expected key output when I run `sudo libinput debug-events --device /dev/input/event4 --show-keycodes` and type keys. When I plug in an external USB keyboard and mouse, they work correctly while the internal keyboard and touchpad remain the same. Outside of those specific situations, absolutely no internal keyboard input -- not even Ctrl+Alt+Del or Ctrl+Alt+F2 VT switching, let alone ordinary typing -- has any effect, and same with the touchpad. + When I haven't had an external keyboard available I've used the on- + screen keyboard to painstakingly run terminal commands by clicking each + letter. However, sometimes the on-screen keyboard also stops sending + keystrokes. The only concrete situation I can report is what I saw after + resuming the system from sleep by opening the lid: at the login prompt + on the lock screen, the onscreen keyboard came up, but didn't do + anything when keys were clicked, forcing me to reboot. + I had the following message in my `journalctl -b` logs: ``` The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Warning: Unsupported maximum keycode 569, clipping. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > X11 cannot support keycodes above 255. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Internal error: Could not resolve keysym Invalid Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: Errors from xkbcomp are not fatal to the X server ``` This looks like it should have something to do with the keyboard issue. If it doesn't, then what is its significance? When I investigated, I was on kernel 5.0.47. When I selected 4.15.0-112 in the boot menu, everything was fine again; keyboard and touchpad working. I also found everything working fine on the install USB demo. Yet when I did a fresh reinstall of Ubuntu from the USB, the keyboard and touchpad did not work. How can it be OK in the Live USB Demo but not the OS it installs? And why did switching down to that old kernel version fix my problem if the problems only happened in the GUI and not the root console? What on earth is the connection between the kernel and GNOME's input handling ... on top of an apparently working libinput?? Ideally I'd want to know the different stages in the lifecycle of a keystroke (post-libinput) and to find out at which stage the key event is getting discarded. I literally went digging through the source code of various GNOME packages and programs, xkb tools, etc. I got as far as vaguely learning about Mutter or Clutter or something before deciding I had better things to do with my evenings. I am lost and I need someone who knows more about this. One person on Ask Ubuntu gave some pessimistic sympathy, describing the issue as "just a thing we have to live with" on this particular laptop model. This is unacceptable, and I am able and wi
[Bug 1908801] [NEW] Acer laptop internal keyboard & touchpad not working
Public bug reported: A fresh install of 20.04 from the live USB doesn't see internal keyboard or touchpad input on my Acer Aspire E15 E5-511-POBM. After much private investigation to no avail (https://askubuntu.com/questions/1275809/ubuntu-20-04-lts-laptop- internal-keyboard-and-touchpad-no-longer-work), I am prepared to assert this as a bug. I'll restate the relevant info here, but see the link for a more chronological account. And I guess, for what it's worth, I would also assert that this is reproducible by installing 20.04 on my specific laptop model. So, I boot up the laptop. I'm presented with GRUB boot menu. At this point the keyboard works, and if I choose advanced options and boot into a root shell I can type commands and do things that way as a last resort. However, all the problems seem to begin right from the start of the graphical session, even the login screen. This, in accordance with the instruction of https://wiki.ubuntu.com/Bugs/FindRightPackage#At_the_login_screen, is why I've filed this as a bug in gdm3. As I couldn't run the graphical bug program in Ubuntu, I ran the CLI in the root shell and attached the apport file here. I've tried to follow the relevant steps, but this is my first bug report so apologies if something is wrong. I first noticed this problem a few weeks after upgrading 18.04 to 20.04. Yes, for the first few weeks of using 20.04, there were no problems. And then, one day, I booted up and the keyboard and touchpad spontaneously stopped working. This was mysterious because to my memory I hadn't done any major upgrade or change to any part of the system the previous day. When the system is asleep / suspended, pressing a key or the touchpad easily wakes it up -- after which, they refuse to work again. The brightness key combos (Fn+←/→) and one that turns off the screen (Fn+F6) do work, but others such as volume (Fn+↑/↓) do not work. I see all expected key output when I run `sudo libinput debug-events --device /dev/input/event4 --show-keycodes` and type keys. When I plug in an external USB keyboard and mouse, they work correctly while the internal keyboard and touchpad remain the same. Outside of those specific situations, absolutely no internal keyboard input -- not even Ctrl+Alt+Del or Ctrl+Alt+F2 VT switching, let alone ordinary typing -- has any effect, and same with the touchpad. I had the following message in my `journalctl -b` logs: ``` The XKEYBOARD keymap compiler (xkbcomp) reports: Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Warning: Unsupported maximum keycode 569, clipping. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > X11 cannot support keycodes above 255. Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: > Internal error: Could not resolve keysym Invalid Sep 17 11:36:20 joel-Aspire-E5-511 gnome-shell[1575]: Errors from xkbcomp are not fatal to the X server ``` This looks like it should have something to do with the keyboard issue. If it doesn't, then what is its significance? When I investigated, I was on kernel 5.0.47. When I selected 4.15.0-112 in the boot menu, everything was fine again; keyboard and touchpad working. I also found everything working fine on the install USB demo. Yet when I did a fresh reinstall of Ubuntu from the USB, the keyboard and touchpad did not work. How can it be OK in the Live USB Demo but not the OS it installs? And why did switching down to that old kernel version fix my problem if the problems only happened in the GUI and not the root console? What on earth is the connection between the kernel and GNOME's input handling ... on top of an apparently working libinput?? Ideally I'd want to know the different stages in the lifecycle of a keystroke (post-libinput) and to find out at which stage the key event is getting discarded. I literally went digging through the source code of various GNOME packages and programs, xkb tools, etc. I got as far as vaguely learning about Mutter or Clutter or something before deciding I had better things to do with my evenings. I am lost and I need someone who knows more about this. One person on Ask Ubuntu gave some pessimistic sympathy, describing the issue as "just a thing we have to live with" on this particular laptop model. This is unacceptable, and I am able and willing to spend more time looking into this myself, if I can get just some pointers. Thank you for your consideration. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: gnome keyboard laptop touchpad ** Attachment added: "Results from running apport-cli -f -p gdm3" https://bugs.launchpad.net/bugs/1908801/+attachment/5445154/+files/BUGREPORT.apport ** Summary changed: - internal keyboard touchpad not working + Acer laptop internal keyboard & touchpad not working -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu
[Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
Just to confirm my monitor is set to 100% scaling and I still get the duplicate cursor after wake from sleep. 20.04.1 here with latest updates still has the issue. -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
Yes I'm on 20.04 now and the issue produces the exact same result seen in the photograph when it goes to sleep. This bug is the only reason I can't use ubuntu daily currently. -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
Issue did return for me. You can always take a picture of the screen with your phone if screenshot does not capture the cursor. I did take a picture of it happening in 19.10 as well (attached) ** Attachment added: "IMG_6554.jpg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875528/+attachment/5397561/+files/IMG_6554.jpg -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
With the latest updates installed for Ubuntu 20.04 I am no longer seeing this double mouse cursor issue after two sleeps in a row. Will report back if the issue returns. -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
Same issue happening to me, was happening on 19.10 and still continues after upgrading to 20.04 today. Logging out and back in again resets/hides the extra "dead" cursor, but it appears again after locking the screen and the monitors go to sleep. -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Also having the same problem. Ubuntu 19.04 Intel® Core™ i7-7700HQ CPU @ 2.80GHz × 8 GeForce GTX 1060/PCIe/SSE2 Gnome: 3.32.1 64-bit +-+ | NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 1060Off | :01:00.0 On | N/A | | N/A 51CP029W / N/A |412MiB / 6069MiB | 0% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 1431 G /usr/lib/xorg/Xorg18MiB | |0 1511 G /usr/bin/gnome-shell 48MiB | |0 1828 G /usr/lib/xorg/Xorg 124MiB | |0 1978 G /usr/bin/gnome-shell 217MiB | |0 27135 G evolution 1MiB | +-+ -- 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/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 118988] Re: No way to disable trash in nautilus
Why is this won't fix? This is extremely annoying. There needs to be a fix that doesn't involve me editing config files or writing complicated script to work around the GUI's obtuseness. This is exactly four clicks in Windows. This is a pretty basic bit of system functionality to put so many hurdles around. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/118988 Title: No way to disable trash in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/118988/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
+1 for gnome-shell 3.28.3-0ubuntu0.18.04.4 bionic-proposed - fixed for me -- 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/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718727] Re: gnome-control-center crashed with SIGSEGV in nm_device_filter_connections()
this also affects Bionic Beaver Development branch ** Tags added: 18.04 beaver bionic ** Tags removed: 18.04 beaver bionic ** Tags added: bionic -- 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/1718727 Title: gnome-control-center crashed with SIGSEGV in nm_device_filter_connections() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718727/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1701133] [NEW] package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: Not sure what caused the error ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:i386 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic i686 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: i386 Date: Wed Jun 28 19:00:57 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-24 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701133 Title: package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701133/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695815] [NEW] Login loop when leaving review for unconfirmed Ubuntu One accounts
Public bug reported: Steps to reproduce: - Fresh 17.04 Install. - New Ubuntu One account with unconfirmed email. - Attempt to write a review (Audacity fore example) - You are prompted with login window - Enter username and password - Login window is shown again and again without error message. Expected behavior: - Give a dialog suggesting how the user can remedy the issue. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.7-0ubuntu3.17.04.2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Jun 5 00:36:47 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2017-06-04 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1695815 Title: Login loop when leaving review for unconfirmed Ubuntu One accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1695815/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640670] [NEW] Crash in GfxICCBasedColorSpace::parse
Public bug reported:
#0 cmsGetColorSpace (hProfile=0x0) at cmsio0.c:934
#1 0x7f174b47b438 in GfxICCBasedColorSpace::parse(Array*, OutputDev*,
GfxState*, int) ()
from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
#2 0x7f174b47a952 in GfxColorSpace::parse(GfxResources*, Object*,
OutputDev*, GfxState*, int) ()
from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
#3 0x7f174b4a0872 in Page::loadThumb(unsigned char**, int*, int*, int*) ()
from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
#4 0x7f174bbb7de9 in poppler_page_get_thumbnail () from
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
#5 0x7f174bdf5b1b in ?? () from
/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
#6 0x557297930bb2 in evince_thumbnail_pngenc_get (document=0x7f1744003700,
thumbnail=0x5572995948c0 "/tmp/.gnome_desktop_thumbnail.ZD13QY", size=256)
at evince-thumbnailer.c:182
#7 0x5572979307d0 in main (argc=, argv=) at
evince-thumbnailer.c:301
getColorSpace, part of lcms, is passed a null pointer.
GfxICCBasedColorSpace::parse has this sequence of code:
if (hp == 0) {
error(errSyntaxWarning, -1, "read ICCBased color space profile error");
} else {
cmsHPROFILE dhp = (state != NULL && state->getDisplayProfile() != NULL) ?
state->getDisplayProfile() : displayProfile;
if (dhp == NULL) dhp = RGBProfile;
unsigned int cst = getCMSColorSpaceType(cmsGetColorSpace(hp));
unsigned int dNChannels = getCMSNChannels(cmsGetColorSpace(dhp));
unsigned int dcst = getCMSColorSpaceType(cmsGetColorSpace(dhp));
hp can't be null, or else we wouldn't be calling cmsGetColorSpace. This
means dhp must be NULL, which can only happen if RGBProfile is null.
RGBProfile is set up in GfxColorSpace::setupColorProfiles(). Assuming
this function has been called, it does the following:
RGBProfile = loadColorProfile("RGB.icc");
if (RGBProfile == NULL) {
/* use built in sRGB profile */
RGBProfile = cmsCreate_sRGBProfile();
}
cmsCreate_sRGBProfile can return NULL in a number of ways.
I'm not sure what the fix is though.
** Affects: poppler (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1640670
Title:
Crash in GfxICCBasedColorSpace::parse
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1640670/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640670] Re: Crash in GfxICCBasedColorSpace::parse
libpoppler61: Installed: 0.44.0-3ubuntu2 liblcms2-2: Installed: 2.7-1ubuntu1 evince: Installed: 3.22.0-0ubuntu1 On Ubuntu 16.10 amd64. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1640670 Title: Crash in GfxICCBasedColorSpace::parse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1640670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
I had the same issue with upgrading from 16.04 to 16.10. and I too had to dismiss MANY identical dialogues about this failure!! I almost power cycled... but kept going.. waiting for upgrade to complete PLEASE fix - or at least don't have an endless cycle of error messages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1583845] Re: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization
*** This bug is a duplicate of bug 1579712 *** https://bugs.launchpad.net/bugs/1579712 This fix also worked for me. https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/comments/24 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1583845 Title: Can't "apt-get update" - appstreamcli stuck at 100% Processor Utilization To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1583845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1563155] Re: No Application Data Found
Here is the list of things I've tried (in order, not sure if the order made a difference in fixing) - changing language and restarting (didn't work) - sudo apt purge gnome-software ubuntu-software sudo apt autoremove sudo apt install gnome-software ubuntu-software (didn't work) - sudo appstreamcli refresh --force --verbose (didn't work) - sudo rm -r /var/cache/app-info && sudo appstreamcli refresh --force --verbose (didn't work) - killall gnome-software ; gnome-software --verbose | tee /tmp/gnome- software.log (then ctrl-c and it worked) I'm assuming some combination of this fixed it. Hopefully this helps in finding the correct solution -- 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/1563155 Title: No Application Data Found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1563155/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551707] Re: Installing local debs gives an error dialog
To install chrome and slack on ubuntu 16.04 until this is fixed I did cd ~/Downloads sudo dpkg -i google-chrome-stable_current_amd64.deb sudo apt-get -f install sudo dpkg -i google-chrome-stable_current_amd64.deb sudo dpkg -i slack-desktop-2.0.3-amd64.deb -- 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/1551707 Title: Installing local debs gives an error dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1551707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551707] Re: Installing local debs gives an error dialog
This bug is still an issue, also encountered when installing slack. I don't get an error message. I press install, the progress bar shows up very briefly and then it becomes install again -- 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/1551707 Title: Installing local debs gives an error dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1551707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1152226] Re: nautilus no longer remembers view per directory
While waiting for more sensible default settings, a tip is to use Ctr+1 and Ctrl+2 to quickly toggle between the list and icon view. -- 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/1152226 Title: nautilus no longer remembers view per directory To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1152226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1414707] Re: Login fails, returns to login and flickering prevents password typing
This issue still persists in Ubuntu Gnome 14.04.2 I could consistently reproduce by installing fresh and then installing steam (and its dependencies). I was not able to restart gdm and login as it just froze in tty7 (the other terminals worked). When doing a hard reset of my computer it would then hang at the grey screen with the gnome logo and the three loading dots . Installing Ubuntu Gnome 15.04 to hopefully resolve this issue -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1414707 Title: Login fails, returns to login and flickering prevents password typing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1414707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1456789] [NEW] Unable to restart services from scripts
Public bug reported: I have a script run as root from cron that tweaks smb.conf and restarts smbd and winbind. Problem is, starting today after working perfectly up till yesterday, this script now hangs on Ubuntu 15.04. When run from cron, the process tree looks like this: service smbd restart \_ systemctl restart smbd.service \_ /bin/systemd-tty-ask-password-agent --watch \_ /usr/bin/pkttyagent --notify-fd 5 --fallback Run from a shell via sudo, same thing except the process tree (obviously) includes the sudo command. It times out after 5 minutes, causing the script to fail. If I manually kill the processes, it fails faster. The simplest possible scripts that reproduce this, run as root or through cron or via sudo, are: #!/bin/sh service smbd restart #!/bin/sh systemctl restart smbd.service Using 'service', this works perfectly on Ubuntu 14.04 and 14.10, and until this morning worked perfectly on 15.04 as well. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Ubuntu 15.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd 219-7ubuntu5 samba 2:4.1.13+dfsg-4ubuntu3 3) What you expected to happen Services to restart 4) What happened instead Services didn't restart, 'systemctl' hung ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1456789 Title: Unable to restart services from scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)
@Gunnar I was originally pointed here from a forum thread, but after looking around some more it seems like https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1385009 is more similar to what I am experiencing. It also suggests some fixes I am trying out now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/406036 Title: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/406036/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)
I am also having this issue on Ubuntu 14.10 with unity. Inkscape often crashers when modifying text boxes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/406036 Title: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/406036/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1352951] [NEW] nautilus crashed with SIGSEGV in g_slice_alloc()
Public bug reported: Nautilus crash when only download a torrent, no copying, deleting or moving files. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.3 Uname: Linux 3.6.11 x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 5 10:14:18 2014 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1405434801 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'group', 'permissions', 'octal_permissions', 'owner', 'mime_type', 'where'] InstallationDate: Installed on 2014-07-30 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: nautilus -n ProcCwd: /home/joel SegvAnalysis: Segfault happened at: 0x7fa82174c297 g_slice_alloc+167: mov (%rbx),%rax PC (0x7fa82174c297) ok source (%rbx) (0x00842552) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- 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/1352951 Title: nautilus crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1352951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1352951] Re: nautilus crashed with SIGSEGV in g_slice_alloc()
*** This bug is a duplicate of bug 1161468 *** https://bugs.launchpad.net/bugs/1161468 The bug 1161468 is private I cannot see the bug. How work in it?. -- 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/1352951 Title: nautilus crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1352951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1350599] [NEW] file-roller crashed with SIGSEGV
Public bug reported: file-roller crashes when I extract an archive (not show bar progress) and I extract it again. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: file-roller 3.10.2.1-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.5.0-51.76-generic 3.5.7.33 Uname: Linux 3.5.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 30 17:55:51 2014 Disassembly: = 0x7fcd9085e63b: No se puede acceder a la memoria en la dirección 0x7fcd9085e63b ExecutablePath: /usr/bin/file-roller ExecutableTimestamp: 1405437685 InstallationDate: Installed on 2014-07-30 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: file-roller /home/joel/Descargas/mono-3.0.0.tar.bz2 ProcCwd: /home/joel SegvAnalysis: Segfault happened at: 0x7fcd9085e63b: No se puede acceder a la memoria en la dirección 0x7fcd9085e63b PC (0x7fcd9085e63b) ok source 0x7fcd9085e63b (0x7fcd9085e63b) ok SP (0x7fff3b896720) ok Reason could not be automatically determined. Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: file-roller crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: file-roller (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-crash trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1350599 Title: file-roller crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1350599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1299245] Re: Rhythmbox fails to start
** Attachment added: _usr_bin_rhythmbox.1000.crash https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1299245/+attachment/4095511/+files/_usr_bin_rhythmbox.1000.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1299245 Title: Rhythmbox fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1299245/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1269651] Re: UI for adding sametime account is empty
The cause of this was a bad libsametime package. If you encounter this bug, make sure you have installed a valid libsametime from the Ubuntu repository. ** Changed in: empathy (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1269651 Title: UI for adding sametime account is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1269651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1269651] [NEW] UI for adding sametime account is empty
Public bug reported: Fresh Ubuntu 13.10 installation. 1. Installed account-plugin-sametime to use sametime. 2. Navigated to the Online Accounts dialog in gnome-control-center 3. selected Add account..., Sametime. 4. UI only shows Please enter your account details, Cancel and Done buttons, nothing else. A screenshot is attached. ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Attachment added: Screenshot of Online Accounts UI https://bugs.launchpad.net/bugs/1269651/+attachment/3949862/+files/Screenshot%20from%202014-01-16%2011%3A56%3A50.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1269651 Title: UI for adding sametime account is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1269651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1250675] [NEW] [clipboard]: gnome-settings-daemon crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 946059 *** https://bugs.launchpad.net/bugs/946059 Public bug reported: gnome-settings-daemon crashed and gtk-window-decorator hidden close button and window's title. It can't restore by itself, must be killed and restart manually. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu15 ProcVersionSignature: Ubuntu 3.5.0-42.65-generic 3.5.7.21 Uname: Linux 3.5.0-42-generic x86_64 ApportVersion: 2.6.1-0ubuntu13 Architecture: amd64 Date: Tue Nov 12 17:39:49 2013 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2013-07-18 (117 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetWindowAttributes () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowAttributes () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: [clipboard]: gnome-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video wireshark ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash clipboard quantal third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1250675 Title: [clipboard]: gnome-settings-daemon crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1250675/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1220383] [NEW] evolution crashed with SIGSEGV in g_settings_backend_path_changed()
Public bug reported: Attempting to find previous Evolution data file. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evolution 3.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Tue Sep 3 11:42:41 2013 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2013-08-27 (7 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130724) MarkForUpload: True ProcCmdline: evolution ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f964cf4cd2c: mov(%rax,%r13,1),%rax PC (0x7f964cf4cd2c) ok source (%rax,%r13,1) (0x0008) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_backend_path_changed () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: evolution crashed with SIGSEGV in g_settings_backend_path_changed() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1220383 Title: evolution crashed with SIGSEGV in g_settings_backend_path_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1220383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1219478] [NEW] gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1212971 *** https://bugs.launchpad.net/bugs/1212971 Public bug reported: I don't know what caused this. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Aug 31 21:39:45 2013 ExecutablePath: /usr/lib/gvfs/gvfs-afc-volume-monitor InstallationDate: Installed on 2013-08-27 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130724) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfs-afc-volume-monitor ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f31ff45a297 g_type_check_instance_cast+71: movzbl 0x16(%r9),%eax PC (0x7f31ff45a297) ok source 0x16(%r9) (0x250016) not located in a known VMA region (needed readable region)! destination %eax ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gvfs StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () ?? () ?? () ?? () from /usr/lib/libimobiledevice.so.4 Title: gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1219478 Title: gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1219478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1215090] [NEW] gvfsd-obexftp crashed with SIGABRT in __libc_message()
Public bug reported: When I connect my Android phone to PC Bluetooth and I want to browse my sdcard, gvfsd-obexftp fail instantly. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gvfs-backends 1.14.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16 Uname: Linux 3.5.0-37-generic x86_64 ApportVersion: 2.6.1-0ubuntu12 Architecture: amd64 CrashCounter: 1 Date: Wed Aug 21 13:09:23 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-obexftp ExecutableTimestamp: 1349728911 InstallationDate: Installed on 2013-07-18 (34 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-obexftp --spawner :1.7 /org/gtk/gvfs/exec_spaw/3 ProcCwd: / Signal: 6 SourcePackage: gvfs StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () Title: gvfsd-obexftp crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gvfs (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash quantal ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1215090 Title: gvfsd-obexftp crashed with SIGABRT in __libc_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1215090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60448] Re: .xsession-errors file grows out of control saturates disk space
This bug locked me out of a server running Ubuntu 12.04 Desktop 64-bit with the latest updates as of 3/28/2013. I only access this server via its freenx/ssh daemons. I discovered the insane disk usage by .xsession-errors.old after my nx client couldn't get past Authenticated during the login process. Logging in via the console, I was able to reboot the system twice, which cleared the file. This bug is still in the wild, performing DOS attacks on unsuspecting sysadmins. I don't want to lose the log file in case it's needed for debugging. But can we please keep it from getting this big in the future? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/60448 Title: .xsession-errors file grows out of control saturates disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/60448/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1105838] [NEW] party mode inescapable unless you know the hotkey
*** This bug is a duplicate of bug 785631 *** https://bugs.launchpad.net/bugs/785631 Public bug reported: Once you launch party mode in Rhythmbox, it is near impossible to go back to normal mode unless you know the F11 hotkey. There should be a button that is around a corner that makes it easy to resume normal mode. Suggestions: 1. A first-run party mode dialogue could be shown to indicate the F11 hotkey. 2. Small close button added to the party mode interface. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: rhythmbox 2.98-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Sat Jan 26 19:25:24 2013 InstallationDate: Installed on 2013-01-19 (6 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130118) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity ** Description changed: - Once you launch party mode in Rhythmbox, it is near-impossible to go + Once you launch party mode in Rhythmbox, it is near impossible to go back to normal mode unless you know the F11 hotkey. There should be a button that is around a corner that makes it easy to resume normal mode. Suggestions: 1. A first-run party mode dialogue could be shown to indicate the F11 hotkey. 2. Small close button added to the party mode interface. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: rhythmbox 2.98-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Sat Jan 26 19:25:24 2013 InstallationDate: Installed on 2013-01-19 (6 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130118) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** This bug has been marked a duplicate of bug 785631 Rhythmbox Party Mode can't be exited in Unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1105838 Title: party mode inescapable unless you know the hotkey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1105838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1103222] Re: Time zone location can't find certain cities
** Package changed: ubuntu = gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1103222 Title: Time zone location can't find certain cities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1103222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 827049] Re: add bookmark is broken in oneiric's nautilus
Hi! Editing the file ~/.gtk-bookmarks worked for me. -- 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/827049 Title: add bookmark is broken in oneiric's nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/827049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1082850] Re: notify-osd bubble on rb exit when no music is playing
** Summary changed: - notify-osd bubble on rb exit when no music is played + notify-osd bubble on rb exit when no music is playing -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1082850 Title: notify-osd bubble on rb exit when no music is playing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1082850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1082850] [NEW] notify-osd bubble on rb exit when no music is played
Public bug reported: When you quit rhythmbox with no music playing, a notify-osd bubble pops up for about ten seconds notifying you Not playing. This seems a little unnecessary. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: rhythmbox 2.98-0ubuntu2 ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6 Uname: Linux 3.7.0-3-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 Date: Sun Nov 25 19:37:20 2012 InstallationDate: Installed on 2012-11-25 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121124) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1082850 Title: notify-osd bubble on rb exit when no music is played To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1082850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
I can confirm that the new package does prevent settings in dconf from propagating into gconf on a dconf update after the package is installed and the user is logged out and back in. I haven't used the new package long enough to identify if there are any regressions, but it does seem to fix this bug. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 963125] Re: Alt-Tab window switcher lost
** Also affects: gsettings-desktop-schemas (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/963125 Title: Alt-Tab window switcher lost To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/963125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
I added my comments to bug 963125 regarding the dconf array keybindings being converted to lists in gconf, where metacity expects strings. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 963125] Re: Alt-Tab window switcher lost
Adding packages gnome-settings-daemon and gsettings-desktop-schemas, as a fix could be done in either. The issue appears to be that dconf stores the keybindings in arrays of strings, and when set there, gnome-settings-daemon will transition those settings to gconf as defined by /usr/share/GConf/gsettings/wm- schemas.convert. metacity expects those keybindings to just be strings, not lists of strings, so after the conversion, metacity can't read the keybindings. Possible solutions would be 1. Allow conversion to a string, which is probably a challenging task, especially if the array in dconf contains multiple values. the .convert files would have to indicate that a type change is required, which would be a syntax change from existing files, and probably not worth the effort. 2. Just remove these keybindings from the .convert files. I suspect they aren't really necessary. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New = Confirmed ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/963125 Title: Alt-Tab window switcher lost To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/963125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
I'm pretty new to dconf, so I'm making some assumptions which may be incorrect. When dconf update is run as root, that only updates settings which are either mandatory or defaults system-wide. Neither of those changes should result in a change in the users home directory, and if a user wasn't logged in, nothing would happen currently. Because of that, I'm not sure that dconf update should be sending any signals which would trigger a gconf sync. At most, it should just re-read the system settings in order to accept the new default or mandatory settings. Even if that doesn't happen, on next login, they will be re-read, right? Unrelated, I'm surprised to find dconf defaults that don't match up with gconf defaults. Like the metacity button_layout dconf default puts the buttons back on the right. This was the primary reason I noticed this was all happening in the first place. when dconf update ran, it updated the gconf setting for the button layout and moved the buttons back the the right. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
This also exposes something else, which might be better as a separate bug. wm-schemas.convert tries to convert metacity keybindings from dconf to gconf. Unfortunately the types are different, so anything accepted by dconf probably won't actually work once it's written to gconf. This was exposed because a dconf update wound up writing all these keybindings into gconf. For example, dconf has org.gnome.desktop.wm.keybindings switch-windows as ['AltTab'] which is an array of strings. However, metacity expects this to be just the string 'AltTab'. When the gconf conversion happens, it seems to actually convert the key to a list of strings in gconf, and metacity stops supporting Alt-Tab. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 954918]
Still running into this on Fedora 18 with: libpurple-2.10.6-4.fc18.x86_64 telepathy-haze-0.6.0-2.fc18.x86_64 empathy-3.6.1-2.fc18.x86_64 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/954918 Title: Missing Server input box for Sametime accounts To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/954918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Under what conditions would the gconf plugin for gsettings daemon convert dconf settings into gconf? This is triggered by a dconf update while a user is logged in, which seems a rare use case under normal conditions. When is this plugin designed to operate normally, and could that other normal operation cause this same issue? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069269] [NEW] Wifi disconnects and can't reconnect until reboot, no wifi problem under 12.04
Public bug reported: When i try to reactive wifi card, it won't Hardware is detected but cant access wifi networks, even with terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Sat Oct 20 23:09:12 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANG=fr_FR.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-10-18 (2 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- 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/1069269 Title: Wifi disconnects and can't reconnect until reboot, no wifi problem under 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1069269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787039] Re: Python 3 Doc not show in Devhelp
But it works for me, I have installed python3.2-doc and python2.7-doc packages, changed the tag name in their DevHelp Book Description solve the problem. A example: the gtkmm documentation packages (2.4 and 3.0) difference the DevHelp Book Description using gtkmm-2.4 and gtkmm-3.0 in attribute name in the tag book. The python documentation packages must do the same. Is possible use Python2.7 and Python3.2, this can help if has installed more than one the same major version: 2.* or 3.* versions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/787039 Title: Python 3 Doc not show in Devhelp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/787039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787039] Re: Python 3 Doc not show in Devhelp
The problem is in tag name in python3.2.devhelp.gz and python2.7.devhelp.gz, this is the same: Python; and DevHelp use the major version (this case python3-doc). A solution is change the tag name to: Python2 and Python3 respectively. ** Changed in: devhelp (Ubuntu) Status: Expired = Incomplete ** Changed in: devhelp (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/787039 Title: Python 3 Doc not show in Devhelp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/787039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787039] Re: Python 3 Doc not show in Devhelp
This problem is in python3.2-dev and python2.7-doc DevHelp Book File (.devhelp.gz) ** Also affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Also affects: python3.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/787039 Title: Python 3 Doc not show in Devhelp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/787039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787039] Re: Python 3 Doc not show in Devhelp
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/787039 Title: Python 3 Doc not show in Devhelp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/787039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017210] Re: Import failed: no user has logged in
You can use `ssh-add` in the meantime. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1017210 Title: Import failed: no user has logged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1017210/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1001579] Re: Incorrect file transfer progress bar
This is really annoying and will probably cause a few people to loose some data because they pull their drives thinking it has crashed etc. -- 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/1001579 Title: Incorrect file transfer progress bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1001579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 823936] Re: cannot empty trash, files are still visible
Cannot empty the Trash Folder!! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/823936 Title: cannot empty trash, files are still visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/823936/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 823936] Re: cannot empty trash, files are still visible
Cannot empty the Trash Folder!! ** Changed in: evolution (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/823936 Title: cannot empty trash, files are still visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/823936/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 790687] Re: nautilus desktop: Unity menu and alt key navigation
Still an issue in precise -- 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/790687 Title: nautilus desktop: Unity menu and alt key navigation To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/790687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 974859] [NEW] shuffle button decreases icon and surrounding panel size
Public bug reported: When you mouse over the shuffle/randomplay songs button, the button itself and the panel of Play, Prev Soung, Next Song and Repeat all shrink a few pixels. This only happens when mousing over the Shuffle button, none of the others. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Fri Apr 6 16:03:01 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120401) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/974859 Title: shuffle button decreases icon and surrounding panel size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/974859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 974859] Re: shuffle button decreases icon and surrounding panel size
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/974859 Title: shuffle button decreases icon and surrounding panel size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/974859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 958507] [NEW] use unsafe storage gnome keyring dialogue is unusable
Public bug reported: gnome keyring pops up wanting to save a new password. I click on use unsafe storage and the normal dialogue warning you about the risks is displayed but the window is completely unclickable (the button to confirm you want to use unsafe storage). The only working feature of the dialogue is pressing the red X at the top left of the dialogue ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Sun Mar 18 23:24:59 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/958507 Title: use unsafe storage gnome keyring dialogue is unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/958507/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 958507] Re: use unsafe storage gnome keyring dialogue is unusable
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/958507 Title: use unsafe storage gnome keyring dialogue is unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/958507/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 433937] Re: Cannot delete messages from Trash Folder
I can not empty the Trash folder! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/433937 Title: Cannot delete messages from Trash Folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/433937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 897169] [NEW] no templates installed in Rt-Click Create New Document
Public bug reported: Hi, when you right click in Nautilus and scroll to Create New Document, it opens another list which has no templates installed (which is greyed-out) and Empty Document There should be some, for example, LibreOffice templates here, such as a Writer, Calc and Impress - otherwise this space is redundant and the Create Empty Document could be merged into the main list. * marking as bitesize as the fixing/implementation should be fairly easy ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Nov 28 21:59:49 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bitesize i386 oneiric running-unity -- 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/897169 Title: no templates installed in Rt-Click Create New Document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/897169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 897169] Re: no templates installed in Rt-Click Create New Document
-- 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/897169 Title: no templates installed in Rt-Click Create New Document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/897169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 372132] Re: Create Document Templates difficult to use
Echoing comment #63, it's annoying installing Ubuntu, a full-featured desktop OS, to find that there's no document templates available. I'd much rather not have it at all than to have something that you have to actually create the templates yourself. -- 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/372132 Title: Create Document Templates difficult to use To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/372132/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 885492] Re: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
same with when I try to issue a 'bzr launchpad-login jpickett' on precise 12.04 (daily 04/11) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/885492 Title: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome- keyring-pkcs11.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/885492/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 620693] Re: Screen not locked when turned off
Martin, this new package looks good on Lucid. I went through the testing procedure before the package, and the screen did not lock. After installing the new package, without changing settings, the screen did indeed lock. Michael, thanks for taking a look at this. -- 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/620693 Title: Screen not locked when turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/620693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 843334] Re: gnome-settings-daemon crashed with SIGABRT in raise()
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/843334 Title: gnome-settings-daemon crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/843334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 843334] [NEW] gnome-settings-daemon crashed with SIGABRT in raise()
Public bug reported: After today's dist-update ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-settings-daemon 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CrashCounter: 1 Date: Tue Sep 6 18:14:09 2011 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en SHELL=/bin/false PATH=(custom, no user) Signal: 6 SourcePackage: gnome-settings-daemon StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: gnome-settings-daemon crashed with SIGABRT in raise() UpgradeStatus: Upgraded to oneiric on 2011-09-01 (5 days ago) UserGroups: ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash oneiric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/843334 Title: gnome-settings-daemon crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/843334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 806773] Re: empathy crashed with SIGABRT in raise()
I just opened empathy, and it crashed... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/806773 Title: empathy crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/806773/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 821440] [NEW] cannot set automatic login through system settings
Public bug reported: Following on from this bug - https://bugs.launchpad.net/ubuntu/oneiric/+source/casper/+bug/819624 I was unable to set automatic login at the install stage. I've installed Ubuntu 11.10 alpha 3 successfully but if I go to user accounts and try to set automatic login, the option doesn't stick. I set it to Automatic login , ON and then exit the program, reopen user settings to see that Automatic login is OFF again ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0 Uname: Linux 3.0.0-7-generic x86_64 Architecture: amd64 Date: Fri Aug 5 22:24:31 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110803.1) ProcEnviron: LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SHELL=/bin/bash 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 oneiric running-unity -- 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/821440 Title: cannot set automatic login through system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/821440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 821440] Re: cannot set automatic login through system settings
-- 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/821440 Title: cannot set automatic login through system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/821440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 821440] Re: cannot set automatic login through system settings
*** This bug is a duplicate of bug 820568 *** https://bugs.launchpad.net/bugs/820568 ** This bug has been marked a duplicate of bug 820568 no autologin available. -- 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/821440 Title: cannot set automatic login through system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/821440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 815279] [NEW] typo in ../mail/evolution-mail.schemas.in.h:44
Public bug reported: Found this small typo while translating into enAU. The string is: Describes wheter message headers in paned view should be collapsed or expanded by default. 0 = expanded 1 = collapsed Should be: Describes whether message headers in paned view should be collapsed or expanded by default. 0 = expanded 1 = collapsed - note the h in whether ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: bitesize -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/815279 Title: typo in ../mail/evolution-mail.schemas.in.h:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/815279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 629258] Re: Battery life estimation never comes around
Happening on HP dv6-3006tx -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (38795). https://bugs.launchpad.net/bugs/629258 Title: Battery life estimation never comes around To manage notifications about this bug go to: https://bugs.launchpad.net/devicekit-power/+bug/629258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 620693] Re: Screen not locked when turned off
I no longer work on the team responsible for maintaining this. I'll leave it and see if anyone on Goobuntu Team cares to test it or speak up. It may not be important to them anymore. However, this is really easy to reproduce, should you want to test it yourself. I just don't have anything newer than Lucid, since we stick with the LTS. to reproduce, assuming the options haven't changed in natty 1. set /apps/gnome-power-manager/timeout/sleep_display_ac to less than /desktop/gnome/session/idle_delay 2a. set /apps/gnome-power-manager/lock/blank_screen OR 2b. set /apps/gnome-screensaver/lock_enabled and /apps/gnome-power-manager/lock/use_screensaver_settings 3. wait until the sleep_delay_ac time expires, and watch the screen turn off. See if it's locked or not. -- 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/620693 Title: Screen not locked when turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/620693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 555315] Re: ondemand CPU Scaling does not work when AC adapter is plugged in
Additional information: When I set the governor to performance, then when the laptop is on battery power the CPU frequency is ramped up from 1.60GHz to the full 2.80GHz. When the A/C power adapter is plugged in and the governor is set to performance, the CPU frequency remains at 1.60GHz and never increases. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/555315 Title: ondemand CPU Scaling does not work when AC adapter is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/555315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 555315] Re: ondemand CPU Scaling does not work when AC adapter is plugged in
** Changed in: gnome-applets (Ubuntu) Status: Incomplete = Confirmed ** Description changed: Binary package hint: gnome-applets + Ubuntu 11.04 Ubuntu 9.10 gnome-applets: - Installed: 2.28.0-0ubuntu2 - Candidate: 2.28.0-0ubuntu2 + Installed: 2.28.0-0ubuntu2 + Candidate: 2.28.0-0ubuntu2 When unplugged, the tool from the panel works just fine and cpufreq-info shows the range of frequencies available as 800-2270. When the AC adapter is plugged in, this range is bounded to 800-800. Performance using Flash or any other semi-demanding task is terrible. cpufreq-info output when plugged into AC power: cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: - driver: acpi-cpufreq - CPUs which need to switch frequency at the same time: 0 - hardware limits: 800 MHz - 2.27 GHz - available frequency steps: 2.27 GHz, 2.27 GHz, 1.60 GHz, 800 MHz - available cpufreq governors: conservative, ondemand, userspace, powersave, performance - current policy: frequency should be within 800 MHz and 800 MHz. - The governor ondemand may decide which speed to use - within this range. - current CPU frequency is 800 MHz. - cpufreq stats: 2.27 GHz:0.00%, 2.27 GHz:0.00%, 1.60 GHz:0.00%, 800 MHz:0.00% (6) + driver: acpi-cpufreq + CPUs which need to switch frequency at the same time: 0 + hardware limits: 800 MHz - 2.27 GHz + available frequency steps: 2.27 GHz, 2.27 GHz, 1.60 GHz, 800 MHz + available cpufreq governors: conservative, ondemand, userspace, powersave, performance + current policy: frequency should be within 800 MHz and 800 MHz. + The governor ondemand may decide which speed to use + within this range. + current CPU frequency is 800 MHz. + cpufreq stats: 2.27 GHz:0.00%, 2.27 GHz:0.00%, 1.60 GHz:0.00%, 800 MHz:0.00% (6) analyzing CPU 1: - driver: acpi-cpufreq - CPUs which need to switch frequency at the same time: 1 - hardware limits: 800 MHz - 2.27 GHz - available frequency steps: 2.27 GHz, 2.27 GHz, 1.60 GHz, 800 MHz - available cpufreq governors: conservative, ondemand, userspace, powersave, performance - current policy: frequency should be within 800 MHz and 800 MHz. - The governor ondemand may decide which speed to use - within this range. - current CPU frequency is 800 MHz. - cpufreq stats: 2.27 GHz:0.00%, 2.27 GHz:0.00%, 1.60 GHz:0.00%, 800 MHz:0.00% (4) + driver: acpi-cpufreq + CPUs which need to switch frequency at the same time: 1 + hardware limits: 800 MHz - 2.27 GHz + available frequency steps: 2.27 GHz, 2.27 GHz, 1.60 GHz, 800 MHz + available cpufreq governors: conservative, ondemand, userspace, powersave, performance + current policy: frequency should be within 800 MHz and 800 MHz. + The governor ondemand may decide which speed to use + within this range. + current CPU frequency is 800 MHz. + cpufreq stats: 2.27 GHz:0.00%, 2.27 GHz:0.00%, 1.60 GHz:0.00%, 800 MHz:0.00% (4) ProblemType: Bug Architecture: i386 Date: Sun Apr 4 15:44:04 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/yelp NonfreeKernelModules: nvidia Package: yelp 2.28.0-0ubuntu2 ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-20.58-generic SourcePackage: yelp Uname: Linux 2.6.31-20-generic i686 XsessionErrors: - (gnome-settings-daemon:2194): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed - (gnome-settings-daemon:2194): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed - (polkit-gnome-authentication-agent-1:2286): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed - (nautilus:2280): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed - (firefox:2594): GLib-WARNING **: g_set_prgname() called multiple times + (gnome-settings-daemon:2194): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed + (gnome-settings-daemon:2194): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed + (polkit-gnome-authentication-agent-1:2286): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed + (nautilus:2280): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed + (firefox:2594): GLib-WARNING **: g_set_prgname() called multiple times -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/555315 Title: ondemand CPU Scaling does not work when AC adapter is plugged in To manage notifications about this bug go to:
[Bug 555315] Re: ondemand CPU Scaling does not work when AC adapter is plugged in
This bug also affects me. When on battery, cpu frequency scales properly on-demand 1.6 to 2.8 GHz. (current policy shows range of 1.6 to 2.8) When AC adapter is plugged in, cpu frequency is locked at 1.6 Ghz. (current policy shows range of 1.6 to 1.6) -Computer- Processor : 2x Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz Memory : 4111MB (543MB used) Operating System: Ubuntu 11.04 cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 2.80 GHz available frequency steps: 2.80 GHz, 2.80 GHz, 2.13 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 1.60 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 2.80 GHz:5.64%, 2.80 GHz:0.28%, 2.13 GHz:0.35%, 1.60 GHz:93.73% (4292) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 2.80 GHz available frequency steps: 2.80 GHz, 2.80 GHz, 2.13 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 1.60 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 2.80 GHz:6.37%, 2.80 GHz:0.09%, 2.13 GHz:0.11%, 1.60 GHz:93.44% (2654) cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 2.80 GHz available frequency steps: 2.80 GHz, 2.80 GHz, 2.13 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 2.80 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 2.80 GHz:5.58%, 2.80 GHz:0.29%, 2.13 GHz:0.35%, 1.60 GHz:93.78% (4371) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us. hardware limits: 1.60 GHz - 2.80 GHz available frequency steps: 2.80 GHz, 2.80 GHz, 2.13 GHz, 1.60 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.60 GHz and 2.80 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.60 GHz. cpufreq stats: 2.80 GHz:6.27%, 2.80 GHz:0.09%, 2.13 GHz:0.11%, 1.60 GHz:93.53% (2720) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/555315 Title: ondemand CPU Scaling does not work when AC adapter is plugged in -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 792787] Re: i lock screen comeback later I don't get a login prompt, I can ctl-alt f6 and login so the system is still working I just can not get back in graphicly without a reboot
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/792787 Title: i lock screen comeback later I don't get a login prompt, I can ctl- alt f6 and login so the system is still working I just can not get back in graphicly without a reboot -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762918] Re: Natty Screensaver freezes system after some period of inactivity
I have multiple users myself, my wife and kids, when it happens to me and i ctrl-alt-f1 I can get in, I switch to graphic mode and then the login screen pops up, if I login as anyone else in the family I can get in but if i try to login as myself it either pops up the login screen again or blank screen with mouse movment -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/762918 Title: Natty Screensaver freezes system after some period of inactivity -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 765847] Re: Send to Email is missing on Natty
While the workaround provided the sendto email option, I also had data migration failures (.evolution --- .local/share/evolution) with this upgrade from Maverick, I could not get past evolution hanging after send to email, it was identical to loicjacquard's post in bug #773121 Did a export backup of evolution, and installed a fresh copy of Natty, workaround is currently working, the sendto option is available and brings up the mail message w/attachment. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/765847 Title: Send to Email is missing on Natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 765847] Re: Send to Email is missing on Natty
Workaround does not work for me, like teimcrr wrote, it doesn't bring up a mail message, it brings evolution to focus if it is open but nothing else, this is a critical bug in my opinion, the importance should not read undecided and it should not be unassigned. My wife is beside herself, this is a common activity in order to send photos out via shotwell. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus-sendto in Ubuntu. https://bugs.launchpad.net/bugs/765847 Title: Send to Email is missing on Natty -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 751432] [NEW] package gstreamer0.10-plugins-ugly 0.10.17-1 failed to upgrade
*** This bug is a duplicate of bug 751343 *** https://bugs.launchpad.net/bugs/751343 Public bug reported: error during apt-get update :trying to overwrite '/usr/share/locale/af/LC_MESSAGES/.mo', which is also in package gstreamer0.10-plugins-bad 0.10.21-1ubuntu10 ProblemType: Package DistroRelease: Ubuntu 11.04 Package: gstreamer0.10-plugins-ugly 0.10.17-1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Tue Apr 5 09:54:34 2011 ErrorMessage: trying to overwrite '/usr/share/locale/af/LC_MESSAGES/.mo', which is also in package gstreamer0.10-plugins-bad 0.10.21-1ubuntu10 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta 1 i386 (20110329.1) SourcePackage: gst-plugins-ugly0.10 Title: package gstreamer0.10-plugins-ugly 0.10.17-1 failed to install/upgrade: trying to overwrite '/usr/share/locale/af/LC_MESSAGES/.mo', which is also in package gstreamer0.10-plugins-bad 0.10.21-1ubuntu10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-ugly0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 natty unity-2d -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-ugly0.10 in Ubuntu. https://bugs.launchpad.net/bugs/751432 Title: package gstreamer0.10-plugins-ugly 0.10.17-1 failed to upgrade -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 751432] Re: package gstreamer0.10-plugins-ugly 0.10.17-1 failed to upgrade
*** This bug is a duplicate of bug 751343 *** https://bugs.launchpad.net/bugs/751343 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-ugly0.10 in Ubuntu. https://bugs.launchpad.net/bugs/751432 Title: package gstreamer0.10-plugins-ugly 0.10.17-1 failed to upgrade -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 751509] [NEW] package gstreamer0.10-plugins-ugly 0.10.17-1 failed to install/upgrade: tentative de remplacement de « /usr/share/locale/af/LC_MESSAGES/.mo », qui appartient aussi au paquet gstream
*** This bug is a duplicate of bug 751343 *** https://bugs.launchpad.net/bugs/751343 Public bug reported: Trying to do an update, and it fails every time ... Apt make an error while trying to install ProblemType: Package DistroRelease: Ubuntu 11.04 Package: gstreamer0.10-plugins-ugly 0.10.17-1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Tue Apr 5 10:48:48 2011 ErrorMessage: tentative de remplacement de « /usr/share/locale/af/LC_MESSAGES/.mo », qui appartient aussi au paquet gstreamer0.10-plugins-bad 0.10.21-1ubuntu10 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110302) SourcePackage: gst-plugins-ugly0.10 Title: package gstreamer0.10-plugins-ugly 0.10.17-1 failed to install/upgrade: tentative de remplacement de « /usr/share/locale/af/LC_MESSAGES/.mo », qui appartient aussi au paquet gstreamer0.10-plugins-bad 0.10.21-1ubuntu10 UpgradeStatus: Upgraded to natty on 2011-03-27 (9 days ago) ** Affects: gst-plugins-ugly0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 natty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-ugly0.10 in Ubuntu. https://bugs.launchpad.net/bugs/751509 Title: package gstreamer0.10-plugins-ugly 0.10.17-1 failed to install/upgrade: tentative de remplacement de « /usr/share/locale/af/LC_MESSAGES/.mo », qui appartient aussi au paquet gstreamer0.10-plugins-bad 0.10.21-1ubuntu10 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 751509] Re: package gstreamer0.10-plugins-ugly 0.10.17-1 failed to install/upgrade: tentative de remplacement de « /usr/share/locale/af/LC_MESSAGES/.mo », qui appartient aussi au paquet gstreamer
*** This bug is a duplicate of bug 751343 *** https://bugs.launchpad.net/bugs/751343 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-ugly0.10 in Ubuntu. https://bugs.launchpad.net/bugs/751509 Title: package gstreamer0.10-plugins-ugly 0.10.17-1 failed to install/upgrade: tentative de remplacement de « /usr/share/locale/af/LC_MESSAGES/.mo », qui appartient aussi au paquet gstreamer0.10-plugins-bad 0.10.21-1ubuntu10 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 75151] Re: Refuses to open files where the character encoding is not recognised
I've attached one file that is supposed to be a text file, but apparently has 'nul' characters in it. It's a log from Microsoft IIS 6.0. The thing that really annoys me is that I can see the file for a little bit when I click Retry. The error I'm getting is Could not open the file ftp://---. gedit has not been able to detect the character encoding. Please check that you are not trying to open a binary file. Select a character encoding from the menu and try again. When I click Retry after selecting UTF-8 I get this error: Could not open the file ftp://--- using the Unicode (UTF-8) character encoding. gedit has not been able to detect the character encoding. Please check that you are not trying to open a binary file. Select a character encoding from the menu and try again. ** Attachment added: IIS log that gedit won't display. https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/75151/+attachment/1888471/+files/ex110305.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/75151 Title: Refuses to open files where the character encoding is not recognised -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 476811] Re: Network users with longer than 8 character usernames do not show up in user list (possible fix included)
+1 from me as well. I originally reported this. It has been over a year, and there have been two Ubuntu releases since my initial report. It's still a daily annoyance, and it appears to be trivial to fix. It should at least be of medium importance, so that it gets some attention. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/476811 Title: Network users with longer than 8 character usernames do not show up in user list (possible fix included) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 660455] Re: clock-applet continually crashing
** Changed in: gnome-panel (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. https://bugs.launchpad.net/bugs/660455 Title: clock-applet continually crashing -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 683659] Re: Empathy problems
-- Empathy problems https://bugs.launchpad.net/bugs/683659 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 683659] [NEW] Empathy problems
Public bug reported: Binary package hint: empathy Empathy will not connect to ICQ, Facebook or gmail ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: empathy 2.32.0.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic x86_64 Architecture: amd64 Date: Wed Dec 1 08:45:58 2010 EcryptfsInUse: Yes ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 SourcePackage: empathy XsessionErrors: (polkit-gnome-authentication-agent-1:1599): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1603): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Empathy problems https://bugs.launchpad.net/bugs/683659 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 653920] Re: resize bug (zoom in/resize window/scroll)
Reproducible on Ubuntu 10.10 32-bit with integrated Intel graphics. -- resize bug (zoom in/resize window/scroll) https://bugs.launchpad.net/bugs/653920 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
