[Desktop-packages] [Bug 2015405] Re: spice-vdagent crashed with SIGSEGV
I saw this again yesterday in a standard Ubuntu Noble install in QEMU/KVM. It's not a ISO install test; it's been updated regularly for a while. Again, other than the crash notice, nothing obvious happens. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/2015405 Title: spice-vdagent crashed with SIGSEGV Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Just launching an ubuntu 23.04 beta VM on libvirtd/qemu/KVM and this brings the reporting crash app as soon as loging into the desktop. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: spice-vdagent 0.22.1-3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 5 23:21:08 2023 ExecutablePath: /usr/bin/spice-vdagent InstallationDate: Installed on 2023-03-31 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcCmdline: /usr/bin/spice-vdagent ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x559a23cd00e0:mov(%r15),%rdi PC (0x559a23cd00e0) ok source "(%r15)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: spice-vdagent StacktraceTop: () __libc_start_call_main (main=main@entry=0x559a23ccfe80, argc=argc@entry=1, argv=argv@entry=0x7ffce18a7c08) at ../sysdeps/nptl/libc_start_call_main.h:58 __libc_start_main_impl (main=0x559a23ccfe80, argc=1, argv=0x7ffce18a7c08, init=, fini=, rtld_fini=, stack_end=0x7ffce18a7bf8) at ../csu/libc-start.c:360 () Title: spice-vdagent crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2015405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed
Not seeing thumbnails of images and pdf in VM install. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2047256 Title: Ubuntu 24.04 Some image thumbnails no longer displayed Status in nautilus package in Ubuntu: Confirmed Bug description: After recent updates on my Ubuntu Noble 24.04 nautilus does not show thumbnails of PDF files. On a different partition same PC Ubuntu Noble 24.04 not recently updated PDF thumbnails are correctly displayed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 22 16:15:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)' InstallationDate: Installed on 2023-12-10 (12 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 nautilus-image-converter 0.4.0-2 nautilus-share0.7.5-0.3 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039459] [NEW] Network manager app doesn't allow scrolling to top of WiFi AP list
Public bug reported: Live session on Budgie 20231016.1, Surface Go 3 tablet with 10 in screen. The Network Manager app in the taskbar is not allowing me to scroll right to the top of the AP list. In order to see all the stations, I need to click on Network Settings and go to the Budgie Control Center. Once I've done this, it connects successfully. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/2039459 Title: Network manager app doesn't allow scrolling to top of WiFi AP list Status in network-manager-applet package in Ubuntu: New Bug description: Live session on Budgie 20231016.1, Surface Go 3 tablet with 10 in screen. The Network Manager app in the taskbar is not allowing me to scroll right to the top of the AP list. In order to see all the stations, I need to click on Network Settings and go to the Budgie Control Center. Once I've done this, it connects successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015405] Re: spice-vdagent crashed with SIGSEGV
This happened when trying out a daily Edubuntu install in a QEMU/KVM VM. Apart from the Apport message, nothing obvious happened. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/2015405 Title: spice-vdagent crashed with SIGSEGV Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Just launching an ubuntu 23.04 beta VM on libvirtd/qemu/KVM and this brings the reporting crash app as soon as loging into the desktop. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: spice-vdagent 0.22.1-3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 5 23:21:08 2023 ExecutablePath: /usr/bin/spice-vdagent InstallationDate: Installed on 2023-03-31 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcCmdline: /usr/bin/spice-vdagent ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x559a23cd00e0:mov(%r15),%rdi PC (0x559a23cd00e0) ok source "(%r15)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: spice-vdagent StacktraceTop: () __libc_start_call_main (main=main@entry=0x559a23ccfe80, argc=argc@entry=1, argv=argv@entry=0x7ffce18a7c08) at ../sysdeps/nptl/libc_start_call_main.h:58 __libc_start_main_impl (main=0x559a23ccfe80, argc=1, argv=0x7ffce18a7c08, init=, fini=, rtld_fini=, stack_end=0x7ffce18a7bf8) at ../csu/libc-start.c:360 () Title: spice-vdagent crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2015405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings
This bug seems to be solved in Xubuntu 22.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxklavier in Ubuntu. https://bugs.launchpad.net/bugs/1805197 Title: cannot switching keyboard layout with xfce4-keyboard-settings Status in Xfce4 Settings: Confirmed Status in libxklavier package in Ubuntu: Confirmed Status in xfce4-settings package in Ubuntu: Triaged Bug description: This is on xubuntu 18.04: With xfce4-keyboard-settings I have loaded the keyboard layouts "English (US)" and "German". Both are listed in the "Keybord layout" table. When I change the order with [key up] or [key down] nothing happens, I still have the old keyboard layout active. To switch the layout I have to DELETE the other one! This was not the case with xubuntu 16.04: just changing the order was sufficent there. To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
I've opened a new bug report: Bug #1874178 I'll mark myself as not affected by this one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874178] [NEW] Unlocking existing session needs two attempts after selecting Switch User
Public bug reported: This has been occurring during the Xubuntu post-install test. It's not the same as Bug #1776475, as it's not necessary to have logged in as another user (or even for another user to exist) for the problem to happen. My sequence of actions is: *Create new user. *Open a program (usually Thunar or Terminal). *Lock session. *Click on "Switch User". <-- This is all that's necessary to trigger it. *Enter password to unlock my own session. *Then there's a delay and screen goes black, then the unlock prompt appears again. *The second time, my session unlocks. This particular report is from a QEMU/KVM vm, but it's also been happening on a bare-metal install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 15:30:29 2020 InstallationDate: Installed on 2020-04-22 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1874178 Title: Unlocking existing session needs two attempts after selecting Switch User Status in lightdm package in Ubuntu: New Bug description: This has been occurring during the Xubuntu post-install test. It's not the same as Bug #1776475, as it's not necessary to have logged in as another user (or even for another user to exist) for the problem to happen. My sequence of actions is: *Create new user. *Open a program (usually Thunar or Terminal). *Lock session. *Click on "Switch User". <-- This is all that's necessary to trigger it. *Enter password to unlock my own session. *Then there's a delay and screen goes black, then the unlock prompt appears again. *The second time, my session unlocks. This particular report is from a QEMU/KVM vm, but it's also been happening on a bare-metal install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 15:30:29 2020 InstallationDate: Installed on 2020-04-22 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
The default value was 0 minutes. I set it to one minute and it made no difference. Incidentally, it seems that clicking on the "Switch user" button is enough to trigger the problem. I did this because I couldn't remember whether or not I'd added another user (I hadn't at that point). It's not necessary to actually log in as the other user. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
A fresh install on an external USB3 drive is showing exactly the same behaviour. Not a VM problem, apparently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
@Stéphane: Sorry, I didn't see this sooner. I must have forgotten to subscribe. (oops) In Xubuntu Final (iso 20200420.1), there is no Security tab in the Power Manager. Only a "security" checkbox which controls "Lock screen when system is going to sleep". I had a look in the configuration editor in case something was hiding there - nothing relevant there. My sequence of actions is: *Create new user. *Open a program (usually Thunar or Terminal). *Lock session. *Log in as new user which I just created. *Log out of new user's session. *Select my original user. *Enter password to unlock. *Then there's a delay and screen goes black, then the unlock prompt appears again. *The second time, the original session unlocks. It's occurred to me that this just might be an issue with the QEMU/KVM vm, if no one else is having problems. I don't have a spare machine for testing, unfortunately, though I might be able to do something with an external drive. If I get a chance later today, I see what I can do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings
This bug seems still to be present in Xubuntu 20.04 To be able to switch keyboard layouts after reboot (or logout), I need to go to keyboard settings, change the keyboard layout switch key to something else (and then back again, though that's not absolutely necessary). It's not so bad on my main machine, because that tends to be left running for days at a time, but on a laptop I imagine it would be really frustrating. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxklavier in Ubuntu. https://bugs.launchpad.net/bugs/1805197 Title: cannot switching keyboard layout with xfce4-keyboard-settings Status in Xfce4 Settings: Confirmed Status in libxklavier package in Ubuntu: Confirmed Status in xfce4-settings package in Ubuntu: Confirmed Bug description: This is on xubuntu 18.04: With xfce4-keyboard-settings I have loaded the keyboard layouts "English (US)" and "German". Both are listed in the "Keybord layout" table. When I change the order with [key up] or [key down] nothing happens, I still have the old keyboard layout active. To switch the layout I have to DELETE the other one! This was not the case with xubuntu 16.04: just changing the order was sufficent there. To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
This seems to have reappeared recently in Xubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854603] Re: Greek (polytonic) keyboard layout not handling some accent marks
This is working correctly in a fresh install of Ubuntu ISO 20200328, in both Wayland and Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks Status in gnome-shell package in Ubuntu: New Bug description: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854603] Re: Greek (polytonic) keyboard layout not handling some accent marks
Sorry, I meant to mention this and forgot: it makes no difference whether I use Wayland or X. That was one of the first things I tried. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks Status in gnome-shell package in Ubuntu: Incomplete Bug description: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854603] Re: Greek (polytonic) keyboard layout not handling some accent marks
Since I first reported this bug, I've noticed that I also encounter it on a fairly minimal Openbox system where I'm using setxkbmap to manage the keyboard layouts. Which suggests that it may not be a Gnome-Shell issue at all. I've also got a Xubuntu 20.04 VM, and I'm not having these problems with the keyboard layout there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks Status in gnome-shell package in Ubuntu: New Bug description: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854603] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1854603/+attachment/5310410/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks Status in gnome-shell package in Ubuntu: New Bug description: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854603] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1854603/+attachment/5310413/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks Status in gnome-shell package in Ubuntu: New Bug description: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854603] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1854603/+attachment/5310412/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks Status in gnome-shell package in Ubuntu: New Bug description: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854603] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1854603/+attachment/5310411/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks Status in gnome-shell package in Ubuntu: New Bug description: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854603] Re: Greek (polytonic) keyboard layout not handling some accent marks
apport information ** Tags added: apport-collected wayland-session ** Description changed: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu13 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-10-29 (38 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028) + Package: gnome-shell 3.34.1+git20191024-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 + Tags: focal wayland-session + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1854603/+attachment/5310409/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks Status in gnome-shell package in Ubuntu: New Bug description: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-29 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191028) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854603] [NEW] Greek (polytonic) keyboard layout not handling some accent marks
Public bug reported: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks Status in gnome-shell package in Ubuntu: New Bug description: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845198] Re: GNOME Shell seemingly locked up at login
PPA package is also working in an eoan QEMU/KVM vm which was locking up with the standard packages. I also ran into a lockup problem on the ISO file when installing. Not sure if it's related to this or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845198 Title: GNOME Shell seemingly locked up at login Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Eoan: In Progress Bug description: In 19.10, and also running the X PPA from http://ppa.launchpad.net/canonical-x/x-staging/ubuntu When I logged in (after having attached a Bluetooth speaker in order to test if it was being reconnected correctly) GNOME Shell isn't responding to mouse or keyboard input. The clock continues to tell the right time, and the mouse moves around the screen and is repainted correctly. Most recent output from gdb here: https://paste.ubuntu.com/p/pSshP8V2SZ/ Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/ Journal here: https://paste.ubuntu.com/p/GZcWsQdRhd/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed
Is now working as expected on my EeePC 900. That includes waking from suspend. (I don't use hibernate.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: [SRU] Re-read the link type if the name changed Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] NM needs to re-read the DEVTYPE after the device name changed, an example is that WiFi network list disappears from network manager applet Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. [Testcase] After upgrading to the new version, the repeating the above steps should give expected behavior. [Regression Potential] Potential of causing regression is relatively small for a one line change to re-read a value to be known. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574347] Re: WiFi network list disappears from network manager applet
@hussain I installed 1.2 on my EeePC by enabling the Proposed repository in Software and Updates. This isn't usually recommended for everyone as it can break things, but is useful for testing. Once the patched version is released and is moved from the Proposed to the regular repository, it will automatically be updated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: WiFi network list disappears from network manager applet Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Confirmed Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574347] Re: WiFi network list disappears from network manager applet
@Cip Man: That explains it, then. I'm happy to wait for the patched version to come through. My current workaround is to add the line service NetworkManager restart to /etc/rc.local -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: WiFi network list disappears from network manager applet Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Confirmed Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574347] Re: WiFi network list disappears from network manager applet
I'm still having the issue on my EeePC 900 after installing NetWorkManager 1.2.0 from xenial-proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: WiFi network list disappears from network manager applet Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Confirmed Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569590] Re: wireless card disabled in network-manager
Bug has been reported at https://bugzilla.gnome.org/show_bug.cgi?id=765123 ** Bug watch added: GNOME Bug Tracker #765123 https://bugzilla.gnome.org/show_bug.cgi?id=765123 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1569590 Title: wireless card disabled in network-manager Status in network-manager package in Ubuntu: Triaged Bug description: Using xenial on Asus EeePC 900 Network manager has worked fine with the wireless card on this machine, until the update of 12 April. Now the wireless card appears greyed out in the nm-applet interface with no SSIDs visible. Ethernet still works. wicd works on this machine, but I'd prefer not to have to install that. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic i686 ApportVersion: 2.20.1-0ubuntu1 Architecture: i386 Date: Wed Apr 13 09:55:01 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 192.168.1.1 dev enp3s0 proto static metric 100 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.67 metric 100 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 745074e0-abba-4f29-8c5d-1bcfbcb13e3a /org/freedesktop/NetworkManager/ActiveConnection/0 wlp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569590] Re: wireless card disabled in network-manager
Additional information: I ran dpkg from the recovery menu. I'm uncertain whether that's caused the following behaviour or not. On logging in, network manager shows "[wireless card name] disconnected" On turning off wireless with the function key, network manager shows "[wireless card name] device not managed" On turning on the wireless using the function key, network manager shows "Enable wifi" box unchecked. Checking the box allows the machine to connect to the router. If I turn the machine off, or reboot, I have to go through the last three steps again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1569590 Title: wireless card disabled in network-manager Status in network-manager package in Ubuntu: New Bug description: Using xenial on Asus EeePC 900 Network manager has worked fine with the wireless card on this machine, until the update of 12 April. Now the wireless card appears greyed out in the nm-applet interface with no SSIDs visible. Ethernet still works. wicd works on this machine, but I'd prefer not to have to install that. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic i686 ApportVersion: 2.20.1-0ubuntu1 Architecture: i386 Date: Wed Apr 13 09:55:01 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 192.168.1.1 dev enp3s0 proto static metric 100 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.67 metric 100 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 745074e0-abba-4f29-8c5d-1bcfbcb13e3a /org/freedesktop/NetworkManager/ActiveConnection/0 wlp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569590] [NEW] wireless card disabled in network-manager
Public bug reported: Using xenial on Asus EeePC 900 Network manager has worked fine with the wireless card on this machine, until the update of 12 April. Now the wireless card appears greyed out in the nm-applet interface with no SSIDs visible. Ethernet still works. wicd works on this machine, but I'd prefer not to have to install that. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic i686 ApportVersion: 2.20.1-0ubuntu1 Architecture: i386 Date: Wed Apr 13 09:55:01 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 192.168.1.1 dev enp3s0 proto static metric 100 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.67 metric 100 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 745074e0-abba-4f29-8c5d-1bcfbcb13e3a /org/freedesktop/NetworkManager/ActiveConnection/0 wlp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1569590 Title: wireless card disabled in network-manager Status in network-manager package in Ubuntu: New Bug description: Using xenial on Asus EeePC 900 Network manager has worked fine with the wireless card on this machine, until the update of 12 April. Now the wireless card appears greyed out in the nm-applet interface with no SSIDs visible. Ethernet still works. wicd works on this machine, but I'd prefer not to have to install that. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic i686 ApportVersion: 2.20.1-0ubuntu1 Architecture: i386 Date: Wed Apr 13 09:55:01 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 192.168.1.1 dev enp3s0 proto static metric 100 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.67 metric 100 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 745074e0-abba-4f29-8c5d-1bcfbcb13e3a /org/freedesktop/NetworkManager/ActiveConnection/0 wlp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1547793] Re: upowerd crashed with SIGSEGV in g_variant_is_trusted()
Still crashing on Asus EeePC 900. I've not tried with the battery removed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1547793 Title: upowerd crashed with SIGSEGV in g_variant_is_trusted() Status in Upower: In Progress Status in upower package in Ubuntu: Fix Released Status in upower package in Debian: New Bug description: Crash when connecting laptop to charger. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: upower 0.99.4-1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Feb 20 16:18:04 2016 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2015-04-07 (319 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7fdb12e38ee0:mov0x20(%rdi),%eax PC (0x7fdb12e38ee0) ok source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: upower StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: upowerd crashed with SIGSEGV in g_variant_builder_add_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1547793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1322724] Re: Ubuntu One in firefox bookmarks
Still present in Firefox in Xenial Xubuntu Beta 1 ISO. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1322724 Title: Ubuntu One in firefox bookmarks Status in epiphany-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Triaged Bug description: I'm running firefox 28 which comes with Xubuntu 14.04 and noticed that there is an 'Ubuntu One' bookmark under the 'Ubuntu and Free Software links' bookmark folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1322724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1322724] Re: Ubuntu One in firefox bookmarks
This bookmark is still present in Firefox in the Wily Xubuntu ISO of 20151020, and very likely the other flavours as well. Ubuntu One file service has been closed for over a year, and the bookmark needs to be removed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1322724 Title: Ubuntu One in firefox bookmarks Status in epiphany-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Triaged Bug description: I'm running firefox 28 which comes with Xubuntu 14.04 and noticed that there is an 'Ubuntu One' bookmark under the 'Ubuntu and Free Software links' bookmark folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1322724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1272716] Re: gnome-sudoku crashed with TypeError in set_value(): unorderable types: int() < NoneType()
Same behaviour. Choosing Undo causes Apport window to appear. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1272716 Title: gnome-sudoku crashed with TypeError in set_value(): unorderable types: int() < NoneType() Status in “gnome-sudoku” package in Ubuntu: Confirmed Bug description: Can't undo last move, and then apport window appears. BTW interface is still in English. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-sudoku 1:3.10.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sat Jan 25 20:54:51 2014 ExecutablePath: /usr/games/gnome-sudoku InstallationDate: Installed on 2013-11-30 (56 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131130) InterpreterPath: /usr/bin/python3.3 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/games/gnome-sudoku ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/games/gnome-sudoku'] SourcePackage: gnome-sudoku Title: gnome-sudoku crashed with TypeError in set_value(): unorderable types: int() < NoneType() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1272716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276912] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1276912 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() Status in “ibus” package in Ubuntu: New Bug description: Running Xubuntu 14.04 I had just quit frescobaldi, qsynth and qjackctl. More likely to be one or both of the latter two, as I've used frescobaldi on its own with no problems with ibus. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ibus 1.5.4-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 Date: Thu Feb 6 18:59:41 2014 ExecutablePath: /usr/bin/ibus-daemon ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lp lpadmin sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1252220] Re: gnome-sudoku crashes with TypeError when saving a "very hard" game
I can confirm that the latest update is working correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1252220 Title: gnome-sudoku crashes with TypeError when saving a "very hard" game Status in “gnome-sudoku” package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-sudoku. This problem was most recently seen with version 1:3.8.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/8c47c556e13b16454ddc18b00d4217bad720461c contains more details. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 52, in inactivate_new_game_etc_ ret = fun(ui, *args, **kwargs) File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 413, in new_cb self.select_game() File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 52, in inactivate_new_game_etc_ ret = fun(ui, *args, **kwargs) File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 150, in select_game choice = game_selector.NewOrSavedGameSelector().run_swallowed_dialog(self.swallower) File "/usr/lib/python3/dist-packages/gnome_sudoku/game_selector.py", line 270, in run_swallowed_dialog self.setup_dialog() File "/usr/lib/python3/dist-packages/gnome_sudoku/game_selector.py", line 93, in setup_dialog self.make_saved_game_model() File "/usr/lib/python3/dist-packages/gnome_sudoku/game_selector.py", line 187, in make_saved_game_model sdifficulty = sr.difficulty() File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 836, in difficulty self.solve() File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 407, in solve while not self.guess_least_open_square(): File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 832, in guess_least_open_square return SudokuSolver.guess_least_open_square(self) File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 448, in guess_least_open_square poss.sort(lambda a, b: len(a[1]) > len(b[1]) and 1 or len(a[1]) < len(b[1]) and -1 or \ TypeError: must use keyword argument for key function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1252220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1264620] [NEW] Gnome sudoku won't load after saving very hard game
Public bug reported: After saving a "very hard" game, Gnome sudoku won't load. The window appear briefly and then the program exits. Launching from command line gives the following message: Traceback (most recent call last): File "/usr/games/gnome-sudoku", line 23, in start_game() File "/usr/lib/python3/dist-packages/gnome_sudoku/gnome_sudoku.py", line 25, in start_game main.start_game() File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 982, in start_game u = UI() File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 138, in __init__ if self.select_game(): File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 52, in inactivate_new_game_etc_ ret = fun(ui, *args, **kwargs) File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 150, in select_game choice = game_selector.NewOrSavedGameSelector().run_swallowed_dialog(self.swallower) File "/usr/lib/python3/dist-packages/gnome_sudoku/game_selector.py", line 270, in run_swallowed_dialog self.setup_dialog() File "/usr/lib/python3/dist-packages/gnome_sudoku/game_selector.py", line 93, in setup_dialog self.make_saved_game_model() File "/usr/lib/python3/dist-packages/gnome_sudoku/game_selector.py", line 187, in make_saved_game_model sdifficulty = sr.difficulty() File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 836, in difficulty self.solve() File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 407, in solve while not self.guess_least_open_square(): File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 832, in guess_least_open_square return SudokuSolver.guess_least_open_square(self) File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 448, in guess_least_open_square poss.sort(lambda a, b: len(a[1]) > len(b[1]) and 1 or len(a[1]) < len(b[1]) and -1 or \ TypeError: must use keyword argument for key function Deleting the saved game file from ~/.config/gnome-sudoku/saved allows the program to run properly once more. I've not had any problems after saving an easy game. I haven't tried with other levels yet. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-sudoku 1:3.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 Date: Sat Dec 28 16:33:43 2013 PackageArchitecture: all ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: gnome-sudoku UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-sudoku (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1264620 Title: Gnome sudoku won't load after saving very hard game Status in “gnome-sudoku” package in Ubuntu: New Bug description: After saving a "very hard" game, Gnome sudoku won't load. The window appear briefly and then the program exits. Launching from command line gives the following message: Traceback (most recent call last): File "/usr/games/gnome-sudoku", line 23, in start_game() File "/usr/lib/python3/dist-packages/gnome_sudoku/gnome_sudoku.py", line 25, in start_game main.start_game() File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 982, in start_game u = UI() File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 138, in __init__ if self.select_game(): File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 52, in inactivate_new_game_etc_ ret = fun(ui, *args, **kwargs) File "/usr/lib/python3/dist-packages/gnome_sudoku/main.py", line 150, in select_game choice = game_selector.NewOrSavedGameSelector().run_swallowed_dialog(self.swallower) File "/usr/lib/python3/dist-packages/gnome_sudoku/game_selector.py", line 270, in run_swallowed_dialog self.setup_dialog() File "/usr/lib/python3/dist-packages/gnome_sudoku/game_selector.py", line 93, in setup_dialog self.make_saved_game_model() File "/usr/lib/python3/dist-packages/gnome_sudoku/game_selector.py", line 187, in make_saved_game_model sdifficulty = sr.difficulty() File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 836, in difficulty self.solve() File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 407, in solve while not self.guess_least_open_square(): File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 832, in guess_least_open_square return SudokuSolver.guess_least_open_square(self) File "/usr/lib/python3/dist-packages/gnome_sudoku/sudoku.py", line 448, in guess_least_open_square poss.sort(lambda a, b: len(a[1]) > len(b[1]) and 1
[Desktop-packages] [Bug 1261600] Re: Window for Sudoku "New Game" is about 30 px high and can't be enlarged (Trusty)
After today's update this bug appears to be fixed. The "New Game" area now takes up most of the main window. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1261600 Title: Window for Sudoku "New Game" is about 30 px high and can't be enlarged (Trusty) Status in “gnome-sudoku” package in Ubuntu: Confirmed Status in “gtk+3.0” package in Ubuntu: New Bug description: I'm running Xubuntu 14.04. Most of the menu items are greyed out (exceptions are "Print" and "Close"). Now that I know the window is there, I can scroll down so that I can see the various game choices. But on first glance, it looks like there's a "New Game" title and the rest of the window didn't render. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-sudoku 1:3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 17 15:24:05 2013 PackageArchitecture: all SourcePackage: gnome-sudoku UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1261600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261600] Re: Window for Sudoku "New Game" is about 30 px high and can't be enlarged (Trusty)
** Summary changed: - Window for "New Game" is about 30 px high and can't be enlarged (Trusty) + Window for Sudoku "New Game" is about 30 px high and can't be enlarged (Trusty) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1261600 Title: Window for Sudoku "New Game" is about 30 px high and can't be enlarged (Trusty) Status in “gnome-sudoku” package in Ubuntu: New Bug description: I'm running Xubuntu 14.04. Most of the menu items are greyed out (exceptions are "Print" and "Close"). Now that I know the window is there, I can scroll down so that I can see the various game choices. But on first glance, it looks like there's a "New Game" title and the rest of the window didn't render. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-sudoku 1:3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 17 15:24:05 2013 PackageArchitecture: all SourcePackage: gnome-sudoku UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1261600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261600] [NEW] Window for "New Game" is about 30 px high and can't be enlarged (Trusty)
Public bug reported: I'm running Xubuntu 14.04. Most of the menu items are greyed out (exceptions are "Print" and "Close"). Now that I know the window is there, I can scroll down so that I can see the various game choices. But on first glance, it looks like there's a "New Game" title and the rest of the window didn't render. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-sudoku 1:3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 17 15:24:05 2013 PackageArchitecture: all SourcePackage: gnome-sudoku UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-sudoku (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1261600 Title: Window for "New Game" is about 30 px high and can't be enlarged (Trusty) Status in “gnome-sudoku” package in Ubuntu: New Bug description: I'm running Xubuntu 14.04. Most of the menu items are greyed out (exceptions are "Print" and "Close"). Now that I know the window is there, I can scroll down so that I can see the various game choices. But on first glance, it looks like there's a "New Game" title and the rest of the window didn't render. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-sudoku 1:3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 17 15:24:05 2013 PackageArchitecture: all SourcePackage: gnome-sudoku UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1261600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy & Trusty
The latest update is working with the following chip: 01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1205643 Title: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy & Trusty Status in “xserver-xorg-video-openchrome” package in Ubuntu: Incomplete Bug description: Please bear with me and read all of this. Since I can't get a working display in Saucy with that graphics chip I need to use this method to file the initial bug report, but I can provide info using a chroot or replacing the "quiet splash" boot parameter with "text" which takes me to a tty interface. I hope using the tty interface provided by using the "text" boot parameter I can use "apport-collect" to collect the info needed from an installed Lubuntu 13.10 but I won't do so until asked by a dev in case some "switch" needs to be set to collect the appropriate info. I also want to say that I'm fully aware that graphics chip is not supported by Ubuntu/compiz itself, or even GNOME's mutter window manager, but I think it should still work with the openbox, metacity, and Xfwm window managers .. at least I hope so :^) So onto what actually happens. When I try to boot either Lubuntu or Xubuntu Saucy Alpha 2, either the live image or an installed version, I just get a frozen progress bar. So it's just 5 frozen dots on the screen. If I try booting through the recovery mode or otherwise trying to "startx" or "'sudo service lightdm start' I just get a blank screen. I can see the backlight is working but that's all. This is the specific hardware: VIA C7 CPU @ 1500MHz VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01) VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60) Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78) 1GB DDR2 RAM I did take a pic of the live image boot process while dealing with an unrelated d-i bug during Lubuntu Alpha 2 testing process: https://launchpadlibrarian.net/145894508/P4M800_xfreeze.JPG Now I'm wondering what else to say ... the same Saucy images and installs work with two other totally different sets of hardware. I'm ready to roll up my sleeves to help gather any needed info. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy
The workaround works on my machine. "Low performance" seems to mean the vesa driver, which I have always used on this PC, and which is fine by me. Xorg cpu and memory usage seem to be the same as in 12.04. Many thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1205643 Title: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy Status in “xorg” package in Ubuntu: Confirmed Bug description: Please bear with me and read all of this. Since I can't get a working display in Saucy with that graphics chip I need to use this method to file the initial bug report, but I can provide info using a chroot or replacing the "quiet splash" boot parameter with "text" which takes me to a tty interface. I hope using the tty interface provided by using the "text" boot parameter I can use "apport-collect" to collect the info needed from an installed Lubuntu 13.10 but I won't do so until asked by a dev in case some "switch" needs to be set to collect the appropriate info. I also want to say that I'm fully aware that graphics chip is not supported by Ubuntu/compiz itself, or even GNOME's mutter window manager, but I think it should still work with the openbox, metacity, and Xfwm window managers .. at least I hope so :^) So onto what actually happens. When I try to boot either Lubuntu or Xubuntu Saucy Alpha 2, either the live image or an installed version, I just get a frozen progress bar. So it's just 5 frozen dots on the screen. If I try booting through the recovery mode or otherwise trying to "startx" or "'sudo service lightdm start' I just get a blank screen. I can see the backlight is working but that's all. This is the specific hardware: VIA C7 CPU @ 1500MHz VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01) VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60) Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78) 1GB DDR2 RAM I did take a pic of the live image boot process while dealing with an unrelated d-i bug during Lubuntu Alpha 2 testing process: https://launchpadlibrarian.net/145894508/P4M800_xfreeze.JPG Now I'm wondering what else to say ... the same Saucy images and installs work with two other totally different sets of hardware. I'm ready to roll up my sleeves to help gather any needed info. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1205643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1178373] Re: Restart spawns a password box
Still seeing this here as well, on an up-to-date install. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1178373 Title: Restart spawns a password box Status in Light Display Manager: Invalid Status in “lightdm” package in Ubuntu: Invalid Status in “xfce4-session” package in Ubuntu: Confirmed Bug description: Daily live Xubuntu. Go to Logout button - choose Restart. Box requiring password appears - impossible to enter password to proceed. Have to logout then shutdown then restart. Shutdown spawns the same password box. If you login as Guest then Shutdown/restart work as anticipated. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1 Uname: Linux 3.9.0-1-generic x86_64 ApportVersion: 2.10-0ubuntu1 Architecture: amd64 Date: Thu May 9 19:26:05 2013 InstallationDate: Installed on 2013-05-09 (0 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130509) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter user-session=xubuntu LightdmGreeterLog: ** (lightdm-gtk-greeter:1094): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory ** (lightdm-gtk-greeter:1094): WARNING **: Failed to load user image: Failed to open file '/home/hob/.face': No such file or directory LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1570): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory ** (lightdm-gtk-greeter:1570): WARNING **: Failed to load user image: Failed to open file '/home/hob/.face': No such file or directory MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1178373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1159398] Re: buggy openchrome driver renders desktop unusable
I'm also having problems with an chrome chipset. So far I've only tested with a liveCD. lspci shows: VGA compatible controller [0300]: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01) (prog-if 00 [VGA controller]) I'm not getting the artefacts that the OP is getting, but the screen is rendering in slow motion and I notice that compiz is maxing out the CPU much of the time. Trying to do anything with the PC is like the proverbial wading through molasses. I don't remember if I've run 12.10 on this machine, but 12.04 and previous versions have been fine. I suspect that the system has been defaulting to vesa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1159398 Title: buggy openchrome driver renders desktop unusable Status in “xserver-xorg-video-openchrome” package in Ubuntu: Confirmed Bug description: I'm having a serious graphics problem in Ubuntu 13.04. When the X starts up, I get a glitchy set of squares that turns red with a discolored overlay of what I should be seeing. I also see no cursor whatsoever. Using lspci I got this for my video card: 01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01) Additional Details: Openchrome has worked perfectly up until this release of Ubuntu 13.04 and assuming latest release of openchrome. What I am guessing is my video card is having problems with GLX, though there doesn't seem to be any easy way to disable it (which is something I shouldn't have to do in the first place). The little bit of what you're *supposed* to see is also updating at an unnervingly low framerate, furthing my suspicion that it's a serious problem with acceleration. It takes a while for the (glitchy) display to appear in the first place. It didn't (thankfully) keep me from switching consoles. The boot splash is show in text-mode only (this specific anomaly has happed in previous releases though strangly on on the live session) Please see if you can fix this or forward this to someone who can see what they can do. Thank you for reading my bug request. --- .tmp.unity.support.test.1: ApportVersion: 2.9.2-0ubuntu2 Architecture: i386 CasperVersion: 1.330 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu GraphicsCard: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] [1106:3344] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Gateway, Inc. Device [107b:0216] LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130321) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gateway MX3215 MarkForUpload: True Package: xserver-xorg-video-openchrome 1:0.3.1-0ubuntu1 PackageArchitecture: i386 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Tags: raring ubuntu single-occurrence reproducible Uname: Linux 3.8.0-13-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: XorgConf: Section "Device" Identifier "VIA Unichrome Pro" Driver "vesa" EndSection dmi.bios.date: 02/22/2006 dmi.bios.vendor: Phoenix dmi.bios.version: 73.07 dmi.board.vendor: Gateway dmi.board.version: Rev1.73.07 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: Gateway dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvr73.07:bd02/22/2006:svnGateway:pnMX3215:pvr73.07:rvnGateway:rn:rvrRev1.73.07:cvnGateway:ct8:cvrN/A: dmi.product.name: MX3215 dmi.product.version: 73.07 dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.9~daily13.03.20-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu2b1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-x
[Desktop-packages] [Bug 582023] Re: HP Officejet 5610 printout mode options ignored
With Lucid close to end-of-life, this bug is now ancient history and should probably be retired. I've not had this problem on Ubuntu 12.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/582023 Title: HP Officejet 5610 printout mode options ignored Status in “cups” package in Ubuntu: New Bug description: Binary package hint: cups Ever since I installed Ubuntu 7.04, my HP Officejet 5610 does not print in full black unless I set the printout mode options to "600 dpi, color, black + color cartridge". I set the default options in CUPS to this setting. If I don't do this, I get a 80-90% grey, which looks like I need to replace the black cartridge. The workaround was successful in Feisty, Gutsy and Hardy. Now that I've moved to 10.04, I've discovered that most programs will not make use of this option. They print out in dark grey instead of black, which does not look very professional. There are three exceptions that I've found: OpenOffice.org, MSWord 2000 through Wine, and Scribus. All these programs use their own printer dialogues instead of the standard one used by the other programs I've tested (geany, gedit, Firefox, Tomboy notes, evince). I booted up a 9.10 live CD and found the same problem there. If I choose "print test page" in CUPS, it prints correctly in full black. There's an error message in cups.log (attached) which I think is irrelevant to this report. It happened when I was trying to reconfigure something and it crashed. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cups 1.4.3-1 ProcVersionSignature: Ubuntu 2.6.32-22.33.lp562742.3-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 CupsErrorLog: E [18/May/2010:10:49:02 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/sample.drv"! E [18/May/2010:10:49:20 +1200] PID 5393 (/usr/lib/cups/daemon/cups-driverd) crashed on signal 11! E [18/May/2010:10:49:57 +1200] Returning IPP client-error-document-format-not-supported for Send-Document (ipp://localhost:631/printers/Officejet-5600-series) from localhost E [18/May/2010:11:57:51 +1200] Unable to remove temporary file "/var/spool/cups/tmp/.hplip" - Is a directory Date: Tue May 18 11:59:37 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1) Lpstat: device for Officejet-5600-series: hp:/usb/Officejet_5600_series?serial=CN66NDF84304B2 device for Officejet-5600-series-Fax: hpfax:/usb/Officejet_5600_series?serial=CN66NDF84304B2 MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Officejet-5600-series-Fax: HP Fax hpijs Officejet-5600-series: HP Officejet 5600 Series hpijs, 3.10.2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=d458c1cf-f605-477d-84de-305d54731aee ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_NZ.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 03/25/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5VD2-VM ACPI BIOS Revision 1302 dmi.board.name: P5VD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5VD2-VMACPIBIOSRevision1302:bd03/25/2008:svnSystemmanufacturer:pnSystemProductName:pvr:rvnASUSTeKComputerINC.:rnP5VD2-VM:rvr1.XX:cvnChassisManufacture:ct3:cvr: dmi.product.name: System Product Name dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/582023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967905] Re: Xorg using excessive CPU
That particular version of Thunderbird is long since superseded, and I don't have the problem any more. The bug can be expired as far as I'm concerned. Are individual reporters supposed to change the status of bugs in cases like this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/967905 Title: Xorg using excessive CPU Status in “thunderbird” package in Ubuntu: Incomplete Bug description: I'm using Thunderbird 11.0 from Mozilla (not the repositories) so that I can share a profile with other installations. Just over the last few days, if I start Thunderbird as soon as I've logged into Precise, xorg starts hogging CPU. Top shows over 90% in use, and the system becomes very sluggish. The only cure seems to be either rebooting or (simpler) logging out and in again. Sometimes I have to kill the Xserver instead of logging out. Waiting for a little while (say, a minute) before launching Thunderbird seems to solve the problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 .tmp.unity.support.test.1: ApportVersion: 1.95-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 29 13:29:41 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=366c0083-3641-4b50-9a87-12c0fbca9703 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5VD2-VM ACPI BIOS Revision 1302 dmi.board.name: P5VD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5VD2-VMACPIBIOSRevision1302:bd03/25/2008:svnSystemmanufacturer:pnSystemProductName:pvr:rvnASUSTeKComputerINC.:rnP5VD2-VM:rvr1.XX:cvnChassisManufacture:ct3:cvr: dmi.product.name: System Product Name dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/967905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964288] Re: NetworkManager fails to make DHCP-supplied nameserver addresses available
@Thomas Hood I haven't seen this error for many weeks now. Do you still want the files? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/964288 Title: NetworkManager fails to make DHCP-supplied nameserver addresses available Status in “network-manager” package in Ubuntu: Incomplete Bug description: On occasion, network manager doesn't find/assign a DNS server. This is with an up-to-date Precise install, and on this occasion when ISO testing. I doubt that it has to do with hardware, because it's happened on two completely different machines (Asus EeePC 900 with Atheros L2 chip and a desktop machine with r8169). When this happens, the computer is assigned an IP number, an internet connection exists and I can ping various websites plus my router by using the IP number. Website names of course don't get resolved. The problem is solved (in the short term) by entering "sudo dhclient" in a terminal. ~$ sudo dhclient RTNETLINK answers: File exists Before issuing this command, /etc/resolv.conf reads: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search lan After issuing the command, /etc/resolv.conf reads: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.254 nameserver 127.0.0.1 search lan ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Sun Mar 25 01:51:16 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/964288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967905] Re: Xorg using excessive CPU
This *may* be related, though I'm not 100% sure. Today, I was running updates in synaptic and writing an email in Thunderbird at the same time. I selected some text and tried to drag it to a new position in the email. X completely locked up. I could move the mouse pointer but couldn't click on anything. Ctrl-alt-backspace (I have it set to kill the X server) did nothing. Alt-sysrq-REISUB brought about a reboot, but a grub error ensued. /dev/sdb (sata disk 2) had completely disappeared from the BIOS listing!! Disconnecting power entirely for a few minutes solved that problem. Had something of this kind not happened to me previously, I'd have been in a first-class panic. Once the system was reloaded, the mouse pointer was still locked and another reboot was needed to fix that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/967905 Title: Xorg using excessive CPU Status in “thunderbird” package in Ubuntu: New Bug description: I'm using Thunderbird 11.0 from Mozilla (not the repositories) so that I can share a profile with other installations. Just over the last few days, if I start Thunderbird as soon as I've logged into Precise, xorg starts hogging CPU. Top shows over 90% in use, and the system becomes very sluggish. The only cure seems to be either rebooting or (simpler) logging out and in again. Sometimes I have to kill the Xserver instead of logging out. Waiting for a little while (say, a minute) before launching Thunderbird seems to solve the problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 .tmp.unity.support.test.1: ApportVersion: 1.95-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 29 13:29:41 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=366c0083-3641-4b50-9a87-12c0fbca9703 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5VD2-VM ACPI BIOS Revision 1302 dmi.board.name: P5VD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5VD2-VMACPIBIOSRevision1302:bd03/25/2008:svnSystemmanufacturer:pnSystemProductName:pvr:rvnASUSTeKComputerINC.:rnP5VD2-VM:rvr1.XX:cvnChassisManufacture:ct3:cvr: dmi.product.name: System Product Name dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/967905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967905] Re: Xorg using excessive CPU
Just to add to the fun, I had the problem occur *without* launching Thunderbird. As before, logging out fixed it. I checked the link, and found it too much for my tired brain at the moment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/967905 Title: Xorg using excessive CPU Status in “thunderbird” package in Ubuntu: New Bug description: I'm using Thunderbird 11.0 from Mozilla (not the repositories) so that I can share a profile with other installations. Just over the last few days, if I start Thunderbird as soon as I've logged into Precise, xorg starts hogging CPU. Top shows over 90% in use, and the system becomes very sluggish. The only cure seems to be either rebooting or (simpler) logging out and in again. Sometimes I have to kill the Xserver instead of logging out. Waiting for a little while (say, a minute) before launching Thunderbird seems to solve the problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 .tmp.unity.support.test.1: ApportVersion: 1.95-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 29 13:29:41 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=366c0083-3641-4b50-9a87-12c0fbca9703 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5VD2-VM ACPI BIOS Revision 1302 dmi.board.name: P5VD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5VD2-VMACPIBIOSRevision1302:bd03/25/2008:svnSystemmanufacturer:pnSystemProductName:pvr:rvnASUSTeKComputerINC.:rnP5VD2-VM:rvr1.XX:cvnChassisManufacture:ct3:cvr: dmi.product.name: System Product Name dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/967905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964288] Re: Network manager not always finding DNS servers
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/964288 Title: Network manager not always finding DNS servers Status in “network-manager” package in Ubuntu: New Bug description: On occasion, network manager doesn't find/assign a DNS server. This is with an up-to-date Precise install, and on this occasion when ISO testing. I doubt that it has to do with hardware, because it's happened on two completely different machines (Asus EeePC 900 with Atheros L2 chip and a desktop machine with r8169). When this happens, the computer is assigned an IP number, an internet connection exists and I can ping various websites plus my router by using the IP number. Website names of course don't get resolved. The problem is solved (in the short term) by entering "sudo dhclient" in a terminal. ~$ sudo dhclient RTNETLINK answers: File exists Before issuing this command, /etc/resolv.conf reads: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search lan After issuing the command, /etc/resolv.conf reads: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.254 nameserver 127.0.0.1 search lan ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Sun Mar 25 01:51:16 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/964288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964288] [NEW] Network manager not always finding DNS servers
Public bug reported: On occasion, network manager doesn't find/assign a DNS server. This is with an up-to-date Precise install, and on this occasion when ISO testing. I doubt that it has to do with hardware, because it's happened on two completely different machines (Asus EeePC 900 with Atheros L2 chip and a desktop machine with r8169). When this happens, the computer is assigned an IP number, an internet connection exists and I can ping various websites plus my router by using the IP number. Website names of course don't get resolved. The problem is solved (in the short term) by entering "sudo dhclient" in a terminal. ~$ sudo dhclient RTNETLINK answers: File exists Before issuing this command, /etc/resolv.conf reads: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search lan After issuing the command, /etc/resolv.conf reads: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.254 nameserver 127.0.0.1 search lan ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Sun Mar 25 01:51:16 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/964288 Title: Network manager not always finding DNS servers Status in “network-manager” package in Ubuntu: New Bug description: On occasion, network manager doesn't find/assign a DNS server. This is with an up-to-date Precise install, and on this occasion when ISO testing. I doubt that it has to do with hardware, because it's happened on two completely different machines (Asus EeePC 900 with Atheros L2 chip and a desktop machine with r8169). When this happens, the computer is assigned an IP number, an internet connection exists and I can ping various websites plus my router by using the IP number. Website names of course don't get resolved. The problem is solved (in the short term) by entering "sudo dhclient" in a terminal. ~$ sudo dhclient RTNETLINK answers: File exists Before issuing this command, /etc/resolv.conf reads: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search lan After issuing the command, /etc/resolv.conf reads: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.254 nameserver 127.0.0.1 search lan ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Sun Mar 25 01:51:16 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/964288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 894347] Re: Force Quit applet never quits
I've noticed the same thing in Ubuntu 12.04. Incidentally, the application doesn't even have to be misbehaving for this to happen. I opened gedit, did nothing with it, and then used "force quit" on it. Everything locked up and I had to restart X. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/894347 Title: Force Quit applet never quits Status in “gnome-panel” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) add "Force Quit" applet to panel 2) get a large file (70 megs in this case) and rename it to end with .sh 3) open the file with gedit. gedit freezes. 4) click on "Force a misbehaving application to quit" applet 5) the applet starts, but clicking anywhere does nothing. Pressing esc does nothing. I didn't find a way to exit this situation without killing gnome- session from VT and this caused unsaved work to be lost. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-panel 1:3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic-pae 3.0.6 Uname: Linux 3.0.0-13-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 CheckboxSubmission: 5411b7083f2413511daec522a712c016 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 Date: Thu Nov 24 13:25:07 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-panel InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: Upgraded to oneiric on 2011-10-20 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/894347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 951464] Re: Wireless connections in network-manager-applet not editable
I found this bug when trying to set up a connection using network- manager in Openbox. I think this is a recent bug. I set up a very similar system a few days ago without this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/951464 Title: Wireless connections in network-manager-applet not editable Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: Right-click on the network manager applet --> edit connections On the tab wireless is the current network shown, I'd like to connect. In order to do so, I need to edit the connection. If I click on edit, the following "error" appears as a dialog: Error initializing editor No agents were available for this request. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Sat Mar 10 12:20:20 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nm-connection-editor InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228) IpRoute: default via 132.176.143.126 dev eth0 proto static 132.176.143.96/27 dev eth0 proto kernel scope link src 132.176.143.98 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-03-10 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1cc30221a-025d-4302-9360-b6e3e63ab9e4 802-3-ethernet1331377520 Sat 10 Mar 2012 12:05:20 PM CETyes no /org/freedesktop/NetworkManager/Settings/0 FU-StZ6e673f08-626e-4293-b943-753fa944b0d3 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/951464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 952620] Re: Evolution freezes when attempting to compose email in html format
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/952620 Title: Evolution freezes when attempting to compose email in html format Status in “evolution” package in Ubuntu: New Bug description: When I choose a different colour when composing an email in html format, Evolution locks up. I can move the mouse but clicking on any of the buttons in the email compose window does nothing. I can still click on the close box, but I'm asked to save or discard the message, so I can't get any further. The only way out is to kill Evolution altogether. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 12 12:38:24 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/952620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 952620] [NEW] Evolution freezes when attempting to compose email in html format
Public bug reported: When I choose a different colour when composing an email in html format, Evolution locks up. I can move the mouse but clicking on any of the buttons in the email compose window does nothing. I can still click on the close box, but I'm asked to save or discard the message, so I can't get any further. The only way out is to kill Evolution altogether. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 12 12:38:24 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/952620 Title: Evolution freezes when attempting to compose email in html format Status in “evolution” package in Ubuntu: New Bug description: When I choose a different colour when composing an email in html format, Evolution locks up. I can move the mouse but clicking on any of the buttons in the email compose window does nothing. I can still click on the close box, but I'm asked to save or discard the message, so I can't get any further. The only way out is to kill Evolution altogether. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 12 12:38:24 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/952620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 946116] Re: lightdm fails to bring up X display automatically after boot
This sounds very similar to Bug #935591. The difference seems to be that another window manager is involved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/946116 Title: lightdm fails to bring up X display automatically after boot Status in “lightdm” package in Ubuntu: Confirmed Bug description: I recently installed Xubuntu 12.04 alpha2 and have updated it equivalent to beta1. The X display does not automatically bring up a login screen. What I currently have to do is to get a login (using Alt-F2 or Alt-F1), login as root, then run lightdm from the bash command line, which brings up a login, and I can login with my user ID, after which X appears to run normally with Xfce etc. Ubuntu version and kernel version DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu precise (development branch)" Linux compaq 3.2.0-17-generic #27-Ubuntu SMP Fri Feb 24 15:37:36 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux model name: AMD Athlon(tm) 64 Processor 3800+ cpu MHz : 1000.000 This problem doesn't seem to depend on whether I have an xorg.conf file in /etc/X11 I have appended a gzip file which includes Xorg.0.* at various stages, my xorg.conf file, and dmesg output. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.4.is.1.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.94-0ubuntu1 Architecture: amd64 Date: Sat Mar 3 22:08:11 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120201.1) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/946116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 933770] [NEW] EDS not registering new data in CalDAV calendar on first sync
Public bug reported: I'm using SyncEvolution (v.1.2.2 from the developer's repo) to sync a Nokia E63 phone with Evolution, via bluetooth. The calendar in question is a CalDAV calendar running on a local Radicale server. When I add new events to the calendar, they appear in Evolution, but on syncing with the phone, they don't migrate to the phone. A second sync will cause the migration to occur. After discussion with the SyncEvolution developer, I understand that the problem lies with EDS not refreshing its copy of the data the first time that SyncEvolution asked for the calendar. This problem doesn't occur in Lucid and looks to me like a regression. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution-data-server 3.2.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Fri Feb 17 10:04:28 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/933770 Title: EDS not registering new data in CalDAV calendar on first sync Status in “evolution-data-server” package in Ubuntu: New Bug description: I'm using SyncEvolution (v.1.2.2 from the developer's repo) to sync a Nokia E63 phone with Evolution, via bluetooth. The calendar in question is a CalDAV calendar running on a local Radicale server. When I add new events to the calendar, they appear in Evolution, but on syncing with the phone, they don't migrate to the phone. A second sync will cause the migration to occur. After discussion with the SyncEvolution developer, I understand that the problem lies with EDS not refreshing its copy of the data the first time that SyncEvolution asked for the calendar. This problem doesn't occur in Lucid and looks to me like a regression. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution-data-server 3.2.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Fri Feb 17 10:04:28 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/933770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 933770] Re: EDS not registering new data in CalDAV calendar on first sync
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/933770 Title: EDS not registering new data in CalDAV calendar on first sync Status in “evolution-data-server” package in Ubuntu: New Bug description: I'm using SyncEvolution (v.1.2.2 from the developer's repo) to sync a Nokia E63 phone with Evolution, via bluetooth. The calendar in question is a CalDAV calendar running on a local Radicale server. When I add new events to the calendar, they appear in Evolution, but on syncing with the phone, they don't migrate to the phone. A second sync will cause the migration to occur. After discussion with the SyncEvolution developer, I understand that the problem lies with EDS not refreshing its copy of the data the first time that SyncEvolution asked for the calendar. This problem doesn't occur in Lucid and looks to me like a regression. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution-data-server 3.2.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Fri Feb 17 10:04:28 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/933770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 930491] Re: Large memory leak in nm-applet
Asus EeePC 900, 1GB RAM, up-to-date install of precise nm-applet was using 6.4 MB of memory at initial boot. Five hours later, that had increased to 49.1 MB, 6.1% of total. There are about 18 or so WiFi access points visible. So far, I've not noticed any unresponsive behaviour in the applet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/930491 Title: Large memory leak in nm-applet Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: In an up-to-date precise install, memory usage by nm-applet climbs rapidly to hundreds of Mb within an hour after it's started. Valgrind log attached. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.0-15-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Fri Feb 10 19:23:00 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1) IpRoute: default via 192.168.2.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.15 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ribeira f828a6c2-179f-41ab-acdd-bf27da31c6d5 802-11-wireless 1328916417 Fri 10 Feb 2012 06:26:57 PM ESTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/930491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 919048] Re: Unable to browse Nokia E63 over bluetooth in Ubuntu Precise
I think that this may be a duplicate of Bug #899858 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/919048 Title: Unable to browse Nokia E63 over bluetooth in Ubuntu Precise Status in “gvfs” package in Ubuntu: New Bug description: When attempting to browse the phone over bluetooth, the phone appears to mount temporarily but then unmounts with the error message: Could not open location 'obex://[BTaddr]/' Error while getting peer-to-peer dbus connection: Message did not receive a reply (timeout by message bus) if I'm using Gnome-bluetooth or Could not display "obex://[BTaddr]/". Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Please select another viewer and try again. Could not open location 'obex://[BTaddr]/' Error while getting peer-to-peer dbus connection: The name :1.132 was not provided by any .service files if I attempt the operation using Blueman. I can mount and browse the phone successfully using obexfs. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gvfs 1.10.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1 Uname: Linux 3.2.0-9-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Fri Jan 20 17:31:21 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/919048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 919048] Re: Unable to browse Nokia E63 over bluetooth in Ubuntu Precise
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/919048 Title: Unable to browse Nokia E63 over bluetooth in Ubuntu Precise Status in “gvfs” package in Ubuntu: New Bug description: When attempting to browse the phone over bluetooth, the phone appears to mount temporarily but then unmounts with the error message: Could not open location 'obex://[BTaddr]/' Error while getting peer-to-peer dbus connection: Message did not receive a reply (timeout by message bus) if I'm using Gnome-bluetooth or Could not display "obex://[BTaddr]/". Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Please select another viewer and try again. Could not open location 'obex://[BTaddr]/' Error while getting peer-to-peer dbus connection: The name :1.132 was not provided by any .service files if I attempt the operation using Blueman. I can mount and browse the phone successfully using obexfs. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gvfs 1.10.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1 Uname: Linux 3.2.0-9-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Fri Jan 20 17:31:21 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/919048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 919048] [NEW] Unable to browse Nokia E63 over bluetooth in Ubuntu Precise
Public bug reported: When attempting to browse the phone over bluetooth, the phone appears to mount temporarily but then unmounts with the error message: Could not open location 'obex://[BTaddr]/' Error while getting peer-to-peer dbus connection: Message did not receive a reply (timeout by message bus) if I'm using Gnome-bluetooth or Could not display "obex://[BTaddr]/". Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Please select another viewer and try again. Could not open location 'obex://[BTaddr]/' Error while getting peer-to-peer dbus connection: The name :1.132 was not provided by any .service files if I attempt the operation using Blueman. I can mount and browse the phone successfully using obexfs. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gvfs 1.10.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1 Uname: Linux 3.2.0-9-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Fri Jan 20 17:31:21 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/919048 Title: Unable to browse Nokia E63 over bluetooth in Ubuntu Precise Status in “gvfs” package in Ubuntu: New Bug description: When attempting to browse the phone over bluetooth, the phone appears to mount temporarily but then unmounts with the error message: Could not open location 'obex://[BTaddr]/' Error while getting peer-to-peer dbus connection: Message did not receive a reply (timeout by message bus) if I'm using Gnome-bluetooth or Could not display "obex://[BTaddr]/". Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Please select another viewer and try again. Could not open location 'obex://[BTaddr]/' Error while getting peer-to-peer dbus connection: The name :1.132 was not provided by any .service files if I attempt the operation using Blueman. I can mount and browse the phone successfully using obexfs. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gvfs 1.10.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1 Uname: Linux 3.2.0-9-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Fri Jan 20 17:31:21 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/919048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913263] Re: gnome-system-log assert failure: *** glibc detected *** gnome-system-log: free(): invalid next size (fast): 0x09850980 ***
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/913263 Title: gnome-system-log assert failure: *** glibc detected *** gnome-system- log: free(): invalid next size (fast): 0x09850980 *** Status in “gnome-utils” package in Ubuntu: New Bug description: On attempting to open a log file in Log File Viewer, the application crashed. Ubuntu version is precise alpha1 (up to date) ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-system-log 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0 Uname: Linux 3.2.0-8-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 AssertionMessage: *** glibc detected *** gnome-system-log: free(): invalid next size (fast): 0x09850980 *** Date: Sun Jan 8 10:35:04 2012 ExecutablePath: /usr/bin/gnome-system-log InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: gnome-system-log Signal: 6 SourcePackage: gnome-utils StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 Title: gnome-system-log assert failure: *** glibc detected *** gnome-system-log: free(): invalid next size (fast): 0x09850980 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/913263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913263] [NEW] gnome-system-log assert failure: *** glibc detected *** gnome-system-log: free(): invalid next size (fast): 0x09850980 ***
Public bug reported: On attempting to open a log file in Log File Viewer, the application crashed. Ubuntu version is precise alpha1 (up to date) ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-system-log 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0 Uname: Linux 3.2.0-8-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 AssertionMessage: *** glibc detected *** gnome-system-log: free(): invalid next size (fast): 0x09850980 *** Date: Sun Jan 8 10:35:04 2012 ExecutablePath: /usr/bin/gnome-system-log InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: gnome-system-log Signal: 6 SourcePackage: gnome-utils StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 Title: gnome-system-log assert failure: *** glibc detected *** gnome-system-log: free(): invalid next size (fast): 0x09850980 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare www-data ** Affects: gnome-utils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/913263 Title: gnome-system-log assert failure: *** glibc detected *** gnome-system- log: free(): invalid next size (fast): 0x09850980 *** Status in “gnome-utils” package in Ubuntu: New Bug description: On attempting to open a log file in Log File Viewer, the application crashed. Ubuntu version is precise alpha1 (up to date) ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-system-log 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0 Uname: Linux 3.2.0-8-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 AssertionMessage: *** glibc detected *** gnome-system-log: free(): invalid next size (fast): 0x09850980 *** Date: Sun Jan 8 10:35:04 2012 ExecutablePath: /usr/bin/gnome-system-log InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: gnome-system-log Signal: 6 SourcePackage: gnome-utils StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 Title: gnome-system-log assert failure: *** glibc detected *** gnome-system-log: free(): invalid next size (fast): 0x09850980 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/913263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 897414] Re: software-center crashed with SIGSEGV
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/897414 Title: software-center crashed with SIGSEGV Status in “software-center” package in Ubuntu: New Bug description: I had installed a package manually - successfully, as far as I can tell. I closed Software Centre normally, and shortly afterwards got the Apport dialogue about reporting a bug. The installation, though it says it's Ubuntu 11.10, is a Precise testing install. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: software-center 5.1.2.1 ProcVersionSignature: Ubuntu 3.2.0-1.3-generic 3.2.0-rc2 Uname: Linux 3.2.0-1-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Tue Nov 29 09:36:32 2011 ExecutablePath: /usr/share/software-center/software-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center /media/18eb5af4-930e-4bdc-b8d1-dc12696f31c6/username/bin/tesseract_1.03-1_i386.deb ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x8119f10: mov0x4(%ebx),%edx PC (0x08119f10) ok source "0x4(%ebx)" (0x0004) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: software-center Stacktrace: #0 0x08119f10 in ?? () No symbol table info available. #1 0x01220045 in ?? () No symbol table info available. Backtrace stopped: Not enough registers or memory available to unwind further StacktraceTop: ?? () ?? () Title: software-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/897414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp