[Bug 497637] [NEW] bash segfaults when TERM=eterm*
Public bug reported: Binary package hint: bash If the value of the environment variable TERM starts with eterm and the EMACS env var is unset, bash will segfault. The cause is not checking that getenv() is returning NULL when EMACS is unset. To reproduce: unset EMACS; TERM=eterm bash Versions: Ubuntu 9.10 bash 4.0-5ubuntu2 See this Fedora bug report for detail and a patch: https://bugzilla.redhat.com/show_bug.cgi?id=530911 --- bash-4.0/shell.c.orig 2009-10-15 15:57:56.0 -0400 +++ bash-4.0/shell.c2009-10-15 15:58:28.0 -0400 @@ -572,7 +572,7 @@ /* running_under_emacs == 2 for `eterm' */ running_under_emacs = (emacs != 0) || (term STREQN (term, emacs, 5)); - running_under_emacs += term STREQN (term, eterm, 5) strstr (emacs, term); + running_under_emacs += term STREQN (term, eterm, 5) (emacs != 0) strstr (emacs, term); if (running_under_emacs) gnu_error_format = 1; ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: bash If the value of the environment variable TERM starts with eterm and the EMACS env var is unset, bash will segfault. The cause is not checking that getenv() is returning NULL when EMACS is unset. To reproduce: - TERM=eterm bash + unset EMACS; TERM=eterm bash Versions: Ubuntu 9.10 bash 4.0-5ubuntu2 See this Fedora bug report for detail and a patch: https://bugzilla.redhat.com/show_bug.cgi?id=530911 --- bash-4.0/shell.c.orig 2009-10-15 15:57:56.0 -0400 +++ bash-4.0/shell.c 2009-10-15 15:58:28.0 -0400 @@ -572,7 +572,7 @@ /* running_under_emacs == 2 for `eterm' */ running_under_emacs = (emacs != 0) || (term STREQN (term, emacs, 5)); - running_under_emacs += term STREQN (term, eterm, 5) strstr (emacs, term); + running_under_emacs += term STREQN (term, eterm, 5) (emacs != 0) strstr (emacs, term); if (running_under_emacs) gnu_error_format = 1; -- bash segfaults when TERM=eterm* https://bugs.launchpad.net/bugs/497637 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388506] Re: udev 60-persistent-storage.rules vol_id cancels hdd spin-down
Indeed, hdparm does not need to open the file RW. I have only tested RO hdparm with -t, -T, -y, -Y, -i, -I, and -C, and not very thoroughly. ** Attachment added: open_ro.patch http://launchpadlibrarian.net/29027667/open_ro.patch -- udev 60-persistent-storage.rules vol_id cancels hdd spin-down https://bugs.launchpad.net/bugs/388506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388506] Re: udev 60-persistent-storage.rules vol_id cancels hdd spin-down
hdparm-9.15 fixes this issue (it opens the file RO). -- udev 60-persistent-storage.rules vol_id cancels hdd spin-down https://bugs.launchpad.net/bugs/388506 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156002] Re: Dolphin crashes (SIGSEGV) under certain drag'n'drop conditions
Running 8.10 amd64. This crash has been with me since I installed 8.10, completely reproducible. I just installed KDE 4.2 from http://ppa.launchpad.net/kubuntu-experimental/ubuntu. Crash happens just as before. Clearly a QT problem; it affects Konqueror and Krusader (my usual file manager). Stack trace is from 4.2 dpkg -l libqtgui4: 4.4.3-0ubuntu1.2 Application: Dolphin (dolphin), signal SIGSEGV 0x7f30a58466b0 in nanosleep () from /lib/libc.so.6 Thread 1 (Thread 0x7f30a8fed6f0 (LWP 5450)): [KCrash Handler] #5 0x7f30a658ef15 in QDragManager::move () from /usr/lib/libQtGui.so.4 #6 0x7f30a65913c9 in QDragManager::eventFilter () from /usr/lib/libQtGui.so.4 #7 0x7f30a77680e4 in QCoreApplicationPrivate::sendThroughApplicationEventFilters () from /usr/lib/libQtCore.so.4 #8 0x7f30a6514ba6 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #9 0x7f30a651d22a in QApplication::notify () from /usr/lib/libQtGui.so.4 #10 0x7f30a80ba5db in KApplication::notify () from /usr/lib/libkdeui.so.5 #11 0x7f30a7768d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #12 0x7f30a651c5c8 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #13 0x7f30a6580da4 in ?? () from /usr/lib/libQtGui.so.4 #14 0x7f30a657f607 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #15 0x7f30a65a72c4 in ?? () from /usr/lib/libQtGui.so.4 #16 0x7f30a1bd3d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #17 0x7f30a1bd750d in ?? () from /usr/lib/libglib-2.0.so.0 #18 0x7f30a1bd76cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #19 0x7f30a779115f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #20 0x7f30a65a6a6f in ?? () from /usr/lib/libQtGui.so.4 #21 0x7f30a7767682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #22 0x7f30a776780d in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #23 0x7f30a658f52b in QDragManager::drag () from /usr/lib/libQtGui.so.4 #24 0x7f30a65273a8 in QDrag::exec () from /usr/lib/libQtGui.so.4 #25 0x7f30a8bd12e8 in ?? () from /usr/lib/libdolphinprivate.so.4 #26 0x7f30a8bc9304 in DolphinIconsView::startDrag () from /usr/lib/libdolphinprivate.so.4 #27 0x7f30a69880d5 in QAbstractItemView::mouseMoveEvent () from /usr/lib/libQtGui.so.4 #28 0x7f30a699e9ba in QListView::mouseMoveEvent () from /usr/lib/libQtGui.so.4 #29 0x7f30a80a3e6c in KCategorizedView::mouseMoveEvent () from /usr/lib/libkdeui.so.5 #30 0x7f30a6567196 in QWidget::event () from /usr/lib/libQtGui.so.4 #31 0x7f30a698c8fd in QAbstractItemView::viewportEvent () from /usr/lib/libQtGui.so.4 #32 0x7f30a7768038 in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4 #33 0x7f30a6514c0c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #34 0x7f30a651d22a in QApplication::notify () from /usr/lib/libQtGui.so.4 #35 0x7f30a80ba5db in KApplication::notify () from /usr/lib/libkdeui.so.5 #36 0x7f30a7768d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #37 0x7f30a651c5c8 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #38 0x7f30a6580be9 in ?? () from /usr/lib/libQtGui.so.4 #39 0x7f30a657f607 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #40 0x7f30a65a72c4 in ?? () from /usr/lib/libQtGui.so.4 #41 0x7f30a1bd3d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #42 0x7f30a1bd750d in ?? () from /usr/lib/libglib-2.0.so.0 #43 0x7f30a1bd76cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #44 0x7f30a779115f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #45 0x7f30a65a6a6f in ?? () from /usr/lib/libQtGui.so.4 #46 0x7f30a7767682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #47 0x7f30a776780d in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #48 0x7f30a68aa7e5 in QMenu::exec () from /usr/lib/libQtGui.so.4 #49 0x7f30a8bd0a41 in DolphinDropController::dropUrls () from /usr/lib/libdolphinprivate.so.4 #50 0x7f30a8bd6f58 in DolphinView::dropUrls () from /usr/lib/libdolphinprivate.so.4 #51 0x7f30a8bd9841 in DolphinView::qt_metacall () from /usr/lib/libdolphinprivate.so.4 #52 0x7f30a777d134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #53 0x7f30a8bc50af in DolphinController::urlsDropped () from /usr/lib/libdolphinprivate.so.4 #54 0x7f30a8bc90c2 in DolphinIconsView::dropEvent () from /usr/lib/libdolphinprivate.so.4 #55 0x7f30a6566ca3 in QWidget::event () from /usr/lib/libQtGui.so.4 #56 0x7f30a698c8fd in QAbstractItemView::viewportEvent () from /usr/lib/libQtGui.so.4 #57 0x7f30a7768038 in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4 #58 0x7f30a6514c0c in
[Bug 295536] Re: cups-pdf fails bad status reported and no pdf created
I got it to work. I changed the permissions on $HOME. Permissions on $HOME were 750. 755 works, 751 and 754 do not work. Permissions on ~/PDF are 700. -- cups-pdf fails bad status reported and no pdf created https://bugs.launchpad.net/bugs/295536 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238745] [NEW] gusty-hardy cdromupgrade breaks
Public bug reported: I'm running Xubuntu 7.10 amd64. I tried to use the cdromupgrade script to upgrade from 7.10 to 8.04 (this is the way I usually upgrade). I followed the instructions in the wiki. I was installing from the Kubuntu alternate CD, because I decided I use more KDE things than any other (I tend to be desktop-agnostic). I had xubuntu-desktop installed before the upgrade. I opted not to grab updates from the web. It complained about nvidia-glx-new, so I uninstalled that (I know, a separate issue). Then it seemed happy and was ready to dist-upgrade. However, as it was calculating updates (I think) two dialogs popped up. They said something about programs crashing, then the cdromupgrade abruptly quit. The programs that crashed were opera-plugin-wrapper and convert (from ImageMagick). It is not surprising to me that these were running at the time: I have a script that uses convert that runs periodically, and I had Opera open. After that, cdromupgrade was broken. My package manager was in a weird state (see below). I decided to push through and did aptitude dist-upgrade. It seems like it worked, I'll report back if it didn't. I have attached /var/log/dist- upgrade/main.log, which shows an unhandled exception, probably caused by the weird state of the package manager. I could not install xubuntu- desktop after the crash because aptitude said there is no candidate version. I have done another successful upgrade (Xubuntu 7.10 - Kubuntu 8.04) using this method, on i386. ** Affects: ubuntu Importance: Undecided Status: New -- gusty-hardy cdromupgrade breaks https://bugs.launchpad.net/bugs/238745 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238745] Re: gusty-hardy cdromupgrade breaks
** Attachment added: main.log from the cdromupgrade http://launchpadlibrarian.net/15165364/main.log.gz -- gusty-hardy cdromupgrade breaks https://bugs.launchpad.net/bugs/238745 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157162] Re: Azureus crashes on icedtea-java7 on x86_64
*** This bug is a duplicate of bug 152362 *** https://bugs.launchpad.net/bugs/152362 I just installed an Azureus update from gutsy-updates, and the launch script is choosing icedtea by default. The bug in icedtea is apparently not fixed, so Azureus crashes. Works fine with sun-java-6. -- Azureus crashes on icedtea-java7 on x86_64 https://bugs.launchpad.net/bugs/157162 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92994] Re: Since update to feisty, CPU fan in laptop won't stop spinning
A similar thing happened to me. I went straight from Dapper to Feisty Beta. The cpu governor works properly out of the box, but the default behavior is different. From what I gather, Dapper used powernowd, but Feisty uses kernelmode governors. powernowd defaults to ignoring nice'd processes in its load calculations. The kernelspace gov doesn't. If I do echo 1 /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load the Dapper behavior returns. -- Since update to feisty, CPU fan in laptop won't stop spinning https://bugs.launchpad.net/bugs/92994 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32906] Re: sudo shouldn’t ABSOLUTEL Y NEED to look up the host it’s running on
Related bug: https://launchpad.net/bugs/19553 From what I understand, sudo can perform commands on several different hosts, hence it needs to know what host it's on. Personally, I keep the root account enabled, because I don't trust sudo. -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://launchpad.net/bugs/32906 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
