[Bug 160656] Re: K3B can't find CD/DVD Writer
Actually, I'm starting to think that this is not only a K3B bug but a (K)Ubuntu system bug. I run a WinXP virtual machine on my Kubuntu box and it cannot find the writer either in cases when K3B cannot. This is in conflict with the report from ssus. ssus - are you still having success with NeroLinux? -- K3B can't find CD/DVD Writer https://bugs.launchpad.net/bugs/160656 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for k3b in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1455323] Re: Regression in KDE5 desktop session save / restore
Just adding my voice to this bug and pointing out that its presence is preventing my migration to the 16.04 version of Kubuntu. I have Xenial installed and ready to go but simply can't use it if it is necessary to restore all my apps in their respective desktops on each boot. 14.04 still works perfectly in this respect. Many thanks to the dedicated folks who turn their attention to this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455323 Title: Regression in KDE5 desktop session save / restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1455323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762864] Re: kate cannot run as root
'Invalid' defined as: Not a bug. May be a support request or spam. This designation seems a bit cavalier. Root could edit in Kate before. Now it can't, presumably because of changes made in the ongoing development. That is a bug. As end users we appreciate the efforts that are made by the developers, but breaking stuff during development is normal and if you break it you should fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762864 Title: kate cannot run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1762864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762864] Re: kate cannot run as root
Yes. Annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762864 Title: kate cannot run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1762864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160656] Re: K3B can't find CD/DVD Writer
First of all, my drive is a 716A like that of ssus not a 719A as I originally stated. Second and most important, this problem appears to be FIXED in the latest version of K3b: 1.0.4-2ubuntu1~gutsy1 NeroLinux was starting to look pretty good, but K3b is the best and my application of choice for most burning. I'm currently on my 4th consecutive disk (3 DVDs and one CD) and everything is A-OK. Many thanks to the developers for addressing this issue. -- K3B can't find CD/DVD Writer https://bugs.launchpad.net/bugs/160656 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 160656] Re: K3B can't find CD/DVD Writer
OK - I spoke too soon. After the 4th disk K3b lost touch with the writer
again. Here is the dmesg output:
[1167230.405850] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167230.405856] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167230.405859] ide: failed opcode was: unknown
[1167230.405861] hdc: drive not ready for command
[1167231.368552] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167231.368562] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167231.368566] ide: failed opcode was: unknown
[1167231.368570] hdc: drive not ready for command
[1167231.369052] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167231.369057] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167231.369060] ide: failed opcode was: unknown
[1167231.369063] hdc: drive not ready for command
[1167231.935806] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167231.935815] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167231.935819] ide: failed opcode was: unknown
[1167231.935823] hdc: drive not ready for command
[1167232.087240] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167232.087250] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167232.087254] ide: failed opcode was: unknown
[1167232.087258] hdc: drive not ready for command
[1167232.087298] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167232.087303] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167232.087306] ide: failed opcode was: unknown
[1167232.087308] hdc: drive not ready for command
[1167232.087335] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167232.087339] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167232.087342] ide: failed opcode was: unknown
[1167232.087344] hdc: drive not ready for command
[1167232.087389] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167232.087394] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167232.087397] ide: failed opcode was: unknown
[1167232.087399] hdc: drive not ready for command
[1167232.392012] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167232.392022] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167232.392026] ide: failed opcode was: unknown
[1167232.392030] hdc: drive not ready for command
[1167232.392521] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167232.392527] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167232.392530] ide: failed opcode was: unknown
[1167232.392532] hdc: drive not ready for command
[1167233.362902] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167233.362911] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167233.362915] ide: failed opcode was: unknown
[1167233.362919] hdc: drive not ready for command
[1167233.363399] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167233.363405] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1167233.363408] ide: failed opcode was: unknown
[1167233.363410] hdc: drive not ready for command
--
K3B can't find CD/DVD Writer
https://bugs.launchpad.net/bugs/160656
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 155150] Re: adept fails to upgrade distribution when already at 7.10
Prodigal wrote: > Ok how exactly did any of you manage to update when the update manager > itself will not work? > > Console apt-get update? If so which program are you updating? I'm > getting security errors when I try to run apt-get install or apt-get > update no matter which package I try to update/install. > > Try this thread: http://ubuntuforums.org/showthread.php?t=590813 Tai Sines -- adept fails to upgrade distribution when already at 7.10 https://bugs.launchpad.net/bugs/155150 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 160656] K3B can't find CD/DVD Writer
Public bug reported:
Binary package hint: k3b
This is similar to #114471 which is now closed. My Plextor 719A DVD
burner worked fine in K3B in Edgy. When I upgraded to Feisty this
scenario occurred: When the machine is booted, it finds the drive and I
can burn exactly one CD or DVD. Then it reports "No CD/DVD writer
found." This condition remains until I reboot the computer after which I
can again burn one disk.
I was hoping for a fix in Gutsy, but no joy. Exactly the same problem.
dmesg output consists of this repeated many times:
[1604360.807844] ide: failed opcode was: unknown
[1604360.807848] hdc: drive not ready for command
[1604360.808382] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1604360.808388] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1604360.808391] ide: failed opcode was: unknown
[1604360.808393] hdc: drive not ready for command
[1604361.338872] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1604361.338883] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1604361.338887] ide: failed opcode was: unknown
[1604361.338891] hdc: drive not ready for command
[1604361.338932] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1604361.338936] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1604361.338939] ide: failed opcode was: unknown
[1604361.338941] hdc: drive not ready for command
[1604361.338968] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1604361.338973] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1604361.338975] ide: failed opcode was: unknown
[1604361.338977] hdc: drive not ready for command
[1604361.339024] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1604361.339028] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
[1604361.339031] ide: failed opcode was: unknown
[1604361.339033] hdc: drive not ready for command
** Affects: k3b (Ubuntu)
Importance: Undecided
Status: New
--
K3B can't find CD/DVD Writer
https://bugs.launchpad.net/bugs/160656
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 487761] Re: Data CDs authored by Kubuntu K3b 1.68.0 are unreadable
For me, the problem was solved by doing a clean install of Karmic. Thank you for all your work on this excellent application. -- Data CDs authored by Kubuntu K3b 1.68.0 are unreadable https://bugs.launchpad.net/bugs/487761 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to k3b in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 417757] Re: [regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups
I have to agree with Derek. With due respect to all the techs who do the hard work of keeping Ubuntu (and especially Kubuntu in my case) so great, I find that, as technical folks, we sometimes get overly focused on the technical side and forget about the larger world in which that exists. Sometimes the technically correct solution is not the right solution in the real world, at least not at first. Because of all the issues with Karmic, this should have been anticipated and accounted for in Lucid. By this I mean that clear documentation, fixes and workarounds should have been provided - if the problem could not be accounted for silently in code. This problem is a huge hassle for users who aren't up to speed on the technical side of connecting to the internet. Those who are may look down on those who are not, but that's no way to run an operating system. Derek wrote: > This is where pragmatism comes in. > We have absolutely no control over those resolvers, and even if we had any > influence whatsoever with those who did, corporate networks are very slow to > change. Ubuntu is the outsider. The Windows machines work. Your solution > is not a pragmatic one. > > So, while being "pure" is good, I thought Ubuntu stayed out of such > things. > > That's why Ubuntu offers easy integration of binary drivers for ATI and > nVidia, why Ubuntu has a restricted-extras for convenient meta. > > Simply because IPv6 is *better* doesn't mean you should sacrifice > adoption for the ideal. > > Using AI_ADDRCONFIG is simple enough, and as noted browsers like Firefox > and Chrome have adopted that. > > What would be nice would be a simple package that forces it across the > board, simply as an option for broken networks. > -- Tai Sines "Share your strengths, not your weaknesses." -- Yogi Bhajan -- [regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups https://bugs.launchpad.net/bugs/417757 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 417757] Re: [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups
FWIW: 1. I'm having this problem intermittently 2. When it occurs on my Karmic box, it also occurs on a Windows 7 laptop (wireless) on my home network. 3. Other computers on the network (XP both wired and wireless) remain functional DNS wise, except that sometimes my web request to the router config page is forwarded to the Karmic box (see 4b below). Router reboot required to fix. 4. Upgrading my router (D-Link DIR-655) firmware seemed to help, but after three days of flawless function, the problem occurred again. I found that I had not checked the (new with latest firmware) 'Advanced DNS' checkbox in the router config. I checked that and rebooted the router. All is well since then, <24 hours. 4a. Because of domestic issues, I shut down all computers and the home network at night and reboot each morning. 4b. Port 80 is forwarded from the router to apache on my Karmic box. 5. My upgrade from Jaunty to Karmic (Kubuntu) is seriously broken. Only terminal shutdowns work (Bug#418509) K3b ruins disks but doesn't burn them and no media players function properly except vlc and totem. 6. A work machine with similar configuration upgraded to Karmic without incident. Brad Peters wrote: > I tested the karmic-proposed package on my work machine, however, I'm > still having intermittent issues with this. Since this is a work > machine, I'm at the mercy of our IT department as far as routers and DNS > resolution goes. I've disabled all workarounds, installed the new > package and rebooted. It worked for about five minutes before going > back to the same behavior I was seeing previously. > > All throughout this bug report, a lot of people (developers, I'm > assuming) have commented that the routers are broken and it shouldn't be > on Ubuntu to fix the problem. I'm sorry, but if I go from a working > version of Ubuntu (Jaunty) and upgrade, I expect everything to work > equally as well, if not better, than the previous release. > -- Tai Sines "Share your strengths, not your weaknesses." -- Yogi Bhajan -- [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups https://bugs.launchpad.net/bugs/417757 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 497296] Re: juk crashed with SIGSEGV in QObjectPrivate::deleteChildren()
Not currently. Juk now acts the same as Amarok and Dragon Player since my upgrade to Karmic: MP3 (and other media types) files simply don't play. I don't believe this is a problem with Juk. (Media files DO play in vlc and totem) I'm going to try a clean install. Thanks for looking at this. Jonathan Thomas wrote: > Is this crash reproducible? > > ** Changed in: kdemultimedia (Ubuntu) >Status: New => Incomplete > > ** Visibility changed to: Public > -- Tai Sines "Share your strengths, not your weaknesses." -- Yogi Bhajan -- juk crashed with SIGSEGV in QObjectPrivate::deleteChildren() https://bugs.launchpad.net/bugs/497296 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdemultimedia in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1762864] Re: kate cannot run as root
While I might not phrase my comment as loneanon has, he is correct on every point. In previous versions of (k)ubuntu users could edit files as root using Kate. Making that no longer possible is taking away functionality that many of us were used to. I have yet to see any justification for this action, just terse and opaque judgments like "Invalid" and "not a bug". How about a little more philosophical insight into why the developers think this capability is not necessary to include? If you bought a new car and found that in place of the ignition switch, there was a hand crank, would you think it was a bug? How would you feel if you complained to the dealer and merely got the response that the car still works without it? In my case, I like using Kate so much that I created an alias in .bashrc so that I can edit root owned scripts. It is: alias sudokate='SUDO_EDITOR=kate sudoedit' It's a little clunky in that, when executing "sudokate myfile.txt", Kate makes a copy of myfile.txt with a temporary file name and then copies over the original file when the changes are saved. Since Linux is supposed to be about choices, why must we go to such lengths just to maintain (an approximation of) the functionality we already had? This is the core question that was asked a year and a half ago when this bug was created. We're still waiting for an answer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762864 Title: kate cannot run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1762864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762864] Re: kate cannot run as root
Oh, I see that I neglected to credit Hedley Finger for the alias code. It's been so long I forgot that I got that here. Thanks Hedley -- that's made my life easier for sure! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762864 Title: kate cannot run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1762864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
