[Bug 1862793] [NEW] Can't login if third-party software is enabled
Public bug reported: Ubuntu 18.04.3 Fresh install If "Third Party Drivers" is checked during install, then I can't login. It flashes to black screen, then login screen shown again. System: Core-i7 2600 NVidia 1660 6GB 16GB RAM ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 18.04.3 Fresh install If "Third Party Drivers" is checked during install, then I can't login. It flashes to black screen, then login screen shown again. + + System: + Core-i7 2600 + NVidia 1660 6GB + 16GB RAM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862793 Title: Can't login if third-party software is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1862793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810220] Re: plasmashell segaults in libkcupslib.so during login
related (or even identical) bugs: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044 https://bugs.launchpad.net/ubuntu/+source/print-manager/+bug/1794526 This bug is crucial. It is annoying. As it still persists. Please harden plasma-shell not to depend on crashing plugins. Please fix the crash in printer-manager. Thank you, folks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810220 Title: plasmashell segaults in libkcupslib.so during login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/print-manager/+bug/1810220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810220] Re: plasmashell segaults in libkcupslib.so during login
cf. https://bugs.launchpad.net/ubuntu/+source/plasma- workspace/+bug/1770044 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810220 Title: plasmashell segaults in libkcupslib.so during login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/print-manager/+bug/1810220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810220] [NEW] plasmashell segaults in libkcupslib.so during login
Public bug reported: It took me quite a while until I found and could confirm an older existing bug in plasma-workframe induced by an non-existent printer. # dmesg | tail -2 [ 336.325887] plasmashell[2335]: segfault at 0 ip 7fa367822556 sp 7ffd1c375180 error 4 in libkcupslib.so[7fa3677e6000+55000] [ 598.156727] Qt bearer threa[2298]: segfault at 30 ip 7f524a434d71 sp 7f522effc720 error 4 in libQt5Core.so.5.9.5[7f524a1ae000+53b000] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: print-manager 4:17.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jan 2 00:08:43 2019 InstallationDate: Installed on 2018-07-05 (180 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: print-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: print-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810220 Title: plasmashell segaults in libkcupslib.so during login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/print-manager/+bug/1810220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794209] [NEW] package python3-pil:amd64 5.1.0-1 failed to install/upgrade: installed python3-pil:amd64 package post-installation script subprocess returned error exit status 1
Public bug reported: Upgrading from 16.04 to 18.04 The message "could not install...-pil" appeared halfway through (see attached screenshot. When the upgrade was almost complete I received another message "could not install upgrades, the upgrade has aborted. Your system could be in an unstable state. A recovery will run now (dpkg-configure-a)." (your program would not let me upload more than one screenshot) When the upgrade was complete a third message "upgrade complete. The upgrade has completed but there were errors during the upgrade process" (see attached screenshot) The reason I upgraded was because the last update kernel I downloaded 4.4.0-135 would not let me reboot properly. Please tell me how to fix this. Thanks. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-pil:amd64 5.1.0-1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sun Sep 23 21:53:45 2018 ErrorMessage: installed python3-pil:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-12-15 (1014 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: pillow Title: package python3-pil:amd64 5.1.0-1 failed to install/upgrade: installed python3-pil:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago) ** Affects: pillow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic python3-pil ** Attachment added: "Could not intall upgrades.png" https://bugs.launchpad.net/bugs/1794209/+attachment/5192633/+files/Could%20not%20intall%20upgrades.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794209 Title: package python3-pil:amd64 5.1.0-1 failed to install/upgrade: installed python3-pil:amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pillow/+bug/1794209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
Yes it does have hybrid graphics. I also use an external GPU. This occurs with or without the EGPU plugged in. However, it may be that there was a problem in that specific version of SDDM in that particular daily build. Somehow, someway installing the Ubuntu Gnome desktop system and gdm2 fixed it. Then I did a full upgrade a couple days ago and got a new version of sddm, switched to that and that seems to have fixed it. The real problem is that a new user when confronted with a utterly BLACK screen won't know to Ctrl alt f6 into a terminal and do things from there. That sort of thing is a typical "why Linux will always be for geeks" moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765923 Title: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
Installing GDM3 does lead to a system which will not boot to a black screen. Note you will need to change the desktop session to plasma to get to kde. For an experienced user used to the command prompt this is an annoyance. I'd rather run a pure KDE kubuntu system. To a newer or less technical user having a black screen (not flashing cursor BLACK) is a show stopper. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765923 Title: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
This is what I get when I log out of X and run sddm
:~$ sddm
[04:28:22.147] (II) DAEMON: Initializing...
[04:28:22.154] (II) DAEMON: Logind interface found
[04:28:22.154] (II) DAEMON: Starting...
[04:28:22.155] (II) DAEMON: Adding new display on vt 1 ...
[04:28:22.155] (II) DAEMON: Loading theme configuration from ""
[04:28:22.155] (II) DAEMON: Display server starting...
[04:28:22.155] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth
/var/run/sddm/{3029e4a4-8913-4abe-ac00-294e7375c132} -background none -noreset
-displayfd 17 -seat seat0 vt1
[04:28:22.157] (EE) DAEMON: Display server failed to start. Exiting
Aborted (core dumped)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765923
Title:
Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765923] [NEW] Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
Public bug reported: Using the April 19th daily build of Kubuntu 18.04 I installed the Nvidia drivers via the following command. sudo ubuntu-drivers autoinstall The install process proceeds fine and after a logout process I get a black screen. I tried this on the April 17th daily build of bionic and a reboot also results in a black screen. The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE After I installed latest Nvidia driver-390 and tried to boot after shutting down once I faced a black screen problem. since, I'm a noob but something related to nvidia drivers couldn't be started. Then I followed https://askubuntu.com/a/968692/802490 While following these instructions re-installing of nvidia drivers failed. The only things that worked is purging the drivers and changing "WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install nvidia drivers again but I'm afraid that this will lead to that problem again. Can anyone help in re-installing the driver such that I won't face that problem? END QUOTE THE WORK AROUND Use Ctrl-Alt-f6 to get to a login prompt. Login run "startx" The x server will start and Nvidia drivers will function. THE PROBLEM When I try to run SDDM I get an error (Which I will try to copy down to add to this bug when I am on a different computer than the one I am reporting the bug about.). Installing lightDM does not work... it installs but is either will not run or will not actually start a x session. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Description changed: Using the April 19th daily build of Kubuntu 18.04 I installed the Nvidia drivers via the following command. sudo ubuntu-drivers autoinstall The install process proceeds fine and after a logout process I get a black screen. I tried this on the April 17th daily build of bionic and a reboot also results in a black screen. - The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE - After I installed latest Nvidia driver-390 and tried to boot after shutting down once I faced a black screen problem. since, I'm a noob but something related to nvidia drivers couldn't be started. Then I followed https://askubuntu.com/a/968692/802490 + After I installed latest Nvidia driver-390 and tried to boot after shutting down once I faced a black screen problem. since, I'm a noob but something related to nvidia drivers couldn't be started. Then I followed https://askubuntu.com/a/968692/802490 While following these instructions re-installing of nvidia drivers failed. The only things that worked is purging the drivers and changing "WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install nvidia drivers again but I'm afraid that this will lead to that problem again. Can anyone help in re-installing the driver such that I won't face that problem? END QUOTE THE WORK AROUND - Use Ctrl-Alt-f6 to get to a login prompt. + Use Ctrl-Alt-f6 to get to a login prompt. Login run "startx" The x server will start and Nvidia drivers will function. THE PROBLEM - When I try to run SDDM I get an error (Which I will try to copy down to add to this bug when I am on a different computer than the one I am reporting the bug about.). + When I try to run SDDM I get an error (Which I will try to copy down to add to this bug when I am on a different computer than the one I am reporting the bug about.). - Installing lightDM does not work. + Installing lightDM does not work... it installs but is either will not + run or will not actually start a x session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765923 Title: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469200] Re: x-tile misses dependency package python-appindicator
Still affects 2.5-3, which is still the version in the Ubuntu 16.04 repositories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1469200 Title: x-tile misses dependency package python-appindicator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x-tile/+bug/1469200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732157] [NEW] yagf crashes when opening pdf or inserting clipboard
Public bug reported: yagf 0.9.3.2-1ubuntu1 (xenial) crashes whenever I trie to open a pdf (7 pages, 5 MB) or insert single pages from clipboard as image. Same happens with gimage and other ocr apps, underlaying library suspected. Can you find the bug from this log, maybe, please? QThread: Destroyed while thread is still running QProcess: Destroyed while process is still running. *** Error in `yagf': corrupted double-linked list: 0x00940ea0 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7faee6f167e5] /lib/x86_64-linux-gnu/libc.so.6(+0x82970)[0x7faee6f21970] /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7faee6f23184] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QListData11detach_growEPii+0x53)[0x7faee7e4e893] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x16e56d)[0x7faee7f2256d] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1a6d7d)[0x7faee7f5ad7d] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN14QObjectPrivate16setParent_helperEP7QObject+0x226)[0x7faee7f590e6] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QLayout14addChildLayoutEPS_+0xe6)[0x7faee8499436] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QLayout11adoptLayoutEPS_+0x12)[0x7faee84994b2] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN10QBoxLayout12insertLayoutEiP7QLayouti+0x26)[0x7faee8479a56] yagf(_ZN16Ui_PopplerDialog7setupUiEP7QDialog+0x975)[0x44f795] yagf(_ZN13PopplerDialogC1EP7QWidget+0x40)[0x44eb40] yagf(_ZN8MainForm9importPDFEv+0x2e)[0x43459e] yagf[0x480f9d] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x4d0)[0x7faee7f53010] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QAction9triggeredEb+0x42)[0x7faee8465d62] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QAction8activateENS_11ActionEventE+0x83)[0x7faee84670b3] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x6219fd)[0x7faee88c89fd] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x625de9)[0x7faee88ccde9] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x2a0)[0x7faee84c28d0] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN5QMenu5eventEP6QEvent+0x6b)[0x7faee88d0ffb] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c)[0x7faee846bfdc] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x476)[0x7faee84730d6] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8d)[0x7faee7f3e90d] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x14d)[0x7faee84726dd] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249d7c)[0x7faee84f0d7c] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0x16b3)[0x7faee84efc83] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272542)[0x7faee8519542] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2a7)[0x7faee655f197] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0)[0x7faee655f3f0] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7faee655f49c] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x9e)[0x7faee7f6f2ce] /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272616)[0x7faee8519616] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x3f)[0x7faee7f3d18f] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x1b5)[0x7faee7f3d4f5] /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x99)[0x7faee7f434b9] yagf(main+0x309)[0x42de79] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7faee6ebf830] yagf[0x42e3d8] === Memory map: 0040-00543000 r-xp 08:06
[Bug 1608416] [NEW] package ncurses-term 6.0+20160213-1ubuntu1 failed to install/upgrade: package ncurses-term is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported:
I thought this was suppose to be fixed. I tried to install lbs package
on my epson XP-620 and download the drivers using the Ubuntu software
center to load the 3rd party drivers from epson as I always have (that
works great under 14.04 after installing the lsb package prior to
downloading the newest/same old Linux drivers from epson that still
work. I had all kinds of box's pop up with errors so I stopped the
install that was stuck anyway. I rebooted and loaded any and all
updates, there were none. I then went back to the epson page and loaded
the lsb and then continued to the epson drivers through the Ubuntu
Software Center it told me I still had errors but it was still trying to
ask me which driver to load so I picked the right one and it did load it
and I was able to print out a test page. I almost stopped and reloaded
14.04.
Ok I forgot to check to see what printed when I hit the print test page
. It sounded like it was printing it made all the right sounds like it
was printing but it
{[printed a blank page}].
and I just tried to print this page and the same thing happened it
acted like it was printing but the printed page was blank. I changed
the all of the ink cartridges a few weeks ago and have printed about 10
to 20 pages with less than half text and a few graphics and it worked
fine then. I have a headache.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ncurses-term 6.0+20160213-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Aug 1 04:10:40 2016
Dependencies:
DpkgTerminalLog:
Preparing to unpack .../epson-inkjet-printer-escpr_1.4.1-1lsb3.2_amd64.deb ...
Unpacking epson-inkjet-printer-escpr (1.4.1-1lsb3.2) ...
dpkg: error processing package ncurses-term (--configure):
package ncurses-term is not ready for configuration
cannot configure (current status 'half-installed')
DuplicateSignature:
package:ncurses-term:6.0+20160213-1ubuntu1
Unpacking epson-inkjet-printer-escpr (1.4.1-1lsb3.2) ...
dpkg: error processing package ncurses-term (--configure):
package ncurses-term is not ready for configuration
ErrorMessage: package ncurses-term is not ready for configuration cannot
configure (current status 'half-installed')
InstallationDate: Installed on 2016-07-31 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.1
apt 1.2.12~ubuntu16.04.1
SourcePackage: ncurses
Title: package ncurses-term 6.0+20160213-1ubuntu1 failed to install/upgrade:
package ncurses-term is not ready for configuration cannot configure (current
status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ncurses (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package need-duplicate-check xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608416
Title:
package ncurses-term 6.0+20160213-1ubuntu1 failed to install/upgrade:
package ncurses-term is not ready for configuration cannot configure
(current status 'half-installed')
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1608416/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433106] [NEW] package libasound2:i386 1.0.27.2-3ubuntu7 failed to install/upgrade: package libasound2:i386 is already installed and configured
Public bug reported: it happens on start up im runnung ubuntu 14.02 lts it doesnt really effect me its just annoying ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libasound2:i386 1.0.27.2-3ubuntu7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Mon Mar 16 22:31:58 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libasound2-data 1.0.27.2-3ubuntu7 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.5 DuplicateSignature: package:libasound2:i386:1.0.27.2-3ubuntu7:package libasound2:i386 is already installed and configured ErrorMessage: package libasound2:i386 is already installed and configured InstallationDate: Installed on 2015-03-17 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: i386 SourcePackage: dpkg Title: package libasound2:i386 1.0.27.2-3ubuntu7 failed to install/upgrade: package libasound2:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433106 Title: package libasound2:i386 1.0.27.2-3ubuntu7 failed to install/upgrade: package libasound2:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1433106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424326] [NEW] package po-debconf 1.0.16+nmu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: trying to install the driver for my epson artisan 837 all in one printer. it dose not matter if I download from epson the latest driver and it uses the software center to install it crashes or if i use the open one for cups it crashes. it works on my other ubuntu computers. This is a recent motherboard replacement a asus JI1800C. with ubuntu 14.10 x64 bit installed. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: po-debconf 1.0.16+nmu3 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 Date: Sun Feb 22 00:26:31 2015 DuplicateSignature: package:po-debconf:1.0.16+nmu3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-02-19 (2 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: po-debconf Title: package po-debconf 1.0.16+nmu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: po-debconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424326 Title: package po-debconf 1.0.16+nmu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/po-debconf/+bug/1424326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] Re: Wi-Fi authentication timed out after upgrade to 14.10
This was causing too many issues so I have installed a clean copy of 14.10 and I can connect to the network now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264937/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264950/+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/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] NetDevice.vmnet1.txt
apport information ** Attachment added: "NetDevice.vmnet1.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264942/+files/NetDevice.vmnet1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264947/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] NetDevice.vmnet8.txt
apport information ** Attachment added: "NetDevice.vmnet8.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264943/+files/NetDevice.vmnet8.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] NetDevice.eth0.txt
apport information ** Attachment added: "NetDevice.eth0.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264939/+files/NetDevice.eth0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264951/+files/nmcli-dev.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] NetDevice.docker0.txt
apport information ** Attachment added: "NetDevice.docker0.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264938/+files/NetDevice.docker0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] NetDevice.wlan1.txt
apport information ** Attachment added: "NetDevice.wlan1.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264945/+files/NetDevice.wlan1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264940/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] NetDevice.wlan0.txt
apport information ** Attachment added: "NetDevice.wlan0.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264944/+files/NetDevice.wlan0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] NetDevice.usb0.txt
apport information ** Attachment added: "NetDevice.usb0.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264941/+files/NetDevice.usb0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264949/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264946/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264935/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264948/+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/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1393662/+attachment/4264936/+files/IpAddr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] Re: Wi-Fi authentication timed out after upgrade to 14.10
apport information ** Tags added: apport-collected third-party-packages ** Description changed: After upgrading to 14.10 I can no longer connect to any wifi network that has WPA authentication regardless of the wifi adapter used (built in BCM4331 and USB dongle RTL8188C). The same setup was working fine before the upgrade. I am able to connect to open networks, which I tested by tethering to a wifi hotspot on my phone. USB tethering also works. I have confirmed that the wifi password is correct and have even removed and added the network. THis is on a 2012 Mac Mini. Expected behaviour: The wifi adapter should have connected to my network Actual behaviour: The wifi adapter is not able to connect. 'dmesg' is full of the following error messages: [53173.494849] wlan0: authenticate with 28:cf:da:b0:1c:83 [53173.501930] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 1/3) [53173.705568] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 2/3) [53173.909450] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 3/3) [53174.113404] wlan0: authentication with 28:cf:da:b0:1c:83 timed out [53185.353644] wlan0: authenticate with 28:cf:da:b0:1c:83 [53185.371975] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 1/3) [53185.575432] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 2/3) [53185.779307] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 3/3) [53185.983204] wlan0: authentication with 28:cf:da:b0:1c:83 timed out [53201.473166] wlan0: authenticate with 28:cf:da:b0:1c:83 [53201.473429] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 1/3) [53201.675127] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 2/3) [53201.878976] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 3/3) [53202.082908] wlan0: authentication with 28:cf:da:b0:1c:83 timed out $ lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 Every 1.0s: iwconfig wlan0; ifconfig wlan0; route -n; echo; (grep wlan0: /var/log/syslog | tail -n 10 | sort -r); echo; ping -I wlan0... Mon Nov 17 21:28:28 2014 wlan0 IEEE 802.11bg ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off wlan0 Link encap:Ethernet HWaddr 28:cf:e9:01:85:e7 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.42.129 0.0.0.0 UG0 00 usb0 172.16.57.0 0.0.0.0 255.255.255.0 U 0 00 vmnet1 172.16.176.00.0.0.0 255.255.255.0 U 0 00 vmnet8 172.17.0.0 0.0.0.0 255.255.0.0 U 0 00 docker0 192.168.42.00.0.0.0 255.255.255.0 U 1 00 usb0 Nov 17 12:22:08 shane-Macmini wpa_supplicant[5642]: wlan0: SME: Trying to authenticate with 28:cf:da:b0:1c:83 (SSID='wombat' freq=2437 MHz) Nov 17 12:22:08 shane-Macmini wpa_supplicant[5642]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wombat" auth_failures=2 duration=20 Nov 17 12:22:08 shane-Macmini wpa_supplicant[5642]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wombat" auth_failures=1 duration=10 Nov 17 12:22:08 shane-Macmini wpa_supplicant[5642]: wlan0: CTRL-EVENT-SCAN-STARTED Nov 17 12:22:08 shane-Macmini kernel: [57232.210525] wlan0: authentication with 28:cf:da:b0:1c:83 timed out Nov 17 12:22:08 shane-Macmini kernel: [57232.006586] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 3/3) Nov 17 12:22:07 shane-Macmini wpa_supplicant[5642]: wlan0: SME: Trying to authenticate with 28:cf:da:b0:1c:83 (SSID='wombat' freq=2437 MHz) Nov 17 12:22:07 shane-Macmini kernel: [57231.802707] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 2/3) Nov 17 12:22:07 shane-Macmini kernel: [57231.599118] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 1/3) Nov 17 12:22:07 shane-Macmini kernel: [57231.580265] wlan0: authenticate with 28:cf:da:b0:1c:83 + --- + ApportVersion: 2.14.7-0ubuntu8 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.10 + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + InstallationDate: Installed on 2014-06-06 (168 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) + IpRoute: + default via 192.168.42.129 dev usb0 proto static + 172.16.57.0/24 dev vmnet1 proto kernel scope link src 172.16.57.1 + 172.16.176.0/24 dev vmnet8 proto kernel scope link src 172.16.176.1 + 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 + 192.168.42.0/24 dev usb0 proto kernel scope link src
[Bug 1393662] Re: Wi-Fi authentication timed out after upgrade to 14.10
It seems I can only connect to the open networks with the dongle. The build in BCM will not connect to an open access point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393662] [NEW] Wi-Fi authentication timed out after upgrade to 14.10
Public bug reported: After upgrading to 14.10 I can no longer connect to any wifi network that has WPA authentication regardless of the wifi adapter used (built in BCM4331 and USB dongle RTL8188C). The same setup was working fine before the upgrade. I am able to connect to open networks, which I tested by tethering to a wifi hotspot on my phone. USB tethering also works. I have confirmed that the wifi password is correct and have even removed and added the network. THis is on a 2012 Mac Mini. Expected behaviour: The wifi adapter should have connected to my network Actual behaviour: The wifi adapter is not able to connect. 'dmesg' is full of the following error messages: [53173.494849] wlan0: authenticate with 28:cf:da:b0:1c:83 [53173.501930] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 1/3) [53173.705568] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 2/3) [53173.909450] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 3/3) [53174.113404] wlan0: authentication with 28:cf:da:b0:1c:83 timed out [53185.353644] wlan0: authenticate with 28:cf:da:b0:1c:83 [53185.371975] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 1/3) [53185.575432] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 2/3) [53185.779307] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 3/3) [53185.983204] wlan0: authentication with 28:cf:da:b0:1c:83 timed out [53201.473166] wlan0: authenticate with 28:cf:da:b0:1c:83 [53201.473429] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 1/3) [53201.675127] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 2/3) [53201.878976] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 3/3) [53202.082908] wlan0: authentication with 28:cf:da:b0:1c:83 timed out $ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 Every 1.0s: iwconfig wlan0; ifconfig wlan0; route -n; echo; (grep wlan0: /var/log/syslog | tail -n 10 | sort -r); echo; ping -I wlan0... Mon Nov 17 21:28:28 2014 wlan0 IEEE 802.11bg ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off wlan0 Link encap:Ethernet HWaddr 28:cf:e9:01:85:e7 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.42.129 0.0.0.0 UG0 00 usb0 172.16.57.0 0.0.0.0 255.255.255.0 U 0 00 vmnet1 172.16.176.00.0.0.0 255.255.255.0 U 0 00 vmnet8 172.17.0.0 0.0.0.0 255.255.0.0 U 0 00 docker0 192.168.42.00.0.0.0 255.255.255.0 U 1 00 usb0 Nov 17 12:22:08 shane-Macmini wpa_supplicant[5642]: wlan0: SME: Trying to authenticate with 28:cf:da:b0:1c:83 (SSID='wombat' freq=2437 MHz) Nov 17 12:22:08 shane-Macmini wpa_supplicant[5642]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wombat" auth_failures=2 duration=20 Nov 17 12:22:08 shane-Macmini wpa_supplicant[5642]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wombat" auth_failures=1 duration=10 Nov 17 12:22:08 shane-Macmini wpa_supplicant[5642]: wlan0: CTRL-EVENT-SCAN-STARTED Nov 17 12:22:08 shane-Macmini kernel: [57232.210525] wlan0: authentication with 28:cf:da:b0:1c:83 timed out Nov 17 12:22:08 shane-Macmini kernel: [57232.006586] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 3/3) Nov 17 12:22:07 shane-Macmini wpa_supplicant[5642]: wlan0: SME: Trying to authenticate with 28:cf:da:b0:1c:83 (SSID='wombat' freq=2437 MHz) Nov 17 12:22:07 shane-Macmini kernel: [57231.802707] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 2/3) Nov 17 12:22:07 shane-Macmini kernel: [57231.599118] wlan0: direct probe to 28:cf:da:b0:1c:83 (try 1/3) Nov 17 12:22:07 shane-Macmini kernel: [57231.580265] wlan0: authenticate with 28:cf:da:b0:1c:83 ** 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/1393662 Title: Wi-Fi authentication timed out after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1393662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349963] [NEW] package texlive-latex-base 2013.20140215-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: failed to install ProblemType: Package DistroRelease: Ubuntu 14.04 Package: texlive-latex-base 2013.20140215-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Jul 30 02:52:26 2014 DuplicateSignature: package:texlive-latex-base:2013.20140215-1:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2011-10-22 (1011 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: texlive-base Title: package texlive-latex-base 2013.20140215-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-07-29 (0 days ago) ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349963 Title: package texlive-latex-base 2013.20140215-1 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/texlive-base/+bug/1349963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277245] Re: nvidia prime causing mouse and screen to freeze
I think this is a duplicate of bug #1220426 but I don't see any way to link them. Anyway, I'm seeing this also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277245 Title: nvidia prime causing mouse and screen to freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1277245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086693] Re: Please don't enable the NetworkManager-controlled dnsmasq by default
It still doesn't work right in 13.04. Why should people installing Ubuntu know to edit a configuration file that their account doesn't even own before their networking will work? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086693 Title: Please don't enable the NetworkManager-controlled dnsmasq by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1086693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
Hi Luigi, I'm glad to hear the the workaround helped. Yes, it's unclear why this bug has reappeared in 12.10 after being fixed in 12.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
/etc/init.d/umountroot does not execute umount, it executes mount with '-o remount,ro' flags to remount the root filesystem in read-only mode. Some process has a file open for write on the root filesystem, which causes the remount to fail. See Bug #963106 and please try my suggestion of unchecking 'Available to all users' in the Network Manager settings for your network connection. In any case the message that we should get while shutting down should be umount / is busy, why is it mount? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. Status in “plymouth” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Invalid Bug description: I arrived here from bug 963106 [https://bugs.launchpad.net/bugs/963106]. I thought that it was a problem with network-manager, but it was not. I was suggested that it is probably a problem with upstart : "that modemmanager simply hasn't had time to complete the shutdown process before umountroot is run. Since modemmanager is an upstart job, sendsigs doesn't kill it." lsb_release -rd: Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy upstart: upstart: Installed: 1.5-0ubuntu7 Candidate: 1.5-0ubuntu7 Version table: *** 1.5-0ubuntu7 0 500 http://kambing.ui.ac.id/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.5-0ubuntu5 0 500 http://kambing.ui.ac.id/ubuntu/ precise/main amd64 Packages Hope this will be fixed. Thanks. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: upstart 1.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sat Jun 30 00:08:18 2012 InstallationMedia: Custom Live CD - Release amd64 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
You might try unchecking 'Available to all users' in the Network Manger settings for your network connection. That works around the problem for me on Linux Mint 14. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086693] Re: DNS lookup fails intermittently with Comcast, when Network Manager's copy of dnsmasq is in use.
** Attachment added: "NetworkManager" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1086693/+attachment/3451985/+files/NetworkManager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086693 Title: DNS lookup fails intermittently with Comcast, when Network Manager's copy of dnsmasq is in use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1086693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086693] [NEW] DNS lookup fails intermittently with Comcast, when Network Manager's copy of dnsmasq is in use.
Public bug reported: In Ubuntu's default configuration, Network Manager spawns a copy of dnsmasq, which breaks DNS lookups for me. It has done this since Ubuntu 12.04, when this was made the default. I've just been following the workaround that has worked for other people of disabling dnsmasq in /etc/NetworkManager/NetworkManager.conf. There have been multiple bug reports about the various problems of this configuration, but it remains the default configuration in 12.10, and breaks my DNS lookups there, as well. Someone mentioned I should file a bug. So, why not? It'll just be ignored like they always are, but fine. You got it! ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: comcast dnsmasq network-manager ** Attachment added: "resolv.conf" https://bugs.launchpad.net/bugs/1086693/+attachment/3451984/+files/resolv.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086693 Title: DNS lookup fails intermittently with Comcast, when Network Manager's copy of dnsmasq is in use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1086693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
You didn't answer my question in #42 above. Type "man null" to learn how /dev/null works. The ps command produced an error message. Assuming that it wasn't mis-typed, that means that the modem-manager process wasn't running, which is the correct result. That's also consistent with last line in the modemmanager.log that you attached. I suspect that your problem could be that modemmanager simply hasn't had time to complete the shutdown process before umountroot is run. Since modemmanager is an upstart job, sendsigs doesn't kill it. I've seen no evidence that your problem is a network-manager bug. If I were you, I would open a new bug report using ubuntu-bug, probably against upstart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
Tuhu, if you type the following three commands into a terminal window what is printed after each command? sudo stop network-manager initctl status modemmanager ps p $(pgrep modem-manager) 2>/dev/null The third command should print something only if modem-manager is still running. It shouldn't be, but your /DEBUG file showed that it was and that's part of the problem. You'll want to restart network-manager by typing: sudo start network-manager What network devices are active on your computer whenever the problem occurs? Any mobile broadband devices at all? Have you looked at the log file /var/log/upstart/modemmanager.log to see if there are any error messages or warnings there? Bug #974187 reports modem-manager taking a very long time to shut down. That bug is unresolved and due to expire soon due to lack of activity. You might want to subscribe to that bug and add a "me too". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
The /DEBUG file shows that modem-manager is still running, and at line 114 you can see that the init process has /var/log/upstart/modemmanager open for write. That explains the "mount: / is busy" message. I would think that modem-manager should have exited before umountroot is run. Looking at /etc/init.d/sendsigs, it appears that processes associated with upstart jobs (like modemmanager) aren't killed, and I see no facility there for waiting on them to exit. I'm not an ubuntu developer, but if you care to try an experiment, you could try adding a sync command to line 64 of /etc/init.d/sendsigs . This is just before a comment that starts 'Upstart jobs have their own' and a sequence of code that collects the pids of upstart jobs into a list of pids to ignore (i.e. pids not to kill). If modem-manager or init are waiting on i/o to complete, a sync here might give modem-manager time to exit before it gets put into the OMITPIDS list. If you decide to change sendsigs, be sure to make a backup copy first: sudo cp -p /etc/init.d/sendsigs ~ Other than that, I don't have any new ideas. Let's hope that Mathieu or another one of the powers-that-be will now jump in with some suggestions as to how to proceed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
Tuhu, no, I wasn't asking that you run the commands from tty1. Now that you've added the ps and lsof commands to the umountroot script, it should create the text file '/DEBUG' when the system is shut down. Please attach the file /DEBUG. The error message "mount: / is busy" is being printed by the mount command in the umountroot script. The /DEBUG file should show us what files were still open just before that mount command is executed. It's likely that a process still has a file open for write. Also, have you ever installed VMware Player (see previous messages in this bug report) or any non-ubuntu software which may have altered the order in which your init scripts are run? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
Tuhu, your ps output shows quite a lot still running. Did you execute the command from a terminal in the desktop environment? To be helpful, the ps and lsof commands should be run from the /etc/init.d/umountroot script. See message #5 above. Before adding debug commands to umountroot, you might want to try un-checking "Available to all users" for your active network connection. If the "mount: / is busy" message is no longer present when you shut the system down, then your problem might be related to this bug. Either way, you'll probably want to proceed with getting some debug print from umountroot. There was a typo in message #5, although I'm not sure that it makes a difference in practice. The lsof command should read: /usr/bin/lsof >> /DEBUG Be sure to make a backup copy of umountroot before editing it: sudo cp -p /etc/init.d/umountroot ~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989900] Re: DNS Resolve Problems in Ubuntu 12.04
Having Network Manager set to use dnsmasq doesn't get along very well with Comcast, using the suggestion of commenting out the dnsmasq line from /etc/NetworkManager/NetworkManager.conf and restarting the network- manager service fixed the problem for me. As usual, the rolling list of crap I have to edit by hand to work around Ubuntu's bugs that they can't or won't fix or claim is not a bug continues to grow. Changing the problem to "Incomplete" instead of attempting to figure out what got you to the point where you have broken internet access for millions of Comcast users and hoping the problem fades off into the sunset with not another word spoken about it exemplifies everything I've come to expect from Ubuntu developers. How about reverting it to the way it was in 11.10, which wasn't broken, and letting the few users who actually NEED dnsmasq turn it on themselves. Radical concept? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989900 Title: DNS Resolve Problems in Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/989900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963106] Re: NetworkManager causes orphaned inodes
Oops, I sent my previous message before I saw yours saying you've fixed things. Congratulations, and thanks for sharing the method - I'll have to remember that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
The perl script /usr/share/sysv-rc/saveconfig prints out the current configuration as a series of update-rc.d commands. If you like, I can send you a copy from a more-or-less vanilla 12.04 install. It can't be completely vanilla without my doing a fresh install in a VM, and I won't volunteer for that (I'm running non-pae hardware, and they've made 12.04 installs *very* aggravating). After logging in to launchpad, you should be able to find my email address. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
Daniel, try: $ sudo update-rc.d -f umountroot remove $ sudo update-rc.d umountroot start 60 0 6 . Note the period at the end of the 2nd command. And yes, my previous suggestion of using mv won't work, you have to use update-rc.d, sorry. When I used update-rc.d to put umountroot at 03 as you have, I see the same symptoms you do. Using the above commands to put it back to 60 fixes the problem. Hope this helps, please let us know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
Daniel, I notice "/etc/rc6.d/S03umountroot stop" in your ps output. On my 12.04 installs I have S60umountroot in /etc/rc0.d and /etc/rc6.d. S03 sounds awfully early to me. Try "sudo mv /etc/rc6.d/S03umountroot /etc/rc6.d/S60umountroot" and then do "sudo shutdown -H now" and see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
After installing network-manager 0.9.4.0-0ubuntu4 from precise-proposed, things are looking good. The root filesystem is clean on reboot even after a reinstall of libc6. Many thanks to Mathieu! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
Yes, yes, I understand all of that, there is no need to continue repeating it. Your motivations don't change the fact that, in trying to fix one problem, you've created another. Your changes are causing umountroot to FAIL at shutdown time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 963106] Re: NetworkManager causes orphaned inodes
The underlying problem is that, at system shutdown time, dhclient isn't given the opportunity to gracefully exit, closing any files it has open. This causes /etc/init.d/umountroot to fail. When umountroot fails, the filesystem must be recovered. There is, to the best of my knowledge, nothing particularly unusual with the various installs of 12.04 that I've been testing, and the problem is evident with all of them. One difference might be that I have the splash screen turned off in grub and so can see the messages. Maybe that explains why you're not seeing them. At some point, possibly in oneiric, changes were made which put the dhclient pid in /var/run/sendsigs.omit.d/ and I believe that's the basis of the problem. And it IS a problem - the root filesystem should not need recovery on every reboot. The "orphaned inodes" messages are just icing on the cake. Do "sudo apt-get install --reinstall libc6" then reboot, and run "dmesg | grep EXT" and you should see the messages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963106] Re: NetworkManager causes orphaned inodes
One last data point: I'm seeing the problem only with wired connections when "Available to all users" has been checked for that connection (right-click on the nm-applet icon, select "Edit Connections...", select the connection and click "Edit..." then check/uncheck "Available to all users" in the lower left). To /etc/init.d/umountroot, just before the 'mount -n -o remount,ro /' sequence, I added: /bin/ps > /DEBUG /usr/bin/lsof >> DEBUG /DEBUG shows that when (and only when) "Available to all users" has been selected for a wired connection, when umountroot runs dhclient is still running and has a dhcp lease file open for write; consequently umountroot fails. I'm attaching a copy of this DEBUG file. For wired connections with "Available to all users" unchecked, and for wireless connections, dhclient has gone away by the time umountroot runs and so there is no problem in those cases. ** Attachment added: "DEBUG" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+attachment/3018629/+files/DEBUG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963106] Re: NetworkManager causes orphaned inodes
Clint, I don't see the dhclient process die when network-manager is stopped. But I think I was guilty of some fuzzy thinking in saying that the problem is due to the pid file being held open; the problem is that the dhclient pid file isn't deleted from /var/run/sendsigs.omit.d (so /etc/init.d/sendsigs doesn't kill dhclient at shutdown time) *and* dhclient has a dhcp lease file open for write. The following should (I hope) show what I'm talking about: $ ps auxw | grep NetworkManager | grep -v grep # NetworkManager and dhclient are both running $ ls /var/run/sendsigs.omit.d # there are pid files for both dhclient and dnsmasq $ sudo stop network-manager $ ps auxw | grep NetworkManager | grep -v grep # now only dhclient is still running $ ls /var/run/sendsigs.omit.d # and the dhclient pid file is still there $ sudo lsof -c dhclient | grep lease # dhclient still has a lease file open for write Because sendsigs won't kill dhclient and the lease file is open for write, /etc/init.d/umountroot fails and the filesystem must be recovered. And dhclient still has libc .so files open as well, which is what leads to orphaned inodes if those files have been overwritten during a libc upgrade. If the dhclient pid file was removed from /var/run/sendsigs.omit.d when network-manager is stopped, then sendsigs would kill dhclient at shutdown. Or, if dhclient could be terminated when network-manager shuts down, that should work too. I don't understand enough to guess why the pid files are written to sendsigs.omit.d in the first place... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952315] Re: root filesystem not cleanly unmounted on reboot
I've submitted Bug #963106 against network-manager for this problem. This bug should probably be closed as invalid since it misidentifies the cause as upstart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952315 Title: root filesystem not cleanly unmounted on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/952315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963106] Re: NetworkManager causes orphaned inodes
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963106] [NEW] NetworkManager causes orphaned inodes
Public bug reported: During system shutdown, NetworkManager neither kills dhclient nor does it remove the dhclient pid file from the directory /var/run/sendsigs.omit.d. As a result, dhclient continues to hold the pid file open for write and when /etc/init.d/umountroot tries to remount the root filesystem read-only, the remount fails. The message: mount: / is busy is seen in the console, and the filesystem must be recovered at boot time: [8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem [8.947057] EXT4-fs (sda1): write access will be enabled during recovery [ 11.234075] EXT4-fs (sda1): recovery complete If shared libraries used by dhclient are updated before the reboot, orphaned inodes associated with the .so files are created. For example, doing "sudo apt-get install --reinstall libc6" and then rebooting leads to: [8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem [8.356521] EXT4-fs (sda1): write access will be enabled during recovery [8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs [8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 313749 [8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 313733 [8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 313725 [8.724544] EXT4-fs (sda1): 3 orphan inodes deleted [8.728544] EXT4-fs (sda1): recovery complete This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 running under 12.04. I don't believe any actual data loss will occur as a result of this bug, but it's likely to produce much user anxiety. Also see Bug 952315, which misidentifies the cause of the problems as upstart. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Mar 23 07:42:20 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952315] Re: root filesystem not cleanly unmounted on reboot
I think I understand what's going on now. In looking over /saved.root.lsof more carefully, I see that the DEL libc .so files are also associated with dhclient. And I was just lucky before that dhclient stayed dead long enough for the reboot. It gets respawned, I believe by NetworkManager. It looks like dhclient is started by NetworkManager with a -pf arg that makes dhclient write his (dhclient's) pid into a file in the directory /var/run/sendsigs.omit.d/. When the system is being brought down, /etc/init.d/sendsigs collects that pid into an "ignore" list, thus declining to kill dhclient. The result is that dhclient has files held open when the system goes down, leading to the "mount: / is busy" console message, and also to orphaned inodes if libc happened to have been updated. I removed network-manager* and installed wicd-gtk and dependencies. Now I can reinstall libc6 and reboot with *no* busy message and *no* orphaned inodes. So, IMHO the blame lies with NetworkManager and not with upstart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952315 Title: root filesystem not cleanly unmounted on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/952315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952315] Re: root filesystem not cleanly unmounted on reboot
Looks to me like there are two separate problems. The first may be a regression of Bug #672177 for which a fix was supposedly released ca April 2011. Upgrading or re-installing libc6 results in orphaned inodes: $ sudo apt-get install --reinstall libc6 && sudo shudown -r now I put '/usr/sbin/lsof -n > /saved.root.lsof' in /etc/init.d/umountroot just before the root filesystem is remounted read-only. The result shows open files of type 'DEL' for several libc .so files. These are probably the files assocated with the orphaned inodes. fsck must be smart enough to know that the files were deleted so it doesn't put anything into /lost+found. The second problem is the "mount: / is busy" console message on every reboot. The /saved.root.lsof file shows that dhclient is still holding a dhcp lease file open for write when umountroot is invoked. Doing 'sudo killall dhclient' before the reboot eliminates the message. I couldn't find an already opened bug report for this; if someone else could have a try I'd appreciate it. Both of these problems are probably benign, but before I trust my data to 12.04, I'd certainly like to hear someone smarter than me say so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952315 Title: root filesystem not cleanly unmounted on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/952315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 958279] [NEW] FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep.
Public bug reported: I have filed a bug report in AMD's bugzilla about this. I would also like to file one here to track that one. --- For quite a while now, I've just turned DPMS off to keep anything from putting the monitor to sleep to work around this problem. When DPMS support is on (which is the default setting), and something attempts to put the display to sleep (in this case, KDE's desktop power management daemon, but I've had this problem with XFCE and GNOME, and under Ubuntu's Unity desktop as well), the monitor cannot come back on when the user returns and moves the mouse or presses a button on the keyboard. The rest of the system is apparently still functional as I've left music playing before, and then when I've returned, the display is asleep and not responding to my attempts to wake it up, but the music is still playing. Steps to reproduce: 1. I am assuming that for the purposes of reproducing this bug that the following is true, even though I've seen it on various distributions and several versions of Catalyst. You are using Ubuntu 11.10 or 12.04 development branch. You are using Catalyst 12.2 with FGLRX 8.95. You are using a RadeonHD 5670. You are using the Unity or KDE desktop environment. (Either one should provoke this problem.) 2. Wait for the display to be turned off/go into sleep mode. NOT dimmed! If you catch it while it is dimmed, but before it is turned off, you will end up back at your desktop. 3. After the display is off/asleep, attempt to move your mouse or press a button on the keyboard. Observe that the system is NOT responding and the monitor is stuck in sleep mode. Actual result: The display fails to resume, anything you left open is trashed, game over man, game over! :) Expected result: The display mode should be resumed properly in the state that it was previously in. The open source radeon driver always manages to do this right. Workaround: Generate a xorg.conf file with this command: sudo amdconfig --initial Open the xorg.conf file: sudo nano /etc/X11/xorg.conf Find this line: (under Section "Monitor") Option "DPMS" "true" change it to read Option "DPMS" "false" Restart the X server. Observe that your desktop is no longer able to put the display to sleep and that AMD's proprietary display driver is contributing to increased global warming and a higher electric bill. (But doesn't screw up the X server and cause all of user's open files to be lost) ** Affects: fglrx Importance: Unknown Status: Unknown ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: dpms fglrx sleep suspend ** Bug watch added: ATi Linux Platform Bugs #463 http://ati.cchtml.com/show_bug.cgi?id=463 ** Also affects: fglrx via http://ati.cchtml.com/show_bug.cgi?id=463 Importance: Unknown Status: Unknown ** Tags added: dpms fglrx sleep suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/958279 Title: FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/958279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 445863] Re: Spell checking doesn't allow US English words when using "English" language
Still a problem in Ubuntu 12.04. VERY annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/445863 Title: Spell checking doesn't allow US English words when using "English" language To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/445863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952315] [NEW] root filesystem not cleanly unmounted on reboot
Public bug reported: 12.04 beta, updated as of 11March2012. The message "mount: / busy" is seen as the system is shut down. During the reboot, messages from fsck regarding recovery of orphaned inodes are seen in the console. These messages appear in kern.log: steve@precise:~$ grep -i orphan /var/log/kern.log Mar 11 09:29:00 precise kernel: [ 12.398913] EXT4-fs (sda1): orphan cleanup on readonly fs Mar 11 09:29:00 precise kernel: [ 12.399492] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 141316 Mar 11 09:29:00 precise kernel: [ 12.409021] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 267343 Mar 11 09:29:00 precise kernel: [ 12.409450] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 267325 Mar 11 09:29:00 precise kernel: [ 12.410062] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 267319 Mar 11 09:29:00 precise kernel: [ 12.410111] EXT4-fs (sda1): 4 orphan inodes deleted ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: upstart 1.4-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Sun Mar 11 09:23:29 2012 ExecutablePath: /sbin/init InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: upstart UpgradeStatus: Upgraded to precise on 2012-03-02 (8 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952315 Title: root filesystem not cleanly unmounted on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/952315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952315] Re: root filesystem not cleanly unmounted on reboot
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952315 Title: root filesystem not cleanly unmounted on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/952315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950353] Re: package gconf2 3.2.4-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 250
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950353 Title: package gconf2 3.2.4-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/950353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950353] [NEW] package gconf2 3.2.4-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 250
Public bug reported: upgrading from 11.10 to 12.04 and gconf2 3.2.4-0ubuntu1 did not install ProblemType: Package DistroRelease: Ubuntu 12.04 Package: gconf2 3.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 1.94.1-0ubuntu1 Architecture: i386 Date: Thu Mar 8 15:11:48 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 250 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: gconf Title: package gconf2 3.2.4-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 250 UpgradeStatus: Upgraded to precise on 2012-03-08 (0 days ago) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950353 Title: package gconf2 3.2.4-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/950353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 391044] Re: Fresh karmic install does not boot due to grub2 adding --no-floppy to "search " lines
> Is this bug present in Ubuntu 11.10? Sorry, I don't know about 11.10, but the bug is not present in 11.04 with grub 1.99-rc1-13ubuntu1 so I would expect 11.10 to be ok as well. Steve -- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/391044 Title: Fresh karmic install does not boot due to grub2 adding --no-floppy to "search " lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/391044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930432] Re: package linux-image-2.6.38-13-generic 2.6.38-13.54 failed to install/upgrade: unable to securely remove '/boot/vmlinuz-2.6.38-13-generic.dpkg-tmp': Read-only file system
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930432 Title: package linux-image-2.6.38-13-generic 2.6.38-13.54 failed to install/upgrade: unable to securely remove '/boot/vmlinuz-2.6.38-13-generic.dpkg-tmp': Read-only file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930432] [NEW] package linux-image-2.6.38-13-generic 2.6.38-13.54 failed to install/upgrade: unable to securely remove '/boot/vmlinuz-2.6.38-13-generic.dpkg-tmp': Read-only file system
Public bug reported: Update manager install of linux-image-2.6.38-13-generic failed. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-13-generic 2.6.38-13.54 ProcVersionSignature: Ubuntu 2.6.38-13.54-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 1693 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 5' Mixer name : 'SigmaTel STAC9750,51' Components : 'AC97a:83847650' Controls : 38 Simple ctrls : 24 Date: Fri Feb 10 14:54:30 2012 DpkgTerminalLog: Preparing to replace linux-image-2.6.38-13-generic 2.6.38-13.54 (using .../linux-image-2.6.38-13-generic_2.6.38-13.55_i386.deb) ... Done. Unpacking replacement linux-image-2.6.38-13-generic ... dpkg: error processing /var/cache/apt/archives/linux-image-2.6.38-13-generic_2.6.38-13.55_i386.deb (--unpack): unable to securely remove '/boot/vmlinuz-2.6.38-13-generic.dpkg-tmp': Read-only file system ErrorMessage: unable to securely remove '/boot/vmlinuz-2.6.38-13-generic.dpkg-tmp': Read-only file system HibernationDevice: RESUME=UUID=8b6118a8-6a85-41b3-aceb-bf6e0e9e5681 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Dell Computer Corporation Inspiron 600m PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-13-generic root=UUID=0f95d6ef-2715-4bd1-9c86-af657b62dc99 ro RelatedPackageVersions: linux-restricted-modules-2.6.38-13-generic N/A linux-backports-modules-2.6.38-13-generic N/A linux-firmware 1.52 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-2.6.38-13-generic 2.6.38-13.54 failed to install/upgrade: unable to securely remove '/boot/vmlinuz-2.6.38-13-generic.dpkg-tmp': Read-only file system UpgradeStatus: Upgraded to natty on 2012-01-27 (14 days ago) dmi.bios.date: 01/18/2005 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A16 dmi.board.name: 0Y8643 dmi.board.vendor: Dell Computer Corporation dmi.chassis.type: 8 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA16:bd01/18/2005:svnDellComputerCorporation:pnInspiron600m:pvr:rvnDellComputerCorporation:rn0Y8643:rvr:cvnDellComputerCorporation:ct8:cvr: dmi.product.name: Inspiron 600m dmi.sys.vendor: Dell Computer Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930432 Title: package linux-image-2.6.38-13-generic 2.6.38-13.54 failed to install/upgrade: unable to securely remove '/boot/vmlinuz-2.6.38-13-generic.dpkg-tmp': Read-only file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930432] Re: package linux-image-2.6.38-13-generic 2.6.38-13.54 failed to install/upgrade: unable to securely remove '/boot/vmlinuz-2.6.38-13-generic.dpkg-tmp': Read-only file system
Please close this bug. It wouldn't have been reported if update-manager had indicated the reason for the installation failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930432 Title: package linux-image-2.6.38-13-generic 2.6.38-13.54 failed to install/upgrade: unable to securely remove '/boot/vmlinuz-2.6.38-13-generic.dpkg-tmp': Read-only file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921974] Re: userconfig kcm module no longer works on Kubuntu 12.04 development branch
Fixed with today's python-kde4 update. ** Changed in: userconfig (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921974 Title: userconfig kcm module no longer works on Kubuntu 12.04 development branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/userconfig/+bug/921974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 827120] Re: FGLRX package does not disable radeon modesetting and prevents X from starting.
This has been fixed for a while. Closing. ** Changed in: fglrx-installer (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827120 Title: FGLRX package does not disable radeon modesetting and prevents X from starting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/827120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921974] [NEW] userconfig kcm module no longer works on Kubuntu 12.04 development branch
Public bug reported: Starting the userconfig applet from the KDE Control Center brings up the kdesudo prompt but entering a password causes the prompt to go away and the applet never starts. Apport is currently crashing itself whenever it reports a bug, so I'm just going to have to report this without any useful information from that. Steps to reproduce: Open System Settings Click on User Management under System Administration. Enter your sudo password. Nothing happens. Running kdesudo kcmshell4 userconfig causes the following output on the terminal. (DrKonqi never comes up) ryan@ryan-MS-7501:~$ kdesudo /usr/bin/kcmshell4 userconfig X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x1c00020 KCrash: Application 'kcmshell4' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit ** Affects: userconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 kcm kcmshell kcmshell4 kde kubuntu userconfig -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921974 Title: userconfig kcm module no longer works on Kubuntu 12.04 development branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/userconfig/+bug/921974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921443] [NEW] KDE Firefox Support / "kmozillahelper" is busted....AGAIN...Brings up GTK file dialogs.
Public bug reported: KDE Firefox Support (aka kmozillahelper) is an ld preload hack for Firefox that forces it to use KDE file dialogs. It has a predisposition to breaking every time there's a new Kubuntu development branch. GTK+ file dialogs make me cry. (Oh no, not really. They're just an eyesore.). This time, on Kubuntu 12.04 with Firefox 10 beta, having this installed does absolutely nothing and brings up GTK+ file dialogs instead. Bringing up the KDE Task Manager shows kmozillahelper is loaded and running, so it's taking up resources and not doing anything if the user installed it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: kmozillahelper (not installed) ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1 Uname: Linux 3.2.0-10-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Wed Jan 25 03:12:43 2012 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120124) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kmozillahelper UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kmozillahelper (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug firefox kde kmozillahelper mozilla precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921443 Title: KDE Firefox Support / "kmozillahelper" is bustedAGAIN...Brings up GTK file dialogs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmozillahelper/+bug/921443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921437] Re: KDM does not properly reset the X server. It must be set to terminate it, or the display will hang when the user logs out.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921437 Title: KDM does not properly reset the X server. It must be set to terminate it, or the display will hang when the user logs out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/921437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921437] [NEW] KDM does not properly reset the X server. It must be set to terminate it, or the display will hang when the user logs out.
Public bug reported: I've had a problem with KDM not properly resetting the X server on log out for the last few releases of Kubuntu. The problem still exists in the 12.04 development branch. On log out, the server does not reset itself and the display goes black or gray except for a mouse cursor. Opening /etc/kde4/kdm/kdmrc and uncommenting the line #TerminateServer=true to TerminateServer=true fixes the problem. The next time I log into KDE, the setting takes effect, and logging out works properly. On log out, the X server is terminated and a new instance is started and I am presented with the KDM log in screen. I have noticed several other distributions that have apparently given up and changed the KDM setting to have the X server terminate itself instead of attempting to reset. I can only guess that others have had the same problem and that resetting the server is far from guaranteed to work. Someone on the #kubuntu channel on Freenode suggested that it might be a video driver issue. I only use RadeonHD cards, and I only use the free/open drivers most of the time. I have checked and the behavior occurs with FGLRX as well. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: kdm 4:4.7.97-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1 Uname: Linux 3.2.0-10-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Wed Jan 25 02:49:25 2012 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120124) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kde-workspace UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.kde4.kdm.kdmrc: 2012-01-24T21:52:28.927927 ** Affects: kde-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kde kdm kubuntu precise x.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921437 Title: KDM does not properly reset the X server. It must be set to terminate it, or the display will hang when the user logs out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/921437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887432] [NEW] Kopete tray icon freezes on subsequent incoming messages
Public bug reported: This has been going on since Natty and it's continuing into Oneiric. It is not a KDE bug since it works fine in other distributions. When using the indicator widget, the envelope only tuns green for the first incoming message then it doesn't for following incoming messages, eventually the indicator thing just screws up and won't allow restoring Kopete anymore, necessitating a killall kopete. IF you get sick of that and disable the indicator widget and go back to using a tray icon, then the tray icon animation works for the first incoming message, but on following incoming messages, it displays the frame for the incoming message animation it last displayed when you clicked on it to get the first message. It does not animate. This might be multiple issues. I noticed that indicator widget is pretty badly broken in Oneiric anyway. I posted a bug about it not working with Konversation anymore, which got no replies. :) ** Affects: kdenetwork (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/887432 Title: Kopete tray icon freezes on subsequent incoming messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/887432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 885836] Re: firefox-kde-support breaks right click > save image as...
Everytime this gets fixed it seems to come back again later. I reported it the last time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/885836 Title: firefox-kde-support breaks right click > save image as... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/885836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 852869] Re: Konversation does not appear in the indicator widget
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/852869 Title: Konversation does not appear in the indicator widget To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konversation/+bug/852869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 852869] [NEW] Konversation does not appear in the indicator widget
Public bug reported: As of "recently"? Konversation has not been appearing in the indicator widget. Additionally, the entry for message indicator is gone from the settings menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: konversation 1.3.1-2ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Sat Sep 17 18:13:50 2011 InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110916) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: konversation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: konversation (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/852869 Title: Konversation does not appear in the indicator widget To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konversation/+bug/852869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850902] [NEW] qapt does not install local packages
Public bug reported: qapt deb install does not install local deb packages, when you click the install button, it sits there doing nothing ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: qapt-deb-installer 1.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Thu Sep 15 09:17:07 2011 InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110915) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qapt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qapt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850902 Title: qapt does not install local packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qapt/+bug/850902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850902] Re: qapt does not install local packages
-- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qapt in Ubuntu. https://bugs.launchpad.net/bugs/850902 Title: qapt does not install local packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qapt/+bug/850902/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 845446] [NEW] Please package Soundconverter 1.54
Public bug reported: The version of Soundconverter in Ubuntu is very old (1.4.4). The current version is 1.5.4 (http://soundconverter.berlios.de/) Looking at the Debian package, it looks like it too hasn't been updated in some time. I'm not sure why this package has been abandoned, but I feel that I should probably post a bug regarding this. ** Affects: soundconverter (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/845446 Title: Please package Soundconverter 1.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/soundconverter/+bug/845446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824842] Re: Click on 'More Apps' et al closes the dash
** Tags added: unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824842 Title: Click on 'More Apps' et al closes the dash To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/824842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775903] Re: Crash when trying to mount NCP volumes.
After upgrading to 11.04 began having this problem. After a segfault, any further attempted operations on the mounted volume hang. Reboot is required to remove the stuck process. Debugging Information Follows: Aug 16 15:26:20 little-sister kernel: [ 4237.115189] [ cut here ] Aug 16 15:26:20 little-sister kernel: [ 4237.115754] kernel BUG at /build/buildd/linux-2.6.38/fs/dcache.c:2134! Aug 16 15:26:20 little-sister kernel: [ 4237.116253] invalid opcode: [#2] SMP Aug 16 15:26:20 little-sister kernel: [ 4237.116726] last sysfs file: /sys/devices/virtual/bdi/ncpfs-3/uevent Aug 16 15:26:20 little-sister kernel: [ 4237.117205] CPU 0 Aug 16 15:26:20 little-sister kernel: [ 4237.117214] Modules linked in: nls_utf8 ncpfs ipx p8023 quota_v2 quota_tree nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc nouveau ttm drm_kms_helper drm ppdev edac_core i2c_nforce2 parport_pc edac_mce_amd i2c_algo_bit lp k8temp video parport raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov floppy 8139too 8139cp sata_nv raid6_pq async_tx pata_amd raid1 forcedeth raid0 multipath linear Aug 16 15:26:20 little-sister kernel: [ 4237.119769] Aug 16 15:26:20 little-sister kernel: [ 4237.120243] Pid: 4110, comm: ls Tainted: G D 2.6.38-10-server #46-Ubuntu FOXCONN MCP61M05/M61PMV Aug 16 15:26:20 little-sister kernel: [ 4237.120757] RIP: 0010:[] [] dentry_update_name_case+0x75/0x80 Aug 16 15:26:20 little-sister kernel: [ 4237.121304] RSP: 0018:880042e39988 EFLAGS: 00010246 Aug 16 15:26:20 little-sister kernel: [ 4237.121895] RAX: 0001 RBX: 880042e39e58 RCX: 880053f9da80 Aug 16 15:26:20 little-sister kernel: [ 4237.122488] RDX: RSI: 880042e39a98 RDI: 880053f9da80 Aug 16 15:26:20 little-sister kernel: [ 4237.123080] RBP: 880042e399a8 R08: 0056 R09: 880053f9dac3 Aug 16 15:26:20 little-sister kernel: [ 4237.123671] R10: a0374000 R11: 880042e39aa8 R12: 880053f9da80 Aug 16 15:26:20 little-sister kernel: [ 4237.124256] R13: 880042e39a98 R14: R15: 880042e39c58 Aug 16 15:26:20 little-sister kernel: [ 4237.124846] FS: 7fc54e2957c0() GS:880077c0() knlGS: Aug 16 15:26:20 little-sister kernel: [ 4237.125140] CS: 0010 DS: ES: CR0: 8005003b Aug 16 15:26:20 little-sister kernel: [ 4237.125140] CR2: 01f49278 CR3: 729f3000 CR4: 06f0 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] DR0: DR1: DR2: Aug 16 15:26:20 little-sister kernel: [ 4237.125140] DR3: DR6: 0ff0 DR7: 0400 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] Process ls (pid: 4110, threadinfo 880042e38000, task 880037135b80) Aug 16 15:26:20 little-sister kernel: [ 4237.125140] Stack: Aug 16 15:26:20 little-sister kernel: [ 4237.125140] 88006d495cc0 880042e39e58 88006d495cc0 88005cde4048 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] 880042e39be8 a037a0bd 880042e39a18 8100a777 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] 880053f9da80 81176c50 880042e39f38 880037aa7280 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] Call Trace: Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ncp_fill_cache.clone.15+0x22d/0x660 [ncpfs] Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? __switch_to+0x157/0x2f0 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? filldir+0x0/0xd0 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? autoremove_wake_function+0x0/0x40 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? map_vm_area+0x32/0x50 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? default_spin_lock_flags+0x9/0x10 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? ncp_do_request+0x15e/0x180 [ncpfs] Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? ncp_request2+0x52/0x90 [ncpfs] Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? ncp_unlock_server+0x29/0x40 [ncpfs] Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? ncp_search_for_fileset+0x1f8/0x260 [ncpfs] Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? filldir+0x0/0xd0 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? filldir+0x0/0xd0 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ncp_do_readdir+0x198/0x1e0 [ncpfs] Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? page_add_new_anon_rmap+0x8d/0xa0 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? do_anonymous_page.clone.41+0x117/0x310 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? radix_tree_lookup_slot+0xe/0x10 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? find_get_page+0x1e/0x90 Aug 16 15:26:20 little-sister kernel: [ 4237.125140] [] ? find_lock_page+0x26/0x80 Aug 16 15:26:20 l
[Bug 827120] Re: FGLRX package does not disable radeon modesetting and prevents X from starting.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827120 Title: FGLRX package does not disable radeon modesetting and prevents X from starting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/827120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 827120] [NEW] FGLRX package does not disable radeon modesetting and prevents X from starting.
Public bug reported: AMD's proprietary Catalyst driver "FGLRX" uses the X server to set the video mode. This behavior is incompatible with the open source radeon kernel module with attempts to set the video mode using the kernel. If a user installs Catalyst/FGLRX and kernel mode setting is not disabled for Radeon with radeon.modeset=0 on the kernel line in GRUB, then eventually the entire system will stop booting at the point where X should be loading, and the monitor will suspend itself since nothing is sending it a video signal. At this time, the system also stops responding to the keyboard so ctrl-alt-del or other key combinations to restart the system have no effect. Since *buntu defaults to no GRUB countdown, it is very difficult to catch it in order to change the kernel boot line to allow it to boot up to where the user can change GRUB's settings. However, the user should not ever reach this point because the FGLRX package should set radeon.modeset=0 for them. This does not appear to be happening as of now in *buntu Oneiric. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: fglrx 2:8.872-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Tue Aug 16 01:15:26 2011 InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fglrx-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827120 Title: FGLRX package does not disable radeon modesetting and prevents X from starting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/827120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 815221] Re: : Value 1594066944 out of range for Int32
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/815221 Title: : Value 1594066944 out of range for Int32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/815221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 815221] [NEW] : Value 1594066944 out of range for Int32
Public bug reported:
Crashes on trying to uninstall synergy
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: aptdaemon 0.41+bzr646-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
NonfreeKernelModules: fglrx
Annotation: Removing software failed
Architecture: amd64
Date: Sat Jul 23 16:56:40 2011
DesktopFile: /usr/share/aptdaemon/aptdaemon.desktop
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
PackageArchitecture: all
SourcePackage: aptdaemon
Title: : Value 1594066944 out of range for
Int32
TransactionDepends: [[], [], ['quicksynergy=0.9-1'], [], [], [], []]
TransactionErrorCode: error-unknown
TransactionKwargs: {}
TransactionLocale: en_US.UTF8
TransactionOutput:
TransactionPackages: [[], [], [dbus.String(u'synergy')], [], [], []]
TransactionRole: role-remove-packages
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: aptdaemon (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-crash natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/815221
Title:
: Value 1594066944 out of range for
Int32
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/815221/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 448041] attaching jpeg to email results in 100% cpu utilization
I have not experienced the problem in Ubuntu 10.10 in quite some time. Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance. ** Changed in: evolution (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/448041 Title: attaching jpeg to email results in 100% cpu utilization Status in “evolution” package in Ubuntu: Incomplete Bug description: Binary package hint: evolution When composing a new email, attaching a 1.2 megabyte jpeg results in 100% cpu utilization by evolution. When evolution is launched from the desktop, it is necessary to power cycle the computer to regain control. Setting soft limits and starting evolution from a terminal allows attaching to the process with gdb, which shows the process to variously be in a cairo or murrine routine. The problem may be associated with rendering the image thumbnail or progress bar in the attachment area of the email. ProblemType: Bug Architecture: i386 Date: Sat Oct 10 07:57:01 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/evolution Package: evolution 2.28.0-0ubuntu4 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/usr/bin/tcsh ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: evolution Uname: Linux 2.6.31-13-generic i686 To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/448041/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/448041 Title: attaching jpeg to email results in 100% cpu utilization -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773979] Re: legacy applications (using system tray) do not work in unity without a porting effort
"Those icons don't behave in a consistant way and are an issue for the user experience." Sebastian, This is exactly the reason Indicators are a solution looking for a problem. Most operating systems have had system trays for years. These system trays all work pretty much like the one in GNOME 2 (which Unity is still using, only with this insane "whitelisting" approach". The removal of this system tray functionality actually ruins the user experience. When you close Xchat, it disappears because it has nowhere to go to. It thinks it is running in the system tray but Ubuntu has hidden it, it it is still open and the user can't shut it down without kill -9. The "indicator" applet for XChat is broken and fails to behave as a replacement for the system tray icon. The user will just click it presuming the first instance is still running and it will open a second Xchat. The problem is there with Banshee too. Once you open it there seems to be no way to close it. It refuses to close, it stays running in the "sound menu" until you log out or, again, bust out kill -9. This combined with the hourly random freezes (which is a whole different issue entirely) are why I used Unity for less than a day before I snapped and went back to KDE. Unity is unusable and replacing worthwhile things like the system tray with proprietary Ubuntu replacements that do exactly the same thing, only broken, doesn't help your user experience, at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773979 Title: legacy applications (using system tray) do not work in unity without a porting effort -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740642] Re: [natty] exchange 2010 evolution-mapi - no folders or calendar, contact, tasks
OK, so after getting all mail to sync I can send/receive mail messages. however, the Global Address List/Calendar/Memo's seems very unstable. I get messages popping-up that say "evolution mapi_e_not_implemented" and then eventually it says that Evolution Memo has quit unexpectedly - your memos will not be available until evolution is restarted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740642 Title: [natty] exchange 2010 evolution-mapi - no folders or calendar, contact, tasks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740642] Re: [natty] exchange 2010 evolution-mapi - no folders or calendar, contact, tasks
I was able to download the to .deb files and install which appears to have allowed my mail to download (it's in progress). My environment is Exchange 2010 (non-SP1) in a clustered CAS configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740642 Title: [natty] exchange 2010 evolution-mapi - no folders or calendar, contact, tasks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754029] Re: Natty: System will not shut down from the GUI.
This seems to be fixed since yesterday. Marked Fix Released. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754029 Title: Natty: System will not shut down from the GUI. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 758223] [NEW] Seamonkey 2.0.13 is available, fixes security issues
Public bug reported: Binary package hint: seamonkey Seamonkey 2.0.13 is available. Ubuntu Natty is carrying 2.0.11 which has known security vulnerabilities and bugs ranging from trivial to crashing the application. Since 2.0.13 is stable and intended to address only bugs and security issues, I would like to request that it be considered for packaging in Natty, so as to avoid shipping software with these known problems. For the release notes for 2.0.12 and 2.0.13 see: http://www.seamonkey-project.org/releases/seamonkey2.0.12/ http://www.seamonkey-project.org/releases/seamonkey2.0.13/ For security issues that were fixed in these versions, see: http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html Short story: I think it's probably in bad taste to go forward with a version that contains a count of 7 Critical, 2 High, and 1 Moderate security vulnerabilities when the patched version is available and Natty is not frozen. Thank you. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: seamonkey (not installed) ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Mon Apr 11 20:07:53 2011 InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110411) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seamonkey UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seamonkey (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/758223 Title: Seamonkey 2.0.13 is available, fixes security issues -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 757052] Re: Right click / Save Image As broken in the Firefox KDE support package
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/757052 Title: Right click / Save Image As broken in the Firefox KDE support package -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 757052] [NEW] Right click / Save Image As broken in the Firefox KDE support package
Public bug reported: Binary package hint: kmozillahelper If you open an image in Firefox and right click on it and select Save Image As, then nothing happens if you have the firefox-kde-support package installed. You can still save the image by clicking File / Save Page As. This is a minor bug bug obviously incorrect behavior. The save as dialog should appear and allow the image to be saved. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox-kde-support 0.6.2-0ubuntu2 Uname: Linux 2.6.38.2-ryan1-drm1+ x86_64 Architecture: amd64 Date: Sun Apr 10 22:55:08 2011 InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110409) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kmozillahelper UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kmozillahelper (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/757052 Title: Right click / Save Image As broken in the Firefox KDE support package -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
