Re: [Bug 228624] Re: DVD writer not working since hardy upgrade
I'm afraid it remained an issue for so long that I got a mac after 10yrs of Linux use. Sent from my iPhone On 23 Jul 2012, at 17:06, "Christopher M. Penalver" wrote: > AllesMeins, this bug was reported a while ago and there hasn't been any > activity in it recently. We were wondering if this is still an issue? > Can you try with the latest development release of Ubuntu? ISO CD images > are available from http://cdimage.ubuntu.com/releases/ . > > If it remains an issue, could you run the following command in the > development release from a Terminal > (Applications->Accessories->Terminal). It will automatically gather and > attach updated debug information to this report. > > apport-collect -p linux > > Also, if you could test the latest upstream kernel available that would > be great. It will allow additional upstream developers to examine the > issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do > not test the kernel in the daily folder, but the one all the way at the > bottom. Once you've tested the upstream kernel, please remove the > 'needs-upstream-testing' tag. This can be done by clicking on the yellow > pencil icon next to the tag located at the bottom of the bug description > and deleting the 'needs-upstream-testing' text. As well, please comment > on which kernel version specifically you tested. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > If you are unable to test the mainline kernel, for example it will not > boot, please add the tag: 'kernel-unable-to-test-upstream', and comment > as to why specifically you were unable to test it. > > Please let us know your results. Thanks in advance. > > ** Tags added: kernel-media needs-upstream-testing > > ** Attachment removed: "hardybug" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+attachment/302461/+files/hardybug > > ** Attachment removed: "unnamed" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+attachment/302742/+files/unnamed > > ** Attachment removed: "unnamed" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+attachment/302856/+files/unnamed > > ** Attachment removed: "all_generic_ide.log" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+attachment/306004/+files/all_generic_ide.log > > ** Attachment removed: "unnamed" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+attachment/306054/+files/unnamed > > ** Attachment removed: "228624.zip" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+attachment/311098/+files/228624.zip > > ** Attachment removed: "228624.zip" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+attachment/311100/+files/228624.zip > > ** Attachment removed: "unnamed" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+attachment/311211/+files/unnamed > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/228624 > > Title: > DVD writer not working since hardy upgrade > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/228624 Title: DVD writer not working since hardy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 507293] Re: sound-juicer crashed with SIGSEGV in start_thread()
Well annoyed by this bug. I have been suffering from a bug with the DVD drive being completely broken on ubuntu since about 3 releases ago. I thought I had a duff drive, so replaced my IDE drive with brand new SATA burner instead. Imagine my shock to see that the bug is now WORSE. I've been an ubuntu user since the start, and exclusively linux for about 10 years. This bug is really wearing me thin. I can't rip an audio CD any more. I tried installing fedora. Same bug, same problems. Believe it or not I have contemplated ditching linux for windows 7, such is my frustration that things that were once in a "just works" state are moving into "just doesn't work"... I know this is all off topic, but really need to get it off my chest -- sound-juicer crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/507293 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 510563] Re: Opening File when Playlist active wipes playlist
I have registered this bug on the gnome bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=607653 Not sure if there's a way launchpad can link to that in a tracking sort of way.. J. ** Bug watch added: GNOME Bug Tracker #607653 https://bugzilla.gnome.org/show_bug.cgi?id=607653 -- Opening File when Playlist active wipes playlist https://bugs.launchpad.net/bugs/510563 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 510563] [NEW] Opening File when Playlist active wipes playlist
Public bug reported: Binary package hint: totem This is probably one of the most frustrating bugs which leads me to remember why I stop using Totem from time to time. If you have a playlist that you're working through, and you then click on a media file (which opens in the default, Totem) it wipes your playlist, stops playing what you're playing and you loose your playlist. If you are working through a playlist of videos/podcasts etc. losing your place and track of where you are in a list of 10/20 files this is unbelievably annoying. Steps: 1. Open Totem 2. Add several items to the playlist for listening/viewing 3. Start listening to an item in the playlist 4. Open a Nautilus window 5. Browse to a media file 6. Click on a media file 7. Note how what you were doing is now gone and playlist lost, you're now watching that video What should happen: Either a new instance of Totem which doesn't lose what I was doing, or add the new file to the playlist. What it certainly should not do is wipe something I took time to get set up and stop playing something that I'm in the middle of. I might pause what I'm doing and then want to quickly view a small video/audio file, I still want to return to that activity. Current Work-around: Don't use totem for playlists, or set something else as the default handler. If you do these things, then it won't wreck your playlist because you're using two different apps for the same thing. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- Opening File when Playlist active wipes playlist https://bugs.launchpad.net/bugs/510563 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 472466] Re: lprm broken in Karmic
Sorry I should also clarify that this happens at home with Karmic and a Samsung ML-1610 printer, and at work with Karmic and an HP laser printer. Both are stock installs. -- lprm broken in Karmic https://bugs.launchpad.net/bugs/472466 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 472466] Re: lprm broken in Karmic
this fails for me and cancel does nothing either. I've tried using lprm -P name-of-print and that does squat either. This is messing with my head rather badly. -- lprm broken in Karmic https://bugs.launchpad.net/bugs/472466 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 390304] Re: unlabeled partitions are mounted under their UUIDs
I cant seem to label it on my android phone. However, either way, it should be consistent with what nautilus is calling it. 169gb drive makes more sense for an unlabled drive than the uuid. Sent From My Awesome Mobile On 15 Nov 2009 10:50, "Martijn Kaandorp" wrote: System -> Administration -> Disk Utility (Palimpsest) -> change label No need to unmount first, just remount (unmount and mount) after changing the label in order to see the mountpoint at your newly given label /media/label. This works great and i hope that canonical will keep this in future releases. The disk, disk-1 solution wasn't working either and confuses a lot more. -- unlabeled partitions are mounted under their UUIDs https://bugs.launchpad.net/bugs/390304 You r... -- unlabeled partitions are mounted under their UUIDs https://bugs.launchpad.net/bugs/390304 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 474650] [NEW] Mounted Volume Names are hex strings, not volume name
Public bug reported: Since updating to karmic, nautilus will display the mounted volume as, for example, "160GB Drive", but when mounted, every reference within the system is as "01EFC-DFDFD-DFDFD-DFDFDF" or similar. This is poor for users who don't understand what on earth that is. I belive the problem is due to dropping HAL, which I think sorted out neat mount points (or symlinks to the volume id) using the name. I think that puts this bug in device kit, but I can't fathom how to report a bug in a given package, I know it's not a bug in nautilus, as it's in the gtk browser and also any terminal access. It took me about half an hour to find how to register this bug in launchpad, I almost gave up. but. that's another bug for another place.. If you want to recreate the bug, just attach a large drive maybe a usb key. See in nautilus it referred to as 160GB drive, mount and enter some folders. See the path bar in the nautilus window reference the hex string. Thanks. ** Affects: ubuntu Importance: Undecided Status: New -- Mounted Volume Names are hex strings, not volume name https://bugs.launchpad.net/bugs/474650 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 340515] Re: Consumes all CPU, logs a lot of output
I noticed this and it took me a while to find what was responsible. For me when viewing processes in system monitor there was an un-named process which kept respawning, dieing and creating a new process every second or so. I tracked it to vino-server. I think the problem with eating processor must relate to some threading code. -- Consumes all CPU, logs a lot of output https://bugs.launchpad.net/bugs/340515 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 273915] Re: Base: Error on saving a new record with no data entered
I can confirm this can be reproduced on openoffice.org 2.2, ubuntu 8.05. ** Changed in: openoffice.org (Ubuntu) Status: New => Confirmed -- Base: Error on saving a new record with no data entered https://bugs.launchpad.net/bugs/273915 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 228624] Re: DVD writer not working since hardy upgrade
my liteon dvd writer suffered similar issues.. The all_generic_ide=1 line seems to have fixed this.. Very interested to know what is causing this issue.. is it a kernel bug? -- DVD writer not working since hardy upgrade https://bugs.launchpad.net/bugs/228624 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 123820] nvidia driver useEDID work-around causes worse problems
Public bug reported: The toshiba satellite 704 laptop suffers from the EDID issues many others have noted. The previous nvidia binary driver releases used IgnoreEDID set to true which did fix the issue. The latest move the useEDID set to false. This does not however work on the 704, it results in bars of bleeding colours etc on the screen that look as though damage could well be being done to the dispay. I have tried all the work arounds other than this and no success. to reproduce simply add the Option "useEDID" "false" to the device section of the x config. Note, that I did succeed in rewriting a bin dump of the EDID data which is received when actually using the EDID data in the driver. details of this are in this bug report: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.20/+bug/91292 someone suggested I register a new bug regarding the EDID work-around failing even worse. ** Affects: linux-restricted-modules-2.6.20 (Ubuntu) Importance: Undecided Status: New -- nvidia driver useEDID work-around causes worse problems https://bugs.launchpad.net/bugs/123820 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 91292] Re: [nvidia-glx] Resolutions lost on upgrade from Edgy to Feisty [nvidia-glx-legacy][nvidia-glx-new]
Sitsofo: Sorry, I neglected to mention that UseEDID causes massive corruption on the screen. This is why I needed to debug the EDID data and give a propper fix. The EDID thing used to work in earlier drivers, but not any more.. I know the nv driver worked at 1024, however not sure about the EDID data. I suppose if I debuged would it show it like the nvidia? Do you suppose there is a way to have the nv driver dump the edid.bin data, and then force the nvidia driver to use that, possibly optionally, to create a more robust fix for others? -- [nvidia-glx] Resolutions lost on upgrade from Edgy to Feisty [nvidia-glx-legacy][nvidia-glx-new] https://bugs.launchpad.net/bugs/91292 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 91292] I Have A Fix (It's Just a Pain ;)
Hi guys, I have been plagued with the poor EDID stuff on my toshiba from day one. Anyway. I was looking through the docs and trying to get a better idea of why 1024x768 was not valid. The docs point you to running x as follows: startx -- -verbose 6 -logverbose 6 this resulted in the EDID information in my Xorg log. Here is the stuff which was important: -snip- (--) NVIDIA(0): --- EDID for Nvidia Default Flat Panel (DFP-0) --- (--) NVIDIA(0): EDID Version : 1.3 (--) NVIDIA(0): Manufacturer : NVD (--) NVIDIA(0): Monitor Name : Nvidia Default Flat Panel (--) NVIDIA(0): Product ID : 0 (--) NVIDIA(0): 32-bit Serial Number : 0 (--) NVIDIA(0): Serial Number String : (--) NVIDIA(0): Manufacture Date : 2002, week 45 (--) NVIDIA(0): DPMS Capabilities: Standby Suspend Active Off (--) NVIDIA(0): Prefer first detailed timing : Yes (--) NVIDIA(0): Supports GTF : No (--) NVIDIA(0): Maximum Image Size : 320mm x 260mm (--) NVIDIA(0): Valid HSync Range: 29 kHz - 49 kHz (--) NVIDIA(0): Valid VRefresh Range : 0 Hz - 60 Hz (--) NVIDIA(0): EDID maximum pixel clock : 70.0 MHz (--) NVIDIA(0): (--) NVIDIA(0): Detailed Timings: (--) NVIDIA(0): 969 x 768 @ 60 Hz (--) NVIDIA(0): Pixel Clock : 65.00 MHz (--) NVIDIA(0): HRes, HSyncStart : 969, 1048 (--) NVIDIA(0): HSyncEnd, HTotal : 1184, 1344 (--) NVIDIA(0): VRes, VSyncStart : 768, 771 (--) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (--) NVIDIA(0): H/V Polarity : -/- -snip Now the thing I notices was that it was under the impression that the DFP was 969 pixels. This was a pain. It's 1024. The 1024 was being reject as it was too big for the DFP. It also explained why there was a black line on the right at lower modes (the scale was to 969, missing the last 55px off. Here clearly was my EDID problem in evidence. Now the solving - it's nasty but works for me. The drive allows for EDIDs to come from another file: Option "CustomEDID" "DFP-0:/etc/X11/edid.bin" the place to get that EDID file is a dump from nvidia-settings. Now to hunt down 969 and set to 1024. Hexedit for the binary file was used. 969 in Hex = 3C9, 1024 = 400. So I had to change 3C9 to 400 and I was a winner. The edid data from the file is: (--) NVIDIA(0): Raw EDID bytes: (--) NVIDIA(0): (--) NVIDIA(0): 00 ff ff ff ff ff ff 00 3a c4 00 00 00 00 00 00 (--) NVIDIA(0): 2d 0c 01 03 80 20 1a 00 ea a8 e0 99 57 4b 92 25 (--) NVIDIA(0): 1c 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 (--) NVIDIA(0): 01 01 01 01 01 01 64 19 c9 77 31 00 26 30 4f 88 (--) NVIDIA(0): 36 00 42 ff 10 00 00 18 00 00 00 fc 00 4e 76 69 (--) NVIDIA(0): 64 69 61 20 44 65 66 61 75 6c 00 00 00 fc 00 74 (--) NVIDIA(0): 20 46 6c 61 74 20 50 61 6e 65 6c 00 00 00 00 fd (--) NVIDIA(0): 00 00 3c 1d 31 07 00 00 20 20 20 20 20 00 00 06 (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (--) NVIDIA(0): (--) NVIDIA(0): --- End of EDID for Nvidia Default Flat Panel (DFP-0) --- However the closest match to 3C9 was the C9 in the 4th line. I upped that a little to CC, and low and behold it increased the screen size in the log to a few pixels more. I upped it to FF and I was at 1023px. 00 back to 640.. booo. so close. I had to find that 3. i messed around with all sorts and diffed the logs to see what data changed. Then I finally found which 3 it was. Just a couple of digits along, not sure why the 77 was skiped, but chaging that to a 4 and it worked! I now have a working X and am about to sort beryl. So that line now was changed: (--) NVIDIA(0): 01 01 01 01 01 01 64 19 __c9__ 77 __3__1 00 26 30 4f 88 (--) NVIDIA(0): 01 01 01 01 01 01 64 19 __00__ 77 __4__1 00 26 30 4f 88 Sorry that this is a real long post. It's just that it's not really a fix that people can sort unless they know where to look. Perhaps this will fix all peoples issues, but I suspect that it may only work for people with the same specs as me. My machine is a toshiba satelite 704, with 1024x768 screen. I really hope this helps people resolve this issue, and again sorry for the long post, but Its amazing I managed to fix it! I have attached my working edid.bin file for people to try if they're feeling brave, perhaps it works in all cases... Thanks ** Attachment added: "Modified EDID.bin dump to correct EDID size data." http://launchpadlibrarian.n
[Bug 106169] Re: Latest kernel update does not boot (7.04)
*** This bug is a duplicate of bug 106063 *** https://bugs.launchpad.net/bugs/106063 My issue too. Anyone know how I can get .13 kernel, as I cleaned them up recently? I have a install disk, so can chroot. anyone give me an apt-get line to get an older one? Or are they gone from the repos? -- Latest kernel update does not boot (7.04) https://bugs.launchpad.net/bugs/106169 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58190] Filetree Browser Selection Issue
Public bug reported: Binary package hint: bluefish Selecting an item in the filebrowser tree shows the elements in the given folder, but does not higlight the selection, causing much confusion. also when adding a file it uses the highlit version not the one displayed. ** Affects: bluefish (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Filetree Browser Selection Issue https://launchpad.net/bugs/58190 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
