[Bug 1020756] Re: GtkTreeView keyboard binding are not intituive
I second the effort of fixing GtkTreeView key bindings, 13 years after it has been originally reported, and 10 years after this issue urged me to comment on GNOME Bugzilla. Please, please, fix it at least on Ubuntu/Debian. Then it will flow to virtually all Linux distro variants I personally use. And world will again be a bit better place :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020756 Title: GtkTreeView keyboard binding are not intituive To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1020756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774071] Re: Indicator-datetime-service renders 100% CPU usage
Since I upgraded to 12.04 recently I've started to notice this problem. Namely, indicator-datetime-service was still running at 100% CPU, and was quickly restarted (with just highter PID) after killing its process. However, I was puzzled why at the same time some geoclue- related service also worked? I've found that indicator-datetime package indeed has a dependency upon: geoclue-yahoo | geoclue-provider. Then I have started to suspect that the real problem somehow comes from issue with geoclue - and I was right (in my case). MY SOLUTION: I have used aptitude and marked geoclue-yahoo to be uninstalled, then I solved the now missing dependency by marking geoclue-ubuntu-geoip to be installed. After installation geoclue provider was essentially switched. Now I have no more 100% CPU problem, but a usable system instead. Probably I could have used any other package that is listed in geoclue-provider virtual package, and there are many. Go figure: * geoclue-ubuntu-geoip 0.0.2-0ubuntu6 * geoclue-gypsy 0.12.0-1ubuntu4 * geoclue-gsmloc 0.12.0-1ubuntu4 * geoclue-gpsd 0.12.0-1ubuntu4 * geoclue-yahoo 0.12.0-1ubuntu12 * geoclue-skyhook 0.12.0-1ubuntu12 * geoclue-plazes 0.12.0-1ubuntu12 * geoclue-manual 0.12.0-1ubuntu12 * geoclue-localnet 0.12.0-1ubuntu12 * geoclue-hostip 0.12.0-1ubuntu12 * geoclue-geonames 0.12.0-1ubuntu12 Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774071 Title: Indicator-datetime-service renders 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/774071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 401446] Re: Gnome lost icons position on the desktop
Correct, this nailed it - only symlinks that point to inodes on another filesystem are affected (desktop position is lost). I've just confirmed it by creating a symbolic link on the desktop to one of directories from my $(HOME). The position is correctly kept after logging out and logging back in. A regression, maybe? -- Gnome lost icons position on the desktop https://bugs.launchpad.net/bugs/401446 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 401446] Re: Gnome lost icons position on the desktop
I'm afraid on Ubuntu Karmic gnome-vfs still affects positions of my desktop icons, but in a little different way. I try to keep my desktop clean and only put the most necessary things there. Specifically, I have several symbolic links to some interesting directories, where I keep my work files. When I arrange icons on the desktop (like in, say, Ubuntu 6.06 - 8.10) and log out, the next time I log in icons for symbolic links are on the LEFT side of my screen, not on the RIGHT side where I wanted them. See attached screenshots: * files-dirs-shortcuts-fine.png - that's what I intend to do * shortcuts-wrong.png - that's what happens after logging out and logging back in * test-dir-created.png - after I have created a test directory somewhere on the desktop * test-dir-moved.png - after moving the test icon, logging out and logging in It seems like regular files and directories are unaffected, and for some reason only symlinks are treated differently. I also attached two files from ~/.local/share/gvfs-metadata, since I've found the names of my desktop icons there (as well as interesting strings like 'icon' and 'postion'). $ uname -a Linux hobbit 2.6.31-10-generic #32-Ubuntu SMP Thu Sep 10 23:33:50 UTC 2009 i686 GNU/Linux $ dpkg -l | grep gnome-vfs ii libgnome-vfs2.0-cil2.24.1-4ubuntu1 CLI binding for GnomeVFS 2.24 ** Attachment added: Examples of how gnome-vfs incorrectly saves positions of symlink icons on my desktop http://launchpadlibrarian.net/31952118/screenshots.tar.gz -- Gnome lost icons position on the desktop https://bugs.launchpad.net/bugs/401446 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 412732] Re: gnome-keybinding-properties crashed with SIGSEGV in gtk_tree_model_get_valist()
Freshly updated karmic, normal keyboard shortcuts do not work (no Alt+F1, Alt+F2, etc.), only multimedia keys work and other compiz shortcuts (Ctrl+Alt+Left/Right for rotate to left/right workspace, Ctrl+Alt+LeftMouseButton for cube, etc). Additionally, gnome-keybinding-properties crash - please fix it, thanks :) -- gnome-keybinding-properties crashed with SIGSEGV in gtk_tree_model_get_valist() https://bugs.launchpad.net/bugs/412732 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 64147] Re: ubuntu splash logo stretched on non-4:3/16:9 displays
@Jessie Lawrence: I undestand your pain but the problem is not in the number of images, the problem is in determining and using the native resolution of the monitor. Think about this: let's suppose the usplash uses only one image of 300x200 pixels. Centering it is no problem, but the end result depends heavily on the resolution and whether the monitor stretches the screen in a specific case or not. Now the resolution depends on VESA suppor in the graphics card... If it was easy, it would be already done, believe me. -- ubuntu splash logo stretched on non-4:3/16:9 displays https://bugs.launchpad.net/bugs/64147 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 269656] Re: AN IRRELEVANT LICENSE IS PRESENTED TO YOU FREE-OF-CHARGE ON STARTUP
@Mike Chambers: Thanks for sharing the idea. This seems to be the most balanced solution. Elegant, clean, yet effective. My compliments for Fedora to achieve this. Please include something like this in Ubuntu as well? -- AN IRRELEVANT LICENSE IS PRESENTED TO YOU FREE-OF-CHARGE ON STARTUP https://bugs.launchpad.net/bugs/269656 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 59695] Re: High frequency of load/unload cycles on some hard disks may shorten lifetime
Brian Visel: Is there a way I could get it published, if I did make such a script? Add an attachment to this bug report so the devs could decide? -- High frequency of load/unload cycles on some hard disks may shorten lifetime https://bugs.launchpad.net/bugs/59695 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
Re: [Bug 64147] Re: ubuntu splash logo stretched on non-4:3/16:9 displays
On iMac G5 rev C, ubuntu logo is stretched vertically. That's really strange on a widescreen, where i expected the usplash to be stretched horizontally. The usplash is correctly centered. That's correct, I've experienced the same problem in two variations: * on my Gutsy installation usplash is stretched horizontally. * on my Hardy installation usplash is stretched vertically. This happens only after I change usplash resolution to 1440x900. When in default, 4:3 mode (like 640x480, 800x600 or 1024x768), usplash is always stretched horizontally, with granular image which is the result of scaling. -- ubuntu splash logo stretched on non-4:3/16:9 displays https://bugs.launchpad.net/bugs/64147 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 200272] Re: Calculator not working.
This problem haunted me as well for a good month or so. Thanks for explaining it and tracking it down to the source. The patch attached at: http://bugzilla.gnome.org/attachment.cgi?id=107901action=view seems to fix the issue. It's a simple fix that modifies a .glade file and a translation file (pl.po). Could you please apply it before Hardy ships? -- Calculator not working. https://bugs.launchpad.net/bugs/200272 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 200272] Re: Calculator not working.
Alas, after going from the GNOME 2.22.1 announcement: http://mail.gnome.org/archives/gnome-announce-list/2008-April/msg00039.html following to the sources: http://ftp.gnome.org/pub/GNOME/desktop/2.22/2.22.1/sources/ http://ftp.gnome.org/pub/GNOME/desktop/2.22/2.22.1/sources/gcalctool-5.22.1.tar.gz I can say the problem is still there. Right now I updated my Hardy installation and: $ dpkg -l gcalctool Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii gcalctool 5.22.1-0ubuntu A GTK2 desktop calculator $ gcalctool Segmentation fault (core dumped) $ LANG=C gcalctool [works] -- Calculator not working. https://bugs.launchpad.net/bugs/200272 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 190515] Re: [Hardy] Backport rt2400/rt2500 drivers
@Nicolas Deschildre You've got 54 Mbs directly because you are using a different driver. rt2500-source = legacy driver (driver name: rt2500). Since the Debianers used rt2500, I have tried the same - but without luck. The version from Ubuntu repository didn't want to compile with module-assistant (it died with error). Your post gave me another idea, to use the rt2500 straight from CVS. And it worked! I've used the rt2500 1.1.0 CVS 2008030802 version, which compiled and worked fine on 2.6.24-11-generic kernel. It gave me full 54Mb/s :) Yes, I blacklisted manually rt2x00lib, rt2x00pci and rt2500pci but I think it was worth it :D Today I've installed the upgrades and along with them came the 2.6.24-12-generic kernel. As expected, the wi-fi card worked no loger, since the relevant modules were left in the previous kernel. So, using a routine I used to in my Gentoo days, I reinstalled the driver after the kernel upgrade. It was only a matter of: make clean ; make ; make install ; modprobe rt2500 And there it is again: # iwconfig wlan0 wlan0 RT2500 Wireless ESSID:przestrzen Mode:Managed Frequency=2.437 GHz Access Point: 00:AA:BB:CC:DD:EE Bit Rate=54 Mb/s Tx-Power:-3 dBm RTS thr:off Fragment thr:off Encryption key:------XX Security mode:open Link Quality=85/100 Signal level:-49 dBm Noise level:-79 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I appreciate the serialmonkey work very much, but just as a quick remedy I'm reverting for now to the legacy rt2500 driver (that works :) Friendly, Wiktor -- [Hardy] Backport rt2400/rt2500 drivers https://bugs.launchpad.net/bugs/190515 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 190515] Re: [Hardy alpha 4] Wrong bandwidth with rt2400/rt2500
I have the same problem on Hardy Alpha 3 and Alpha 4 (can't remember earlier). This doesn't happen in Feisty and Gutsy. However, I installed 64-bit Debian Sid and there is no slowdown at all. I even get 54Mbps instead of typical 11Mbps (!) over WPA-protected access point. I have built rt2500-source twice: * 1:1.1.0-b4-3 for 2.6.21-2-amd64 kernel * 1:1.1.0-b4+cvs20070924-3 for 2.6.24-1-amd64 kernel Details follow: # uname -smvro Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 16:01:54 UTC 2008 x86_64 GNU/Linux # COLUMNS=160 dpkg -l rt2500* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==-==- un rt2500 none (no description available) un rt2500-2.6.18-4-amd64 none (no description available) un rt2500-2.6.21-2-amd64 none (no description available) un rt2500-2.6.24-1-amd64 none (no description available) pn rt2500-modules-2.6.18-4-amd64 none (no description available) ii rt2500-modules-2.6.21-2-amd64 1:1.1.0-b4-3+2.6.21-5 RT2500 wireless network drivers ii rt2500-modules-2.6.24-1-amd64 1:1.1.0-b4+cvs20070924-3+2.6.24-4 rt2500 wireless network driver ii rt2500-source 1:1.1.0-b4+cvs20070924-3 source for rt2500 wireless network driver # iwconfig eth2 eth2 RT2500 Wireless ESSID:my-essid Mode:Managed Frequency=2.437 GHz Access Point: 00:11:95:7E:00:86 Bit Rate=54 Mb/s Tx-Power:-3 dBm RTS thr:off Fragment thr:off Encryption key:3B5D-3C7D-207E-37DC-EEED-D301-E4 Security mode:open Link Quality=84/100 Signal level:-51 dBm Noise level:-80 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 -- [Hardy alpha 4] Wrong bandwidth with rt2400/rt2500 https://bugs.launchpad.net/bugs/190515 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
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
@ Fabio Marzocca [EMAIL PROTECTED]: -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 You received this bug notification because you are a direct subscriber of the bug. I have already written an Ubuntu-specific tutorial concerning this issue and K/Ubuntu usplash as well. It works great for me and it has been reported by several folks that it works for them too :) To can find my post in the forums: * GeForce 1440x900 resolution, virtual terminals and wide usplash-theme-ubuntu http://ubuntuforums.org/showthread.php?t=622018 Though personally I would rather prefer things to work out of the box, so my howto would not be needed at all. If you have more questions, feel free to comment on the aforementioned thread. Friendly, Wiktor -- Registered Linux user #390131 (http://counter.li.org) -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 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 190404] Re: 'Reading state information' string not translated to polish
** Attachment added: Refreshed pl.po file for apt-0.7.9 and 0.7.10 http://launchpadlibrarian.net/11879618/apt-0.7.9-0.7.10_pl.po -- 'Reading state information' string not translated to polish https://bugs.launchpad.net/bugs/190404 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 190404] Re: 'Reading state information' string not translated to polish
This problem comes from the apt package, that is used by update-manager. Strings displayed by apt-get and the rest of apt programs are copied and displayed in graphical managers, like synaptic and update-manager. I've filed an upstream bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465347 Additionally, I created the refreshed pl.po file for the apt package. Hopefully the Polish translators will pick it up so this problem could be resolved. -- 'Reading state information' string not translated to polish https://bugs.launchpad.net/bugs/190404 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
Re: [Bug 189681] [NEW] The window X is not responding is not translated into polish
I filed an upstream bug: http://bugs.opencompositing.org/show_bug.cgi?id=775 Now what we need is time and a right developer assistance. -- The window X is not responding is not translated into polish https://bugs.launchpad.net/bugs/189681 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 152911] Re: [Gutsy] The window X is not responding message dialog can't be translated
I filed an upstream bug: http://bugs.opencompositing.org/show_bug.cgi?id=775 Now what we need is time and a right developer assistance. -- [Gutsy] The window X is not responding message dialog can't be translated https://bugs.launchpad.net/bugs/152911 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 177576] Re: rt2x00 badly broken in hardy
osteenbergen wrote on 2008-01-07: In hardy i had speed trouble 1/4 of my download speed was availible with rt2500pci driver. I now use ndiswrapper (had troubles but latest version works) but i will revert to rt2500 to report information about rt2500 in Hardy Exact;y the same hit me too with Hardy Alpha 3 (i386-desktop). I have only 30kB-60kB rate while downloading the updates (236MB takes a long time, mind you) - but in Feisty/Gutsy the same PCI card using rt2500pci module gives me a full speed of 240kB-250kB download rate. My mainboard is ASUS A8V Deluxe, and the hardware: # lspci -v 00:0e.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) Subsystem: ASUSTeK Computer Inc. WL-130g Flags: bus master, slow devsel, latency 64, IRQ 21 Memory at fbb0 (32-bit, non-prefetchable) [size=8K] Capabilities: [40] Power Management version 2 PS. I'm writing this comment while the updates are downloading in the chroot'ed Hardy environment, started from inside otherwise perfectly working Gutsy installation. :-) -- rt2x00 badly broken in hardy https://bugs.launchpad.net/bugs/177576 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 179336] Re: Hardy alpha 2 CD won't boot
I've seen similar behaviour on a PC at university, so I removed the splash quiet options to see the boot messages. Shortly after booting an Alpha-2 hardy-desktop-i386 CD the floppy drive LED turned on, the drive started making noises and lots of floppy I/O errors were displayed. After a while hard drive started moving its heads. After that floppy started moving again, and then the hard drive. This process repeated several times and after that only the BusyBox prompt appeared. After putting a floppy disk inside the drive and rebooting the process was faster, but still stopped at the BusyBox prompt. On my laptop which obviously doesn't have a floppy drive, the booting process just stuck - no X, no installer, no normal login: prompt. I was able, however, to reboot the machine using Alt+Ctrl+Delete. I checked the CD and the MD5 checksums match. Previously other LiveCD's worked, Feisty, PCLinuxOS, Mint, OpenSUSE, Etch. It's only the Hardy CD that's broken at the moment. What information would you like to receive to diagnose this problem? Unluckily, I'd be able to get at the problematic university machine on Monday 14th. -- Hardy alpha 2 CD won't boot https://bugs.launchpad.net/bugs/179336 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 129910] Re: Blank ttys when using vesafb (vga=xxx)
@Loye Young I have already written an Ubuntu-specific tutorial concerning this issue and K/Ubuntu usplash as well, using only hwinfo program and traditional vga= instead of video= parameter. I haven't posted here earlier, because this bug already has had lots of comments. But since you've mentioned it... To can find my post in the forums: * GeForce 1440x900 resolution, virtual terminals and wide usplash-theme-ubuntu http://ubuntuforums.org/showthread.php?t=622018 Though I would rather prefer things to work out of the box, so my howto would not be needed at all. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 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 64147] Re: ubuntu splash logo stretched on non-4:3/16:9 displays
Maybe you can use some info from my post in the Ubuntu Forums? See: GeForce 1440x900 resolution, virtual terminals and wide usplash-theme-ubuntu [gutsy] http://ubuntuforums.org/showthread.php?t=622018 I've compiled there the information from this bug report, a bug #129910 and my experiments. I believe that at least some instructions, from point 6. to 8. you may find useful. And if usplash documentation is right, the 1440x900 usplash image could be displayed correctly on displays with 16:9 or 16:10 ratios, even in resolutions higher than 1440x900. -- ubuntu splash logo stretched on non-4:3/16:9 displays https://bugs.launchpad.net/bugs/64147 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 66637] Re: After running mkswap, swap space is discarded, system fails to hibernate (invalid swap signature)
There is another alternative to solve the UUID problem, that is use the
mkswap-uuid program.
Look at these two locations:
* http://www.nabble.com/DRBL-1.8.0-15-(stable)-released-t4492611.html
* http://free.nchc.org.tw/drbl-core/old/src/
You need to compile it manually, but the whole process takes only
several minutes :-)
So here are the steps:
1. sudo apt-get install build-essential uuid-dev
2. mkdir ~/work ; cd ~/work
3. wget http://free.nchc.org.tw/drbl-core/old/src/mkswap-uuid-0.1.0-2.tar.bz2
4. tar -xjf mkswap-uuid-0.1.0-2.tar.bz2
5. cd mkswap-uuid
6. make sudo cp mkswap-uuid /usr/local/bin
After that you have the mkswap-uuid binary which you can use to
recreate the swap partition with desired UUID:
7. swap_device=/dev/name-of-swap-partition
8. swap_uuid=put-desired-swap-uuid-here
9. sudo swapoff ${swap_device}
10. sudo mkswap-uuid -U ${swap_uuid}
11. sudo swapon ${swap_device}
12. sudo blkid ${swap_device}
There.
--
After running mkswap, swap space is discarded, system fails to hibernate
(invalid swap signature)
https://bugs.launchpad.net/bugs/66637
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 66637] Re: After running mkswap, swap space is discarded, system fails to hibernate (invalid swap signature)
A goblin ate some of my words. It should be:
10. sudo mkswap-uuid -U ${swap_uuid} ${swap_device}
Cheers!
--
After running mkswap, swap space is discarded, system fails to hibernate
(invalid swap signature)
https://bugs.launchpad.net/bugs/66637
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 129910] Re: tty[1-6] are active but display nothing in Gutsy
ASUS F3SC-AS218E here, with GeForce 8400M. I was testing all Tribes and RC of Ubuntu Gutsy and recently I installed it from official ISO. I have nvidia-glx-new driver installed by Restricted Drivers Manager and I have obviously noticed problems with black virtual terminals. Since this notebook has 1440x900 screen I tried at first to enable this or similarly high resolution. However, my attempts proved I was able to turn on only 1024x768. The following applies only to this kernel (it works as I type): $ uname -a Linux ghost 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux Here's the procedure I've used to enable high resolution on consoles: 1. Select font used in framebuffer mode: $ sudo dpkg-reconfigure console-setup * select Fixed font or any other you like/prefer 2. Modify kernel parameters: $ sudo nano /boot/grub/menu.lst * change: # defoptions=quiet splash locale=pl_PL * to: # defoptions=vga=791 quiet splash locale=pl_PL 3. Make sure the changes are applied: $ sudo update-grub 4. Modify usplash configuration: $ sudo nano /etc/usplash.conf * change: xres= yres= * to: xres=1024 yres=768 5. Enable modules autoloading: $ sudo nano /etc/initramfs-tools/modules * at the end of file add: fbcon vesafb vga16fb 6. Remove modules from blacklist: $ sudo nano /etc/modprobe.d/blacklist-framebuffer * change: blacklist vesafb blacklist vga16fb * to: # blacklist vesafb # blacklist vga16fb 7. Just in case: $ sudo depmod -a 8. Apply all changes in one go, including initrd generation: $ sudo dpkg-reconfigure usplash After restart all is right, just like it was in Feisty. -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
I can happily report that at least in Ubuntu 7.10 RC this problem no longer exists. I was able to test the installation today and even though the installer still complained somewhat (the migration-assistant not being able to unmount partitions), it was no longer hanging nor indefinitely waiting after creating the filesystems. I noticed however, that the NTFS volumes were no longer mounted during the installation process - only FAT32 and ext3 partitions were mounted in the target filesystem: $ mount -l | grep target /dev/sda8 on /target type ext3 (rw) [] /dev/sda6 on /target/data type ext3 (rw) [DATA] /dev/sda7 on /target/mnt/gutsy type ext3 (rw) [GUTSY] /dev/sda9 on /target/mnt/linux3 type ext3 (rw) [LINUX3] /dev/sda1 on /target/mnt/recovery type vfat (rw) [RECOVERY] But this didn't make much difference, since the mountpoints for NTFS volumes were created in correct places anyway: $ ls /target/media cdrom cdrom0 homek vista BTW, my disk is now partitioned as follows: $ sudo fdisk -l Disk /dev/sda: 160.0 GB, 160041885696 bytes 129 heads, 4 sectors/track, 605778 cylinders Units = cylinders of 516 * 512 = 264192 bytes Disk identifier: 0x3184f443 Device Boot Start End Blocks Id System /dev/sda1 4 27787 7168000 1c Hidden W95 FAT32 (LBA) -- RECOVERY /dev/sda2 * 27787 190357419430407 HPFS/NTFS-- VistaOS /dev/sda3 190361 605771 107176038f W95 Ext'd (LBA) /dev/sda5 190361 312289314572807 HPFS/NTFS -- HOMEK /dev/sda6 312290 45895037838536 83 Linux -- DATA (separate /home) /dev/sda7 458951 50772112582916 83 Linux -- GUTSY /dev/sda8 507722 55649212582916 83 Linux -- GUTSY-RC /dev/sda9 556493 60526312582916 83 Linux -- LINUX3 /dev/sda10 605264 605771 131062 82 Linux swap / Solaris I suppose the upgrade of ntfs-3g and libntfs-3g12 to 1:1.913-2ubuntu1 helped much in this aspect :-). Good job anyway! -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 145012] Re: installer hangs retrieving langpacks when network is down
I just tried to install Gutsy beta in Polish, without network and the installation hangs at 87%. Then I configured the network manually (so I am typing this using LiveCD), but in Polish the installation still hangs at 87%, trying to download the lang packs. But this time it at least displayed that there is 1:09 estimated time left. Not to mention that installation still hangs after mounting Vista's NTFS partitions, as described in Bug #135370. It's apparently bug squash time! -- installer hangs retrieving langpacks when network is down https://bugs.launchpad.net/bugs/145012 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 147023] Re: ubiquity hangs at 5% when formatting partitions
Maybe it's the same problem as described in Bug 135370 ? -- ubiquity hangs at 5% when formatting partitions https://bugs.launchpad.net/bugs/147023 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 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
I tried to install Gutsy using defaults, i.e: * English language (to overcome Bug #145012) * all mountpoints at default locations names (/media/sda*) To my surprise I was able to finish the installation. I made a bunch of screenshots with all the steps I've taken. I will attach them in a .tar.gz and the /var/log/syslog as suggested in https://wiki.ubuntu.com/DebuggingUbiquity Then I will try to do one step at a time towards the installation configuration I have used while the installer and/or mount.ntfs were hanging. -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] default settings that worked
** Attachment added: default settings that worked http://launchpadlibrarian.net/9609428/default-settings.tar.gz -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
** Attachment added: /var/log/syslog after the installation succeeded http://launchpadlibrarian.net/9609438/syslog -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
I think I was able to isolate the problem. I've tried to reinstall Gutsy and now it hung. Basically what I did differently this time was to specify a different mountpoint for NTFS volumes: /dev/sda2 at /mnt/vista instead of /media/sda2 /dev/sda5 at /mnt/homek instead of /media/sda5 You can see that mount.ntfs calls don't finish, as they are listed in process list: # ps axf | grep mount.ntfs 27549 pts/0S+ 0:00 \_ grep mount.ntfs 26621 ?Ss 0:00 /sbin/mount.ntfs /dev/sda5 /target/mnt/homek -o rw 26628 ?Ss 0:00 /sbin/mount.ntfs /dev/sda2 /target/mnt/vista -o rw Mountings at this point are as such: # mount -l proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) tmpfs on /lib/modules/2.6.22-12-generic/volatile type tmpfs (rw,mode=0755) tmpfs on /lib/modules/2.6.22-12-generic/volatile type tmpfs (rw,mode=0755) varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755) varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777) udev on /dev type tmpfs (rw,mode=0755) devshm on /dev/shm type tmpfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /tmp type tmpfs (rw,nosuid,nodev) /dev/sda7 on /target type jfs (rw) [] /dev/sda5 on /target/mnt/homek type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096) [HOMEK] /dev/sda2 on /target/mnt/vista type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096) [VistaOS] I will attach two more screenshots and syslog for closer inspection. -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] ntfs mountpoints at /mnt
** Attachment added: ntfs mountpoints at /mnt http://launchpadlibrarian.net/9609608/ntfs-mountpoints-at-slash-mnt.tar.gz -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] /var/log/syslog while installer hungs
** Attachment added: /var/log/syslog while installer hungs http://launchpadlibrarian.net/9609623/syslog -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] /var/log/partman while installer hangs
** Attachment added: /var/log/partman while installer hangs http://launchpadlibrarian.net/9609632/partman -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
# which mount.ntfs /sbin/mount.ntfs # ls -al /sbin/mount.ntfs lrwxrwxrwx 1 root root 12 2007-09-30 21:15 /sbin/mount.ntfs - /bin/ntfs-3g That says it all. -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
And maybe this one too: # mount.ntfs ntfs-3g: No device is specified. ntfs-3g 1.710 - Third Generation NTFS Driver Copyright (C) 2005-2006 Yura Pakhuchiy Copyright (C) 2006-2007 Szabolcs Szakacsits Usage:ntfs-3g device|image_file mount_point [-o option[,...]] Options: ro, force, locale=, uid=, gid=, umask=, fmask=, dmask=, streams_interface=. Please see details in the manual. Example: ntfs-3g /dev/sda1 /mnt/win -o force,locale=en_EN.UTF-8 Ntfs-3g news, support and information: http://ntfs-3g.org -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
No, I observed the same behavior with ext2 and ext3 (as you can see /dev/sda8 still has ext2 after the previous testings). As a side note, when I resized Vista partitions to free up space for Ubuntu (it's a new laptop right now), the partitioner offered ext2 as a default (!) for all Linux partitions (type 83). I overlooked that and only later tried ext3 and jfs to see if everything still work. Now after I know what's going on, I have a plan for a clean reinstall, with ext3 of course :-) -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
Gosh, it's late... When I wrote: I observed the same behavior with ext2 and ext3 I wanted to say that it didn't matter what other file systems I have used. In all my cases the installer was hanging, no matter if I used ext2, ext3 or jfs for Linux partitions. And yes, you've got a good eye. I really wondered if anybody would notice my file system experiments ;-) And you did! -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
The laptop has 2GiB. It's an ASUS F3S-AS218E (T7250). But right now I don't want to create a custom installer. I have enough after fighting recently with debugging LTSP (Edubuntu) startup sequence. -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 122834] Re: FTDI USB Serial Device converter disconnects
Looks like the problem is well-known since February 2007. Additional info: * Bug #84139 - https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/84139 * brltty mailing list: ** http://mielke.cc/pipermail/brltty/2007-February/001812.html ** http://mielke.cc/pipermail/brltty/2007-February/thread.html#1812 The conclusion is that udev rules should be changed. So, awaiting the action from maintainers... A simple, one-liner removal. Please! -- FTDI USB Serial Device converter disconnects https://bugs.launchpad.net/bugs/122834 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 84139] Re: Arduino detected as braille device
I've been hit by this problem too. Even though answers found through Google suggested a complete removal of brltty, I dig deeper. Finally I narrowed down the problem to one of the udev rule, specifically tailored for an otherwise generic 0403:6001 Vendor/Product combination. After commenting it out, my USB-Serial adapter worked flawlessly. Additional info: * Bug #122834 - FTDI USB Serial Device converter disconnects The conclusion is that udev rules should be changed. So, awaiting the action from maintainers... A simple, one-liner removal. Please! -- Arduino detected as braille device https://bugs.launchpad.net/bugs/84139 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 122834] Re: FTDI USB Serial Device converter disconnects
Recently I've tried to connect an USB to RS232 adapter. In Ubuntu Edgy
6.10 and in Windows XP the cable worked flawlessly. However, in Ubuntu
Feisty 7.04 and in Ubuntu Gutsy 7.10 the system was automatically
removing the device, rendering /dev/ttyUSB0 inaccessible. In the end I
narrowed it down to brltty package, and specifically one line in
/etc/udev/rules.d/85-brltty.rules - details follow.
A quick look in the system log:
$ sudo tail -f /var/log/messages
Sep 14 18:16:51 fine-2 kernel: [ 1409.164000] usb 2-1: new full speed USB
device using ohci_hcd and address 3
Sep 14 18:16:51 fine-2 kernel: [ 1409.392000] usb 2-1: configuration #1 chosen
from 1 choice
Sep 14 18:16:51 fine-2 kernel: [ 1409.396000] ftdi_sio 2-1:1.0: FTDI USB Serial
Device converter detected
Sep 14 18:16:51 fine-2 kernel: [ 1409.396000] drivers/usb/serial/ftdi_sio.c:
Detected FT232BM
Sep 14 18:16:51 fine-2 kernel: [ 1409.396000] usb 2-1: FTDI USB Serial Device
converter now attached to ttyUSB0
Sep 14 18:16:51 fine-2 kernel: [ 1409.60] usb 2-1: usbfs: interface 0
claimed by ftdi_sio while 'brltty' sets config #1
Sep 14 18:16:51 fine-2 kernel: [ 1409.604000] ftdi_sio ttyUSB0: FTDI USB Serial
Device converter now disconnected from ttyUSB0
Sep 14 18:16:51 fine-2 kernel: [ 1409.604000] ftdi_sio 2-1:1.0: device
disconnected
Sep 14 18:18:52 fine-2 kernel: [ 1529.388000] usb 2-1: USB disconnect, address 3
$ lsusb
Bus 003 Device 001: ID :
Bus 004 Device 001: ID :
Bus 002 Device 006: ID 0403:6001 Future Technology Devices International, Ltd
8-bit FIFO
Bus 002 Device 001: ID :
Bus 001 Device 001: ID :
The line mentioning 'brltty' looked suspicious, so I did a little search
with the exact error message:
Google: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1
*
http://www.google.pl/search?hl=plq=usbfs%3A+interface+0+claimed+by+ftdi_sio+while+%27brltty%27+sets+config+%231
Interesting results - from what I could tell, all the answers suggested the
removal of brltty package.
However, I started noticing something interesting with regard to USB
VendorID+ProductId combinations, namely 0403:6001. Device that I posess
had exactly the same characteristics. Here are the places describing the
same problem:
* http://www.mail-archive.com/linux-usb-
[EMAIL PROTECTED]/msg56580.html
FTDI UM245R
Vendor Id: 0403
Product Id: 6001
* http://dub.net.nz/hal
FT232BM
/org/freedesktop/Hal/devices/usb_device_403_6001_FTCXA3R6
* https://answers.launchpad.net/ubuntu/+source/gnome-
panel/+question/7438
Google: linux usbserial
* http://www.google.pl/search?hl=plq=linux+usbserial
* http://ftdi-usb-sio.sourceforge.net/
FTDI_SIO
Vendor=0403 ProdID=8372 (ok, this is different)
FT8U232AM
Vendor=0403 ProdID=6001
245 USB - Serial
Vendor=0403 ProdID=6001
Finally I checked the brltty package itself, and looked for its udev rules:
$ dpkg -L brltty | grep udev
/etc/udev
/etc/udev/rules.d
/etc/udev/rules.d/85-brltty.rules
Now for the interesting part:
$ grep 6001 /etc/udev/rules.d/85-brltty.rules
SYSFS{idVendor}==0403, SYSFS{idProduct}==6001, RUN+=/lib/brltty/brltty.sh
-b ht -d usb:
And to give it more context:
$ grep -B3 -A3 6001 /etc/udev/rules.d/85-brltty.rules
# HandyTech
SYSFS{idVendor}==0921, SYSFS{idProduct}==1200, RUN+=/lib/brltty/brltty.sh
-b ht -d usb:
SYSFS{idVendor}==0403, SYSFS{idProduct}==6001, RUN+=/lib/brltty/brltty.sh
-b ht -d usb:
# Papenmeier
SYSFS{idVendor}==0403, SYSFS{idProduct}==f208, RUN+=/lib/brltty/brltty.sh
-b pm -d usb:
After I placed a # comment at the beginning of line containing 0403:6001
combination and killed the running brltty daemon, my USB - RS232 converter
started to work!
$ grep 6001 /etc/udev/rules.d/85-brltty.rules
# SYSFS{idVendor}==0403, SYSFS{idProduct}==6001,
RUN+=/lib/brltty/brltty.sh -b ht -d usb:
$ ps axfu | grep brltty
root 12403 0.0 0.1 2892 764 pts/1S+ 18:54 0:00 \_
grep brltty
root 5720 0.0 0.1 1960 800 ?Ss 17:56 0:02 /sbin/brltty
-P /var/run/brltty -b ht -d usb:
$ sudo killall brltty
Now after inserting the converter I got a working /dev/ttyUSB0 device:
$ sudo tail -f /var/log/messages
Sep 14 18:55:36 fine-2 kernel: [ 3727.712000] usb 2-1: new full speed USB
device using ohci_hcd and address 9
Sep 14 18:55:37 fine-2 kernel: [ 3727.94] usb 2-1: configuration #1 chosen
from 1 choice
Sep 14 18:55:37 fine-2 kernel: [ 3727.944000] ftdi_sio 2-1:1.0: FTDI USB Serial
Device converter detected
Sep 14 18:55:37 fine-2 kernel: [ 3727.944000] drivers/usb/serial/ftdi_sio.c:
Detected FT232BM
Sep 14 18:55:37 fine-2 kernel: [ 3727.944000] usb 2-1: FTDI USB Serial Device
converter now attached to ttyUSB0
$ ls -l /dev/ttyU*
crw-rw 1 root dialout 188, 0 2007-09-14 18:55 /dev/ttyUSB0
Now for conclusion. It seems like brltty's udev rules contain a line
which obviously interferes with normal mode of operation of USB -
Serial converters. However, it appears only for USB devices with
Re: [Bug 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
Why did /sbin/mount.ntfs look suspicious? The output of 'mount -l' displayed the first partition with NTFS as the last one mounted (see the result above). So I suspected /something/ with mounting this type of filesystem (ext3 fs were mounted correctly). Other than that I guessed. And since killing the mount.ntfs process cured my situation, I called it 'suspicious'. That's all. I also started Windows shortly before starting the installer, so this NTFS volume was in a good shape, no chkdsk or fsck complaints, thank you. How long did you wait? Several hours (around 5). I left the installer at the aforementioned message and went away for a visit. After returning home it was still in the same place. Trying to cancel the installation and restarting it rendered the installer useless, because it was complaining about the partitioner ending unexpectedly with the error number 10. Talk about informative messages ;-) I restarted the machine from LiveCD and started the installer again. As expected, it stopped in the same moment. Looking proactively, I guessed that something was happening because of ntfs-3g being used by default (up to feisty this was not the case) - just look at the provided mount list, you can easily see fusectl filesystem mounted and winxp partition as fuseblk type instead of simple ntfs. Isn't it possible that it was importing (searching for and copying) files from the NTFS partition to the Linux one? I don't think so. It displayed an empty list of other operating systems and didn't offer an option to import the settings. IIRC, when installing Feisty it detected this Windows XP install and the offer for importing settings was displayed correctly. But I haven't used it anyway :-) I work a lot more often with Linux than Windows, so there wouldn't be aby serious profile information to import. ;-) Thanks. Yup. Thanks for your time too. Still being proactive I will install this version of Gutsy on another machine, with similar partitioning scheme (with WinXP on the first partition, separate /home and several Linux systems as well). Then I'll let you know. -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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
Re: [Bug 135370] Re: [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
I just did what I've said earlier: I started the installation of Ubuntu Gutsy Tribe-5 on my laptop. The 5% stop with mount.ntfs happened again, with the same solution. So in my case the problem is repeatable. And now for something completely different... ;-) I noticed that the current installer is stubborn and doesn't want to install over an empty, existing ext3 partition (I just did 'rm -rf *' there) and insists on formatting it, as well as swap partition (sic!). Having partitions in /etc/fstab mounted via UUID= (which is changed upon reformat) means to me that I am forced to manually edit all fstab files in other Linux systems I have on this machine. Sigh... Plus, in the 'Edit partition' popup the partitioner doesn't allow a simple 'Advanced' button to specify additional options for mounting a partition - like PCLOS or SUSE have for example. Just the filesystem size, type and mount point, rest are plain defaults. I can work around it and I know how, but... Sigh. -- [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs https://bugs.launchpad.net/bugs/135370 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 135370] [gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
Public bug reported: Binary package hint: ubiquity After manual partitioning installer stopped/froze displaying 5% - creating a filesystem message. I've found a suspicious program (/sbin/mount.ntfs) using process list that looked like the reason of the trouble. After killing it the installation process continued correctly and then the final message was shown. After that the /target, /target/data and /target/mnt/winxp partitions were left mounted, while other /target/mnt/* partitions were unmounted correctly. Looks like some problem with fuse and/or ntfs-3g to me. I admit, I have a complicated disk layout, with separate home partition (mounted as /data and symlinked), many Linux partitions and several of them are even unformatted. Since I was able to complete the install, the problem I described is not a big deal for me. I wonder, however, if other people may find themselves in the same situation. All the meaty details below: $ ps axf PID TTY STAT TIME COMMAND 2 ?S 0:00 [kthreadd] 3 ?S 0:00 \_ [migration/0] 4 ?SN 0:00 \_ [ksoftirqd/0] 5 ?S 0:00 \_ [watchdog/0] 6 ?S 0:00 \_ [events/0] 7 ?S 0:00 \_ [khelper] 27 ?S 0:00 \_ [kblockd/0] 28 ?S 0:00 \_ [kacpid] 29 ?S 0:00 \_ [kacpi_notify] 132 ?S 0:00 \_ [kseriod] 156 ?S 0:00 \_ [pdflush] 157 ?S 0:00 \_ [kswapd0] 208 ?S 0:00 \_ [aio/0] 2023 ?S 0:00 \_ [khpsbpkt] 2034 ?S 0:00 \_ [knodemgrd_0] 2037 ?S 0:00 \_ [ata/0] 2038 ?S 0:00 \_ [ata_aux] 2049 ?S 0:00 \_ [scsi_eh_0] 2050 ?S 0:00 \_ [scsi_eh_1] 2051 ?S 0:00 \_ [scsi_eh_2] 2073 ?S 0:00 \_ [ksuspend_usbd] 2074 ?S 0:00 \_ [khubd] 2218 ?S 0:00 \_ [scsi_eh_3] 2219 ?S 0:00 \_ [scsi_eh_4] 2981 ?S 0:00 \_ [unionfs_siod/0] 3010 ?S 0:00 \_ [loop0] 6935 ?S 0:00 \_ [kgameportd] 7023 ?S 0:00 \_ [rt2500pci] 7041 ?S 0:00 \_ [kpsmoused] 8253 ?S 0:00 \_ [kondemand/0] 8756 ?S 0:00 \_ [krfcommd] 9953 ?S 0:00 \_ [jfsIO] 9954 ?S 0:00 \_ [jfsCommit] 9955 ?S 0:00 \_ [jfsSync] 9976 ?S 0:00 \_ [xfslogd/0] 9977 ?S 0:00 \_ [xfsdatad/0] 30752 ?S 0:00 \_ [pdflush] 31000 ?S 0:00 \_ [kjournald] 31011 ?S 0:00 \_ [kjournald] 31022 ?S 0:00 \_ [kjournald] 31028 ?S 0:00 \_ [kjournald] 31034 ?S 0:00 \_ [kjournald] 1 ?Ss 0:01 /sbin/init 5898 ?Ss0:00 /sbin/udevd --daemon 7918 tty4 Ss 0:00 /bin/login -f 7921 tty4 S+ 0:00 \_ -bash 7922 tty5 Ss 0:00 /bin/login -f 7925 tty5 S+ 0:00 \_ -bash 7928 tty2 Ss 0:00 /bin/login -f 7946 tty2 S+ 0:00 \_ -bash 7932 tty3 Ss 0:00 /bin/login -f 7935 tty3 S+ 0:00 \_ -bash 7936 tty1 Ss 0:00 /bin/login -f 7937 tty1 S+ 0:00 \_ -bash 7938 tty6 Ss 0:00 /bin/login -f 7941 tty6 S+ 0:00 \_ -bash 8221 ?Ss 0:00 /usr/sbin/acpid -c /etc/acpi/events -s /var/run/acpid.socket 8311 ?Ss 0:00 /sbin/syslogd 8368 ?S 0:00 /bin/dd bs 1 if /proc/kmsg of /var/run/klogd/kmsg 8370 ?Ss 0:00 /sbin/klogd -P /var/run/klogd/kmsg 8391 ?Ss 0:00 /usr/bin/dbus-daemon --system 8407 ?Ssl0:00 /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.pid 8421 ?Ss 0:00 /usr/sbin/NetworkManagerDispatcher --pid-file /var/run/NetworkManager/NetworkManagerDispatcher.pid 8434 ?Ss 0:00 /usr/bin/system-tools-backends 8435 ?S 0:00 \_ dbus-daemon --session --print-address --nofork 8451 ?Ss 0:01 /usr/sbin/hald 8452 ?S 0:00 \_ hald-runner 8459 ?S 0:00 \_ hald-addon-keyboard: listening on /dev/input/event1 8460 ?S 0:00 \_ hald-addon-keyboard: listening on /dev/input/event4 8461 ?S 0:00 \_ hald-addon-keyboard: listening on /dev/input/event5 8462 ?S 0:00 \_ hald-addon-keyboard: listening on /dev/input/event6 8464 ?S 0:00 \_ /usr/lib/hal/hald-addon-cpufreq 8465 ?S 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.socket 8471 ?S 0:00 \_ hald-addon-storage: no polling because /dev/hdc is locked via O_EXCL 8473 ?S 0:00 \_ hald-addon-storage: polling /dev/hdd (every 2 sec) 8623 ?Ssl0:00 /usr/sbin/console-kit-daemon 8706 ?Ss 0:00 avahi-daemon: running [ubuntu.local] 8707 ?Ss 0:00 \_ avahi-daemon: chroot
[Bug 108528] Re: [regression] cannot connect to WEP-protected access point in Feisty
** Attachment added: output of lsmod | sort http://librarian.launchpad.net/7380575/rt2500-feisty-lsmod-sort.txt -- [regression] cannot connect to WEP-protected access point in Feisty https://bugs.launchpad.net/bugs/108528 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 108528] Re: [regression] cannot connect to WEP-protected access point in Feisty
** Attachment added: output of lspci -v http://librarian.launchpad.net/7380583/rt2500-feisty-lspci-v.txt -- [regression] cannot connect to WEP-protected access point in Feisty https://bugs.launchpad.net/bugs/108528 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 108528] Re: [regression] cannot connect to WEP-protected access point in Feisty
** Attachment added: output of lspci -vv http://librarian.launchpad.net/7380585/rt2500-feisty-lspci-vv.txt -- [regression] cannot connect to WEP-protected access point in Feisty https://bugs.launchpad.net/bugs/108528 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 108528] [regression] cannot connect to WEP-protected access point in Feisty
Public bug reported: Binary package hint: rt2500 Media used: Ubuntu 7.04 desktop i386 LiveCD My computer has ASUS A8V Deluxe motherboard, with ASUS WiFi-g WL-130g wireless PCI card (RaLink-based chipset, operated by rt2500 module). Symptoms: Network Manager doesn't work. It correctly displays access point's ESSID, asks for WEP 128-bit Passphrase, but is unable to connect. Manual configuration which worked flawlessly in Ubuntu 6.06 and 6.10 doesn't help either. I tried to comment out all auto IFACE lines in /etc/networking/interfaces and add the following section: iface ra0 inet dhcp wireless-essid przestrzen wireless-key REAL-26-CHARS-LONG-HEX-KEY auto ra0 Then I did the following: # ifdown ra0 # modprobe -r rt2500 # modprobe rt2500 # /etc/init.d/networking restart This procedure works in current Ubuntu 6.10 installation. However, in Ubuntu 7.04 it fails. This is bad, because it leaves the machine without any internet connection. Additional information: # uname -a Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux # dpkg -l | grep linux-image ii linux-image-2.6.20-15-generic 2.6.20-15.27 Linux kernel image for version 2.6.20 on x86 ii linux-image-generic2.6.20.15.14 Generic Linux kernel image ** Affects: rt2500 (Ubuntu) Importance: Undecided Status: Unconfirmed -- [regression] cannot connect to WEP-protected access point in Feisty https://bugs.launchpad.net/bugs/108528 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 64765] Re: [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished
I've found one more quirk, namely in chapter: 6.3. Using Individual Components (installation-guide-i386/en/ch06s03.html) in subsection 6.3.1.3. Choosing a Keyboard the guide claims that it is possible to configure the keyboard by using kbdconfig program. However, after installation no such program can be found, both under normal and administrative account. (i.e. both $ kbdconfig and $ sudo kbdconfig lead to an error) SUGGESTION: Since the keyboard can be configured now by the means of: dpkg-reconfigure console-setup consider replacing the kbdconfig invocation by the above command. -- [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished https://launchpad.net/bugs/64765 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64765] Re: [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished
Additionally, I've found that using the debootstrap method shadow passwords are turned off by default. I think it would be beneficial to mention the following command: # shadowconfig on Probably near the base system installation, before adding a user account for normal operations. -- [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished https://launchpad.net/bugs/64765 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64765] Re: [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished
I evaluated more the alternative installation method, Installing Ubuntu from a Unix/Linux System and I have further suggestions. First of all, languages and locales. By following the guide to the letter one still will not have a full native language support. It turns out that additional steps are necessary. Also, the default user is missing several useful abilities by not being added to the right groups. SUGGESTIONS: 1. After installing ubuntu-desktop using tasksel one should issue: # sudo apt-get install language-support-de or similar (just change -de to another language) to get a full native language support. 2. It's also necessary to run: # sudo tzconfig to prevent the system from warning about time zone being set to Unknown at the first system upgrade. This is especially annoying, as one must click on the embedded Terminal control inside Synaptics progress window and type y, name of the region and capital *while doing the upgrade*. (user surprised, upgrade seems to hang) 3. It may be also advisable to run: # sudo editor /etc/default/rcS and change UTC=yes to UTC=no if one doesn't want to use universal time (it's wise to turn off UTC if one runs Windows on the same machine, for example). 4. Default system-wide locale can be set by issuing: # sudo echo LANGUAGE=\de_DE:de:en_US:en\ /etc/environment # sudo echo LANG=de_DE.UTF8 /etc/environment (substitute de_DE:de for any other language you need). This influences the default language on the gdm login screen. 5. Default user (with administrative privileges) cannot hear or play any sound by default, as well as doing some typical activities like using USB disks. It's easy to change this by adding the account to the right groups: # sudo adduser myusername cdrom floppy audio plugdev If you think it's worth to add some more commands to the guide in order to make it more on par with default Ubuntu installation, then please consider to do so. Especially since the guide recommends to install ubuntu-desktop task, but doesn't help with setting the system in a similar way like the LiveCD installer does. -- [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished https://launchpad.net/bugs/64765 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64765] Re: [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished
First of all, thank you for a quick action and accurate reply! I was able to repeat the steps on another machine, using the updated guide. Still, the devices in /dev were missing. But now this is quite understandable, simply because it contains only the files from /usr/lib/debootstrap/devices.tar.gz file (see attached default-dev.txt file). As a workaround one can do (at least in Linux, not sure about other OS's): # mount --bind /dev /mnt/ubuntu/dev before chrooting into installation environment, to use the /dev hierarchy of the running host system. Alternatively, one can mknod required devices in chroot just before installing grub and then remove them safely, because Linux kernel + udev should handle this gracefully from now on. ** Attachment added: Comparison between /mnt/ubuntu/dev and debootstrap's devices.tar.gz http://librarian.launchpad.net/4780586/default-dev.txt -- [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished https://launchpad.net/bugs/64765 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64765] installation-guide-i386 for Edgy - several steps are misleading or cannot be finished
version: sudo tasksel install ubuntu-desktop took almost an hour (it was a slow machine, 1,7 Celeron, 256MB RAM), but eventually it succeeded. It was a reat reward after all the struggle! :) Finishing thoughts: I'm not sure if these are the real, repeatable problems or if this was the classical example of PEBKAC. I suggest someone to take a similar approach and try to install Edgy using this method, before making a final release. Some of these problems may quite easily be resolved by changing the dependencies of packages. Some may require documenting additional steps. I've managed to overcome all those hurdles, but given the fact that they exist today means that the current documentation is at least misleading. Please look into it, if you have time. I was abel to deal with this breakage, but not everyone have to be so lucky. With best regards, Wiktor Wandachowicz ** Affects: installation-guide (Ubuntu) Importance: Undecided Status: Unconfirmed -- installation-guide-i386 for Edgy - several steps are misleading or cannot be finished https://launchpad.net/bugs/64765 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64765] Re: installation-guide-i386 for Edgy - several steps are misleading or cannot be finished
savedefault option in menu.lst prevented the system from starting. Removing this line resolved this problem for good. 11. installing the Ubuntu Desktop via: sudo tasksel install ubuntu-standard ubuntu-desktop was unsuccessful (there is no ubuntu-standard task). The shorter version: sudo tasksel install ubuntu-desktop took almost an hour (it was a slow machine, 1,7 Celeron, 256MB RAM), but - eventually it succeeded. It was a reat reward after all the struggle! :) - + eventually it succeeded. It was a great reward after all the struggle! + :) Finishing thoughts: I'm not sure if these are the real, repeatable problems or if this was the classical example of PEBKAC. I suggest someone to take a similar - approach and try to install Edgy using this method, before making a - final release. Some of these problems may quite easily be resolved by - changing the dependencies of packages. Some may require documenting - additional steps. + approach and try to install Edgy using this method before making a final + release. Some of these problems may quite easily be resolved by changing + the dependencies of packages. Some may require documenting additional + steps. I've managed to overcome all those hurdles, but given the fact that they exist today means that the current documentation is at least misleading. - Please look into it, if you have time. I was abel to deal with this + Please look into it if you have time. I was able to deal with this breakage, but not everyone have to be so lucky. With best regards, Wiktor Wandachowicz ** Summary changed: - installation-guide-i386 for Edgy - several steps are misleading or cannot be finished + installation-guide-i386 [Edgy] - several steps are misleading or cannot be finished ** Summary changed: - installation-guide-i386 [Edgy] - several steps are misleading or cannot be finished + [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished ** Tags added: installer -- [Edgy] installation-guide-i386 - several steps are misleading or cannot be finished https://launchpad.net/bugs/64765 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
