[Bug 173904] Re: [gutsy] (un)markauto tries to remove packages
i just used eukleides and xeukleides as an example - because they were packages I knew I could easily add and remove, this behaviour can be seen with any automatically installed packages: Assuming package foo is automatically installed, once all packages depending on foo have been removed, trying to run aptitude unmarkauto foo, causes foo to be removed instead of being unmarked and kept on the system as I would expect. Interestingly using aptitude to remove the last package depending on foo (where foo is marked autoinstalled) causes foo to be removed too, while apt-get does not remove foo but simply warns that nothing depends on foo and that it can be removed. If you're looking for another test case (assuming neither pi nor libcln5 is installed already), do aptitude install pi apt-get remove pi aptitude unmarkauto libcln5 although any other autoinstalled package will do just as well. Incidentally, i originally noticed this behaviour under Gutsy, but the same happens in Hardy... -- [gutsy] (un)markauto tries to remove packages https://bugs.launchpad.net/bugs/173904 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 201318] Re: acpi reporting incorrect battery state
** Attachment added: "after unplugging and reconnecting AC" http://launchpadlibrarian.net/20919041/pm_debug-after.out -- acpi reporting incorrect battery state https://bugs.launchpad.net/bugs/201318 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 201318] Re: acpi reporting incorrect battery state
I'm having a similar problem on my laptop running Hardy. If I boot on AC, the gnome-power-manager notification icon seems to indicate that that I'm running on AC but when holding the mouse over the icon, the tooltip indicates that I'm running on battery. If I unplug the power cable and plug it back in again, both the icon and tooltip correctly indicate that I'm running on AC. I first noticed that something strange was going on when I tried to debug a problem with gnome-screensaver only blanking the screen instead of showing my screensaver - it turned out to be because gnome- screensaver also thought I was running on battery when I'm actually on AC. running acpi -v (or cat /proc/acpi/ac_adapter/ACAD/status) correctly shows that AC is online. hal-find-by-capability --capability "ac_adapter" | xargs -n 1 hal-device shows: ac_adapter.present = false (bool) I'll upload output from gnome-power-bugreport.sh hal-find-by-capability --capability "battery" | xargs -n 1 hal-device hal-find-by-capability --capability "ac_adapter" | xargs -n 1 hal-device before and after unplugging and reconnecting the power cable. ** Attachment added: "before unplugging and reconnecting AC" http://launchpadlibrarian.net/20919039/pm_debug-before.out -- acpi reporting incorrect battery state https://bugs.launchpad.net/bugs/201318 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 60394] Re: screensaver starts but shows only a black screen
I think I know what's going on. I managed to turn on gnome-screensaver debugging on login (I had to rename /usr/bin/gnome-screensaver and replace it with a script that launches gnome-screensaver with debugging enabled. Comparing the debug output from when the screensaver worked to when it doesn't I noticed that when the screensaver wasn't working the output contained lines like: [listener_add_ref_entry] gs-listener-dbus.c:723 (13:48:37): adding throttler from Power screensaver for reason 'On battery power' on connection :1.6 and [manager_maybe_start_job_for_window] gs-manager.c:215 (13:48:53):Not starting job because throttled There is no mention of throttling in the debug output when the screensaver does work correctly. So it seems that gnome-screensaver is only blanking the screen because it thinks the machine is running on battery power (it's not - i'm running on AC). I tried pulling out the power cable and plugging it back in, after which the screensaver was worked correctly. This would seem to indicate that the problem is not with gnome- screensaver but somewhere else. Perhaps in gnome-power-manager. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 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 60394] Re: screensaver starts but shows only a black screen
I thought I'd try to get to the bottom of this by killing gnome-screensaver, running gnome-screensaver --no-daemon --debug > screensaver.debug 2>&1 and then doing gnome-screensaver-command -a but when I did that, the screensaver worked correctly. I did some more experimentation and found that if I kill gnome-screensaver and start it again manually, then it works correctly. If I can find out where gnome-screensaver gets started on login I could change that to enable debugging and see if that gets me any closer to an anwer. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 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 60394] Re: screensaver starts but shows only a black screen
I forgot to mention, I've been running Ubuntu on this laptop for a bit over two years, never had this problem when I was running Dapper, Edgy, Fiesty or Gutsy... -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 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 60394] Re: screensaver starts but shows only a black screen
I'm having the same problem on my laptop running Hardy. Screensaver previews work fine, but when I lock the screen, or when the screensaver activates when the machine is idle or when I run gnome-screensaver- command -a I only get a blank screen. At first I thought the problem was due to some misconfiguration in my user account, so I created a new user, but when I log in using that new account the problem persists. I chose the "pictures folder" screensaver in the screensaver properties dialog and tried doing: gnome-screensaver-command -a && ps ax I would have expected to see some mention of /usr/lib/gnome-screensaver/gnome-screensaver/slideshow in the output, but it's not there (i tried the same with various different screensavers all with the same result). For what it's worth, my graphics card is an Intel 82852/855GM Integrated Graphics Device (rev 02) using the i810 driver (the newer intel driver is rather buggy) and I have all desktop effects disabled. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 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 307288] Re: roaming wireless network interfaces don't work after resume
it is a link to dash actually. turns out i was just misreading the error message. the problem was that PM_FUNCTIONS was not defined. i changed the line to . /usr/lib/pm-utils/functions but it would appear that sourcing that file in dash gives errors anyway (it uses some bash specific syntax). -- roaming wireless network interfaces don't work after resume https://bugs.launchpad.net/bugs/307288 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 202203] Re: suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included)
OK, I failed to realise that Hardy uses pm-utils (and the scripts in /etc/pm/sleep.d) instead of acpi-support (and the scripts in /etc/acpi/suspend.d) to suspend and hibernate the machine. Sebastian Wiesinger posted a script at https://bugs.launchpad.net/bugs/307288 which solves the problem under Hardy. -- suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included) https://bugs.launchpad.net/bugs/202203 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 307288] Re: roaming wireless network interfaces don't work after resume
Thanks for this script! I experienced the same problem on Gutsy and fixed it by patching /etc/acpi/suspend.d/55-down-interfaces.sh (see https://bugs.launchpad.net/bugs/202203). I was rather surprised to discover that my fix no longer worked after I recently upgraded to Hardy. Your script has everything working the way it should again - although I did have to change it to run under /bin/bash rather than /bin/sh (sh was complaining about the . on line 9) -- roaming wireless network interfaces don't work after resume https://bugs.launchpad.net/bugs/307288 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 202203] Re: suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included)
The patch I posted earlier worked on Gutsy. I recently did a clean install of Hardy on my laptop though, and it no longer works. It appears the scripts in /etc/apci/suspend.d never get executed - the access times on all the files there (except the one i patched), is 2008-04-14 09:51. -- suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included) https://bugs.launchpad.net/bugs/202203 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 248053] Re: Debian-style wpa-roam configurations don't work with suspend-to-ram
*** This bug is a duplicate of bug 202203 *** https://bugs.launchpad.net/bugs/202203 ** This bug has been marked a duplicate of bug 202203 suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included) -- Debian-style wpa-roam configurations don't work with suspend-to-ram https://bugs.launchpad.net/bugs/248053 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 165323] Re: xeukleides uses very ugly font
Well, my desktop machine is still running 7.10. I did upgrade my laptop (where there was no problem with the font) to 8.04, but xeukleides is not available in the 8.04 repositories. I haven't installed 8.10 anywhere, and i don't plan on doing so anytime soon, so i don't know whether the problem still exists in 8.10. -- xeukleides uses very ugly font https://bugs.launchpad.net/bugs/165323 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 202203] Re: suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included)
I think this is a bit more important than just a wishlist item. This is not a feature request, it's an actual bug. On Gutsy, and on Hardy too, suspending the computer breaks any network interfaces set up using wpa_roam. After resuming from suspend it is necessary to manually bring such interfaces down (using wpa_action) and then bring them up again. -- suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included) https://bugs.launchpad.net/bugs/202203 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 247921] Re: nautilus crashed with SIGSEGV in pthread_mutex_lock()
I couldn't get a complete backtrace. Nautilus seems to go into an infinite recursion before the crash and gdb crashes after printing the first 58203 stack frames. So, instead of uploading an 11MB file here, I just printed the innermost 21 frames. The pattern that can be seen here continues all the way down the stack (or at least as far as gdb will go). I tried to get the outermost few stack frames as well, but that also causes gdb to crash. ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/16775063/gdb-nautilus.txt -- nautilus crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/247921 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 247644] Re: Nautilus crashes on symlink loops
** Description changed: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) + + to duplicate: + $ mkdir test + $ cd test + $ ln -s s1 s2 + $ ln -s s2 s1 + + Open the directory test in Nautilus -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 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 247644] [NEW] Nautilus crashes on symlink loops
Public bug reported: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 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 241704] [NEW] geomview 1.8.1-15ubuntu1 segfaults
Public bug reported: Binary package hint: geomview Whenever I try to run geomview on Gutsy AMD64, it complains about _XmStrings having a different size in a shared object, and then segfaults: $ geomview /usr/lib/geomview/gvx: Symbol `_XmStrings' has different size in shared object, consider re-linking InstCreate: Undefined option: 7962592 Geomview: internal error: Segmentation violation; dump core now (y/n) [n] ? y Segmentation fault (core dumped) $ This happens everytime I try to run geomview. Geomview works fine on my laptop running Hardy 32bit, but I'd prefer to be able to use it on my desktop machine (which I don't want to upgrade to Hardy yet). ** Affects: geomview (Ubuntu) Importance: Undecided Status: New -- geomview 1.8.1-15ubuntu1 segfaults https://bugs.launchpad.net/bugs/241704 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 44194] Re: wpasupplicant doesn't start when the network start
Gareth Fitzworthington wrote on 2008-04-05: (permalink) >This is a Network Manager bug. >Fix released for Hardy. This is definitely not a Network Manager bug. I (and others who have commented on this bug and its duplicates) do not use Network Manager at all. It is an ifupdown bug that occurs because the ifupdown udev rule tries to bring up interfaces listed as auto in /etc/network/interfaces (and thus ignored by Network Manager) too early at boot. -- wpasupplicant doesn't start when the network start https://bugs.launchpad.net/bugs/44194 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127655] Re: [Gutsy] Manual WPA network doesn't connect on reboot
*** This bug is a duplicate of bug 44194 *** https://bugs.launchpad.net/bugs/44194 ** This bug is no longer a duplicate of bug 53387 Manual WPA networks doesn't connect at boot ** This bug has been marked a duplicate of bug 44194 wpasupplicant doesn't start when the network start -- [Gutsy] Manual WPA network doesn't connect on reboot https://bugs.launchpad.net/bugs/127655 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 53387] Re: Manual WPA networks doesn't connect at boot
*** This bug is a duplicate of bug 44194 *** https://bugs.launchpad.net/bugs/44194 This seems to be a duplicate of bug #44194. There Roman Yepishev posted a similar (but somewhat more elegant) workaround to what I posted here. ** This bug has been marked a duplicate of bug 44194 wpasupplicant doesn't start when the network start -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 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 114310] Re: Have to manually restart networking on every reboot
*** This bug is a duplicate of bug 44194 *** https://bugs.launchpad.net/bugs/44194 ** This bug is no longer a duplicate of bug 53387 Manual WPA networks doesn't connect at boot ** This bug has been marked a duplicate of bug 44194 wpasupplicant doesn't start when the network start -- Have to manually restart networking on every reboot https://bugs.launchpad.net/bugs/114310 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 50099] Re: network has to be started each time system is booted
*** This bug is a duplicate of bug 44194 *** https://bugs.launchpad.net/bugs/44194 ** This bug is no longer a duplicate of bug 53387 Manual WPA networks doesn't connect at boot ** This bug has been marked a duplicate of bug 44194 wpasupplicant doesn't start when the network start -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 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 53387] Re: Manual WPA networks doesn't connect at boot
--Scott James Remnant wrote: >Nothing in this bug report suggests a udev bug? I agree, I'd say it's an ifupdown bug. ** Also affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 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 53387] Re: Manual WPA networks doesn't connect at boot
** Attachment added: "patch /etc/init.d/networking to create /var/run/network/started when networking is started" http://launchpadlibrarian.net/12737818/networking.patch -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 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 53387] Re: Manual WPA networks doesn't connect at boot
OK, I should have looked more closely at the init scripts before. It turns out that lo is brought up by S08loopback in /etc/rcS.d before udev is started. So testing whether lo is up doesn't do much good. I have come up with a temporary workaround though. I modified /etc/init.d/networking to touch a file (/var/run/network/started) when networking is started (or restarted), and remove it when networking is stopped. I also changed my udev ifup script to test for this file to determine whether to bring up the interface. It's a horrible hack, and I hope someone can come up with a better solution soon, but for now it works at least. ** Attachment added: "patch for /etc/udev/ifup.sh" http://launchpadlibrarian.net/12737809/ifup.sh.patch -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 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 53387] Re: Manual WPA networks doesn't connect at boot
My apologies, I am officially an idiot. The ifup script I uploaded was severely broken, which means using it is more or less equivalent to having the udev rule disabled (that's what happens when I try to code before sunset). I've fixed the error in the script, but it seems it doesn't work -- the original problem has returned. I don't really understand it. The only explanations I can come up with is that either there's some other stupid mistake in my script, that I'm just not seeing; or lo is actually brought up somewhere before /etc/init.d/networking starts; or it is possible to ping localhost over lo even when lo hasn't been brought up yet. For what it's worth, I'm attaching the patch to fix my ifup script anyway. ** Attachment added: "ifup.sh.patch" http://launchpadlibrarian.net/12723596/ifup.sh.patch -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 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 53387] Re: Manual WPA networks doesn't connect at boot
I have implemented something like what I suggested in my previous comment and it seems to work. I haven't been able to test it as completely as I'd like, but my wireless network is starting correctly at boot now with the 85-ifupdown udev rule enabled. I wrote a script that tests whether the loopback interface is up before bringing an interface up. The idea being that if lo is not up yet when a network device is added, then presumably the system is booting and /etc/init.d/networking has not been started yet (and when it is started, it will bring up the interface). If lo is up, on the other hand, then /etc/init.d/networking has been started already and so the new interface should be brought up by the udev rule. I'm attaching the script with this comment, save it as /etc/udev/ifup.sh (and make it executable, obviously) and then apply the patch to 85-ifupdown.rules (which I'll also upload here). ** Attachment added: "ifup.sh" http://launchpadlibrarian.net/12689304/ifup.sh -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 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 53387] Re: Manual WPA networks doesn't connect at boot
here's my patch for /etc/udev/rules.d/85-ifupdown.sh ** Attachment added: "85-ifupdown.rules.patch" http://launchpadlibrarian.net/12689312/85-ifupdown.rules.patch -- Manual WPA networks doesn't connect at boot https://bugs.launchpad.net/bugs/53387 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 202203] Re: suspend.d/55-down-interfaces.sh does not call wpa_action stop
** Attachment added: "55-down-interfaces.sh.patch" http://launchpadlibrarian.net/12671906/55-down-interfaces.sh.patch ** Summary changed: - suspend.d/55-down-interfaces.sh does not call wpa_action stop + suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included) -- suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included) https://bugs.launchpad.net/bugs/202203 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 202203] [NEW] suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included)
Public bug reported: Binary package hint: acpi-support I use the wpa-roam (in /etc/network/interfaces) to manage my wireless network on my laptop (running Gutsy). When I suspend the machine, then, on resume, the wireless network stops working properly. The interface is brought up, but wpa_supplicant fails to authenticate with any networks. To fix it, I have to stop wpa_supplicant using wpa_action eth1 stop and then bring the interface up again using sudo ifup eth1. It seems that just calling ifdown (instead of using wpa_action stop) on an interface managed using wpa-roam confuses wpa_supplicant. I've managed to fix this problem by changing /etc/acpi/suspend.d/55 -down-interfaces.sh to check for each interface x, whether /var/run/wpa_action.$x.pid exists, and calling wpa_action $x stop if it does. This brings down the interface gracefully and stops wpa_supplicant and wpa_cli on the interface. The interface is then restarted correctly when the system resumes. ** Affects: acpi-support (Ubuntu) Importance: Undecided Status: New -- suspend.d/55-down-interfaces.sh does not call wpa_action stop (patch included) https://bugs.launchpad.net/bugs/202203 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 53387] Re: Manual WPA networks doesn't connect at boot
I have been having the same problem. When I boot up, my eth1 is brought
up, but wpa_supplicant is not started, so I have to manually bring eth1
down and up again to get my wireless networking working. Disabling the
ifupdown udev rule has fixed the problem, so I'm fairly certain that
this bug is caused by udev bringing up the interface too early, so that
wpa_supplicant fails to start. I thought perhaps the problem might be
that / is still mounted read-only when udev brings up the interface?
Perhaps a fix would be to somehow modify the udev rule so that it does
not trigger at boot time? I don't know if there's a way to do this, but
surely the intention of this rule is to do hotplugging of network
devices after bootup, rather than bringing up interfaces at boot (that's
what /etc/init.d/networking is for). So perhaps instead of bringing up
the interface, the udev rule should call a script that tests whether the
system is booted up already and then brings up the interface.
Here's my interfaces file:
auto lo eth1
iface lo inet loopback
iface eth0 inet dhcp
iface eth1 inet manual
wpa_roam /etc/wpa_supplicant.conf
iface solis-air inet dhcp
iface huisnet inet static
address 192.168.0.2
netmask 255.255.255.0
broadcast 192.168.0.255
iface default inet dhcp
And my wpa_supplicant.conf:
# allow config file overwrite
update_config=1
# path to UNIX socket control interface
ctrl_interface=/var/run/wpa_supplicant
# scanning mode
ap_scan=2
# auth timeout
dot11RSNAConfigSATimeout=90
# Ad-Hoc home network
network={
priority=2
id_str="huisnet"
scan_ssid=1
ssid="Hein"
mode=1
key_mgmt=NONE
auth_alg=SHARED
group=WEP104
wep_key0=
wep_tx_keyidx=0
}
# SOLIS_AIR
network={
priority=2
id_str="solis-air"
ssid="SOLIS-AIR"
scan_ssid=1
key_mgmt=IEEE8021X
eap=TTLS
phase2="auth=PAP"
identity=""
password=""
}
# other (open)
network={
key_mgmt=NONE
}
--
Manual WPA networks doesn't connect at boot
https://bugs.launchpad.net/bugs/53387
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 183969] Re: xserver-xorg-core update breaks java apps
I installed the update this afternoon. It's not causing any problems on my AMD64 Gutsy installation. Eclipse, VLC, Azureus, everything is still working fine. Perhaps this bug only affects 32bit systems? -- xserver-xorg-core update breaks java apps https://bugs.launchpad.net/bugs/183969 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 114505] Re: ntp brought up before network is ready; fails not resolve any ip or host names; ntp does not recover
greetings, As J Carerra mentioned, I was also having some problems with ntpd on Gutsy. I managed to solve my problems though, so I'm posting the solution here in the hope that it might help someone else too. My original analysis of the problem I was having with ntpd (which J Carerra has quoted here) was not quite correct (after hours of digging through init scripts I got slightly confused about which scripts run from rcS.d and which from rc2.d). The DHCP server in the building where I live doesn't provide NTP servers, so I can't comment on what happens when your DHCP server does provide NTP servers. I basically had two separate problems that were preventing ntpd and ntpdate from working properly: * With NetworkManager managing my ethernet connection, ntpd was being started before eth0 was up, so ntpd couldn't associate with any other ntp servers. Then, when eth0 did come up, ntpdate couldn't run, because ntpd was already running. * When I stopped NetworkManager from managing my ethernet connection by adding an entry for eth0 in /etc/network/interfaces, so that eth0 would be brought up by rcS.d/S40networking before ntpd was started by rc2.d/S23ntp everything worked most of the time. However /etc/network/if-up.d/ntpdate was running ntpdate in the background, which meant that every once in a while ntpdate would still be running by the time rc2.d/S23ntp tried to start ntpd, thus preventing ntpd from starting. I managed to solve my ntp problems by writing a new script (which I'm attaching here) to replace /etc/network/if-up.d/ntpdate. This script works for me regardless of whether NetworkManager is managing my internet connection. If you want to try this solution, do the following: * Leave the symlinks to /etc/init.d/ntp intact (the script won't start ntpd if it is disabled in the current runlevel) * Deactivate (remove executable permissions from) /etc/network/if-up.d/ntpdate * Put the new ntpd script at /etc/network/if-up.d/ntpd (and give it proper ownership and executable permissions) * Enjoy (hopefully) For every network interface that is brought up (except the loopback interface), this script: * Stops ntpd (if it was running already) * Runs /usr/bin/ntpdate-debian and - if ntpdate successfully sets the clock, also runs hwclock --systohc * Starts ntpd again (but only if it is configured to start in the current runlevel) Be warned though, that this script may cause misleading log entries (particularly if NetworkManager is not managing your internet connection) claiming that ntpd failed to start when it actually did start. Unfortunately I don't really see a way of preventing this from happening. ** Attachment added: "ntpd.sh" http://launchpadlibrarian.net/11066008/ntpd.sh -- ntp brought up before network is ready; fails not resolve any ip or host names; ntp does not recover https://bugs.launchpad.net/bugs/114505 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 174134] Re: apt-file search prints all results twice
Same thing here, except that everything gets printed three times, not just twice. This happens with "apt-file list" as well as "apt-file search" Same version of apt-file, on gutsy amd64. A simple workaround is to pipe apt-file's output through uniq: apt-file [list|search] | uniq -- apt-file search prints all results twice https://bugs.launchpad.net/bugs/174134 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 173904] [gutsy] (un)markauto tries to remove packages
Public bug reported: Binary package hint: aptitude On gutsy, using aptitude unmarkauto or aptitude markauto, to change the automatically installed status of a package that does not have any other packages dependent on it, causes aptitude to remove the package. For example: $ aptitude search ~neukleides i A eukleides - Euclidean geometry drawing language i xeukleides - System for drawing and viewing Euclidean geometry figures xeukleides depends on eukleides, I can mark eukleides as not automatically installed without any problems: $ sudo aptitude unmarkauto eukleides [...] $ aptitude search ~neukleides i eukleides - Euclidean geometry drawing language i xeukleides - System for drawing and viewing Euclidean geometry figures And I can mark eukleides as automatically installed again: $ sudo aptitude unmarkauto eukleides [...] $ aptitude search ~neukleides i A eukleides - Euclidean geometry drawing language i xeukleides - System for drawing and viewing Euclidean geometry figures No packages depend on xeukleides. When I try to mark xeukleides as automatically installed, aptitude wants to remove xeukleides: $ aptitude -s markauto xeukleides Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Building tag database... Done The following packages are unused and will be REMOVED: eukleides xeukleides 0 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 872kB will be freed. Do you want to continue? [Y/n/?] Would download/install/remove packages. I now remove xeukleides: $ sudo apt-get remove xeukleides [...] The following packages were automatically installed and are no longer required: eukleides Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: xeukleides 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 254kB disk space will be freed. Do you want to continue [Y/n]? Y (Reading database ... 160896 files and directories currently installed.) Removing xeukleides ... Now no packages depend on eukleides, I try to mark eukleides as not automatically installed and aptitude wants to remove it: $ aptitude -s unmarkauto eukleides Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Building tag database... Done The following packages are unused and will be REMOVED: eukleides 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 618kB will be freed. Do you want to continue? [Y/n/?] Would download/install/remove packages. I'm using aptitude version 0.4.6.1: $ aptitude --version aptitude 0.4.6.1 compiled at Sep 15 2007 09:21:46 Compiler: g++ 4.1.3 20070831 (prerelease) (Ubuntu 4.1.2-16ubuntu1) NCurses version: 5.6 libsigc++ version: 2.0.17 ** Affects: aptitude (Ubuntu) Importance: Undecided Status: New -- [gutsy] (un)markauto tries to remove packages https://bugs.launchpad.net/bugs/173904 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 173466] Re: [gutsy] aptitude shows opposite value for "Automatically installed" field
I can confirm this on gutsy (amd64) For example: $ aptitude search ~neukleides i A eukleides - Euclidean geometry drawing language i xeukleides - System for drawing and viewing Euclidean geometry figures $ aptitude why eukleides i xeukleides Depends eukleides $ aptitude show ~neukleides Package: eukleides State: installed Automatically installed: no [...] Package: xeukleides State: installed Automatically installed: yes $aptitude --version aptitude 0.4.6.1 compiled at Sep 15 2007 09:21:46 Compiler: g++ 4.1.3 20070831 (prerelease) (Ubuntu 4.1.2-16ubuntu1) NCurses version: 5.6 libsigc++ version: 2.0.17 -- [gutsy] aptitude shows opposite value for "Automatically installed" field https://bugs.launchpad.net/bugs/173466 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 165323] xeukleides uses very ugly font
Public bug reported: Binary package hint: xeukleides On gutsy, the font xeukleides uses to display figure source is nearly unreadable at high resolutions. It displays fine on my laptop's 83x84dpi monitor, but on my desktop machine's 95x96dpi monitor it is severely pixelated. I'm using version 1.0.1-1ubuntu1, this problem did not exist on feisty (version 0.9.2rev2-1ubuntu1, I believe). ** Affects: xeukleides (Ubuntu) Importance: Undecided Status: New -- xeukleides uses very ugly font https://bugs.launchpad.net/bugs/165323 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 45570] Re: xfig crash using arc drawing
This bug still exists in Feisty on AMD64 (xfig 3.2.5-alpha5-9ubuntu1). According to the Debian bug tracking system this has been fixed upstream (http://www.mail-archive.com/[EMAIL PROTECTED]/msg125449.html) -- xfig crash using arc drawing https://bugs.launchpad.net/bugs/45570 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
