Re: [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Will do, thanks.Michael Peek On Thu, 2020-08-20 at 15:10 +, Paride Legovini wrote: > Hi Michael and thanks for all the digging. If I understand > correctlythere are two issues here: > 1. The slapd crash due to the caseExactMatch/caseExactIA5Match typo, > forwhich you submitted a fix upstream [1]. > 2. The need to "start ; stop ; restart" the slapd service in order > toavoid the "invalid per syntax" errors. > What I suggest is to: > A. Let's wait for upstream to comment on or pickup your patch. > We'llthen be able to cherry-pick the fix from the upstream > repository. Thismakes things easier to manage and give us more > confidence on thecorrectness on the patch (could be obvious for a > ldap/autofs expert, Iam not.) > B. File a separate bug for the "start ; stop ; restart" thing, > whichappears to be unrelated. If you do so, please make it clear it's > aBionic -> Focal regression. Having a minimal steps to reproduce > theissue from a fresh Focal install would be the best. > What do you think? > Paride > [1] https://www.spinics.net/lists/autofs/msg02276.html > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
I didn't realize that this was considered unusual. AutoFs integration has been a critical part of our infrastructure across multiple departments at our university for decades, starting with NIS/NIS+. Without AutoFS integration we would be ... very, very sad. I have filed a bug report w/ Debian and included a patch against Debian Sid's autofs-5.1.6 source package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968675 Since this is the same source file as Ubuntu 20.04 uses I've included the patch file for your use, on the off chance that it would make things easier (attached). Looking at the up-stream source from https://mirrors.edge.kernel.org/pub/linux/daemons/autofs/v5/ it appears that version 5.1.2's autofs.schema file was correct. The typo first appears in 5.1.3, released in May 24th 2017, and has affected every release of autofs since. I have also submitted a bug report, including a patch file, to the aut...@vger.kernel.org mailing list for the autofs developers. Michael Peek On Tue, 2020-08-18 at 16:42 +, Robie Basak wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > Since this affects an unusual end-user configuration, I'm setting > Importance to Low, and I don't expect anyone to work on this soon. > However if you can help definitively explain what needs adjusting to fix > this correctly, then that would be helpful and we can try to help get > that fix landed. Caveat: normally we'd expect an explanation and patch > to be sent to Debian first. > > I'm deferring a decision on whether or not this requires a fix in > openldap until the above is clear. > > ** Changed in: autofs (Ubuntu) >Importance: Undecided => Low > > ** Changed in: openldap (Ubuntu) >Importance: Undecided => Low > ** Bug watch added: Debian Bug tracker #968675 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968675 ** Patch added: "autofs-5.1.6-schema-fix.diff" https://bugs.launchpad.net/bugs/1891548/+attachment/5402829/+files/autofs-5.1.6-schema-fix.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
As a follow-up, I figured out a workaround for the following error that
I reported earlier:
adding new entry "ou=auto.master,dc=example,dc=org"ldap_add: Invalid
syntax (21) additional info: objectClass: value #1 invalid per
syntax
Original steps:
1) Install /etc/ldap/slapd.conf (which includes the "caseExactIA5Match"
fixed version of the autofs schema)
2) Start slapd
3) Attempts to enter an automountMap entry causes an invalid syntax
error
Workaround:
1) Install /etc/ldap/slapd.conf (which includes the "caseExactIA5Match"
fixed version of the autofs schema)
2) start slapd
3) stop and restart slapd again
4) Attempts to enter automountMap entry now succeed
Why this is necessary I can't say but the behavior is consistent. This
extra restart was not necessary for versions of slapd+autofs that
shipped with 18.04 and previous Ubuntu versions.
Also I'm going to further show my ignorance here and say that I found
"caseExactMatch" in several other schema files too. I'm wondering why
other users haven't run into something similar?
# find /etc/ldap/schema/ -type f -exec grep -q caseExactMatch {} \;
-print/etc/ldap/schema/corba.schema/etc/ldap/schema/duaconf.ldif/etc/ld
ap/schema/core.schema <-- commented
out/etc/ldap/schema/duaconf.schema/etc/ldap/schema/java.schema/etc/ldap
/schema/core.ldif <-- commented
out/etc/ldap/schema/java.ldif/etc/ldap/schema/autofs.schema
Thank you again for your help on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891548
Title:
autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
SORRY -- This is the correct autofs-fixed.schema. That last one was a file I was poking around with using a schema I found online. The only difference between this file and the one that ships with autofs-ldap is "caseExactMatch" -> "caseExactIA5Match". ** Attachment added: "autofs-fixed.schema" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401483/+files/autofs-fixed.schema -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
** Attachment added: "Replaced "exactCaseMatch" w/ "exactCaseIA5Match" to fix bug that caused slapd to crash on startup" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401476/+files/autofs-fixed.schema -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Attached is an example /etc/ldap/slapd.conf file that I'm working from.
Maybe there's a problem in here somewhere that I'm not catching.
Including it just in case. Database password is "superSecretPassword"
-> "{MD5}Yy8s0xf5ONysHHbtpvA+ig==". The include for
/etc/ldap/schema/autofs.schema has been replaced with /etc/ldap/schema
/autofs-fixed.schema (see additional attachment below).
** Attachment added: "Example /etc/ldap/slapd.conf file -- aybe a problem in
here somewhere?"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401475/+files/slapd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891548
Title:
autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
** Attachment added: "LDAP entries to recreate my test setup" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+attachment/5401474/+files/input.ldif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Example entry #1, using /usr/share/doc/autofs-ldap/examples/ldap-automount-auto.direct dn: ou=auto.master,dc=example,dc=org ou: auto.master objectClass: top objectClass: automountMap Output: adding new entry "ou=auto.master,dc=example,dc=org" ldap_add: Invalid syntax (21) additional info: objectClass: value #1 invalid per syntax Example entry #2 from an existing 18.04 slapd server (base replaced w/ dc=example,dc=org) dn: ou=automount,dc=example,dc=org ou: automount objectClass: top objectClass: organizationalUnit dn: ou=auto.master,ou=automount,dc=example,dc=org ou: auto.master objectClass: top objectClass: automountMap Output: adding new entry "ou=automount,dc=example,dc=org" adding new entry "ou=auto.master,ou=automount,dc=example,dc=org" ldap_add: Invalid syntax (21) additional info: objectClass: value #1 invalid per syntax -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Attempted to modify /etc/ldap/schema/autofs.scheme to replace "caseExactMatch" with "caseExactIA5Match". This fixed the problem with slaptest reporting an error. However, there are other problems that have arisen that may or may not be related. Attempts to add automount entries fail for "objectClass: automountMap" with "invalid per syntax" errors. Neither old, working entries from slapd running on an existing 18.04 server, nor new entries built using /usr/share/doc/autofs- ldap/examples/ldap-automount-auto.direct as a template, are accepted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Schemas included in slapd.conf: include /etc/ldap/schema/core.schema include /etc/ldap/schema/cosine.schema include /etc/ldap/schema/nis.schema include /etc/ldap/schema/inetorgperson.schema include /etc/ldap/schema/autofs.schema -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891548] [NEW] autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Public bug reported: Ubuntu Release: # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 Version of packages in use: # dpkg -l autofs autofs-ldap slapd | grep '^ii' ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based automounter for Linux ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for autofs ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd) Expected: No errors from slaptest Actual Output: 5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType inappropriate matching rule: "caseExactMatch" ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1891548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
This really isn't acceptable for our use. We may have a rather smallish organization (I manage 103 Ubuntu machines, most of them user-facing workstations) but we are a national research institute and we give Linux and Ubuntu international attention every time we have a group of scientists arrive for a workshop simply by running something other than the standard Winblows ecosystem. Creating a second account for them really isn't feasible, and trying to convince them to log in a second time, "just in case," just doesn't work. For many of them this will be their first exposure to a Linux desktop environment, and if they get bitten by a bug like this then it'll probably be their last. This bug makes both Ubuntu and Linux in general look bad, and that makes me sad. There are some functions that you just expect to work without fail, and this is one of them. Michael On 07/21/2017 04:49 PM, Vincent Snijders wrote: > @Klemen, as a work around I make sure that a second user is logged in > (most of the time one of my children). If I am locked out, I can switch > to a different X-session (ctrl-alt-f8 or so) and then switch to my user > with the menu in the top left corner. Then I can enter my password. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()
I have not come across this bug yet in 16.04. It may have been fixed. Michael On 10/26/2016 06:08 PM, Joshua Powers wrote: > ** Changed in: openssh (Ubuntu) >Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530914 Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611777] Re: When using metacity, nautilus has no menu bar
Next, here is nautilus, again with the application menu set for display in indicator-applet-appmenu. ** Attachment added: "nautilus-under-metacity-with-indicator-applet-appmenu-with-menu-in-menu-bar.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+attachment/4733012/+files/nautilus-under-metacity-with-indicator-applet-appmenu-with-menu-in-menu-bar.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611777 Title: When using metacity, nautilus has no menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611777] Re: When using metacity, nautilus has no menu bar
** Attachment added: "Unity with menus in the window title bar -- again, works as expected" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+attachment/4733010/+files/nautilus-under-unity-with-menu-in-window-title-bar.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611777 Title: When using metacity, nautilus has no menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611777] Re: When using metacity, nautilus has no menu bar
And finally, here is nautilus, under metacity, with indicator-applet- appmenu installed and on the panel, but with settings configured to display the menu in the window's title bar. ** Attachment added: "nautilus-under-metacity-with-indicator-applet-appmenu-with-menu-in-window-title-bar.jpg" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+attachment/4733013/+files/nautilus-under-metacity-with-indicator-applet-appmenu-with-menu-in-window-title-bar.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611777 Title: When using metacity, nautilus has no menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611777] Re: When using metacity, nautilus has no menu bar
Here are some screenshots taken from a freshly-created user account to demonstrate what I'm talking about. ** Attachment added: "A screen shot of the default setup: nautilus, unity, and menus in the menu bar" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+attachment/4733009/+files/nautilus-under-unity-with-menu-in-menu-bar.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611777 Title: When using metacity, nautilus has no menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611777] Re: When using metacity, nautilus has no menu bar
Next, I fired up metacity. I created a brand new panel with nothing on it except indicator-applet-appmenu. Here's a screenshot showing the appmenu working just fine for the terminal. ** Attachment added: "nautilus-under-metacity-with-indicator-applet-appmenu-terminal.jpg" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+attachment/4733011/+files/nautilus-under-metacity-with-indicator-applet-appmenu-terminal.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611777 Title: When using metacity, nautilus has no menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1611777] Re: When using metacity, nautilus has no menu bar
I have done as indicated, but the application menu still does not show up for Nautilus. It shows up for other applications, but not Nautilus. Michael On 08/10/2016 12:40 PM, Khurshid Alam wrote: > You first need to install "indicator-applet-appmenu" and then add the > applet to panel to get/have application menubar. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611777 Title: When using metacity, nautilus has no menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1611777] Re: When using metacity, nautilus has no menu bar
I have System Settings > Appearance > Behavior > Show the menus for a window == In the widnow's title bar This works for all of the other applications that I've run, but not for nautilus. Is there no way to get the menu back in nautilus the same as for the other apps? Michael On 08/10/2016 12:40 PM, Khurshid Alam wrote: > You first need to install "indicator-applet-appmenu" and then add the > applet to panel to get/have application menubar. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611777 Title: When using metacity, nautilus has no menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1611777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611777] [NEW] When using metacity, nautilus has no menu bar
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ dpkg -l nautilus metacity gnome-panel Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii gnome-panel1:3.18.2-1ub amd64launcher and docking facility for ii metacity 1:3.18.5-0ub amd64lightweight GTK+ window manager ii nautilus 1:3.18.4.is. amd64file manager and graphical shell 3) What you expected to happen Expected to be able to access the menu bar (File, Edit, View, Go, Bookmarks, Help) at the top of the window (or via some other mechanism/menu/button). 4) What happened instead No menu is available, either on the window titlebar or via right- or middle-clicking on the window titlebar, or via some other button/menu. See attached screenshot. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Screenshot from 2016-08-10 09-23-45.png" https://bugs.launchpad.net/bugs/1611777/+attachment/4718330/+files/Screenshot%20from%202016-08-10%2009-23-45.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611777 Title: When using metacity, nautilus has no menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1611777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611777] Re: When using metacity, nautilus has no menu bar
** Attachment added: "Screenshot from 2016-08-10 09-42-47.png" https://bugs.launchpad.net/ubuntu/+bug/1611777/+attachment/4718331/+files/Screenshot%20from%202016-08-10%2009-42-47.png ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial - - 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center + 2) The version of the package you are using, via 'apt-cache policy + pkgname' or by checking in Software Center $ dpkg -l nautilus metacity gnome-panel Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii gnome-panel1:3.18.2-1ub amd64launcher and docking facility for ii metacity 1:3.18.5-0ub amd64lightweight GTK+ window manager - ii nautilus 1:3.18.4.is. amd64file manager and graphical shell - + ii nautilus 1:3.18.4.is. amd64file manager and graphical shell 3) What you expected to happen Expected to be able to access the menu bar (File, Edit, View, Go, Bookmarks, Help) at the top of the window (or via some other - mechanism/menu/button). Functionality such as "File" > "Connect To - Server..." are unavailable. + mechanism/menu/button). 4) What happened instead No menu is available, either on the window titlebar or via right- or middle-clicking on the window titlebar, or via some other button/menu. See attached screenshot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611777 Title: When using metacity, nautilus has no menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1611777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611375] [NEW] Launcher remains on all screens regardless of "Launcher placement" setting
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy unity-control-center unity-control-center: Installed: 15.04.0+16.04.20160705-0ubuntu1 Candidate: 15.04.0+16.04.20160705-0ubuntu1 Version table: *** 15.04.0+16.04.20160705-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 15.04.0+16.04.20160413-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen Expected launcher to disappear from one monitor after selecting anything other than "All displays" and clicking "Apply" 4) What happened instead Launcher remains on all monitors ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611375 Title: Launcher remains on all screens regardless of "Launcher placement" setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1611375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990032] Re: Dual monitor sticky edges are still enabled when turned off in display manager and Launcher placement is "All Displays"
This bug has resurfaced for me in 16.04.1 LTS. However, I cannot confirm that restricting the launcher to a single screen prevents the stickiness, as changing the launcher placement has no effect. This is another bug that I will file separately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990032 Title: Dual monitor sticky edges are still enabled when turned off in display manager and Launcher placement is "All Displays" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/990032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
*** This bug is a duplicate of bug 1003842 *** https://bugs.launchpad.net/bugs/1003842 I reformatted over 14.04 and installed 16.04 as a fresh start. I use a slightly customized server install ISO image that includes my own preseed file for automation. My approach is to start with a bare-bones server install on all machines and then install extra packages based on the machine's function (ubuntu-desktop on workstations, for instance). According to my installation logs, dnsmasq was installed during an "apt-get install ubuntu-desktop unity-tweak-tool" on a workstation (which of those two packages actually resulted in a dependency on dnsmasq I don't know), and on a server it was installed during an "apt-get install polipo". Michael On 04/28/2016 06:01 AM, Thomas Hood wrote: > *** This bug is a duplicate of bug 1003842 *** > https://bugs.launchpad.net/bugs/1003842 > > What remains unexplained is why the dnsmasq package was installed on > your machine at all. Is it the case that dnsmasq was not installed > before the upgrade and it was installed after the upgrade? In that case, > please file a new bug report describing that particular misbehavior. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1575644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
I'll give it a go and see if any problems occur. Thanks for your help! Michael On 04/27/2016 03:21 PM, Thomas Hood wrote: > That name service does not work properly when dnsmasq is installed is > most probably due to bug #1003842. If that is the case then if you > remove 8.8.8.8 from the list of nameserver addresses then name service > will work reliably. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
No, it does not work when dnsmasq is installed. At least, not reliably. I discovered this when apache2 started ignoring the configuration for my virtual hosts because it couldn't resolve the virtual host names. I could reach some hosts, like archive.ubuntu.com for instance whenever I did an apt-get update, or I would have noticed it right away. Michael On 04/27/2016 01:59 PM, Thomas Hood wrote: > Everything looks correct. Does name service work both when dnsmasq is > installed and when it is not installed? If so then there is no problem. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
Ah, I understand now. Sorry. Michael On 04/27/2016 12:42 PM, Thomas Hood wrote: > The answer to the question "shouldn't those DNS servers should be > included in /etc/resolv.conf regardless of the presence of dnsmasq?" is > "no". Resolvconf doesn't list any nameserver addresses after any > loopback address, unless > TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=no in > /etc/default/resolvconf. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
Maybe I'm just confused about how resolvconf and dnsmasq should work, but here's how it's working on my new 16.04 system: root@ecoli:~# dpkg -l | grep dnsmasq ii dnsmasq 2.75-1 all Small caching DNS proxy and DHCP/TFTP server ii dnsmasq-base 2.75-1 amd64 Small caching DNS proxy and DHCP/TFTP server root@ecoli:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp0s10 iface enp0s10 inet static address 160.36.130.174 netmask 255.255.255.0 network 160.36.130.0 broadcast 160.36.130.255 gateway 160.36.130.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 160.36.0.66 160.36.128.66 8.8.8.8 dns-search nimbios.org root@ecoli:~# cat /etc/resolv.conf # 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 nimbios.org root@ecoli:~# dpkg --purge dnsmasq (Reading database ... 429253 files and directories currently installed.) Removing dnsmasq (2.75-1) ... Purging configuration files for dnsmasq (2.75-1) ... root@ecoli:~# cat /etc/resolv.conf # 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 160.36.0.66 nameserver 160.36.128.66 nameserver 8.8.8.8 search nimbios.org root@ecoli:~# dpkg -l | grep dnsmasq ii dnsmasq-base 2.75-1 amd64 Small caching DNS proxy and DHCP/TFTP server root@ecoli:~# apt-get install dnsmasq Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: dnsmasq 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/16.0 kB of archives. After this operation, 71.7 kB of additional disk space will be used. Selecting previously unselected package dnsmasq. (Reading database ... 429242 files and directories currently installed.) Preparing to unpack .../dnsmasq_2.75-1_all.deb ... Unpacking dnsmasq (2.75-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu4) ... Setting up dnsmasq (2.75-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu4) ... root@ecoli:~# cat /etc/resolv.conf # 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 nimbios.org root@ecoli:~# dpkg -l | grep dnsmasq ii dnsmasq 2.75-1 all Small caching DNS proxy and DHCP/TFTP server ii dnsmasq-base 2.75-1 amd64 Small caching DNS proxy and DHCP/TFTP server root@ecoli:~# This is on a machine that was previously running 14.04, and now has a fresh re-formatted/re-installed 16.04. Under 14.04 this wasn't a problem. This just started under 16.04. And the contents of my /etc/network/interfaces hasn't changed from 14.04. Michael On 04/27/2016 12:21 PM, msp3k wrote: > They are specified in /etc/network/interfaces just as you instructed, > and the dnsmasq-base package is installed. But when dnsmasq is > installed then resolvconf generates an incorrect /etc/resolv.conf. If I > remove the dnsmasq package then resolvconf works properly and generates > the expected contents for /etc/resolv.conf. > > This is a new bug with 16.04. It was not present under 14.04, and the > contents of my /etc/network/interfaces file has not changed. > > Michael > > On 04/27/2016 12:06 PM, Thomas Hood wrote: >> Not dnsmasq but dnsmasq-base is pulled in by ubuntu-desktop. >> >> If you define your interfaces statically using /etc/network/interfaces >> then you have to add the nameserver information >> /etc/network/interfaces on lines like "dns-nameserver 1.2.3.4". See >> resolvconf(8) for more info. >> >> ** Changed in: resolvconf (Ubuntu) >> Status: New => Incomplete >> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1575644] Re: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
They are specified in /etc/network/interfaces just as you instructed, and the dnsmasq-base package is installed. But when dnsmasq is installed then resolvconf generates an incorrect /etc/resolv.conf. If I remove the dnsmasq package then resolvconf works properly and generates the expected contents for /etc/resolv.conf. This is a new bug with 16.04. It was not present under 14.04, and the contents of my /etc/network/interfaces file has not changed. Michael On 04/27/2016 12:06 PM, Thomas Hood wrote: > Not dnsmasq but dnsmasq-base is pulled in by ubuntu-desktop. > > If you define your interfaces statically using /etc/network/interfaces > then you have to add the nameserver information > /etc/network/interfaces on lines like "dns-nameserver 1.2.3.4". See > resolvconf(8) for more info. > > ** Changed in: resolvconf (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575644] [NEW] resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used
Public bug reported: By default, when installing ubuntu-desktop (and when installing some other packages as well), apt will also install dnsmasq as a dependency. When dnsmask is installed, and static IP addresses are used, resolv.conf creates a nearly empty /etc/resolv.conf file. The file only contains entries for localhost and the search domain. If static IP addresses are defined in /etc/network/interfaces, then shouldn't those DNS servers should be included in /etc/resolv.conf regardless of the presence of dnsmask? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: resolvconf 1.78ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 27 08:34:24 2016 InstallationDate: Installed on 2016-04-26 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575644 Title: resolvconf doesn't create the correct /etc/resolv.conf file when static IP addresses are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555171] Re: systemd does not shut down rsyslog
Nevermind. Apparently "systemctl stop " doesn't do what I thought it should do. Rsyslogd can be stopped with: systemctl disable rsyslog systemctl stop rsyslog After issuing the disable command, the stop command worked as I expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555171 Title: systemd does not shut down rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1555171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555171] Re: systemd does not shut down rsyslog
This is on Ubuntu Server 16.04 beta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555171 Title: systemd does not shut down rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1555171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555171] [NEW] systemd does not shut down rsyslog
Public bug reported: This bug is 100% reproducible. Example output: Script started on Wed 09 Mar 2016 10:04:42 AM EST root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5219 1 0 10:04 ?00:00:00 /usr/sbin/rsyslogd -n root 5240 5227 0 10:04 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# systemctl stop rsyslog Warning: Stopping rsyslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop syslog Warning: Stopping syslog.service, but it can still be activated by: syslog.socket root@flea:/etc/init.d# systemctl stop rsyslogd Failed to stop rsyslogd.service: Unit rsyslogd.service not loaded. root@flea:/etc/init.d# ps -ef | grep rsyslog syslog5254 1 0 10:05 ?00:00:00 /usr/sbin/rsyslogd -n root 5263 5227 0 10:05 pts/000:00:00 grep --color=auto root@flea:/etc/init.d# exit Script done on Wed 09 Mar 2016 10:05:12 AM EST ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555171 Title: systemd does not shut down rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1555171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()
I tried following one of the links to ubuntu.com, but was told "Sorry, you are not a member of a group that is allowed to see the data from error reports." If you think it's safe to do so, I can reply with the last few links. Would it be safe to assume that they are listed in a newest-first order? Thanks, Michael On 01/05/2016 09:17 PM, Seth Arnold wrote: > It may not be making its way to errors.ubuntu.com. If you've got the GUI > installed, you can find a link to reported issues via the control panel, > security & privacy, diagnostics --> "show previous reports". I didn't > see any errors that matched _IO_vfprintf_internal(), though I did notice > that the pam_winbind module was segfaulting a lot for someone... > > Thanks > -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1530914 Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1530914] Re: sshd crashed with SIGSEGV in _IO_vfprintf_internal()
I tried following one of the links to ubuntu.com, but was told "Sorry, you are not a member of a group that is allowed to see the data from error reports." If you think it's safe to do so, I can reply with the last few links. Would it be safe to assume that they are listed in a newest-first order? Thanks, Michael On 01/05/2016 09:17 PM, Seth Arnold wrote: > It may not be making its way to errors.ubuntu.com. If you've got the GUI > installed, you can find a link to reported issues via the control panel, > security & privacy, diagnostics --> "show previous reports". I didn't > see any errors that matched _IO_vfprintf_internal(), though I did notice > that the pam_winbind module was segfaulting a lot for someone... > > Thanks > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530914 Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530914] [NEW] sshd crashed with SIGSEGV in _IO_vfprintf_internal()
Public bug reported: sshd crashes several times a day with the following information: ExecutablePath: /usr/sbin/sshd Package: openssh-server 1:6.6p1-2ubuntu2.3 ProblemType: Crash Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Architecture: amd64 DistroRelease: Ubuntu 14.04 I've been reporting this bug for months now through apport-gtk, but there never seems to be an entry for it on launchpad. So just in case this isn't making it into the bug reports, for whatever reason, I'm reporting it manually here. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530914 Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530914] [NEW] sshd crashed with SIGSEGV in _IO_vfprintf_internal()
Public bug reported: sshd crashes several times a day with the following information: ExecutablePath: /usr/sbin/sshd Package: openssh-server 1:6.6p1-2ubuntu2.3 ProblemType: Crash Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() Architecture: amd64 DistroRelease: Ubuntu 14.04 I've been reporting this bug for months now through apport-gtk, but there never seems to be an entry for it on launchpad. So just in case this isn't making it into the bug reports, for whatever reason, I'm reporting it manually here. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1530914 Title: sshd crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1530914/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
My understanding is that if you type: dpkg -l unity And see the version number 7.2.x, then you have the patch. Michael Peek On 03/18/2015 05:11 AM, Jonathan Laserson wrote: How do I obtain the fix? This still happens. I have Ubuntu 14.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
On 12/10/2014 09:24 PM, Andrea Azzarone wrote: Please consider answering the question markes ad *** IMPORTANT *** in the description. 2014-12-11 1:26 GMT+01:00 harrychillboy 1311...@bugs.launchpad.net: Bug description: *** IMPORTANT ** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** 1. Yes. Dual monitors. 2. No. The problem is random. 3. Yes. We have just switched to gnome-screensaver for testing purposes. Initial tests look promising. 4. Included auth.log entries in a previous message 5. unity7.2.3+14.04.20140826-0ubuntu1 Michael Peek -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
1) The bug just bit my boss again. Here's the auth.log: Dec 10 09:13:23 anolis compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 10 09:13:23 anolis compiz: PAM adding faulty module: pam_kwallet.so Dec 10 09:15:01 anolis CRON[21745]: pam_unix(cron:session): session opened for user root by (uid=0) Dec 10 09:15:01 anolis CRON[21744]: pam_unix(cron:session): session opened for user root by (uid=0) Dec 10 09:15:01 anolis CRON[21744]: pam_unix(cron:session): session closed for user root Dec 10 09:15:03 anolis CRON[21745]: pam_unix(cron:session): session closed for user root Dec 10 09:20:42 anolis sshd[21993]: Accepted publickey for root from 160.36.130.180 port 33420 ssh2: RSA fe:34:35:5b:47:90:1b:7f:fb:cb:7d:5c:2e:32:69:f5 Dec 10 09:20:42 anolis sshd[21993]: pam_unix(sshd:session): session opened for user root by (uid=0) Dec 10 09:20:56 anolis compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 10 09:20:56 anolis compiz: PAM adding faulty module: pam_kwallet.so Dec 10 09:21:01 anolis CRON[22258]: pam_unix(cron:session): session opened for user root by (uid=0) Dec 10 09:21:03 anolis CRON[22258]: pam_unix(cron:session): session closed for user root Dec 10 09:22:02 anolis sshd[22333]: Accepted publickey for root from 160.36.130.180 port 33431 ssh2: RSA fe:34:35:5b:47:90:1b:7f:fb:cb:7d:5c:2e:32:69:f5 Dec 10 09:22:02 anolis sshd[22333]: pam_unix(sshd:session): session opened for user root by (uid=0) There's nothing out of the ordinary here compared to my other hosts. There's a mysterious complaint about pam_kwallet.so, but all of my hosts complain about that. 2) There is something new to note: When the bug bites, not only is there no password field, but the indicator apps also disappear from the top-right of the screen. I noticed this when I tried to switch to another user in hopes of being able to log back in. Attached is a screenshot I grabbed via vinagre. 3) I set System Settings Universal Access Typing On Screen Keyboard = On We'll see if the problem persists when using gnome-screensaver. Michael Peek On 11/23/2014 08:40 AM, Andrea Azzarone wrote: Can you post your auth.log? ** Attachment added: Screenshot from 2014-12-10 09:21:32.png https://bugs.launchpad.net/bugs/1311316/+attachment/4277621/+files/Screenshot%20from%202014-12-10%2009%3A21%3A32.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
1) Maybe I'm just derping, but how do I run gnome-screensaver? $ ps -ef | grep -i screensaver peek 24604 24163 0 08:51 pts/47 00:00:00 grep -i screensaver $ gnome-screensaver ** (gnome-screensaver:24665): WARNING **: screensaver already running in this session 2) If this is an LDAP issue, then why does it only affect 1 out of my 110 users? I thank you guys for your hard work on this, and if there is anything I can do to help track down the source of the problem let me know. Michael Peek On 12/08/2014 01:57 PM, Andrea Azzarone wrote: All these services (login, lightdm, polkit-1, sudo, sshd) are working fine. They run as root that's why. Try to lock using gnome-screensaver (without running it as root!) and let me know if you can unlock the screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Okay, I set System Settings Universal Access Typing On Screen Keyboard = On Then I hit alt+control+L to lock. Sure enough, I got what looks like gnome-screensaver. Via an SSH login I confirmed that gnome-screensaver was indeed running, and running as me and not as root. Entering my password returned me to the desktop with no problem. I repeated the lock test four times. I'll ask my boss to make the same settings change and let me know if/how that changes things for him, and pass the results on to you guys. Michael Peek On 12/09/2014 09:28 AM, Andrea Azzarone wrote: You need to enable accessibility (e.g. on screen keyabord) from the control center. 2014-12-09 14:56 GMT+01:00 msp3k p...@nimbios.org: 1) Maybe I'm just derping, but how do I run gnome-screensaver? $ ps -ef | grep -i screensaver peek 24604 24163 0 08:51 pts/47 00:00:00 grep -i screensaver $ gnome-screensaver ** (gnome-screensaver:24665): WARNING **: screensaver already running in this session 2) If this is an LDAP issue, then why does it only affect 1 out of my 110 users? I thank you guys for your hard work on this, and if there is anything I can do to help track down the source of the problem let me know. Michael Peek On 12/08/2014 01:57 PM, Andrea Azzarone wrote: All these services (login, lightdm, polkit-1, sudo, sshd) are working fine. They run as root that's why. Try to lock using gnome-screensaver (without running it as root!) and let me know if you can unlock the screen. -- You received this bug notification because you are a bug assignee. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I must have missed something. Permissions on what path? And what should the permissions be? Michael Peek On 12/06/2014 09:03 AM, Andrea Azzarone wrote: We released a fix but it does not work. The one we released was about text entry not showing randomly on multimonitor and seems to be fixed. Probably what you can reproduce now is a problem with permissions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
We use the same setup, and have had the same experiences: 1) LDAP configuration hasn't changed in years 2) Login screen works fine 3) Home areas are served via NFS+automount 4) Problems only appeared after installing 14.04 (we did fresh installs though, not upgrades) Michael Peek On 12/08/2014 03:41 AM, Philipp Wendler wrote: Also our LDAP configuration is working for several years now without problems. Only since the upgrade to Ubuntu 14.04 this problem with the lock screen has started appearing. All other applications, including the login screen (lightdm) are working fine. By the way, we have a dual monitor setup, too. Our home file systems are on an NFS fileserver, mounted using automount and with root_squash enabled (this means that root does not have full access to my home directory, but only the same rights as all other accounts). If there is a root process trying to access files in my home this would fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I am using ldap as well. Out of 80 hosts and 110 users this bug only affects one user on one host. (Unfortunately that user happens to be one of my bosses.) It's irregular, but frequent. Michael Peek On 12/05/2014 09:06 AM, Andrea Azzarone wrote: @Philipp also I just read you are using ldap. That can be a different issue (maybe is solved in trunk because now unity and lightdm do not share pam configuration). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Light-locker is not installed on our machines. On 12/01/2014 10:56 AM, LGB [Gábor Lénárt] wrote: I don't know if it helps, but I always had problems like no input field for password or the double unlock (if the first problem does not occur, unlock presented another unlock field with a sightly different screen) problem on my notebook. Then I noticed, I have a package installed named light-locker (I am not sure about the name though, just by heart now). After removing that package I had no problem like these since then! Since I've installed meta-packages xubuntu-desktop and lubuntu-desktop as well (so I can test different desktops) it can be a reason as (if I am correct) these packages depends on light-locker. Removing them caused those meta packages to be removed as well (again, if I remember well enough), but at least since then I have no problem with regular ubuntu (unity) desktop lockingunlocking. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Out of 90-somethign users this bug only seems to affect one user. (Of course, that user happens to be one of my bosses...) Because the problem is hard to reproduce I have a feeling that it'lll be difficult to track down and fix. Michael On 11/03/2014 05:18 PM, Bruce MacNaughton wrote: msp3k - I got the same thing but just ran unity --replace in a terminal window I had left open on the desktop. I didn't check to see if could open a terminal. But running unity --replace from the desktop (w/o dash, launcher, panel, menu bar, etc.) resulted in getting them all back. It was ugly - many errors but it worked. Everything seems fine afterwards. Any idea when I can specifically target the software for an update? The fix clearly hasn't hit me yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I would like to know the answer to that as well. Back in the good 'ol days the screen lock was a separate process, and pkill -9 gnome-screensaver would bring back the desktop. But now...? There is a process called /usr/lib/unity/unity-panel-service --lockscreen-mode, but if I kill -9 on it, it just comes back with a new PID. Michael On 11/03/2014 08:38 AM, Bruce MacNaughton wrote: I have this problem but can access the desktop using SSH. Is there a process I can kill/restart to fix this condition? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
When I do that, I get the desktop back, but no dash, launcher, or panel. On 11/03/2014 08:54 AM, Erik wrote: unity --replace On Mon, Nov 3, 2014 at 5:38 AM, Bruce MacNaughton bmacnaugh...@msn.com wrote: I have this problem but can access the desktop using SSH. Is there a process I can kill/restart to fix this condition? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374434] [NEW] nslcd daemon dies
Public bug reported: Sometimes the nslcd daemon starts normally, but then dies later, with no error output to syslog stating why the process died. Checking ps -ef shows no nslcd process running. Attached is an example output from syslog showing the restart (Sep 25 18:23:03), the point at which pam notices that nslcd has died (Sep 25 18:27:02), and the point at which nslcd is restarted manually by the admin (Sep 26 07:36:51). Sep 25 18:23:03 diatom nslcd[2778]: version 0.8.13 starting Sep 25 18:23:08 diatom nslcd[2778]: accepting connections Sep 25 18:27:02 diatom lightdm: pam_ldap(lightdm:auth): error opening connection to nslcd: Connection refused Sep 25 18:27:14 diatom lightdm: pam_ldap(lightdm:auth): error opening connection to nslcd: Connection refused Sep 25 18:27:34 diatom lightdm: pam_ldap(lightdm:auth): error opening connection to nslcd: Connection refused Sep 25 18:28:00 diatom lightdm: pam_ldap(lightdm:auth): error opening connection to nslcd: Connection refused Sep 25 18:29:33 diatom lightdm: pam_ldap(lightdm:auth): error opening connection to nslcd: Connection refused Sep 25 18:29:59 diatom lightdm: pam_ldap(lightdm:auth): error opening connection to nslcd: Connection refused Sep 25 18:30:50 diatom sshd[3486]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 25 18:30:50 diatom sshd[3486]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 25 18:31:00 diatom sshd[3486]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 25 18:31:00 diatom sshd[3486]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 25 18:36:43 diatom sshd[3698]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 25 18:36:43 diatom sshd[3698]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 25 18:41:42 diatom smbd[3842]: pam_ldap(samba:session): error opening connection to nslcd: Connection refused Sep 25 23:17:03 diatom sshd[12931]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 25 23:17:03 diatom sshd[12931]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 25 23:21:06 diatom sshd[13105]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 25 23:21:06 diatom sshd[13105]: pam_ldap(sshd:auth): error opening connection to nslcd: Connection refused Sep 26 07:36:51 diatom nslcd[30075]: version 0.8.13 starting Sep 26 07:36:56 diatom nslcd[30075]: accepting connections This is one example. The same problem has been noted on multiple hosts. All hosts are running fully up-to-date Ubuntu 14.04.1 on amd64 architecture. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nslcd 0.8.13-3 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Fri Sep 26 08:21:06 2014 InstallationDate: Installed on 2014-06-20 (97 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: nss-pam-ldapd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nss-pam-ldapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374434 Title: nslcd daemon dies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1374434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1374434] Re: nslcd daemon dies
On 09/26/2014 11:10 AM, Arthur de Jong wrote: Does the kernel log anything (segmentation fault)? No mention of nslcd in /var/log/kern.log What is your nslcd.conf like? # /etc/nslcd.conf # nslcd configuration file. See nslcd.conf(5) # for details. # The user and group nslcd should run as. uid nslcd gid nslcd # The location at which the LDAP server(s) should be reachable. uri ldap://ldap.nimbios.org:389/ # The search base that will be used for all queries. base dc=nimbios,dc=org # The LDAP protocol version to use. #ldap_version 3 # The DN to bind with for normal lookups. #binddn cn=annonymous,dc=example,dc=net #bindpw secret # The DN used for password modifications by root. #rootpwmoddn cn=admin,dc=example,dc=com # SSL options #ssl off #tls_reqcert never # The search scope. #scope sub If you run nslcd in debug mode (start manually with -d) does it output any useful information around the time of the crash? If this is at all reproducable running it under gdb, valgrind or even strace could provide valuable information. I'll see if I can gather some more information for you. Thank you for Ubuntu! Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374434 Title: nslcd daemon dies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1374434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246092] Re: Ubuntu 13.10 upgrade: audacity sound is trashed, program highly unstable
For months solution #14 w/ PULSE_LATENCY_MSEC=1 worked for me. Something changed recently and now this solution no longer works. Any setting for PULSE_LATENCY_MSEC less than 25 results in no playback at all. Any value greater results in the same static that I get when I don't use PULSE_LATENCY_MSEC at all. Also, the solution from #21 does not work for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246092 Title: Ubuntu 13.10 upgrade: audacity sound is trashed, program highly unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1246092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358745] [NEW] Screen lock has no place to type in a password
Public bug reported: After the screen saver kicks in, there is a chance that, upon returning to the machine, there will be no place to type in a password. (Picture included.) The bug does not occur regularly, but does occur quite often. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 19 09:21:02 2014 InstallationDate: Installed on 2014-06-04 (76 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) upstart.lightdm.override: manual ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: A screenshot snippet showing the bug biting https://bugs.launchpad.net/bugs/1358745/+attachment/4181575/+files/ligthdm-screenlock-password-bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358745 Title: Screen lock has no place to type in a password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1358745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285444] Re: Login Successful, Desktop Never Loads
As mysteriously as the problem appeared, it disappeared. Still no clue what caused it. But for six hours two of my users could not use the unity desktop -- one of whom was my boss. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1285444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285444] Re: Login Successful, Desktop Never Loads
This bug is affecting me as well. I have one user out of 83 who cannot log in. Other users can log in on the same machine without a problem. I have: * Deleted their ~/.compiz-1/ * Reinstalled the nvidia video drivers * Reinstalled the unity packages from http://askubuntu.com/questions/478126/unity-not-working-after-upgrade- ubuntu-13-04-to-14-04#answer-478145 * And, in a fit of desperation, I renamed their home directory and created a new home directory from /etc/skel/. No change in behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1285444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1323861] Re: Installer looses eth0
Network issues continued after rebooting into my newly-installed system, but I have resolved the issue with a firmware update for the network device from Dell. For future reference, the firmware update can be downloaded from here, along with all of the other updates: http://www.dell.com/support/home/us/en/04/product- support/product/poweredge-r300/drivers The firmware that you want is the one for the Broadcom NeXtreme I and II Network Device Firmware 7.8.0 FYI: Dell provides firmware update programs for RedHat and Windows. The RedHat version did not work under Ubuntu (would not run the update at all), nor did it work under a Fedora Live CD (the update ran, but failed, and restored the original firmware upon failure). In order to install the firmware update I had to wipe the drive and install Windows, and then run the Windows version of the firmware update program. That made me sad. I did not have to install any of the other updates in order to get things working, only the update for the Broadcom was required. After upgrading the firmware and repeating the installation everything has gone smoothly. I apologize for the inconvenience to the Ubuntu developer team, and I thank you for all of your hard work. I consider the matter closed. Michael On 05/28/2014 08:35 PM, Christopher M. Penalver wrote: msp3k, thank you for reporting this and helping make Ubuntu better. As per www.dell.com/support/home/us/en/04/product-support/product/poweredge-r300/drivers an update to your BIOS is available (1.5.2). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Thank you for your understanding. ** Tags added: bios-outdated-1.5.2 ** Summary changed: - Installer looses eth0 + [Dell PowerEdge R300] Installer looses eth0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: [Dell PowerEdge R300] Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] Re: Installer looses eth0
apport information ** Tags added: apport-collected trusty ** Description changed: During installation of Ubuntu 14.04 Server amd64, the installer correctly configures eth0 (via static IP in my case) and retrieves the host name and domain name from the DNS server. But it then loses connection with eth0 sometime shortly afterwards. /var/log/syslog shows the following: May 27 21:26:24 kernel: [ 38.244015] tg3 :01:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. The installation continues and completes, but hangs periodically whenever the installation process attempts to access the network. After rebooting the network devices work fine. (Although it does mean that my pre-seeded post-install scripts fail to install my repository and custom packages, as that requires network access.) - The hardware in question is a Dell R300 with dual Broadcom Corporation - NetXtreme BCM5722 Gigabit Ethernet. Said hardware has been running - Ubuntu 10.04, 11.04, and 12.04 flawlessly for years. + The hardware in question is a Dell R300 with dual Broadcom Corporation NetXtreme BCM5722 Gigabit Ethernet. Said hardware has been running Ubuntu 10.04, 11.04, and 12.04 flawlessly for years. + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=358fe5e4-5a40-4e20-9fda-385b27f5e416 + InstallationDate: Installed on 2014-05-27 (0 days ago) + InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) + IwConfig: + eth0 no wireless extensions. + + eth1 no wireless extensions. + + lono wireless extensions. + MachineType: Dell Inc. PowerEdge R300 + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=f5b0e58b-8a20-48b8-a6ea-85097de75e22 ro + ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.13.0-27-generic N/A + linux-backports-modules-3.13.0-27-generic N/A + linux-firmware 1.127.2 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty + Uname: Linux 3.13.0-27-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 08/15/2008 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.3.0 + dmi.board.name: 0TY179 + dmi.board.vendor: Dell Inc. + dmi.board.version: A02 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd08/15/2008:svnDellInc.:pnPowerEdgeR300:pvr:rvnDellInc.:rn0TY179:rvrA02:cvnDellInc.:ct23:cvr: + dmi.product.name: PowerEdge R300 + dmi.sys.vendor: Dell Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121450/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121451/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121452/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121453/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121455/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121457/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121454/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121459/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121460/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121456/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121461/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1323861/+attachment/4121458/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323861] [NEW] Installer looses eth0
Public bug reported: During installation of Ubuntu 14.04 Server amd64, the installer correctly configures eth0 (via static IP in my case) and retrieves the host name and domain name from the DNS server. But it then loses connection with eth0 sometime shortly afterwards. /var/log/syslog shows the following: May 27 21:26:24 kernel: [ 38.244015] tg3 :01:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. The installation continues and completes, but hangs periodically whenever the installation process attempts to access the network. After rebooting the network devices work fine. (Although it does mean that my pre-seeded post-install scripts fail to install my repository and custom packages, as that requires network access.) The hardware in question is a Dell R300 with dual Broadcom Corporation NetXtreme BCM5722 Gigabit Ethernet. Said hardware has been running Ubuntu 10.04, 11.04, and 12.04 flawlessly for years. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323861 Title: Installer looses eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1323861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 797485] Re: Status Bar Covers File Name at Bottom
This is what I do. I have an empty file named 'zzz' (or 'ZZZ', I forget) to take up the bottom line. Michael On 09/16/2013 04:11 PM, Allen Talbot wrote: I ditched Windoze years ago and always promote Ubuntu to my students. This is so fustrating when working with lots of files/documents, I'm even tempted to start creating an x.txt in every folder I use to avoid editing/removing the wrong file by mistake. Please escalate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/797485 Title: Status Bar Covers File Name at Bottom To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1147696] Re: Spamassassin crashes on one particular mail message
Apache bug report can be found here: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6916 Michael On 03/05/2013 04:23 PM, Scott Kitterman wrote: Please file a bug upstream with spamassassin.apache.org. ** Bug watch added: SpamAssassin Bugzilla #6916 http://issues.apache.org/SpamAssassin/show_bug.cgi?id=6916 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1147696 Title: Spamassassin crashes on one particular mail message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1147696/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1147696] Re: Spamassassin crashes on one particular mail message
Apache bug report can be found here: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6916 Michael On 03/05/2013 04:23 PM, Scott Kitterman wrote: Please file a bug upstream with spamassassin.apache.org. ** Bug watch added: SpamAssassin Bugzilla #6916 http://issues.apache.org/SpamAssassin/show_bug.cgi?id=6916 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1147696 Title: Spamassassin crashes on one particular mail message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1147696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1147696] [NEW] Spamassassin crashes on one particular mail message
Public bug reported: Spamassassin crashes on one particular mail message. Debug output from spamassassin shows: Mar 5 14:48:47 mx spamd[24004]: rules: ran body rule __NONEMPTY_BODY == got hit: C Mar 5 14:50:43 mx kernel: [359648.499809] spamd child[24004]: segfault at 2a ip 7f6c23fb36ab sp 7fffadd37930 error 4 in libperl.so.5.14.2[7f6c23ef1000+173000] Mar 5 14:50:43 mx spamd[24002]: spamd: handled cleanup of child pid [24004] due to SIGCHLD: DIED, signal 11 (000b) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: spamassassin 3.3.2-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Tue Mar 5 15:28:36 2013 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US: SourcePackage: spamassassin UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.spamassassin: 2013-03-05T15:28:31.844123 ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ** Description changed: Spamassassin crashes on one particular mail message. Debug output from spamassassin shows: - Mar 5 14:48:47 gero spamd[24004]: rules: ran body rule __NONEMPTY_BODY == got hit: C + Mar 5 14:48:47 mx spamd[24004]: rules: ran body rule __NONEMPTY_BODY == got hit: C Mar 5 14:50:43 mx kernel: [359648.499809] spamd child[24004]: segfault at 2a ip 7f6c23fb36ab sp 7fffadd37930 error 4 in libperl.so.5.14.2[7f6c23ef1000+173000] Mar 5 14:50:43 mx spamd[24002]: spamd: handled cleanup of child pid [24004] due to SIGCHLD: DIED, signal 11 (000b) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: spamassassin 3.3.2-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Tue Mar 5 15:28:36 2013 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: - TERM=xterm - SHELL=/bin/bash - PATH=(custom, no user) - LANG=en_US.UTF-8 - LANGUAGE=en_US: + TERM=xterm + SHELL=/bin/bash + PATH=(custom, no user) + LANG=en_US.UTF-8 + LANGUAGE=en_US: SourcePackage: spamassassin UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.spamassassin: 2013-03-05T15:28:31.844123 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1147696 Title: Spamassassin crashes on one particular mail message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1147696/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1147696] [NEW] Spamassassin crashes on one particular mail message
Public bug reported: Spamassassin crashes on one particular mail message. Debug output from spamassassin shows: Mar 5 14:48:47 mx spamd[24004]: rules: ran body rule __NONEMPTY_BODY == got hit: C Mar 5 14:50:43 mx kernel: [359648.499809] spamd child[24004]: segfault at 2a ip 7f6c23fb36ab sp 7fffadd37930 error 4 in libperl.so.5.14.2[7f6c23ef1000+173000] Mar 5 14:50:43 mx spamd[24002]: spamd: handled cleanup of child pid [24004] due to SIGCHLD: DIED, signal 11 (000b) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: spamassassin 3.3.2-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Tue Mar 5 15:28:36 2013 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US: SourcePackage: spamassassin UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.spamassassin: 2013-03-05T15:28:31.844123 ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ** Description changed: Spamassassin crashes on one particular mail message. Debug output from spamassassin shows: - Mar 5 14:48:47 gero spamd[24004]: rules: ran body rule __NONEMPTY_BODY == got hit: C + Mar 5 14:48:47 mx spamd[24004]: rules: ran body rule __NONEMPTY_BODY == got hit: C Mar 5 14:50:43 mx kernel: [359648.499809] spamd child[24004]: segfault at 2a ip 7f6c23fb36ab sp 7fffadd37930 error 4 in libperl.so.5.14.2[7f6c23ef1000+173000] Mar 5 14:50:43 mx spamd[24002]: spamd: handled cleanup of child pid [24004] due to SIGCHLD: DIED, signal 11 (000b) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: spamassassin 3.3.2-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Tue Mar 5 15:28:36 2013 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: - TERM=xterm - SHELL=/bin/bash - PATH=(custom, no user) - LANG=en_US.UTF-8 - LANGUAGE=en_US: + TERM=xterm + SHELL=/bin/bash + PATH=(custom, no user) + LANG=en_US.UTF-8 + LANGUAGE=en_US: SourcePackage: spamassassin UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.spamassassin: 2013-03-05T15:28:31.844123 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1147696 Title: Spamassassin crashes on one particular mail message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1147696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1132561] [NEW] Software Center crashes on start-up
Public bug reported: Software Center crashes on start-up. Running /usr/share/software-center /software-center from the command line shows: $ /usr/share/software-center/software-center 2013-02-24 17:12:42,495 - softwarecenter.ui.gtk3.app - INFO - setting up proxy 'None' 2013-02-24 17:12:42,497 - softwarecenter.db.database - INFO - open() database: path=None use_axi=True use_agent=True 2013-02-24 17:12:42,748 - softwarecenter.backend.reviews - WARNING - Could not get usefulness from server, no username in config file 2013-02-24 17:12:42,840 - softwarecenter.ui.gtk3.app - INFO - show_available_packages: search_text is '', app is None. 2013-02-24 17:12:43,146 - softwarecenter.db.pkginfo_impl.aptcache - INFO - aptcache.open() Traceback (most recent call last): File /usr/share/software-center/softwarecenter/db/pkginfo_impl/aptcache.py, line 243, in open self._cache = apt.Cache(GtkMainIterationProgress()) File /usr/lib/python2.7/dist-packages/apt/cache.py, line 102, in __init__ self.open(progress) File /usr/lib/python2.7/dist-packages/apt/cache.py, line 149, in open self._list.read_main_list() SystemError: E:Opening /etc/apt/sources.list.d/playdeb.list - ifstream::ifstream (13: Permission denied) 2013-02-24 17:12:45,791 - softwarecenter.db.enquire - ERROR - _get_estimate_nr_apps_and_nr_pkgs failed Traceback (most recent call last): File /usr/share/software-center/softwarecenter/db/enquire.py, line 115, in _get_estimate_nr_apps_and_nr_pkgs tmp_matches = enquire.get_mset(0, len(self.db), None, xfilter) File /usr/share/software-center/softwarecenter/db/appfilter.py, line 89, in __call__ if (not pkgname in self.cache and File /usr/share/software-center/softwarecenter/db/pkginfo_impl/aptcache.py, line 263, in __contains__ return self._cache.__contains__(k) AttributeError: 'NoneType' object has no attribute '__contains__' Traceback (most recent call last): File /usr/share/software-center/software-center, line 176, in module app.run(args) File /usr/share/software-center/softwarecenter/ui/gtk3/app.py, line 1422, in run self.show_available_packages(args) File /usr/share/software-center/softwarecenter/ui/gtk3/app.py, line 1352, in show_available_packages self.view_manager.set_active_view(ViewPages.AVAILABLE) File /usr/share/software-center/softwarecenter/ui/gtk3/session/viewmanager.py, line 154, in set_active_view view_widget.init_view() File /usr/share/software-center/softwarecenter/ui/gtk3/panes/availablepane.py, line 171, in init_view self.apps_filter) File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 238, in __init__ self.build(desktopdir) File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 511, in build self._build_homepage_view() File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 271, in _build_homepage_view self._append_whats_new() File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 450, in _append_whats_new whats_new_cat = self._update_whats_new_content() File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 439, in _update_whats_new_content docs = whats_new_cat.get_documents(self.db) File /usr/share/software-center/softwarecenter/db/categories.py, line 124, in get_documents nonblocking_load=False) File /usr/share/software-center/softwarecenter/db/enquire.py, line 317, in set_query self._blocking_perform_search() File /usr/share/software-center/softwarecenter/db/enquire.py, line 212, in _blocking_perform_search matches = enquire.get_mset(0, self.limit, None, xfilter) File /usr/share/software-center/softwarecenter/db/appfilter.py, line 89, in __call__ if (not pkgname in self.cache and File /usr/share/software-center/softwarecenter/db/pkginfo_impl/aptcache.py, line 263, in __contains__ return self._cache.__contains__(k) AttributeError: 'NoneType' object has no attribute '__contains__' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: software-center 5.2.7 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Sun Feb 24 17:08:58 2013 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ** Attachment added: Screenshot https://bugs.launchpad.net/bugs/1132561/+attachment/3545358/+files/Screenshot%20from%202013-02-24%2016%3A29%3A33.png -- You received this bug notification because you are a member of Ubuntu
Re: [Bug 1132561] [NEW] Software Center crashes on start-up
The culprit was found to be a /etc/apt/sources.list.d/*.list file that was not world readable. But I maintain my stance on the bug -- the software center should be smart enough to recognize such an error and report a meaningful error message rather than crashing. Michael On 02/24/2013 05:13 PM, msp3k wrote: Public bug reported: Software Center crashes on start-up. Running /usr/share/software-center /software-center from the command line shows: $ /usr/share/software-center/software-center 2013-02-24 17:12:42,495 - softwarecenter.ui.gtk3.app - INFO - setting up proxy 'None' 2013-02-24 17:12:42,497 - softwarecenter.db.database - INFO - open() database: path=None use_axi=True use_agent=True 2013-02-24 17:12:42,748 - softwarecenter.backend.reviews - WARNING - Could not get usefulness from server, no username in config file 2013-02-24 17:12:42,840 - softwarecenter.ui.gtk3.app - INFO - show_available_packages: search_text is '', app is None. 2013-02-24 17:12:43,146 - softwarecenter.db.pkginfo_impl.aptcache - INFO - aptcache.open() Traceback (most recent call last): File /usr/share/software-center/softwarecenter/db/pkginfo_impl/aptcache.py, line 243, in open self._cache = apt.Cache(GtkMainIterationProgress()) File /usr/lib/python2.7/dist-packages/apt/cache.py, line 102, in __init__ self.open(progress) File /usr/lib/python2.7/dist-packages/apt/cache.py, line 149, in open self._list.read_main_list() SystemError: E:Opening /etc/apt/sources.list.d/playdeb.list - ifstream::ifstream (13: Permission denied) 2013-02-24 17:12:45,791 - softwarecenter.db.enquire - ERROR - _get_estimate_nr_apps_and_nr_pkgs failed Traceback (most recent call last): File /usr/share/software-center/softwarecenter/db/enquire.py, line 115, in _get_estimate_nr_apps_and_nr_pkgs tmp_matches = enquire.get_mset(0, len(self.db), None, xfilter) File /usr/share/software-center/softwarecenter/db/appfilter.py, line 89, in __call__ if (not pkgname in self.cache and File /usr/share/software-center/softwarecenter/db/pkginfo_impl/aptcache.py, line 263, in __contains__ return self._cache.__contains__(k) AttributeError: 'NoneType' object has no attribute '__contains__' Traceback (most recent call last): File /usr/share/software-center/software-center, line 176, in module app.run(args) File /usr/share/software-center/softwarecenter/ui/gtk3/app.py, line 1422, in run self.show_available_packages(args) File /usr/share/software-center/softwarecenter/ui/gtk3/app.py, line 1352, in show_available_packages self.view_manager.set_active_view(ViewPages.AVAILABLE) File /usr/share/software-center/softwarecenter/ui/gtk3/session/viewmanager.py, line 154, in set_active_view view_widget.init_view() File /usr/share/software-center/softwarecenter/ui/gtk3/panes/availablepane.py, line 171, in init_view self.apps_filter) File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 238, in __init__ self.build(desktopdir) File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 511, in build self._build_homepage_view() File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 271, in _build_homepage_view self._append_whats_new() File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 450, in _append_whats_new whats_new_cat = self._update_whats_new_content() File /usr/share/software-center/softwarecenter/ui/gtk3/views/catview_gtk.py, line 439, in _update_whats_new_content docs = whats_new_cat.get_documents(self.db) File /usr/share/software-center/softwarecenter/db/categories.py, line 124, in get_documents nonblocking_load=False) File /usr/share/software-center/softwarecenter/db/enquire.py, line 317, in set_query self._blocking_perform_search() File /usr/share/software-center/softwarecenter/db/enquire.py, line 212, in _blocking_perform_search matches = enquire.get_mset(0, self.limit, None, xfilter) File /usr/share/software-center/softwarecenter/db/appfilter.py, line 89, in __call__ if (not pkgname in self.cache and File /usr/share/software-center/softwarecenter/db/pkginfo_impl/aptcache.py, line 263, in __contains__ return self._cache.__contains__(k) AttributeError: 'NoneType' object has no attribute '__contains__' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: software-center 5.2.7 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Sun Feb 24 17:08:58 2013 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage
Re: [Bug 1123595] Re: [System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute speakers when headphones are plugged
As far as I know there are only 3 speakers on the machine: Front left, front right, and a third on the bottom. THIS IS EXACTLY WHAT I NEEDED! === I suspected that there had to be some configuration file somewhere that would control mixer settings on plug/unplug, I just didn't know where to look. Now you have shown me the light! I looked at /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf: [Element Front] switch = mute volume = zero I changed that to read: [Element Front] switch = off volume = zero And then rebooted. Now the speakers mute and un-mute properly when headphones are inserted. AWESOME! Thank you guys for all your help! Michael On 02/15/2013 11:22 AM, Raymond wrote: Now many internal speaker did your notebook have ? the pin-ctls of three speaker nodes were zero do you mean setting pin-ctls is not enough to mute ? you can modified pulseaudio conf to mute those front, surround,.. playback switch http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/modules/alsa/mixer/paths Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name=Front Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0001003e: IN OUT HP EAPD Detect Trigger EAPD 0x2: EAPD Pin Default 0x99130120: [Fixed] Speaker at Int ATAPI Conn = ATAPI, Color = Unknown DefAssociation = 0x2, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 1 0x0c Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name=Center Playback Switch, index=0, device=0 ControlAmp: chs=1, dir=Out, idx=0, ofs=0 Control: name=LFE Playback Switch, index=0, device=0 ControlAmp: chs=2, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x0036: IN OUT Detect Trigger Pin Default 0x99130130: [Fixed] Speaker at Int ATAPI Conn = ATAPI, Color = Unknown DefAssociation = 0x3, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 1 0x0d Node 0x16 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name=Surround Playback Switch, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x0036: IN OUT Detect Trigger Pin Default 0x99130140: [Fixed] Speaker at Int ATAPI Conn = ATAPI, Color = Unknown DefAssociation = 0x4, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 1 0x0e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123595 Title: [System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute speakers when headphones are plugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1123595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1126592] [NEW] Nautilus' tooltip hides the last file
Public bug reported: The tooltip hides the last file in the Nautilus window. If the last file has a sufficiently long name, then it becomes difficult or impossible to click on the last file. Workaround: Use the File Edit... etc. tools from the application bar to manipulate the last file. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: An example screenshot https://bugs.launchpad.net/bugs/1126592/+attachment/3530745/+files/Screenshot%20from%202013-02-15%2015%3A00%3A10.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1126592 Title: Nautilus' tooltip hides the last file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1126592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1123595] Re: [System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute speakers when headphones are plugged
It seems to have no effect: $ amixer -c 0 | grep -i auto-mute Simple mixer control 'Auto-Mute Mode',0 $ amixer -c 0 set 'Auto-Mute Mode' Enabled Simple mixer control 'Auto-Mute Mode',0 Capabilities: enum Items: 'Disabled' 'Enabled' Item0: 'Enabled' $ amixer -c 0 | grep -i auto-mute Simple mixer control 'Auto-Mute Mode',0 Plugging and unplugging the headphones still leaves Front speakers on. On 02/13/2013 08:31 PM, Raymond wrote: you have disabled the auto mute Simple mixer control 'Auto-Mute Mode',0 Capabilities: enum Items: 'Disabled' 'Enabled' Item0: 'Disabled' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123595 Title: [System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute speakers when headphones are plugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1123595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1123595] Re: [System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute speakers when headphones are plugged
I re-ran alsa-info.sh both with and without headphones. Attached is the
output. With headphones attached it reads:
control.33 {
iface CARD
name 'Headphone Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
Michael
On 02/13/2013 08:29 PM, Raymond wrote:
did you run alsa-info.sh after you plugged the headphone ?
control.33 {
iface CARD
name 'Headphone Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
** Attachment added: alsa-info.txt.no-headphones
https://bugs.launchpad.net/bugs/1123595/+attachment/3528735/+files/alsa-info.txt.no-headphones
** Attachment added: alsa-info.txt.with-headphones
https://bugs.launchpad.net/bugs/1123595/+attachment/3528736/+files/alsa-info.txt.with-headphones
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123595
Title:
[System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute
speakers when headphones are plugged
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1123595/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1123595] Re: [System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute speakers when headphones are plugged
I have: $ dpkg -l | grep system76 ii system76-driver 3.2.3 Universal driver for System76 computers. I have: 1) Run System76 Driver 2) Clicked Install Drivers 3) Rebooted And the problem persists. Don't know if a quick screenshot might help, but here it is: Before plugging in headphones: After plugging in headphones: Michael On 02/13/2013 12:38 AM, Dave Lentz wrote: Make sure the System76 driver = 2.6.5 Version 2.6.5 - Fix Bonobo (bonp5) headphone detection and speaker mute http://www.knowledge76.com/index.php/System76_Driver_Changelog ** Summary changed: - Alsa does not mute speakers when headphones are plugged + [System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute speakers when headphones are plugged ** Attachment added: Screenshot from 2013-02-13 09:41:20.png https://bugs.launchpad.net/bugs/1123595/+attachment/3526533/+files/Screenshot%20from%202013-02-13%2009%3A41%3A20.png ** Attachment added: Screenshot from 2013-02-13 09:41:42.png https://bugs.launchpad.net/bugs/1123595/+attachment/3526534/+files/Screenshot%20from%202013-02-13%2009%3A41%3A42.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123595 Title: [System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute speakers when headphones are plugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1123595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1123595] Re: Alsa does not mute speakers when headphones are plugged
Attached. On 02/12/2013 08:55 PM, Raymond wrote: post the output of alsa-info.sh ** Attachment added: alsa-info.txt.USy4hXJVUI https://bugs.launchpad.net/bugs/1123595/+attachment/3526547/+files/alsa-info.txt.USy4hXJVUI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123595 Title: [System76 Bonobo Pro, Realtek ALC892, jack sensing] Alsa does not mute speakers when headphones are plugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1123595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123595] [NEW] Alsa does not mute speakers when headphones are plugged
Public bug reported: When plugging in headphones, the headphone sense happens properly, and most speaker output is muted (Surround, Center, LFE), but the Front speakers are still at regular volume. Muting the Front speakers also mutes the Master, and sound stops to both headphone and speakers. a workaround is to set Front to 0 after plugging the speakers with the following command: /usr/bin/amixer -c 0 set 'Front' 0 This is a new development brought on by a recent update. Sound used to work properly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael1995 F pulseaudio /dev/snd/controlC0: michael1995 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf650 irq 52' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,15587100,00100302' Controls : 37 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf608 irq 17' Mixer name : 'Nvidia GPU 15 HDMI/DP' Components : 'HDA:10de0015,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Tue Feb 12 19:00:51 2013 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Bonobo Professional dmi.board.vendor: System76, Inc. dmi.board.version: bonp5 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: bonp5 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd04/06/2011:svnSystem76,Inc.:pnBonoboProfessional:pvrbonp5:rvnSystem76,Inc.:rnBonoboProfessional:rvrbonp5:cvnSystem76,Inc.:ct10:cvrbonp5: dmi.product.name: Bonobo Professional dmi.product.version: bonp5 dmi.sys.vendor: System76, Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123595 Title: Alsa does not mute speakers when headphones are plugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1123595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1117676] [NEW] Lightdm autologin no longer works unless autologin-user-time=0
Public bug reported: Lightdm's autologin feature no longer works unless autologin-user- timeout is set to exactly 0. Any value greater than 0 no longer works. This functionality worked properly in lightdm 1.2.1-0ubuntu1.1. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Feb 6 15:28:34 2013 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MarkForUpload: True ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US: SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1117676 Title: Lightdm autologin no longer works unless autologin-user-time=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1117676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1117682] [NEW] apt-get crashes with a segmentation fault
Public bug reported: When trying to --reinstall multiple packages with apt-get, it crashes with a segmentation fault. The command line: apt-get --reinstall install 2-or-more-packages... Syslog shows: kernel: [ 3322.059837] apt-get[14417]: segfault at 7fa5c24d65bc ip 7fa5bb931329 sp 7fffb0170528 error 4 in libapt-pkg.so.4.12.0[7fa5bb8e1000+121000] ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apt 0.8.16~exp12ubuntu10.7 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Feb 6 15:39:44 2013 InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MarkForUpload: True ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US: SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1117682 Title: apt-get crashes with a segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1117682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 790016] Re: Touchpad enable/disable button no longer works in 11.04
I will test this as time allows. For the moment, the machine is a laptop that is in active use in the field, so it could be a while. If the bug closes before I can get to it then I'll not sweat it, I'll just re-open it or file a new one. Thanks for your work! Ubuntu is great! Michael On 10/17/2012 11:30 PM, Christopher M. Penalver wrote: msp3k, thank you for reporting this and helping make Ubuntu better. Natty reached EOL on October 2012. Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux replace-with-bug-number Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag: needs-upstream-testing This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text: needs-upstream-testing If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: kernel-unable-to-test-upstream kernel-unable-to-test-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. Please let us know your results. Thank you for your understanding. Helpful Bug Reporting Tips: https://help.ubuntu.com/community/ReportingBugs ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790016 Title: Touchpad enable/disable button no longer works in 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1039023] [NEW] apt fails on packages greater than 3.3GB in size
Public bug reported: I roll custom packages for use in-house to distribute software to machines. One package distributes the free-but-proprietary Intel software development suite. It is 3.7GB in size. When installing, I see the following error: (Note that host and domain name information has been replaced with mydomain.) The following NEW packages will be installed: mydomain-intel-software-development-products 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 3,636 MB of archives. After this operation, 12.9 GB of additional disk space will be used. Get:1 http://mydomain/flagon/repositories/mydomain-proprietary/ stable/main mydomain-intel-software-development-products amd64 2011-3 [3,636 MB] Fetched 3,636 MB in 1min 38s (36.8 MB/s) E: Unable to seek ahead 3633241954 E: Prior errors apply to /var/cache/apt/archives/mydomain-intel-software-development-products_2011-3_amd64.deb debconf: apt-extracttemplates failed: No such file or directory Selecting previously unselected package mydomain-intel-software-development-products. (Reading database ... 660705 files and directories currently installed.) Unpacking mydomain-intel-software-development-products (from .../mydomain-intel-software-development-products_2011-3_amd64.deb) ... Setting up mydomain-intel-software-development-products (2011-3) ... Either apt and apt-extracttemplates should be able to handle packages of this size, or the package build tools should generate an error and refuse to allow the user to generate packages of this size to begin with. Either way, it seems to me to be a bug. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039023 Title: apt fails on packages greater than 3.3GB in size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1039023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1039023] Re: apt fails on packages greater than 3.3GB in size
Addendum: The package payload seems to be installed correctly, and apt's exit code is 0. However, this is a simple package. It consists solely of payload data, with no install scripts, templates, menu entry, cron job, etc. Judging from the error message produced, I am guessing that if this package had contained template data, that part of the installation, at least, would have failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039023 Title: apt fails on packages greater than 3.3GB in size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1039023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984705] Re: IMAP session crashes when i'm using UID FETCH (ENVELOPE) on some emails.
Please disregard my earlier post. This does not seem to fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984705 Title: IMAP session crashes when i'm using UID FETCH (ENVELOPE) on some emails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/courier/+bug/984705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984705] Re: IMAP session crashes when i'm using UID FETCH (ENVELOPE) on some emails.
The following will allow one to compile courier 0.68.2, which supposedly does not suffer from this bug. It's untested though. ** Attachment added: courier_0.68.2-1ubuntu5.dsc https://bugs.launchpad.net/ubuntu/+source/courier/+bug/984705/+attachment/3215321/+files/courier_0.68.2-1ubuntu5.dsc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984705 Title: IMAP session crashes when i'm using UID FETCH (ENVELOPE) on some emails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/courier/+bug/984705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984705] Re: IMAP session crashes when i'm using UID FETCH (ENVELOPE) on some emails.
The following will allow one to compile courier 0.68.2, which supposedly does not suffer from this bug. It's untested though. ** Attachment removed: courier_0.68.2-1ubuntu5.dsc https://bugs.launchpad.net/ubuntu/+source/courier/+bug/984705/+attachment/3215321/+files/courier_0.68.2-1ubuntu5.dsc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984705 Title: IMAP session crashes when i'm using UID FETCH (ENVELOPE) on some emails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/courier/+bug/984705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984705] Re: IMAP session crashes when i'm using UID FETCH (ENVELOPE) on some emails.
Supposedly the latest 0.68.2 version of courier does not suffer from this bug. You can take the patch from http://archive.ubuntu.com/ubuntu/pool/universe/c/courier/courier_0.66.1-1ubuntu4.diff.gz and apply it to the latest courier-0.68.1.tar.bz2 and compile to get packages that you can then install w/ dpkg. Attached is a patch that I created against 0.68.2. It compiles, but it's not yet tested, so caveat emptor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984705 Title: IMAP session crashes when i'm using UID FETCH (ENVELOPE) on some emails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/courier/+bug/984705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1009729] Re: Compiz crashed on an NVIDIA NV37GL w/ nvidia-current drivers installed
Found this in the log file: Jun 7 14:40:43 ardea kernel: [77769.411006] NVRM: The NVIDIA Quadro FX 330 GPU installed in this system is Jun 7 14:40:43 ardea kernel: [77769.411010] NVRM: supported through the NVIDIA 173.14.xx Legacy drivers. Please Jun 7 14:40:43 ardea kernel: [77769.411012] NVRM: visit http://www.nvidia.com/object/unix.html for more Jun 7 14:40:43 ardea kernel: [77769.411013] NVRM: information. The 295.40 NVIDIA driver will ignore Jun 7 14:40:43 ardea kernel: [77769.411015] NVRM: this GPU. Continuing probe... Jun 7 14:40:43 ardea kernel: [77769.411919] NVRM: No NVIDIA graphics adapter found! However, attempts to install the nvidia-173 package failed: ~# apt-get install nvidia-173 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: nvidia-173 : Depends: xorg-video-abi-10 but it is not installable E: Unable to correct problems, you have held broken packages. ~# apt-get install nvidia-173 xorg-video-abi-10 Reading package lists... Done Building dependency tree Reading state information... Done Package xorg-video-abi-10 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'xorg-video-abi-10' has no installation candidate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009729 Title: Compiz crashed on an NVIDIA NV37GL w/ nvidia-current drivers installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1009729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1009729] [NEW] Compiz crashed on an NVIDIA NV37GL w/ nvidia-current drivers installed
Public bug reported: After installing nvidia-current, nvidia-settings, and screen-resolution-extra, compiz crashes w/ the following error: segfault at 0 ip 7fe3cfc0cae4 sp 7fffec35b760 error 4 in libc-2.15.so[7fe3cfb6d000+1b3000] ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: compiz 1:0.9.7.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Wed Jun 6 16:55:37 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current, 295.40, 3.2.0-24-generic, x86_64: installed vboxhost, 4.1.14, 3.2.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation NV37GL [Quadro PCI-E Series] [10de:00fd] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0215] InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MachineType: Dell Inc. Precision WorkStation 470 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=1d01309f-42ef-4ed9-a6c8-8398c7196959 ro SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0P7996 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/18/2005:svnDellInc.:pnPrecisionWorkStation470:pvr:rvnDellInc.:rn0P7996:rvr:cvnDellInc.:ct3:cvr: dmi.product.name: Precision WorkStation 470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 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 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug needs-reassignment precise regression-update ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009729 Title: Compiz crashed on an NVIDIA NV37GL w/ nvidia-current drivers installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1009729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1009729] Re: Compiz crashed on an NVIDIA NV37GL w/ nvidia-current drivers installed
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009729 Title: Compiz crashed on an NVIDIA NV37GL w/ nvidia-current drivers installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1009729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948118] [NEW] installer netcfg for 12.04 fails to set dns nameservers during installation
Public bug reported: Running the March 5 2012 beta server installer for Precise Pangolin, the installer fails to set dns-nameservers in /etc/network/interfaces on the install client during installation. ** Affects: netcfg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948118 Title: installer netcfg for 12.04 fails to set dns nameservers during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/948118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 948118] Re: installer netcfg for 12.04 fails to set dns nameservers during installation
Attached. Michael Peek On 03/06/2012 11:04 AM, Stéphane Graber wrote: Can you please attach /var/log/installer/syslog from your installed system? ** Changed in: netcfg (Ubuntu) Status: New = Incomplete ** Attachment added: syslog https://bugs.launchpad.net/bugs/948118/+attachment/2823427/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948118 Title: installer netcfg for 12.04 fails to set dns nameservers during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/948118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 941667] Re: package flashplugin-installer 11.1.102.62ubuntu0.11.10.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Here is the error message: Setting up flashplugin-installer (11.1.102.62ubuntu0.11.10.2) ... Downloading... --2012-02-27 18:45:38-- http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.1.102.62.orig.tar.gz Resolving \\... failed: Name or service not known. wget: unable to resolve host address `\\' download failed The Flash plugin is NOT installed. dpkg: error processing flashplugin-installer (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: flashplugin-installer E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/941667 Title: package flashplugin-installer 11.1.102.62ubuntu0.11.10.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/941667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 943350] [NEW] apport-cli crashes while attempting to report a bug in package xserver-xorg
Public bug reported:
.ERROR: hook /usr/share/apport/package-hooks//source_xorg.py crashed:
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/apport/report.py, line 659, in
add_hooks_info
symb['add_info'](self, ui)
File /usr/share/apport/package-hooks//source_xorg.py, line 451, in add_info
attach_graphic_card_pci_info(report, ui)
File /usr/share/apport/package-hooks//source_xorg.py, line 274, in
attach_graphic_card_pci_info
key, value = line.split(': ', 1)
ValueError: need more than 1 value to unpack
..
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: apport 1.20.1-0ubuntu5.1
ProcVersionSignature: Ubuntu 2.6.38-13.56-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashReports: 644:0:0:22158:2012-02-28 09:29:49.038614481 -0500:2012-02-28
09:29:53.438657726 -0500:/var/crash/blcr-dkms.0.crash
Date: Wed Feb 29 10:49:01 2012
InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64
(20110426)
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
LANGUAGE=en_US:
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943350
Title:
apport-cli crashes while attempting to report a bug in package
xserver-xorg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/943350/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
