[Bug 1055930] [NEW] Documentation uses wrong directory for squid configuration files
Public bug reported: The documentation on this page: https://help.ubuntu.com/12.04/serverguide/squid.html is inaccurate in that it refers to configuration files in /etc/squid/ when they are actually placed by default in /etc/squid3/. So, for instance, when instructed to edit the file /etc/squid/squid.conf, the user will find that that file does not exist -- it is actually named /etc/squid3/squid.conf. ** Affects: ubuntu-docs (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/1055930 Title: Documentation uses wrong directory for squid configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1055930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055930] Re: Documentation uses wrong directory for squid configuration files
Also, it says to run sudo /etc/init.d/squid restart but the actual command in 12.04 will have to be sudo service squid3 restart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055930 Title: Documentation uses wrong directory for squid configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1055930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 809514] [NEW] Instructions for creating SSL CSR in server guide are out of date
Public bug reported: The instructions in the Ubuntu Server Guide for creating a certificate signing request (for instance at https://help.ubuntu.com/10.04/serverguide/C/certificates-and- security.html) are out of date in that they instruct the user to create a 1024-bit key: openssl genrsa -des3 -out server.key 1024 Most certificate authorities no longer accept 1024-bit RSA keys and instead require a minimum key size of 2048. The instructions could be amended to replace 1024 with 2048 (and the corresponding sample output text modified to match) without additional changes. ** Affects: ubuntu-docs (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/809514 Title: Instructions for creating SSL CSR in server guide are out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/809514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 494699] Re: Does not support current Lucid kernel (2.6.32) or xserver (1.7)
I installed the fglrx_8.721-0ubuntu3 packages on my beta 1 install (up to date as of late March 20). X started properly but all gl-related applications segfaulted. These included the fglrx-specific programs like fglrxinfo and also glxgears, glxinfo, etc. I then removed the packages and gl-related applications like glxinfo, glxgears and glxdemo started functioning again. -- Does not support current Lucid kernel (2.6.32) or xserver (1.7) https://bugs.launchpad.net/bugs/494699 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 494699] Re: Does not support current Lucid kernel (2.6.32) or xserver (1.7)
Got it to run on my system by running sudo aticonfig --initial, and then sudo service gdm restart. -- Does not support current Lucid kernel (2.6.32) or xserver (1.7) https://bugs.launchpad.net/bugs/494699 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 540525] Re: Attempting to join an AIM buddy chat through Room Join always fails silently
Sorry about that. I misunderstood the instructions in chat the first time, and then when I was told what incomplete meant I and Sebastien tried to change at the same time. I am still getting used to launchpad. Thanks for your patience =) -- Attempting to join an AIM buddy chat through Room Join always fails silently https://bugs.launchpad.net/bugs/540525 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 525240] Re: gnome-panel not starting on login
The twitter feed @ubuntustatus directed people who were having trouble with gnome-panel and nautilus to this bug, apparently inaccurately. Most people coming here from @ubuntustatus probably want Bug #542343. -- gnome-panel not starting on login https://bugs.launchpad.net/bugs/525240 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
Problem still exists in 10.04 Alpha 3. I have not done extensive testing of different combinations of settings, etc, in the alpha yet but at the default configuration definitely does not work. -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 540525] Re: Attempting to join an AIM buddy chat through Room Join always fails silently
Omer, I decided to split this report into two bugs: this one addresses that Empathy fails silently and asks for an error message or that the feature be disabled for AIM users (easy fix that I can nominate for Lucid) and the other one addresses that Empathy doesn't support AIM buddy chat in general (complicated fix that's probably not suitable for a release only a month out). Should I have kept those two things together after all? -- Attempting to join an AIM buddy chat through Room Join always fails silently https://bugs.launchpad.net/bugs/540525 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 540525] Re: Attempting to join an AIM buddy chat through Room Join always fails silently
I coded a fix with the upstream sources. I'll have to figure out how to submit the patch and get it to percolate down to Ubuntu, though. ** Changed in: empathy (Ubuntu) Status: Triaged = In Progress ** Changed in: empathy (Ubuntu) Assignee: (unassigned) = Andrew Gorcester (andrewsg) -- Attempting to join an AIM buddy chat through Room Join always fails silently https://bugs.launchpad.net/bugs/540525 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 540525] Re: Attempting to join an AIM buddy chat through Room Join always fails silently
The patch is being processed upstream. I was advised in #ubuntu-bugs to unassign this bug and mark it as incomplete so that it won't be passed over for upload when the time comes. ** Changed in: empathy (Ubuntu) Assignee: Andrew Gorcester (andrewsg) = (unassigned) ** Changed in: empathy (Ubuntu) Status: In Progress = Incomplete -- Attempting to join an AIM buddy chat through Room Join always fails silently https://bugs.launchpad.net/bugs/540525 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 540525] Re: Attempting to join an AIM buddy chat through Room Join always fails silently
** Changed in: empathy (Ubuntu) Status: Triaged = In Progress -- Attempting to join an AIM buddy chat through Room Join always fails silently https://bugs.launchpad.net/bugs/540525 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 510571] Re: Lucid guest won't boot with acpi in virtualbox
I can confirm that arand's patched virtualbox-ose from his PPA does solve the problem on my Ubuntu 9.10 host/10.04 client. -- Lucid guest won't boot with acpi in virtualbox https://bugs.launchpad.net/bugs/510571 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 540525] [NEW] Attempting to join an AIM buddy chat through Room Join always fails silently
Public bug reported: Binary package hint: empathy I tried to join an AIM buddy chat in Empathy using the Room menu's Join... option. In the Join dialog box I was asked for the server and room. The server is not applicable for AIM buddy chat at any rate as chats are only identified by the room name. Leaving the server blank and filling in the room field un-greyed out the Join button. However, clicking the Join button closed the dialog box and did nothing. This happened in both 9.10 and in 10.04 testing. Apparently Empathy's AIM module has no support for AIM buddy chat. Either the Join dialog should be disabled for AIM accounts entirely, or attempting to join a chat room with an AIM account selected should produce an error message. ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Empathy does not support AIM buddy chat and attempting to join a chat through Room Join fails silently + Attempting to join an AIM buddy chat through Room Join always fails silently ** Description changed: Binary package hint: empathy I tried to join an AIM buddy chat in Empathy using the Room menu's Join... option. In the Join dialog box I was asked for the server and room. The server is not applicable for AIM buddy chat at any rate as chats are only identified by the room name. Leaving the server blank and filling in the room field un-greyed out the Join button. However, clicking the Join button closed the dialog box and did nothing. This happened in both 9.10 and in 10.04 testing. - Apparently Empathy's AIM module has no support for buddy chat at all. - Either AIM buddy chat support for Empathy should be implemented or the - Join dialog should be disabled for AIM accounts. At the very least, + Apparently Empathy's AIM module has no support for AIM buddy chat. + Either the Join dialog should be disabled for AIM accounts entirely, or attempting to join a chat room with an AIM account selected should - produce an error message or some sort of feedback. + produce an error message. -- Attempting to join an AIM buddy chat through Room Join always fails silently https://bugs.launchpad.net/bugs/540525 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 540536] [NEW] Empathy does not support AIM buddy chat
Public bug reported: Binary package hint: empathy Empathy does not support AIM buddy chat. This is a request to implement AIM buddy chat support in Empathy, similar to how it is supported in Pidgin. Empathy already has support for multiuser chats for other protocols so only the AIM-specific logic should be needed. Related to bug #540525 ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: empathy Empathy does not support AIM buddy chat. This is a request to implement AIM buddy chat support in Empathy, similar to how it is supported in Pidgin. Empathy already has support for multiuser chats for other protocols so - only the AIM-specific logic is needed. + only the AIM-specific logic should be needed. Related to bug #540525 - (https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/540525). -- Empathy does not support AIM buddy chat https://bugs.launchpad.net/bugs/540536 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 540525] Re: Attempting to join an AIM buddy chat through Room Join always fails silently
** Description changed: Binary package hint: empathy I tried to join an AIM buddy chat in Empathy using the Room menu's Join... option. In the Join dialog box I was asked for the server and room. The server is not applicable for AIM buddy chat at any rate as chats are only identified by the room name. Leaving the server blank and filling in the room field un-greyed out the Join button. However, clicking the Join button closed the dialog box and did nothing. + Empathy also silently fails to display invitations to buddy chat rooms + sent by other AIM users. + This happened in both 9.10 and in 10.04 testing. Apparently Empathy's AIM module has no support for AIM buddy chat. Either the Join dialog should be disabled for AIM accounts entirely, or attempting to join a chat room with an AIM account selected should produce an error message. + + AIM's network frequently has temporary outages and fails to connect + people to buddy chat rooms, in addition to any problems a specific + client might have with the protocol. So, the current behavior does not + make it clear that the problem is with Empathy and not with AIM or the + specific chat room. -- Attempting to join an AIM buddy chat through Room Join always fails silently https://bugs.launchpad.net/bugs/540525 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
Leann, I downloaded the 9.10 alpha and put it on my MicroSD card and booted from it using a USB reader. As before, system seemed to enter suspend but did not wake up properly. Symptoms were substantially the same as I previously reported (though I didn't notice any strange numlock light activity this time). -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
Erik, thanks for the tip. My motherboard was already in Auto mode. I tried switching it to S3 only and also toggling ACPI 2.0 and other suspend-related options to no effect. Attempting to suspend in S1 only mode results in an altogether different problem, where the computer powers down into suspend, but instead of resuming, instead simply reboots. -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
Leann, thank you for the link. I think most (?) of the relevant information was included when the system prompted me to file a suspend/resume bug report, but if there is anything missing that I'm not aware of, please let me know. I have never had suspend work on this system as far as I can recall. However, because the result is inevitably a crash and restart, I don't think to test it very often. -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
Attached is the dmesg from a test with pm_trace enabled. I'm not sure what to make of it, though. ** Attachment added: dmesg.txt http://launchpadlibrarian.net/24383104/dmesg.txt -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
Further tests, each producing a different magic number. Since I'm not getting any hash matches, and since I'm not experiencing any expected side-effects of pm_trace such as filesystem checks, I'm skeptical that pm_trace is working at all. ** Attachment added: dmesg1.txt http://launchpadlibrarian.net/24383526/dmesg1.txt -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
This dmesg was produced while booting into recovery mode. The preceding suspend operation was not performed in recovery mode, however. ** Attachment added: dmesg2.txt http://launchpadlibrarian.net/24383531/dmesg2.txt -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
Lastly, this dmesg is from a normal boot; however, the preceding suspend operation was performed at the command line in recovery mode. Prior to the suspend I tried to remove as many device drivers as I could; for instance, I removed the firewire, graphics and sound card modules. I did not do this in a scientific fashion and I was not familiar with all of the modules so I don't know if this was productive. This is the last one for now. I hope this information is more helpful than it looks, and not just spamming everybody's inboxes. ** Attachment added: dmesg3.txt http://launchpadlibrarian.net/24383549/dmesg3.txt -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
Manoj, did as instructed but no additional messages were displayed. Screen blanked immediately, computer went into suspend, and screen again did not display anything at all on wake. -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 347657] [NEW] [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
Public bug reported: On suspend system powered almost completely down. Keyboard numlock LED turned off but flashed on whenever any key was pressed. No keyboard key would wake the system. Upon pressing the power button system fans, etc. turned back on, numlock LED turned on and stayed on. However, nothing appeared on screen, and system appeared unresponsive to input except for the numlock light which turned off temporarily whenever any key was pressed, then reverted to on. Pressing power button to soft shutdown didn't work, had to use reset button to restart system. ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python2.6 MachineType: System manufacturer P5E-VM HDMI NonfreeKernelModules: fglrx Package: linux-image-2.6.28-11-generic 2.6.28-11.36 ProcAttrCurrent: unconfined ProcCmdLine: root=UUID=35cd789e-60be-4fbb-94d6-f57a389f1bc4 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.28-11.36-generic SourcePackage: linux StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log' Tags: resume suspend Title: [System manufacturer P5E-VM HDMI] suspend/resume failure [non-free: fglrx] UserGroups: pulse-rt ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume suspend -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 347657] Re: [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx]
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/24294721/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/24294722/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24294723/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/24294724/HalComputerInfo.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/24294725/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/24294726/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/24294727/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/24294728/ProcInterrupts.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/24294729/ProcMaps.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/24294730/ProcModules.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/24294731/ProcStatus.txt -- [Asus P5E-VM HDMI] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/347657 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 130496] Re: [gutsy] network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it
After some testing, it appears that the bug no longer occurs in my specific case. network-manager correctly switches from the DHCP- acquired DNS information on the wired connection to the manually set DNS information on the wireless connection and back again without assistance. Thank you for following up on this bug. -- [gutsy] network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it https://bugs.launchpad.net/bugs/130496 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 138307] unzip manpage does not document -O and -I options
Public bug reported: Binary package hint: unzip Ubuntu's unzip has a special patch that allows it to handle non-standard charsets with the options -O and -I (more info at https://blueprints.launchpad.net/unzip/+spec/unzip-detect-filename- encoding). However, this patch doesn't update the manpage, which does not document these new options. ** Affects: unzip (Ubuntu) Importance: Undecided Status: New -- unzip manpage does not document -O and -I options https://bugs.launchpad.net/bugs/138307 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 132357] Re: files with unusual character sets are sometimes completely invisible to the driver
Adding locale=en_US.UTF-8 does solve the problem. Thank you for the help. I think it would be helpful if the driver accepted a tag like nls=utf8, which is used with the stock read-only NTFS driver, just to avoid surprising people who try to upgrade like I did (by simply changing ntfs to ntfs-3g. But maybe other users will be wise enough to read the entire man page. =) -- files with unusual character sets are sometimes completely invisible to the driver https://bugs.launchpad.net/bugs/132357 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 132357] files with unusual character sets are sometimes completely invisible to the driver
Public bug reported: Binary package hint: ntfs-3g When I boot my computer, files with Japanese characters in my NTFS partition are simply not displayed through the ntfs-3g driver. They are not shown in Nautilus, or on the command line, and the driver apparently doesn't recognize that they exist at all. However, unmounting and remounting manually makes them display properly. The relevant line in my /etc/fstab is: UUID=0A00172E00171FED /media/hdd1 ntfs-fusedefaults,uid=1000 0 0 The only possible explanation I can think of is that when I mount it manually (sudo umount /media/hdd1; sudo mount /media/hdd1) this is somehow different from what is done at boot. ** Affects: ntfs-3g (Ubuntu) Importance: Undecided Status: New -- files with unusual character sets are sometimes completely invisible to the driver https://bugs.launchpad.net/bugs/132357 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 130496] network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it
Public bug reported: Binary package hint: network-manager My normal connection is wireless, with a static ip and manually set DNS info. When I temporarily connect my computer to a wired network, network-manager automatically configures using DHCP. In doing so, it overwrites the manual DNS info in /etc/resolv.conf with the DNS info from DHCP completely. When the wired line is disconnected, wireless doesn't work because the manually set DNS info is not restored. I assume the culprit is network-manager in this case because the overwritten /etc/resolv.conf appears as follows (some whitespace removed): # generated by NetworkManager, do not edit! nameserver 192.168.2.1 This happens on Ubuntu 7.10 testing, Tribe 3, up-to-date as of 2007-08-05. network-manger version is 0.6.5-0ubuntu7. The install is one day old and relatively clean. This bug is probably related to [#126592 resolv.conf overwritten on dhcp renew when using NetworkManager vpn plugins] ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it https://bugs.launchpad.net/bugs/130496 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 130496] Re: [gutsy] network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it
** Summary changed: - network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it + [gutsy] network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it ** Description changed: Binary package hint: network-manager My normal connection is wireless, with a static ip and manually set DNS info. When I temporarily connect my computer to a wired network, network-manager automatically configures using DHCP. In doing so, it overwrites the manual DNS info in /etc/resolv.conf with the DNS info from DHCP completely. When the wired line is disconnected, wireless doesn't work because the manually set DNS info is not restored. I assume the culprit is network-manager in this case because the overwritten /etc/resolv.conf appears as follows (some whitespace removed): # generated by NetworkManager, do not edit! nameserver 192.168.2.1 - This happens on Ubuntu 7.10 testing, Tribe 3, up-to-date as of 2007-08-05. network-manger version is 0.6.5-0ubuntu7. The install is one day old and relatively clean. + This happens on Ubuntu 7.10 testing, Tribe 3, up-to-date as of 2007-08-05. network-manger version is 0.6.5-0ubuntu7. The install is one day old and relatively clean. I'm not sure if the bug is gutsy-specific or not. This bug is probably related to [#126592 resolv.conf overwritten on dhcp renew when using NetworkManager vpn plugins] -- [gutsy] network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it https://bugs.launchpad.net/bugs/130496 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 130496] Re: [gutsy] network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it
** Description changed: Binary package hint: network-manager My normal connection is wireless, with a static ip and manually set DNS info. When I temporarily connect my computer to a wired network, network-manager automatically configures using DHCP. In doing so, it overwrites the manual DNS info in /etc/resolv.conf with the DNS info from DHCP completely. When the wired line is disconnected, wireless - doesn't work because the manually set DNS info is not restored. + doesn't work because the manually set DNS info is not restored. This + happens even when the original DNS info in /etc/resolv.conf was set + manually through network-manager itself. I assume the culprit is network-manager in this case because the overwritten /etc/resolv.conf appears as follows (some whitespace removed): # generated by NetworkManager, do not edit! nameserver 192.168.2.1 This happens on Ubuntu 7.10 testing, Tribe 3, up-to-date as of 2007-08-05. network-manger version is 0.6.5-0ubuntu7. The install is one day old and relatively clean. I'm not sure if the bug is gutsy-specific or not. This bug is probably related to [#126592 resolv.conf overwritten on dhcp renew when using NetworkManager vpn plugins] -- [gutsy] network-manager overwrites /etc/resolv.conf on DHCP connect and doesn't restore it https://bugs.launchpad.net/bugs/130496 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
