penalvch's question makes no sense and is an extremely bad excuse for
that status change.
It also shows that penalvch has not read the comments on this page.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And WTF did penalvch remove attachments that are referred to in the
comment thread?
If you have nothing useful to add, then at least have the common
courtesy to refrain from vandalism.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With reference to what I wrote in comment #7
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980083/comments/7
:
I have now plugged in another hard drive and briefly installed Windows
XP Professional to see if suspend works there at all with this
mainboard, and suspend does indeed work in
Upon further research, it is also possible that bug #772834 *may* be the
same issue. Maybe. It's the same manufacturer and the symptoms appear to
be identical.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just burned a bunch of different Linux LiveCDs from various
distributions and booted them and tried their suspend features, to see
if someone else has already fixed this problem elsewhere. I tried the
currently most up-to-date live CDs from Debian, Knoppix, Fedora, Mageia,
PCLinuxOS and
I have tried this: http://ubuntuforums.org/showpost.php?p=10800028postcount=11
which required installing grub 2 (grub-pc in synaptic in the 10.04 LTS repos)
first.
That method did *NOT* fix this issue. Apparently that method is for a
different issue.
(And I have since reverted the changes
I have also had this problem for quite some time. What seems to happen
is that I select suspend or hibernate and the system will not go to
sleep – the fans continue to whirr. I have actually gone back and tried
some old Ubuntu Live CDs and it seems that up to Ubuntu 7.04 it used to
be possible to
This issue looks like it *may* be (or may not be) related to bug
#219675: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/219675
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980083
Title:
What's throwing people off here is that if you're using an older version
of Ubuntu (10.04 LTS) in my case, there is no field to specify the URL
to download the blocklist from. So all the user ever sees is that the
update blocklist button now no longer works -- it produces the said
Update
in
futility carried out, then please, by any means, go right ahead and do
it. Nobody's stopping you. You're welcome. :)
regards,
--ropers
--
Cannot move some items into new menus in alacarte menu editor
https://bugs.launchpad.net/bugs/502136
You received this bug notification because you
Public bug reported:
Binary package hint: alacarte
In the alacarte menu editor, some items cannot be moved into new menus
(folders).
PROBLEM:
Steps to reproduce the problem:
1. Right click on the Ubuntu logo .. Applications .. Places .. System area in
gnome-panel.
2. Select Edit Menus. This
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37345942/Dependencies.txt
--
Cannot move some items into new menus in alacarte menu editor
https://bugs.launchpad.net/bugs/502136
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Alright, so I just booted off the 9.10 live CD, and I can confirm the
exact same behaviour under Ubuntu 9.10, with alacarte version
0.12.4-0ubuntu2.
--
Cannot move some items into new menus in alacarte menu editor
https://bugs.launchpad.net/bugs/502136
You received this bug notification because
...and what's worse, the default installation of Ubuntu even includes
CD/DVD Creator, trying to move which triggers this bug, in
Applications -- Accessories. Eat that, overeager premature Ubuntu bug
closers!
--
Cannot move some items into new menus in alacarte menu editor
going again without
fully rebooting them. It's a good thing.
See: http://en.wikipedia.org/wiki/REISUB
Kind regards,
--ropers
--
Alt-SysReq-K has no effect, or unintended effect (depending on system it is
used on)
https://bugs.launchpad.net/bugs/329644
You received this bug notification because you
*** This bug is a duplicate of bug 303601 ***
https://bugs.launchpad.net/bugs/303601
2009/7/29 ropers rop...@gmail.com:
2009/7/29 NappingUnderBricks afarri...@gmail.com:
I've got no idea what the 'REISUB' key is
It's not a single key. It's a key combination sequence that's
customarily
2009/4/28 Michael Jones eternal...@gmail.com:
@gorillastrong2
You can re-enable control-alt-backspace by modifying your xorg conf
file to include the lines
Section “ServerFlags”
Option “DontZap” “false”
EndSectionOption “DontZap” “false”
Jens Ropers rop...@gmail.com wrote
2009/4/28 Michael Jones eternal...@gmail.com:
@gorillastrong2
You can re-enable control-alt-backspace by modifying your xorg conf
file to include the lines
Section “ServerFlags”
Option “DontZap” “false”
EndSectionOption “DontZap” “false”
The above is slightly bad information because
2009/5/8 Michael Jones eternal...@gmail.com:
How exactly are you able to verify that when you received the information
from a website that undoubtedly modified the input it was given to be
correctly represented internally, and then transmitted to be displayed on an
unknown browser that
Thank you! :)
2009/3/31 jaduncan jaduncan+launchpad@jaduncan.com:
Original refusal was based on an IRC refusal, but upstream have now said
that while they won't do the work they are interested in patches.
Reopened to track.
** Changed in: coreutils (Ubuntu)
Status: Invalid =
2009/3/30 jaduncan jaduncan+launchpad@jaduncan.com:
This is correct behaviour as per POSIX - it's how it should work!
Says who?
This is something that would be an upstream bug, but they will not want
to change this behaviour.
Well, have you asked them?
--
incorrect cp(1) behaviour
2009/3/31 C de-Avillez hgg...@gmail.com:
Interesting. Jim Meyring's answer did not make it here (although,
AFAICS, it was correctly addressed). So, here it is:
Jens Ropers wrote:
2009/3/30 jaduncan jaduncan+launchpad@jaduncan.com:
This is correct behaviour as per POSIX - it's how
I can also confirm this. And to repeat what I previously posted here (
http://www.reddit.com/r/linux/comments/7vry9/help_my_magic_sysrq_keys_reisub_no_longer_work_in/
) :
Ever since I started running Ubuntu 8.10 (Intrepid Ibex), I found that
the magic SysRq keys (REISUB or similar) no longer work
Public bug reported:
Some time ago, I did some research about the way Ubuntu uses screen real
estate. I posted the results here:
http://www.reddit.com/r/linux/comments/7kn5y/is_it_just_me_or_do_nix_des_do_a_horrible_job_at/14xg
It turns out that Ubuntu is roughly on par with OS X, but only
. Some legacy software doesn't run as well on Wine, and I
got a legal Win ME license for free.)
Thanks and regards,
ropers
2008/11/7 Bryce Harrington [EMAIL PROTECTED]:
Hi ropers,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while
2008/11/8 ropers [EMAIL PROTECTED]:
Hi Bryce,
Do you think it will be possible to test this from a live-CD?
I'm asking because I've rebuilt and mixed and matched a lot of my PCs,
and my SiS 630 256MB 1GHz PIII with that unichrome onboard graphics
hardware actually currently runs Windows ME
Public bug reported:
Binary package hint: gnome
Currently, some Ubuntu/Linux applications move items to ~/.Trash/ when
deleting files, while other programs move the data to
~/.local/share/Trash/ .
~/.local/share/Trash/ seems to be the newer location, apparently it's
recommended by the XDG Base
PS: To add to the above workaround, using not just
xvattr -a XV_BRIGHTNESS -v 24
but also
xvattr -a XV_CONTRAST -v 3000
makes the picture better, and more similar to a gamma 1.6 corrected picture.
(The default values are 0 and 4096, respectively.)
--
totem overrides XV_CONSTRAST to wrong
I am having the same problem with 7.10.
I have a very old and dark HP D2808 monitor.
In my /etc/X11/xorg.conf file, I have set this line
Gamma 1.6
to adjust the gamma correction.
However, in Ubuntu 7.10 Gutsy Gibbon, XVideo does not respect the X
Window system-wide gamma correction setting.
I'm having the same problem.
Maybe this will clarify things a bit:
The problem is that in a Rhythmbox installation in Ubuntu 7.10, the GOOM
visualization plugin does not work -- when visualization is active and
GOOM is selected, Rhythmbox can even seize up and almost freeze.
Sometimes even the
PPS: While GOOM now works, there still is a significant delay upon
activating a GOOM visalization. The music playback may even stop for a
while. This is on an Intel Celeron 2.8 GHz PC with 2 GB RAM, so this
probably should not happen.
--
Rhythmbox not display graphics if click on visualization
Maybe if the issue with the GOOM visualization cannot be fixed, then a
good alternative would be to remove the GOOM entry from the Rhythmbox
visualization menu. libvisual-0.4-plugins might be a good alternative.
Upon installing this package (not installed by default), a number of
nice and
PS: The OP mentioned Compitz. I don't think Compitz has anything to do
with it; for what it's worth, I have it disabled and I'm having the same
problem. I don't even think OpenGL is necessarily at fault -- OpenGL
works on my system, and I can use demanding OpenGL applications such as
Chromium
-xr-x 3 ropers ropers 4096 2007-10-19 22:57 ./
| drwxr-xr-x 85 ropers ropers 4096 2007-10-19 22:56 ../
| drwxr-xr-x 2 ropers ropers 4096 2007-10-19 22:57 foo/
| -rw-r--r-- 1 ropers ropers0 2007-10-19 22:56 testfile
| [EMAIL PROTECTED]:~$ ll foo/foo
| total 8
| drwxr-xr-x 2 ropers ropers 4096
Public bug reported:
I am running Ubuntu 7.04 with the Openchrome video drivers (
http://www.openchrome.org/ ). I have configured my xorg.conf to set a
gamma correction of 1.7. The gamma adjustment works fine in X, but does
not work with any application using xvideo (aka xv, aka the X video
I should add that I have not found a way to get Gamma correction to work
with the (default) Totem Movie Player. I have resorted to adjusting the
brightness and contrast in Totem under Edit - Preferences - Display -
Color balance; but it's not as good a solution as proper Gamma
correction.
--
Another addition:
agpart detects my chipset as follows (from dmesg):
agpgart: Detected VIA VT3314 chipset
--
Gamma correction does not work with xvideo using Openchrome drivers
https://bugs.launchpad.net/bugs/152377
You received this bug notification because you are a member of Ubuntu
Bugs,
It shouldn't be necessary to use your packaged SVN version. This page:
https://help.ubuntu.com/community/OpenChrome describes all that should
be needed to get things to work.
--
Unsupported Chipset - VT3344
https://bugs.launchpad.net/bugs/109626
You received this bug notification because you are
I've previously posted the following info at bug 26118, but was advised
that it's probably related to this bug, so I'm reposting things here:
I'm also seeing absolutely atrocious font rendering with some PDF files
in evince.
gpdf renders the same PDFs much better, but appears to use different
To add: I'm just noticing now that after upgrading to Ubuntu 7.04, the
issue appears to be resolved for me -- I get decent PDF rendering in
evince 0.8.1 now. If others can confirm this, then maybe this bug could
be closed?
--
[Feisty] Low quality of text rendering in Evince
Thanks Peter. I've reposted my info there.
--
Bad rendering (hinting) in Evince and Xpdf
https://bugs.launchpad.net/bugs/26118
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
IMHO VF's suggestion is probably somewhat useful.
I'm still not sure how to avoid that commands that might not be
installed are mentioned on man pages -- maybe it cannot be avoided, or
maybe it would require fairly involved changes to the entire man system,
so that only those see also entries are
@Marciano Siniscalchi
Thank you for your comment.
Do you/does anyone know if there is another bug filed for that Type 3 fonts
rendering issue?
--
Bad rendering (hinting) in Evince and Xpdf
https://bugs.launchpad.net/bugs/26118
You received this bug notification because you are a member of
Just encountered this bug as well. Here are my two eurocents:
The fact that '/bin/kill -L' *does* work as documented in 'man 1 kill'
but 'kill' (ie. bash built-in kill) *does not* is an inconsistency.
Inconsistencies should be avoided. IMHO this could be fixed EITHER by:
- removing the 'kill -L'
Public bug reported:
I've encountered the following documentation error: In 'man 1 wall', it
says:
SEE ALSO
mesg(1), talk(1), write(1), shutdown(8)
However, talk(1) does not exist on a default Ubuntu install:
$ talk
bash: talk: command not found
$ which talk
$ sudo find / -name talk
I don't know if this is related, but I'm also seeing absolutely
atrocious font rendering with some PDF files in evince.
gpdf renders the same PDFs much better, but appears to use different
fonts and ignore settings such as bold.
Please see the following two screenshot for comparison. Yes, this
** Attachment added: gPDF pdf screenshot
http://librarian.launchpad.net/7035138/Screenshot.gpdf.png
--
Bad rendering (hinting) in Evince and Xpdf
https://launchpad.net/bugs/26118
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is the actual PDF file the above screenshots were taken with.
** Attachment added: PDF file that is rendered badly in evince (and gPDF is
not too great either)
http://librarian.launchpad.net/7035319/18280.pdf
--
Bad rendering (hinting) in Evince and Xpdf
This needs to be investigated by someone knowledgeable enough before
it's committed.
man hosts
sudo vi /etc/hosts
ji# ESC$bywk$a ESCp:x
(DISCLAIMER: I'm a BSD guy. If this, for whatever weird and wonderful
reason, breaks shit in Linux, don't blame me.)
--
[feisty] Slow gnome application
On 12/12/06, David Farning [EMAIL PROTECTED] wrote:
Jens,
Thanks for your crash report.
Could you please download you crash report, run
apport-retrace -d [filename]
and resubmit it. Instructions can be found at
https://wiki.ubuntu.com/Apport
I am working my way though all of the
Public bug reported:
I do not know whether this is reproducible, but this is what I did:
1. Open graveman.
2. record an iso from a CD-ROM
3. Tell graveman to write that iso to a blank disk
This is when graveman crashed, 3/4 thru the operation.
** Affects: graveman (Ubuntu)
Importance:
** Attachment added: .crash file
http://librarian.launchpad.net/5059437/_usr_bin_graveman.1000.crash
--
crash while writing a previously recorded iso image to CD-ROM
https://launchpad.net/bugs/71579
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Movie Player (totem) crashes repeatedly. Not sure if I can get it to
work with ANY movie after upgrading to Efty Eft. It worked under Dapper.
** Affects: totem (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Movie Player (totem) crashes
Public bug reported:
I had Realplayer installed in Dapper.
This worked with the BBC News website.
I upgraded to Edgy Eft.
I then visited the BBC News website and tried to watch a video and couldn't.
I then tried to change the video preferences, by clicking on a link in the
bottom left of the
** Attachment added: problem report
http://librarian.launchpad.net/4939392/_usr_lib_firefox_firefox-bin.1000.crash
--
firefox crash in connection with attempt to change video console preferences at
BBC News website
https://launchpad.net/bugs/68921
--
ubuntu-bugs mailing list
Public bug reported:
Hi,
When having a 1GB USB keyfob / flash drive plugged in while booting a
Ubuntu 6.06 LTS default install, the FAT32 partition gets mounted in
case-sensitive mode.
At the very end of the dmesg it says this after bootup:
[17179647.74] FAT: utf8 is not a recommended IO
I probably didn't explain myself very well and/or didn't put the
emphasis right here:
Having figured things out as far as this, I don't see the utf8 is not a
recommended part of the error message as central or even as much of an
issue. Yes, I do think it's not nice to have error message thrown if
Thanks for your replies.
I'm noticing that a FAT32 hard drive partition I am mounting via
/etc/fstab does not have the problem of (incorrectly) being case-
sensitive. It (correctly) is case-insensitive.
From my /etc/fstab:
/dev/hdc1 /mnt/fattie vfat
user,auto,uid=ropers,gid=ropers
58 matches
Mail list logo