[Bug 632026] Re: simple-scan fails to scan: invalid argument
I found a fix someone else posted: http://ubuntu-ky.ubuntuforums.org/showthread.php?p=9943325 In summary: Edit /etc/sane.d/dll.conf, comment out the line "epson2" and un-comment the line "epson". -- simple-scan fails to scan: invalid argument https://bugs.launchpad.net/bugs/632026 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 632026] Re: simple-scan fails to scan: invalid argument
Fault still exists in release version of Ubuntu 10.10 i386 Desktop. -- simple-scan fails to scan: invalid argument https://bugs.launchpad.net/bugs/632026 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 632026] [NEW] simple-scan fails to scan: invalid argument
Public bug reported: Binary package hint: simple-scan Ubuntu 10.10 beta st...@steve-desktop:~$ apt-cache policy simple-scan simple-scan: Installed: 2.31.91-1ubuntu1 Candidate: 2.31.91-1ubuntu1 Version table: *** 2.31.91-1ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages 100 /var/lib/dpkg/status Simple-scan appears to detect my scanner properly (Epson Perfection 640 USB scanner) but when I try to start a scan it pops up an error box saying "Failed to scan, unable to start scan". When running from command line, it prints this error message: st...@steve-desktop:~$ simple-scan ** (simple-scan:2477): WARNING **: Unable to start device: Invalid argument ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New -- simple-scan fails to scan: invalid argument https://bugs.launchpad.net/bugs/632026 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 632021] [NEW] flegita crashes trying to scan
Public bug reported: Binary package hint: flegita Ubuntu 10.10 beta st...@steve-desktop:~$ apt-cache policy flegita flegita: Installed: 0.6.2-0ubuntu2 Candidate: 0.6.2-0ubuntu2 Version table: *** 0.6.2-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages 100 /var/lib/dpkg/status When run from command line, flegita appears to work until I click the scan button, then crashes. st...@steve-desktop:~$ flegita ** (flegita:2423): DEBUG: Initializing gnome-scan 0.6.2 for flegita (flegita) ** (flegita:2423): DEBUG: gsane-module.c:39: SANE version is 1.0.21 (flegita:2423): GLib-CRITICAL **: g_utf8_strlen: assertion `p != NULL || max == 0' failed ** (flegita:2423): DEBUG: Number of options ((null)): ** (flegita:2423): DEBUG: gint none (GParamInt), (null) ** (flegita:2423): DEBUG: default = 37 ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: === Device Epson Perfection640 (37 options) === ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: -- Group « Scan Mode » -- ** (flegita:2423): DEBUG: Scan mode (mode): ** (flegita:2423): DEBUG: gchararray none (GSParamEnumSpec), {"Lineart", "Gray", "Color"} ** (flegita:2423): DEBUG: default = "Lineart" ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Bit depth (depth): ** (flegita:2423): DEBUG: gint none (GSParamEnumSpec), {8} ** (flegita:2423): DEBUG: default = 8 ; flags = {} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Halftoning (halftoning): ** (flegita:2423): DEBUG: gchararray none (GSParamEnumSpec), {"None", "Halftone A (Hard Tone)", "Halftone B (Soft Tone)", "Halftone C (Net Screen)"} ** (flegita:2423): DEBUG: default = "Halftone A (Hard Tone)" ; flags = {} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Dropout (dropout): ** (flegita:2423): DEBUG: gchararray none (GSParamEnumSpec), {"None", "Red", "Green", "Blue"} ** (flegita:2423): DEBUG: default = "None" ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Brightness (brightness): ** (flegita:2423): DEBUG: gint none (GSParamRangeSpec), [0;1;0] ** (flegita:2423): DEBUG: default = 0 ; flags = {} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Sharpness (sharpness): ** (flegita:2423): DEBUG: gint none (GSParamRangeSpec), [-2;1;2] ** (flegita:2423): DEBUG: default = 0 ; flags = {} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Gamma Correction (gamma-correction): ** (flegita:2423): DEBUG: gchararray none (GSParamEnumSpec), {"User defined (Gamma=1.0)", "User defined (Gamma=1.8)"} ** (flegita:2423): DEBUG: default = "User defined (Gamma=1.8)" ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Color correction (color-correction): ** (flegita:2423): DEBUG: gchararray none (GSParamEnumSpec), {"None", "Built in CCT profile", "User defined CCT profile"} ** (flegita:2423): DEBUG: default = "Built in CCT profile" ; flags = {} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Scan resolution (resolution): ** (flegita:2423): DEBUG: gint dpi (GSParamEnumSpec), {75, 150, 300, 600} ** (flegita:2423): DEBUG: default = 75 ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Threshold (threshold): ** (flegita:2423): DEBUG: gint none (GSParamRangeSpec), [0;1;255] ** (flegita:2423): DEBUG: default = 128 ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: -- Group « Advanced » -- ** (flegita:2423): DEBUG: Mirror image (mirror): ** (flegita:2423): DEBUG: gboolean none (GParamBoolean), (null) ** (flegita:2423): DEBUG: default = FALSE ; flags = {} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Auto area segmentation (auto-area-segmentation): ** (flegita:2423): DEBUG: gboolean none (GParamBoolean), (null) ** (flegita:2423): DEBUG: default = TRUE ; flags = {} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Red intensity (red-gamma-table): ** (flegita:2423): DEBUG: gint none (GSParamRangeSpec), [0;1;255] ** (flegita:2423): DEBUG: default = 0 ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Green intensity (green-gamma-table): ** (flegita:2423): DEBUG: gint none (GSParamRangeSpec), [0;1;255] ** (flegita:2423): DEBUG: default = 0 ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Blue intensity (blue-gamma-table): ** (flegita:2423): DEBUG: gint none (GSParamRangeSpec), [0;1;255] ** (flegita:2423): DEBUG: default = 0 ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: Wait for Button (wait-for-button): ** (flegita:2423): DEBUG: gboolean none (GParamBoolean), (null) ** (flegita:2423): DEBUG: default = FALSE ; flags = {writable} ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: ** (flegita:2423): DEBUG: -- Group « Color correction » -- ** (flegita:2423): DEBUG: CCT Profile Type (cct-type): ** (flegita:2423): DEBUG: gchararray none (GSParamEnumSpec), {"Automatic", "Reflectiv
[Bug 632000] [NEW] Scanner utility crashes - fletiga no such file
Public bug reported: Binary package hint: flegita Ubuntu 10.10 beta The Graphics menu offers an application "Scanner Utility". However, this crashes when I try to launch it with an error "fletiga" (no such file or directory). Perhaps a message saying you need to install the flegita package would be more helpful. ** Affects: gnomescan (Ubuntu) Importance: Undecided Status: New -- Scanner utility crashes - fletiga no such file https://bugs.launchpad.net/bugs/632000 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 558627] Re: Power manager mistakenly thinks my battery power is critically low, and hibernates -- MSI Wind U100
This procedure fixed it for me (Advent 4211 which is a wind clone): Press Ctrl-Alt-F2 and use the pop-up to launch gconf-editor. Navigate to Apps / gnome-power-manager / general. De-select the option use_time_for_policy. No need to restart, just close the config editor. I read in another forum thread that the same problem / workround also work on a Dell Vostro 1310. -- Power manager mistakenly thinks my battery power is critically low, and hibernates -- MSI Wind U100 https://bugs.launchpad.net/bugs/558627 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 545064] Re: kubuntu lucid beta1 can't get IP address
And here's the log file ** Attachment added: "wicd.log" http://launchpadlibrarian.net/41715356/wicd.log -- kubuntu lucid beta1 can't get IP address https://bugs.launchpad.net/bugs/545064 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 545064] Re: kubuntu lucid beta1 can't get IP address
** Attachment added: "snapshot1.png" http://launchpadlibrarian.net/41715325/snapshot1.png -- kubuntu lucid beta1 can't get IP address https://bugs.launchpad.net/bugs/545064 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 545064] [NEW] kubuntu lucid beta1 can't get IP address
Public bug reported: Binary package hint: wicd Installed wicd on kubuntu Lucid beta1 desktop 386. Wicd is unable to connect to access point. It fails at the stage of trying to get an IP address. While it's trying to get an IP address, the status bar shows lots of hex strings which might be a clue. I attach a screenshot an d acopy of wicd.log, although it doesn't seem to say anything interesting. I know the hardware works because knetworkmanager connects reliably (I want wicd so I can have wireless without a gui). Network hardware is: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection ** Affects: wicd (Ubuntu) Importance: Undecided Status: New -- kubuntu lucid beta1 can't get IP address https://bugs.launchpad.net/bugs/545064 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 542778] Re: Alternate CD unable to create partition
Aargh. copy/paste error typing out the partition table. Sorry, Herre is the correct partiton table (#8 is 102GB not 10GB). /dev/sda - 160.0 GB ATA WDC WD1600BJKT-7 #1 primary 238.5 MB fat16 #2 primary 21.0 GB B ntfs #5 logical 10.5 GB jfs #6 logical 10.5 GB jfs #7 logical5.2 GB F swap swap #8 logical 102.0 GB jfs pri/log 10.6 GB FREE SPACE -- Alternate CD unable to create partition https://bugs.launchpad.net/bugs/542778 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 542778] [NEW] Alternate CD unable to create partition
Public bug reported: Binary package hint: base-installer Alternate installer is unable to create a new partition to install into. Using manual partitioning. Here is the existing partition table it shows me: /dev/sda - 160.0 GB ATA WDC WD1600BJKT-7 #1 primary 238.5 MB fat16 #2 primary 21.0 GB B ntfs #5 logical 10.5 GB jfs #6 logical 10.5 GB jfs #7 logical5.2 GB swap swap #8 logical 10.5 GB jfs pri/log 10.6 GB FREE SPACE I was trying to create a partition in the free space at the end, but could not. I tried to fill the space (default) and also tried to create a small (500M) partition both at the start and at the end of the free space. In every case I said I wanted a logical partition. In every case, the partitioner gave an error "Can't have overlapping partitions.". It was prepared to create a primary partition in the space, but this is not what I wanted. I rebooted into Karmic and verified with gparted that the free space was indeed inside the extended partition, meaning the extended partition ended at the end of the disk, not at the end of partition #8 with the free space afterwards. I was able to create the logical partitions I wanted inside that free space using gparted from Karmic, without resizing the extended partition. ** Affects: base-installer (Ubuntu) Importance: Undecided Status: New -- Alternate CD unable to create partition https://bugs.launchpad.net/bugs/542778 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 525291] [NEW] Live CT triggers security alert
Public bug reported: A couple of times recently, I have started an Ubuntu live CD at work, shortly after which I get an upset security guy wanting to know why my IP address is trying to log into lots of the network infrastructure. Sure enough I can see that as I started the live CD, all switches in the building sent an Authentication Failed trap to their management systems, naming my IP address as the source of the failed access attempt. IT are suspicious enough of Linux and open source software in general as it is, and finding out that Ubuntu is trying to access all the local network infrastructure without permission and without the users knowlege only serves to prove their suspicions correct. I have just started a live CD at home while watching it with wireshark, and I think the cause of the problem is that the live CD broadcasts an SNMP GET (actually, a local subnet multicast) with a community string set to "public". I have no idea what process does this, but I think it's a Really Bad Idea. It means I can't start a live CD at work because the security folk will have a hissi fit, and I really can't imagine that it would ever glean anything useful from the results anyway. So I would like to propose that you remove this "feature" from future releases. I specifically saw this behaviour in the Karmic 9.10 i386 Desktop live/installer CD. ** Affects: ubuntu Importance: Undecided Status: New -- Live CT triggers security alert https://bugs.launchpad.net/bugs/525291 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 435352] Re: regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails
@knuutsen@ Thanks for the help. You are right, I forgot the binary-indep step after the compile. I have now managed to install and run my home-compiled kernel. Hooray! Now I can start trying different values for the udelay. Steve -- regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails https://bugs.launchpad.net/bugs/435352 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 435352] Re: regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails
Gah! I'm so far behind you guys! I followed the procedure in #126 with little or no comprehension of what I was doing. Copy/paste, so I shouldn't have got it wrong. Woke up this morning and found that I only have 2 of the 5 debs I'm supposed to have: linux-headers-2.6.31-15-core2_2.6.31-15.49_i386.deb linux-image-2.6.31-15-core2_2.6.31-15.49_i386.deb Any idea where I might have gone wrong? Those won't install on their own because of dependencies on the missing ones. -- regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails https://bugs.launchpad.net/bugs/435352 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 435352] Re: regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails
@jbob (#119): Is there a bug A (on the camera problem/USB itself)? I still haven't found one. @Stefan, Catcrash: I don't know how to compile a kernel. But if you can show me how or provide a link to a download, I will be happy to try it out and give feedback. I have an Advent wind clone. -- regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails https://bugs.launchpad.net/bugs/435352 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 435352] Re: regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails
It's not the failure to fix it I'm upset about. There's not anything the Ubuntu folk can really do other than report upstream. I know that. And I read that there already has been upstream discussion. It's the self deception, pretending that it's fixed that bothers me. Makes the fix rate look good though, doesn't it. I suspect that's what really matters. If there is another bug report somewhere that says the problem has been reported upstream and awaits a fix then I owe an apology. But I haven't seen a link to any such report - I think the problem has been just made to go away. So there's nowhere I can keep watch on to see if there's ever any progress towards a fix. Because of course, it already IS fixed, isn't it? -- regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails https://bugs.launchpad.net/bugs/435352 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 435352] Re: regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails
It looks to me as though their "fix" is to make a note in the relase note and then completely ignore the bug. They don't even have the courage to actually admit here that that's what theyre doing. "Fix released" they say. The bureaucrats have well and truly taken over. With that kind of attitude floating around, it's no wonder that this release of Ubuntu is the most problematic I have seen for years. But then, maybe I only think it has problems because I didn't read the small print. -- regression: uvcvideo module makes "cannot reset port" error on usb with bison webcam (5986:0203): USB and suspend fails https://bugs.launchpad.net/bugs/435352 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 480601] Re: mysql 5.1 client segfault talking to 4.0 server
OK. It took a while to figure out that I don't get any output from mysql - no prompt. But it did crash appropriately when I entered the status command. Debug output attached (IP address and username manually edited). ** Attachment added: "gdb-mysql.txt" http://launchpadlibrarian.net/35582257/gdb-mysql.txt -- mysql 5.1 client segfault talking to 4.0 server https://bugs.launchpad.net/bugs/480601 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 480601] [NEW] mysql 5.1 client segfault talking to 4.0 server
Public bug reported: Binary package hint: mysql-client-5.1 Connecting to an old (4.0) mysql server. Segfault when using the "status" command. I also find that mysql-admin crashes when trying to look at the server status, and I presume it is the same problem. This is using Ubuntu 9.10 as the client OS (server is on windows). Here is a copy of my login session: st...@dingly:~$ mysql -h 1.2.3.4 -u -p -C Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 9966075 Server version: 4.0.22-debug-log Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> status -- mysql Ver 14.14 Distrib 5.1.37, for debian-linux-gnu (i486) using EditLine wrapper Connection id: 9966075 SSL:Not in use Current pager: stdout Using outfile: '' Using delimiter:; Server version: 4.0.22-debug-log Protocol version: 10 Connection: 1.2.3.4 via TCP/IP ERROR 1193 (HY000): Unknown system variable 'character_set_client' ERROR 1193 (HY000): Unknown system variable 'character_set_client' Segmentation fault st...@dingly:~$ ** Affects: mysql-dfsg-5.1 (Ubuntu) Importance: Undecided Status: New -- mysql 5.1 client segfault talking to 4.0 server https://bugs.launchpad.net/bugs/480601 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 434941] [NEW] ubiquity crashes runnung update-grub
Public bug reported: Binary package hint: ubiquity Karmic alpha- 6 i386 desktop, installing from USB stick (created with Jaunty USB boot stick creator) onto a Dell E5500. Using custom partitioning to install to a preexisting (ex Intrepid) partition. Installation runs normally until the stage "running update-grub" at which point the ubiquity window closes without warning. On rebooting, Karmic produces a few error messages and then a totally black screen (I think the backlight is turned off too). The kernel is alive because Ctrl-Alt-Delete causes a reboot. Booting into recovery mode I can see errors about a read-only filesystem. Running fsck on the ext4 / partition and then rebooting allows Karmic to boot to GDM and I can log in to a normal desktop. Possible causes - I also have Jaunty installed on a JFS partition on the install disk, which is unusual and may be acting as a trigger for this bug. Also possibly significant - while the installer is booting from USB I see error messages about being unable to read from (if I remember right) sr0. I have tried this 3 times with the same result. I have re-checked the MD5sum of the ISO image and re-created the USB stick. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- ubiquity crashes runnung update-grub https://bugs.launchpad.net/bugs/434941 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 408532] Re: tty uk keyboard map wrong
P.S. In case it's relevant - the computer in question is a Dell Latitude E5500 laptop. -- tty uk keyboard map wrong https://bugs.launchpad.net/bugs/408532 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 408532] [NEW] tty uk keyboard map wrong
Public bug reported: Ubuntu Karmic Koala alpha3 After specifying a UK keyboard during installation, the keyboard mapping on the TTY consoles is wrong. It appears to be mainly a US keyboard layout, but shift-2 and shift-3 don't seem to work at all. As it happens, this prevented me from logging in using a tty because of the password chosen during install. No such problem with the Gnome terminal keyboard layout which appears to be perfect - just the TTY console layout. It may be significant that the installer crashes during the GRUB install and so doesn't complete fully - I'm not sure at what point the TTY keyboard layout gets cocnfigured. ** Affects: ubuntu Importance: Undecided Status: New -- tty uk keyboard map wrong https://bugs.launchpad.net/bugs/408532 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 408516] [NEW] ubiquity crash while installing grub
Public bug reported: Binary package hint: ubiquity Karmic Koala Alpha3. Installer crashed while installing GRUB. I think it was looking for other operating systems at the time. Actually, every installer has done this for a couple of years or more on my system. I suspect it may be because I have one / partition housed on JFS. Here is my fdisk -l: Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xb800 Device Boot Start End Blocks Id System /dev/sda1 1 29 232911 de Dell Utility /dev/sda2 * 30257920482345+ 7 HPFS/NTFS /dev/sda32580 19457 1355725355 Extended /dev/sda52580385410241406 83 Linux /dev/sda63855512910241406 83 Linux /dev/sda751305766 5116671 82 Linux swap / Solaris /dev/sda85767 19457 109972926 83 Linux and blkid: /dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="07D9-0603" TYPE="vfat" /dev/sda2: UUID="E0D4E1AED4E186DE" TYPE="ntfs" /dev/sda5: UUID="f00b4cfc-e4ed-4fa7-a9bb-6fc2c86f9f10" TYPE="jfs" /dev/sda6: UUID="a9536fa0-93cb-4aa8-8566-ecd184a9ed1d" TYPE="ext4" /dev/sda7: TYPE="swap" UUID="27539b62-3acd-454c-8ce8-b5e3dc01f7c6" /dev/sda8: UUID="f59c8794-0b38-4d7b-933b-eb3dfb3784b8" TYPE="jfs" GRUB was in fact succesfully installed (using sda6 as root), but didn't list sda5 as an operating system option. I was able to boot and edit brub.cfg by hand to add the sda5 boot option. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- ubiquity crash while installing grub https://bugs.launchpad.net/bugs/408516 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 357257] Re: nautilus crash showing long filename
Correction: The html file crashes the gnome-panel when I view the file in FIREFOX, not nautilus as I wrote. Sorry. -- nautilus crash showing long filename https://bugs.launchpad.net/bugs/357257 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 357257] Re: nautilus crash showing long filename
** Attachment added: "CrashNautilus.tar" http://launchpadlibrarian.net/24970883/CrashNautilus.tar -- nautilus crash showing long filename https://bugs.launchpad.net/bugs/357257 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 357257] [NEW] nautilus crash showing long filename
Public bug reported: Binary package hint: nautilus The attached tar file contains a file with a name that makes nautilus crash. The filename contains two UTF8 3-byte sequences which I think represent a pair ot Line Separator characters, but it's nto as simple as that because shortening the filename makes the problem go away, as does replacing the odd characters. The tar file also contains a small HTML file. The page title is the same as the filename that crashes nautilus. When I view this document in nautilus, my gnome-panel crashes repeatedly until I swithch away from that page. I think gnome-panel is crashing trying to diaplay the title in the Window List applet. Note that this just might have the same root cause as bug #28640, but I'm not sure. I can see the file name OK in a gnome-terminal shell. The crash is apparent in both Ubuntu 8.10 and in 9.04 beta. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- nautilus crash showing long filename https://bugs.launchpad.net/bugs/357257 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 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
It's a bug to my mind. It prevents me from browsing to the camera. Something I have done regularly for years. Fortunately, it's easily fixed like this: *sudo killall gvfs-gphoto2-volume-monitor sudo chmod -x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor* 2009/3/28 David Tombs > This is a bug. The problem is that whatever app has it locked is not > letting go. > > If I plug in my camera, I cannot access it in any application. I do not > get the normal "You have just inserted..." prompt, and I cannot mount it > manually. This is not expected behavior. > > ** Changed in: gvfs (Ubuntu) > Status: Invalid => Confirmed > > -- > Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 > could not lock the device message > https://bugs.launchpad.net/bugs/285682 > You received this bug notification because you are a direct subscriber > of the bug. > -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 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 347361] Re: libsnmp-python segmentation fault
** Attachment added: "CrashTest.py" http://launchpadlibrarian.net/24276402/CrashTest.py -- libsnmp-python segmentation fault https://bugs.launchpad.net/bugs/347361 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 347361] [NEW] libsnmp-python segmentation fault
Public bug reported: Binary package hint: libsnmp-python Using the snmp python bindings, I can walk the system mib (of the localhost Ubuntu machine) but I get a segmentation fault when I try to walk the hrStorage mib. Walking the mib using snmpwalk from the command line fetches the table without any problem, so I think the problem is in the python bindings and not the net-anmp package. Ubuntu version 8.10 (Intrepid): package version: libsnmp-python 5.4.1~dfsg-7.1ubuntu6.1 Attached is a small python program that demonstrates the problem. You have to install snmpd and configure it by mapping community public to readonly rather than paranoid first. ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New -- libsnmp-python segmentation fault https://bugs.launchpad.net/bugs/347361 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 326351] [NEW] sane crashes, invalid argument, v4l:/dev/video0
Public bug reported: Binary package hint: libsane Whan starting xsane, it crashes with the following popup error: Failed to open device 'v4l:/dev/video0': Invalid argument. This is on an Advent 4211 which I believe is an MSI Wind clone. Ubuntu 8.10 Intrepid OS. The error happens even if I have no scanner attached. I think the problem is actually the built-in web-cam. scanimage -L reports: device `v4l:/dev/video0' is a Noname USB 2.0 Camera virtual device and lsusb reports: Bus 005 Device 003: ID 0c45:62c0 Microdia Pavilion Webcam I have discovered that I can get rid of the error message by commenting out the line /dev/video0 in the file /etc/sane.d/v4l.conf. ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New -- sane crashes, invalid argument, v4l:/dev/video0 https://bugs.launchpad.net/bugs/326351 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 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
More info. When I plug the camera in and I am logged into gnome, the camera does not work. Gnome offers to open the camera, and sometimes the folder view shows the top-level DCIM directory, but it hangs when I try to look inside that directory. I attach a screenshot of the problem (with a tail of /var/log/messages behind). I notice that the camera does NOT show up in fdisk. However, if I kill GDM and work in text consoles, when I turn the camera on it DOES show up in fdisk as /dev/sdb1. I am then able to mount it, launch startx and browse the camera in nautilus. This demonstrates to me that the problem is not in the kernel USB handling but is misconfiguration of whatever auto-mounts the camera filesystem. Tailing /var/log/messages, these following messages occur that don't occur when a gnome user is logged in: Nov 28 01:18:37 StevesPC kernel: [ 444.138675] scsi7 : SCSI emulation for USB Mass Storage devices Nov 28 01:18:42 StevesPC kernel: [ 449.148557] scsi 7:0:0:0: Direct-Access PENTAX PENTAX OPTIO 550 1.00 PQ: 0 ANSI: 2 Nov 28 01:18:42 StevesPC kernel: [ 449.163535] sd 7:0:0:0: [sdb] 4022272 512-byte hardware sectors (2059 MB) Nov 28 01:18:42 StevesPC kernel: [ 449.181116] sd 7:0:0:0: [sdb] Write Protect is off Nov 28 01:18:42 StevesPC kernel: [ 449.199543] sd 7:0:0:0: [sdb] 4022272 512-byte hardware sectors (2059 MB) Nov 28 01:18:42 StevesPC kernel: [ 449.206534] sd 7:0:0:0: [sdb] Write Protect is off Nov 28 01:18:42 StevesPC kernel: [ 449.211476] sdb: sdb1 Nov 28 01:18:42 StevesPC kernel: [ 449.229683] sd 7:0:0:0: [sdb] Attached SCSI removable disk Nov 28 01:18:42 StevesPC kernel: [ 449.230274] sd 7:0:0:0: Attached scsi generic sg2 type 0 I read in another bug report that gphoto2 was being excluded from Hardy, and I notice that in my screenshot, the non-functional URL is a gphoto2 URL, so I am guessing that this is where the problem lies and it is suppressing the normal mass storage SCSI emulation. ** Attachment added: "Screenshot.png" http://launchpadlibrarian.net/20013673/Screenshot.png -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 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 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
I also habe a problem, with a Pentax optio 550. Worked perfectly with every version of Ubuntu until 8.10. In 8.10, the camera is recognides and I choose to browse as a folder - I always use this method. In intrepid, nautilus freezes trying to browse the camera. While the frozen window is on the screen, dragging it across desktop icons erases them and they don't repaint. Right-clicking the desktop camera icon and choosing to unmount also freezes until I power the camera off or unplug it. gvfs-mount -li returns without printing anything. dmesg shows these lines - they look OK to me... [ 540.908034] usb 2-4: new full speed USB device using ohci_hcd and address 4 [ 541.129424] usb 2-4: configuration #1 chosen from 1 choice [ 541.404169] usbcore: registered new interface driver libusual [ 541.483984] Initializing USB Mass Storage driver... [ 541.497650] scsi6 : SCSI emulation for USB Mass Storage devices [ 541.502535] usbcore: registered new interface driver usb-storage [ 541.504259] USB Mass Storage support registered. [ 541.506317] usb-storage: device found at 4 [ 541.506326] usb-storage: waiting for device to settle before scanning Intrepid was installed from scratch, not an upgrade although the /home partition was previously used by Hardy. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 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 225141] Re: Nautilus doesn't read Domain/user from SMB URLs
Aargh. Hardy is 8.04, not 8.10. Sorry. -- Nautilus doesn't read Domain/user from SMB URLs https://bugs.launchpad.net/bugs/225141 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 225141] [NEW] Nautilus doesn't read Domain/user from SMB URLs
Public bug reported: Binary package hint: nautilus nautilus version 2.2.22 from Hardy (8.10) does not understand SMB URLs - it does not extract the domain name and username. For example, the URL: smb://MYDOMAIN;[EMAIL PROTECTED]/D$ pops up a dialog box filled in with the default values of my username and domain WORKGROUP. In previous versions (Feisty, Gutsy) the domain and username were correctly extracted from the URL into the password dialog box. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus doesn't read Domain/user from SMB URLs https://bugs.launchpad.net/bugs/225141 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 84537] Re: sysctl.conf, net.ipv4.conf.default.forwarding, race condition?
This bug report (marked as a duplicate) fixes it for me: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/156017 -- sysctl.conf, net.ipv4.conf.default.forwarding, race condition? https://bugs.launchpad.net/bugs/84537 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 161183] Re: Printer PPD (HP 1280) errors
Attached my hand-modified file "cupstestppd HP-DeskJet_1280-hpijs.ppd" reports PASS. I load the hpijs PPD because this seems to fix the problem with wrong margins that the default Ubuntu drivers have. Also, the GIMP printer setup doesn't offer an option for Deskjet 1280, so use the PPD file there too. ** Attachment added: "Hand edited PPD" http://launchpadlibrarian.net/10321925/HP-DeskJet_1280-hpijs.ppd -- Printer PPD (HP 1280) errors https://bugs.launchpad.net/bugs/161183 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 161183] Re: Printer PPD (HP 1280) errors
Forgot to mention, this is with Ubuntu version 7.10, hpijs-ppds version 2.7.7 -- Printer PPD (HP 1280) errors https://bugs.launchpad.net/bugs/161183 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 161183] Printer PPD (HP 1280) errors
Public bug reported: Binary package hint: hpijs-ppds The PPD for the HP Deskjet-1280 has naming errors resulting in the user being offered a printer mode of "High Quality" three times in the print dialog. Two of these are actually monochrome and one is also draft quality. Additionally, it appears to be missing a "*End" statement between one pair of definitions. I have a hand-edited correction here, but don't know how to submit it (or if anyone is even interested). ** Affects: hplip (Ubuntu) Importance: Undecided Status: New -- Printer PPD (HP 1280) errors https://bugs.launchpad.net/bugs/161183 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 160833] Dolphin corrupts / forgets smb username and password
Public bug reported: Binary package hint: dolphin This on Gutsy. Dolphin 0.9.2 on KDE 3.5.8 Dolphin fails to remember the username and password after connecting to an SMB share. If you double-click a folder (or try to change up to the parent folder), the user/password dialog is re-presented. Further, the username/password in the re-presented dialog is corrupted by shortening and inserting "..." in the middle. This corruption also occurs on the first username/password dialog if the username is entered on the address bar, e.g. smb://[EMAIL PROTECTED]/share Forgetting the user/pass is bad enough to make SMB with dolphin essentially unuseable. Same problem seems to happen with konqueror. ** Affects: dolphin (Ubuntu) Importance: Undecided Status: New -- Dolphin corrupts / forgets smb username and password https://bugs.launchpad.net/bugs/160833 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 156017] Commented out lines in sysctl.conf wrong
Public bug reported: I want to have IPv4 forwarding enabled when the PC boots. Googling found a forum thread that says to add this line to /etc/sysctl.conf: net.ipv4.ip_forward=1 The above line works. However, the file contains the following commented-out lines: # Uncomment the next line to enable packet forwarding for IPv4 #net.ipv4.conf.default.forwarding=1 The above line does NOT turn IP forwarding on. I suspect (but haven't tested) that every other example line in the file is wrong too. ** Affects: ubuntu Importance: Undecided Status: New -- Commented out lines in sysctl.conf wrong https://bugs.launchpad.net/bugs/156017 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 134918] Re: Misleading error message - software source for package is not enabled
Thanks for the acknowlegement. It just struck me as soon as I saw it that this message was going to be a real slap in the face for noobs. We really don't want to send them away feeling insulted. Hell, even if you understand what the message means, it's not true! How the hell is a noob supposed to cope with that? Still, you've been there, haven't you. Enjoy Linux. Its different to windows, but its not really harder, just different. Similar in some ways, fundamentally different in other ways. But I find it liberating - its more open that Win, and deeper too. There's no point at which you hit a brick wall that says you can't look in here its private. You can get to do computing as opposed to just running applications, if you see the difference (which might take time). Use ubuntuforums.org as a resource. They are friendly and helpful, and more often than not can give you a good answer to your questions. On 15/10/2007, epicflux <[EMAIL PROTECTED]> wrote: > > I'm a noob to installing Ubuntu. I was ready to give up on the install > till I found this forum. I went and checked off the repositories, the > driver installed, and now the graphics card is fully operational. A link > (or hint) to the Software Sources would have avoided a 6 hour stumper. I > spent way to much in forums about editing the xorg.conf file. Thanks! > > -- > Misleading error message - software source for package is not enabled > https://bugs.launchpad.net/bugs/134918 > You received this bug notification because you are a direct subscriber > of the bug. > -- Misleading error message - software source for package is not enabled https://bugs.launchpad.net/bugs/134918 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 134918] Re: Misleading error message - software source for package is not enabled
Yes, this was a fresh install of Gutsy tribe 5. The only deviation from a standard install, which I don't think is relevant, was that I tried to install Grub to the superblock of my jfs root partition instead of to the MBR, and this failed leaving me to manually install GRUB and create a menu.lst afterwards. The little dialog coming from the notification area was there when I first logged in. My concern is really that this is probably the first interaction that newcomers will have with Ubuntu Linux, and it will simply confirm all their fears and the FUD that says Linux is hard and not suitable for normal users. It goes along the lines of; There are special drivers available for your hardware. Would you like me to install them? Ooh, yes please. Well, I'm not going to. Figure out why for yourself. It's going to send them running away screaming. -- Misleading error message - software source for package is not enabled https://bugs.launchpad.net/bugs/134918 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 134918] Misleading error message - cannot install 3d drivers
Public bug reported: I just installed Gutsy tribe 5. Impressively, I get an alert straight away that a proprietary video driver is available. Of course I choose to install the driver, to which I receive a box with a no entry sign and the text: The software source for package nvidia-glx-new is not enabled. Now, I know enough to know that I should launch Synaptic and enable the Multiverse and Universe repositories, but the Restricted Drivers icon in the system tray is for newcomers who will not know this. Worst, the messace could be interpreted as meaning that the software servers out there in the Internet are not enabled - perhaps I should try again in a few days when someone has enabled them? I suggest that the message should go on to explain that the extra repositories can be enabled from the System->Software Sources configuration utility. Perhaps it should also say which repositories should be enabled. I just went to Software Sources, and I see that Multiverse and Universe are indeed enabled. In fact, I kept getting that error message until I did a Reload in synaptic. Well done on prompting the user with driver info, but I think they need more help than the above error message. ** Affects: ubuntu Importance: Undecided Status: New -- Misleading error message - cannot install 3d drivers https://bugs.launchpad.net/bugs/134918 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 14010] Re: grub-install fails for JFS root partition
Confirmed (again) for Gutsy Tribe-5 (installing to jfs root partition). -- grub-install fails for JFS root partition https://bugs.launchpad.net/bugs/14010 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86893] Re: [Feisty] Starting HPLIP Toolbox in DVD edition or after update through internet: No python-qt3, but plenty of space on DVD or internet repository
You work for an HP competitor perhaps? I agree that it cold be prettier, but having an HP printer myself, I find being able to check the ink levels rather useful. On 24/08/07, Jeffrey Baker <[EMAIL PROTECTED]> wrote: > > I think the real question is why we need this useless program cluttering > up the Preferences menu. It doesn't work well, it doesn't fit in with > the Ubuntu look-and-feel, its icon is a hideous, meaningless vendor > logo, and in general the program is a user-hostile insult. > > -- > [Feisty] Starting HPLIP Toolbox in DVD edition or after update through > internet: No python-qt3, but plenty of space on DVD or internet repository > https://bugs.launchpad.net/bugs/86893 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- [Feisty] Starting HPLIP Toolbox in DVD edition or after update through internet: No python-qt3, but plenty of space on DVD or internet repository https://bugs.launchpad.net/bugs/86893 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 86893] Re: [Feisty] Starting HPLIP Toolbox in DVD edition or after update through internet: No python-qt3, but plenty of space on DVD or internet repository
That's odd. I did a fresh install of feisty from the "alternate" installer CD, and I get a suitable pop-up telling me what package needs installing to get the HPLIP GUI and the command to do it. -- [Feisty] Starting HPLIP Toolbox in DVD edition or after update through internet: No python-qt3, but plenty of space on DVD or internet repository https://bugs.launchpad.net/bugs/86893 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 63869] Re: Cannot install grub into root partition
This problem still exists in Feisty beta. I told the installer not to install GRUB on the MBR, and then told it to install on (hd0, 6) instead. This is the partition (/dev sda7) that I was installing to. In this instance, it was formatted with JFS, but last time it was formatted EXT3, so I don't think the JFS is significant. It's a SATA disk. Anyway, I got a pretty red screen saying the GRUB install had failed. I finished the install by using the "rescue a broken system" option on the installer, chroot to the newly installed root partition and run "grub-install (hd0,6)" by hand, then create a menu.lst. >From memory (I'm on a different machine at the moment), my partitions are hda1 - reiserfs (Breezy) hda2 - NTFS - windoze hda5 - vfat - shared stuff hda6 - ext3 - Edgy hda7 - jfs - Feisty install target hda8 - swap hda9 - reiserfs /home -- Cannot install grub into root partition https://launchpad.net/bugs/63869 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97629] Re: Feisty Beta - Cannot disable installer CD repo in Synaptic
No, I use normal Ubuntu with the Gnome desktop. Screenshot attached. I do hope I'm not missing something stupidly obvious. ** Attachment added: "Screenshot.png" http://librarian.launchpad.net/7112549/Screenshot.png -- Feisty Beta - Cannot disable installer CD repo in Synaptic https://bugs.launchpad.net/bugs/97629 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 97629] Re: Feisty Beta - Cannot disable installer CD repo in Synaptic
Sebastian, Sorry for the delay in answering - I only just got home from work. I looked in both those locations, and they both give me the same dialog. Maybe I'm being dumb, but I cannot find where to disable the CD. I can see checkboxes for Main, Universe, Restricted and Multiverse, but not to disable the install CD as a repository. See attached screenshot. And in fact, the first time I installed anything, it asked for the install CD. I had to manually edit sources.lst before it would download anything. This is Feisty Beta we're talking about. The dialog is very different to the Edgy one. But maybe I just don't understand the new dialog box. Regards, Steve. On 29/03/07, Sebastian Heinlein <[EMAIL PROTECTED]> wrote: > > Choose Sysem -> Adminsitration -> Software Sources from the GNOME main > menu or Settings -> Repositores in Synaptic. > > Does this dialog doesn't work as intended or haven't you been aware of > it yet? > > Cheers, > > Sebastian > > ** Changed in: software-properties (Ubuntu) >Status: Unconfirmed => Needs Info > > -- > Feisty Beta - Cannot disable installer CD repo in Synaptic > https://launchpad.net/bugs/97629 > -- Feisty Beta - Cannot disable installer CD repo in Synaptic https://launchpad.net/bugs/97629 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97629] Feisty Beta - Cannot disable installer CD repo in Synaptic
Public bug reported: Binary package hint: synaptic There doesn't seem to be a way to disable the original installer CD as a repository in the new Feisty Beta Synaptic. It's easy to do by editing sources.lst of course, but given that many users will not be keeping their original installer disk handy, I would thing an option (like a checkbox) where the rest of the repo settings are set in the Synaptic GUI would make sense. ** Affects: synaptic (Ubuntu) Importance: Undecided Status: Unconfirmed -- Feisty Beta - Cannot disable installer CD repo in Synaptic https://launchpad.net/bugs/97629 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 14010] Re: grub-install fails for JFS root partition
I confirm this bug is still present in Feisty Beta 1 Alternate installer CD. During the install, I chose manual partitioning and selected an existing partition for reformatting as my root partition. Then at the question "Install bootloader to MBR?" I chose No, and instead said to install to /dev/sda9 (SATA drive). As error message told me that grub-install failed and this was fatal. I continued the installation and then used the installer CD as a rescue disk and ran "grub-install /dev/sda7" manually. I then had to create my own menu.lst. This was with a JFS partition, and specifying both /dev/sda7 and (hd0,6) fail the same way. Same bug existed in Edgy, except I was installing to EXT3 and not JFS then. I seem to remember i has the same bug in Dapper too, but can't swear to it. -- grub-install fails for JFS root partition https://launchpad.net/bugs/14010 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86893] Re: [Feisty] Clicking on HPLIP Toolbox in gnome menu does nothing
Till - I just tried the following: Used Synaptic to uninstall py-qt3, hplip, hplip-data and hpjis packages. Installed hpijs-ppds_2.7.2+1.7.3-0ubuntu1_all.deb, hpijs_2.7.2+1.7.3-0ubuntu1_i386.deb, hplip-data_1.7.3-0ubuntu1_all.deb and hplip_1.7.3-0ubuntu1_i386.deb from your link above by downloading them and double-clicking them in synaptic. None of these called in python-qt3, so when starting hp-toolbox from the command-line, I still get the error message about midding python-qt3. And I notice that by looking at the properties of package hplip in Synaptic, it both suggests and recommends python-qt3 but does not depend on it. Installing python-qt3 of course fixes the toolbox and it runs fine then. On 27/03/07, Till Kamppeter <[EMAIL PROTECTED]> wrote: > > What is in your ~/.local/share/applications/ directory? > > If there is a file hplip.desktop, hp-toolbox.desktop, or any other > hp-*.desktop, delete them. This should fix your problem. If nothing > happens immediately, log out and log in again. > > -- > [Feisty] Clicking on HPLIP Toolbox in gnome menu does nothing > https://launchpad.net/bugs/86893 > -- [Feisty] Clicking on HPLIP Toolbox in gnome menu does nothing https://launchpad.net/bugs/86893 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95737] HPLIP Toolbox won't start, missing python-qt3
Public bug reported: Binary package hint: hplip I think the hplip package should list python-qt3 as a dependency. On Feisty beta, HPLIP fails to start and no error window is shown without qt3. Fortunately, starting it in a console shows a good error message. ProblemType: Bug Architecture: i386 Date: Sun Mar 25 00:54:00 2007 DistroRelease: Ubuntu 7.04 Uname: Linux StevesPC 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux ** Affects: hplip (Ubuntu) Importance: Undecided Status: Unconfirmed -- HPLIP Toolbox won't start, missing python-qt3 https://launchpad.net/bugs/95737 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93288] Re: gxine hangs on resizing video
Confirming, problem still there in Feisty beta. I also notice there is no maximise button on the window title bar - just minimise and close buttons. Don't know it it's relevant but it's a change since Edgy. -- gxine hangs on resizing video https://launchpad.net/bugs/93288 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79490] Re: Problems with partitioning on Feisty Herd1 and Herd2 (alternate iso)
Problem confirmed still present in the daily download as of 15th Feb. It's a corker! It thinks sda5 is a primary partition, it uses error text from an Exception as partition table data, and wants to write five separate sda7 partitions. I added a comment to the forums thread: http://www.ubuntuforums.org/showpost.php?p=2166325&postcount=15 -- Problems with partitioning on Feisty Herd1 and Herd2 (alternate iso) https://launchpad.net/bugs/79490 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 32529] Re: Installer corrupting partition table
If end is last-used rather than first-free, then so do partitions 7 and 8. I think the table had been manually edited with cfdisk to create those partitions, and then Linux installed into the existing partitions, but I'm not certain - it's been a long time. This doesn't necessarily mean that the partitions actually overlap though, it just means that the partitions don't start and end on a cylinder boundary. I think this is what the + symbol means. They may well end halfway through a cylinder and the next one start on the following sector, still in the middle of the same cylinder. To know exactly, you need the detailed partition table rather than this summary printout. Is anyone interested in the 512 byte bootsector images of before and after if I can still find them? On 27/10/06, Rolf Leggewie <[EMAIL PROTECTED]> wrote: > > I guess something is indeed wrong. But what struck me when reading > through the report report is: Don't partitions 2 and 3 overlap at > cylinder 52801 (which is not used in the end in the hda2 container, but > nonetheless)? > > -- > Installer corrupting partition table > https://launchpad.net/bugs/32529 > -- Installer corrupting partition table https://launchpad.net/bugs/32529 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 63869] Re: Cannot install grub into root partition
Ooh! I haven't tried Windows again yet. Fortunately, all I have to do is restore the MBR from a backup, because I haven't been changing partitioning, just installing onto a pre-existing partition. They really need to get their act together with partitioning - diskDrake was doing this kind of stuff with its eyes shut years ago. Not-invented-here syndrome, perhaps? Steve On 04/10/06, Torsten Eichstädt <[EMAIL PROTECTED]> wrote: > > I had the same bug. > > The partitioning tool shipped with edgy beta is _definitely_ broken. It > writes wrong (incompatible with at least XP) partition informations onto > the harddisk. > > It broke my system -- I could not boot anymore. Running the XP CD in > rescue mode, issueing "fixboot c:" and "fixmbr" did not help. > I made my system bootable again with the following: > > Supposed workaround: > 1. If you have a dual-boot system Windows/Linux, boot from the Windows CD > and > 2. select the rescue mode (not the "automatic rescue mode that asks you > for a floppy, s/th rarely found nowadays on modern hardware) > 3. Log into your Windows system > 4. Start "diskpart" and alter the partition table, e.g. delete the Linux > partitions (it's garbish, otherwise it wouldn't shred your partition table) > 5. start "fixmbr" > 6. type "exit" to reboot > 7. If that does not help, do the same and in step 5 add "fixboot c:" > 8. Wait for the Ubuntu team to take a crash course on software release > "best practices", i.e. when to call a release alpha, beta or stable, and > what tools _not_ to change from a certain point on. > > > Cheers > > -- > Cannot install grub into root partition > https://launchpad.net/bugs/63869 > -- Cannot install grub into root partition https://launchpad.net/bugs/63869 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63869] Cannot install grub into root partition
Public bug reported: Binary package hint: base-installer The Edgy (beta) alternate installer cannot install grub into the system root partition. Since I quad-boot, I don't want my BMR bootloader replaced, thanks. I told the installer not to install GRUB on the MBR, but to install into /dev/sda6 (the / partition I am installing Edgy on, filesystem is reiserfs). It produced an error saying it could not install grub. To gain a working installation, I had to complete the following steps: Boot the alternate installer CD, choose rescue mode, and open a shell in /dev/sda6. Issue the command "grub-install /dev/sda6". This installs grub, but it still cannot boot because there is no menu.lst file. Mount another Ubuntu install and copy the menu.lst file from there. Edit menu.lst to reflect the actual kernel files present. This is not so easy, as the shell that the rescue mode dumps you into is incapable of using either vi or nano, so I had to boot a different OS, mount the new partition and edit menu.lst from there. Call that a rescue disk? With no working editor? Edit the master bootloader to add Edgy to the menu and chainload the partition - this step was expected of course. ** Affects: base-installer (Ubuntu) Importance: Undecided Status: Unconfirmed ** Description changed: Binary package hint: base-installer The Edgy (beta) alternate installer cannot install grub into the system root partition. Since I quad-boot, I don't want my BMR bootloader replaced, thanks. I told the installer not to install GRUB on the MBR, but to install into /dev/sda6 (the / partition I am installing Edgy on, filesystem is reiserfs). It produced an error saying it could not install grub. To gain a working installation, I had to complete the following steps: - Boot the alternate CD, choose rescue mode, and open a shell in + Boot the alternate installer CD, choose rescue mode, and open a shell in /dev/sda6. Issue the command "grub-install /dev/sda6". This installs grub, but there is still no menu.lst created. Mount another Ubuntu install and copy the menu.lst file from there. Edit menu.lst to reflect the actual kernel files present. This is not so easy, as the shell that the rescue mode dumps you into is incapable of using either vi or nano, so I had to boot a different OS, mount the new partition and edit menu.lst from there. Call that a rescue disk? With no working editor? Edit the master bootloader to add Edgy to the menu and chainload the partition - this step was expected of course. ** Description changed: Binary package hint: base-installer The Edgy (beta) alternate installer cannot install grub into the system root partition. Since I quad-boot, I don't want my BMR bootloader replaced, thanks. I told the installer not to install GRUB on the MBR, but to install into /dev/sda6 (the / partition I am installing Edgy on, filesystem is reiserfs). It produced an error saying it could not install grub. To gain a working installation, I had to complete the following steps: Boot the alternate installer CD, choose rescue mode, and open a shell in /dev/sda6. Issue the command "grub-install /dev/sda6". This installs - grub, but there is still no menu.lst created. + grub, but it still cannot boot because there is no menu.lst file. Mount another Ubuntu install and copy the menu.lst file from there. Edit menu.lst to reflect the actual kernel files present. This is not so easy, as the shell that the rescue mode dumps you into is incapable of using either vi or nano, so I had to boot a different OS, mount the new partition and edit menu.lst from there. Call that a rescue disk? With no working editor? Edit the master bootloader to add Edgy to the menu and chainload the partition - this step was expected of course. -- Cannot install grub into root partition https://launchpad.net/bugs/63869 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs