I'm on Mist 17.1 (didn't know there was a 17.2 - I'll have to go take a
peek!)
I am disturbed by the repeated comments, both here and other places,
that describe this error as a "nuisance".
Unfortunately, I am not a developer so my ability to investigate (fork)
such-and-so is painfully limited.
Folks, here is my dos centavos, dva kopekie, two cents, or whatever. . .
.
Note: Distro used is Ubuntu 10.04 LTS.
1. Allowing physical icons to overlap is just plain messy and un-
professional.
Most of the places I have worked for had a bug-rating from 1-4, 1 being
"hotter-than-hell" and 4 bei
Re: Reply to my question #173052
(https://answers.launchpad.net/ubuntu/+question/173052)
Viz.:
(quote)
actionparsnip (andrew-woodhead666) said 34 minutes ago: #1
I suggest you report a bug so the new version is brought into the
opfficial repos.
Even Oneiric has 0.8.1-1 so the bug report should
Public bug reported:
It appears that the package "aqemu" (0.7.3.1) has a nasty bug where it
is unable to find USB port information.
Viz.:
http://sourceforge.net/tracker/index.php?func=detail&aid=3011540&group_id=229794&atid=1078458
The fix to this is in aqemu 0.8.n - with the most current versio
Additional data point:
After I upgraded udev/libudev0 to 151-12.3 0 I experienced the issue
described above.
I then used Synaptic to force-downgrade both packages back to 151-12 0.
After a reboot, the problem still persists.
Conclusion: The upgrade brings something else with it - an upgraded
co
Additional info:
"Pinned" (downgraded) versions:
udev and libudev0 - 151-12 (to correct inability for mdadm to assemble /
manage a preexisting array)
udisks 1.0.1-1build1 (Corrects inability to mount or read floppy drive - a
separate bug.)
AFAIK, this is the only "non-standard" stuff I have d
Note that mdadm, and the RAID 5 array it manages, were working
wonderfully up until the time of the referenced upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750761
Title:
Lucid: Update ude
** Attachment added: "listing of all versions of packages prior to updating
udev"
https://bugs.launchpad.net/bugs/750761/+attachment/1979788/+files/Package%20Versions.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
Binary package hint: udev
Issue:
Upgrading udev and libudev0 from 151-12 0 to 151-13.3 breaks mdadm where
it cannot read mdadm.conf, and will not assemble, start, or mount a
previously configured and working RAID array.
I did not try updating each package seperately as I "a
@Kris
That is because you have the floppy in your fstab. Remove or comment-
out the "floppy disk" (/dev/fd - /dev/fd0) line in your FSTAB and
resave. You will still be able to use the floppy with the downgraded
udev - and it will automount just like a USB drive.
--
You received this bug notifi
This is another example of a short-sighted decision *somewhere* that
"nobody" would EVER want to use a floppy!
Admittedly, I use floppies less-and-less often, but I do use them and
some of my most valuable and powerful utilities will ONLY work from a
floppy. . . . running DOS 6.22. (and yes, I've
For me this is extremely important, bordering on critical, as I
frequently need to move huge amounts of data onto, around within, and
off of my multi-T file server based on the needs of the client-/du-
jour/.
Thanks!
** Summary changed:
- Memory leak in Nautilus?
+ Memory leak in Nautilus/Kerne
Ref: question #148866 in Launchpad.
I have taken the (admittedly great) liberty of inviting the Kernel team
to weigh-in on this since I am beginning to suspect that this may
actually be a kernel issue.
Summary:
When moving huge files - hundred+gig to terabyte sized file groups - eventually
all
** Also affects: linux
Importance: Undecided
Status: New
** Tags added: leak memory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734552
Title:
Memory leak in Nautilus?
--
ubuntu-bugs m
All work described above was done at the "console" (direclty logged into
the machine - not from a remote session or Samba)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734552
Title:
Memory leak in
Public bug reported:
Yesterday when moving relatively huge amounts of data between hard
drives on my system (using the GUI - drag-and-drop) I discovered that
after some time I had consumed all available memory and all available
swap.
System:
Athlon 64 X2 processor on ASUS A8R32-MVP Deluxe MoBo.
4
Date: March 2, 2010 - appx 7:05 pm EST.
Installed 9.10 desktop on an AMD X2 64 bit system using the 64 bit
distribution.
I am currently running kernel version 2.6.31-19 - with all current
updates installed.
This &^...@! bug should be (IMHO) be rated as darn-near a show-
stopper severity and
That system is currently off line while I am desperately working on a hard
drive recovery crisis.
Can I get this to you a bit later? (say < 1 week?)
Thanks!
Jim "JR" Harris
Senior QA Analyst, Systems QA
508-595-9382 (Desk)
508-864-8404 (Cell)
( - )
-Original Message---
Public bug reported:
Binary package hint: gnome-control-center
Issue:
If a particular monitor - with particular specifications and limitations
- is plugged into a Windows system, attempting to change the monitor
resolution is accompanied by a check-box that says "Hide resolutions
this monitor ca
p.s. . . . .
I actually tried "xfix" several times in a row to see if that would
help. No cigar
--
Screennresolution applet no longer asks for confirmation of new resolution
settings
https://bugs.launchpad.net/bugs/279569
You received this bug notification because you are a member of Ubunt
Luke,
I hate to break the bad news to you - but (at least in Intrepid), that's
NOT true.
I set my screen resolution/refresh rate to something higher than my
monitor could display - and I got a blank screen. I had to actually
*KILL POWER* to get the beast to reboot, and when I booted into recover
** Description changed:
Binary package hint: gnome
(Update - 1/23/09 by Jim (JR))
Completely re-writing description based on new information
Issue:
- If visual effects are turned on - mousing-over the title bar controls (upper
right hand corner), causes title bar to reverse color, t
Re: Pedro Villavicencio changing target package to compiz.
1. Thanks for the update!
2. What is "compiz"?
I have seen other references to it, and it appears to have something to do with
the "eye candy" part of things - I saw a brainstorm suggestion complaining that
"application animations" (?
Public bug reported:
Note: This is NOT a bug (I hope!) It is merely intended to be a "wish list"
for future enhancements if possible.
Note: If, due to my abysmal ignorance, this is NOT the correct forum
for posting product enhancements, a *polite* and *respectful* e-mail
guiding my path woul
I suspect that this is the correct package, based on the log report
containing "libgnome-window-settings1 1:2.24.0.1-0ubuntu7.1" which I
believe to be relevant to this bug.
Note that this is pure, unmitigated guess-work. If you know better,
feel free to change.
Flame mail to /dev/null
Jim
** S
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/21579742/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/21579743/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/21579744/ProcStatus.txt
** Descrip
Public bug reported:
Binary package hint: gnome
Issue:
When I open a file browser window - pointing to virtually anywhere - clicking
elsewhere, (i.e. a child window, inside the current window, the menu panel bar,
etc.), the title bar sometimes turns white (as if the window had lost focus),
and
Ref: Bug 316961 (duplicate of this)
I experienced the exact same issue, and (not finding THIS bug), wrote it
up yet again.
Essentially my steps to reproduce involved selecting an invalid display
resolution and accepting it.
The result (as of 8.10) is a functionally "bricked" box. Even though I
A thousand humble apologies.
My original bug was marked as a duplicate of THIS bug - and THIS is not
a duplicate of anything else - so I felt it was reasonable to believe
that this bug was the "root" bug that all other duplicates should point
toward.
Especially since there was a post-fix comment
Sebastien,
I have decided to toss this into your in-basket for disposition.
(I'm not sure if I'm supposed to even DO this - apologies in advance if this is
a huge breach of protocol.)
1. This REALLY needs to be fixed.
2. I have no idea who the "responsible developer" would be at this
point in
*** This bug is a duplicate of bug 197673 ***
https://bugs.launchpad.net/bugs/197673
beN,
Up between the "System" section in my bug report, and "Steps to
Reproduce" I disclose the operating system - Ubuntu 8.10. ( ;-) )
pak33m,
You are most welcome. And you are right, I had no package lis
Changing from FIXED to INCOMPLETE (= not-fixed, re-opened?)
Added comment and reference to duplicate bug 316961 entered by me on 1/13/09
Jim
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Released => Incomplete
--
gnome-display-properties should revert change automatically if
Unfortunately, in Ubuntu 8.10 this is still WY broken. (Ref: bug 316961)
Doing the same thing - trying out resolutions on a ViewSonic A75F
monitor, not only did I totally hoze my session - I hozed it in classic
style.
It took me several hours of hacking around with a recovery terminal
before
Public bug reported:
Issue: When changing screen refresh rate within "System --> Preferences
--> Screen Resolution" (on the top bar) selection of an invalid refresh
rate for the monitor being used results in an unusable system.
What should happen is this: After a resolution is selected and the
34 matches
Mail list logo
