The duplicate link has been removed.
** This bug is no longer a duplicate of private bug 1441038
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442568
Title:
Docker causes a segfault when starting
Public bug reported:
When using Intel Skylake Graphics the dmesg logs send the message
"i915_bpo :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus
alignment" every couple of minutes.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-video-intel
Public bug reported:
After leaving redshift-gtk open for an extended period and then opening
info it displays no info. After closing and reopening (or trying to)
redshift-gtk will segfault because of GTK3.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: redshift-gtk 1.10-5ubuntu1
Public bug reported:
When playing any type of video on an Skylake CPU with Intel graphics
(open-source) with or without acceleration VLC (and many othe
applications) show the context and file menus under the video making
them invisible to the user even though technically they are there
just
I still get this problem in Xenial as well... randomly but it happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications
It should be noted that the link above my comment that claims that it's
stable download, it's not stable, and 2.5 has lots of UI issues on
Ubuntu which have not been addressed (as of my last testing) so be
prepared if you plan to use 2.5.
--
You received this bug notification because you are a
I mean parted* sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325708
Title:
Error in `/usr/sbin/gpartedbin': malloc(): smallbin double linked list
corrupted: 0x0107d210
To manage
This error is actually caused by libparted even though it claims to
originate from gparted as the same error can happen in fat32.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325708
Title:
Error
Public bug reported:
When opening VLC from the command line and being unable to find the file
VLC will consume 100% of the CPU usage and retry-reopening it over and
over again consuming 100% of the CPU. This can be replicated on Ubuntu
14.04.
---
VLC media player 2.1.2 Rincewind (revision
ii libvlc5 2.1.2-2build2
amd64multimedia player and streamer library
ii libvlccore7 2.1.2-2build2
amd64base library for VLC and its modules
ii
Indeed it looks to be related to the repeat feature as that fixed it,
but I don't know if that is expected behavior as software should behave
and this doesn't seem like behaving, could this behavior not be adjusted
so that if it detects a single file with a missing over and over again
it does not
Fair enough, I can actually agree with that logic.
** Changed in: vlc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314964
Title:
vlc 100% cpu usage when
Can't tell if trolling because nothing is stopping you from opening VLC
and disabling overlay video for the time being. Stop trying to open it
with a video and you wouldn't have it crashing your X while trying to
fix the problem.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1279412 ***
https://bugs.launchpad.net/bugs/1279412
Thank you for taking the time to help Ubuntu and for reporting this bug,
but I believe this bug is a duplicate of #1279412 so I have marked it as
so.
** This bug has been marked a duplicate of bug 1279412
This is an upstream bug, and it's been fixed in 13.1 so please either
install 13.1 or wait until Ubuntu updates fglrx in the repository (even
though they are practically the same -- minus a few differences -- if
you build them.)
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
I forgot all about that until you had mentioned the 12.12 driver, for
those of you who cannot wait you can get the 12.11 beta (which of course
is the 12.12) and install it:
http://support.amd.com/us/kbarticles/Pages/AMDCatalyst1211betadriver.aspx
--
You received this bug notification because you
Crap, I had a strong suspicion this was the case because I too didn't
experience this bug in 12.10 but 12.10 did not really appeal to my
tastes (because of some personal reasons that aren't necessary to this
bug.) I don't remember if I ever mentioned that in another bug or not.
Just as a side
*** This bug is a duplicate of bug 1033226 ***
https://bugs.launchpad.net/bugs/1033226
Nearly is subjective IMO. While I think the behavior can/should change
I don't think it's forced at all. Much like Windows it allows you to
minimize it but it makes sure to (try and) keep itself inside
Why is this constantly being pushed? And being pushed at all, this is a
pretty critical issue that breaks quite a few laptops, I don't even
understand why you would ignore an issue like this and push it instead
of making it a top priority issue...
--
You received this bug notification because
While we're at it, can anyone update us on the status of this bug in
Precise? When I tested it on Quantal it was working exactly as intended
with no side-affects like this so I'm wondering if there are plans to
fix this soon? Since it seems like it didn't make it into the point.
--
You received
I don't know if this is related or not but this might not be a GNOME
bug, this might actually be a Kernel bug with HP's as on my system the
Kernel reports that it is unable to obtain the brightness with the
message [Firmware Bug]: ACPI: No _BQC method, cannot determine initial
brightness
--
You
@racb Setting aside the fact that you think I don't know how to
configure a server or prevent it, the faulty logic is that because you
can fork bomb already this problem doesn't matter and it's not worth it
yeah? I don't know if that's funny or what...
--
You received this bug notification
@racb Setting aside the fact that you think I don't know how to
configure a server or prevent it, the faulty logic is that because you
can fork bomb already this problem doesn't matter and it's not worth it
yeah? I don't know if that's funny or what...
--
You received this bug notification
** Attachment added: Screenshot from 2012-07-16 13:34:04.png
https://bugs.launchpad.net/bugs/1025418/+attachment/3225301/+files/Screenshot%20from%202012-07-16%2013%3A34%3A04.png
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
You received
** Summary changed:
- Using ProxyCommand with a non-existant URL results in infinite spawns.
+ Using ProxyCommand with a non-existant host results in infinite spawns.
** Summary changed:
- Using ProxyCommand with a non-existant host results in infinite spawns.
+ Using ProxyCommand w/a
** Attachment added: Screenshot from 2012-07-16 13:34:04.png
https://bugs.launchpad.net/bugs/1025418/+attachment/3225301/+files/Screenshot%20from%202012-07-16%2013%3A34%3A04.png
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
You received
** Summary changed:
- Using ProxyCommand with a non-existant URL results in infinite spawns.
+ Using ProxyCommand with a non-existant host results in infinite spawns.
** Summary changed:
- Using ProxyCommand with a non-existant host results in infinite spawns.
+ Using ProxyCommand w/a
As a work around for some people you can install compizconfig-settings-
manager and go into the General Options then hit up display settings and
disable smart-mode. Although I assume this fix only works for people
with different monitors with different resolutions (such as the people
like me who
This bug affects all my G series and Envy series HP laptops, as well as
my Dell. They all either have an AMD APU (all my HP laptops) or an i5
(the Dell). We had the same problem back in 11.10. There is one thing
in common between all my laptops and that's that they all have 7 series
graphics,
openssl s_client -showcerts -connect d3vwyrdyja2n00.cloudfront.net:443 - Fails
openssl s_client -showcerts -tls1 -connect d3vwyrdyja2n00.cloudfront.net:443 -
Works
** Changed in: openssl (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of
Please do not update my description as that is the description that
affected me if you are having something similar but different add your
own comment, do not update mine as if I am having the same issue.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Nobody cares what you believe. A persons attitude and opinion (read
opinion, you know what that means yes?) does not dictate whether a bug
is legit or not. Go see a shrink if you have personal problems with a
way a person acts and don't close a legit bug because you have issues
with the way people
Ubuntu looks like trash with a white menu on a dark theme regardless of
where it is placed or where it is sourced from or whatever the
justification is. It's an ignorant design decision and any designer who
would stand for such an ugly mark should not be designing. I know I'm
being harsh here but
Don't mark a bug as invalid just because you think you can. This bug is
still affecting people and there are still issues going on regardless of
the bad design decision there are still obvious bugs. I find it ironic
you call somebody rude and then go and do something like that.
** Changed in:
Who in their right mind decided that light right click menus was good
taste? Is the goal to punish users who spend most of their lives in a
dark terminal? To punish programmers? To punish anybody who doesn't
like such contrasting design decisions? I just don't understand who
could have approved
@andrea so just one question. Will the final goal be that dark
sources create dark context menus and light sources create light
context menus? If that's the case I'm down for that but the only thing
that is catching me as possibly eye fracturing is the possible white
context menu on dark places
This is more than likely a Unity compiz-plugin issue and I'll have to
look at your and my logs more but this is certainly confirmed and it's
confirmed that the fix is to set the colour to anything but RGB 0,0,0
(example: I used 1, 1, 1 and could set the opacity to anything above 50
and it would
@om26er RGB(0, 0, 0), set the transparency to 10. Bug Recreated.
Screenie attached.
** Attachment added: screenshot#2012-02-04#05:10:42.png
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/926144/+attachment/2713272/+files/screenshot%232012-02-04%2305%3A10%3A42.png
--
You received this
@fitoschido I don't quite understand what you are on about? You
experience the bug (but not in the indicator but in other menus -- not
realising that I /didn't/ imply it only happens to indicator) yet you
don't acknowledge this as a bug? Or am I missing something entirely in
your statement?
--
@fitoschido There is a difference between bright and white (and when it
comes to good monitors -- like the one I have -- you can see every step
of black they use -- really well.) I would not personally see a white
menu or even a 'bright' menu on a black theme any valid design decision,
it's bad
Public bug reported:
After the latest light-themes update today the menus for Ambiance are
light as if they actually belong to Radiance. Some icons also end up
having a orange box as a background as well but that's an entirely
different bug.
Distributor ID: Ubuntu
Description: Ubuntu precise
** Attachment added: screenshot_at#2012-02-03#01:17:51.png
https://bugs.launchpad.net/bugs/925895/+attachment/2709430/+files/screenshot_at%232012-02-03%2301%3A17%3A51.png
** Description changed:
After the latest light-themes update today the menus for Ambiance are
- light as if they
** Changed in: file-roller (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916806
Title:
file-roller crashes with CTRL+click on items in archive
To manage
I just checked out the development branch (http://bazaar.launchpad.net
/~ubuntu-branches/ubuntu/precise/light-themes/precise/revision/46) and
this problem is still going on unless I am missing something special.
Is there some hidden branch I'm not seeing?
--
You received this bug notification
*** This bug is a duplicate of bug 879950 ***
https://bugs.launchpad.net/bugs/879950
Everyone, please do not post your 'this fix worked for me' and 'this bug
also affects me and here is why it matters', there is a button for that,
also: please next time merge the newer bug into the older, it
** This bug is no longer a duplicate of bug 879960
Impossible to get contact list visible in Unity after reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879950
Title:
pidgin not showing up
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916806
Title:
file-roller crashes with CTRL+click on items in archive
To manage notifications about this bug go to:
Public bug reported:
Distributor ID: Ubuntu
Description: Ubuntu precise (development branch)
Release: 12.04
Codename: precise
Command: date
Package: coreutils
What happened: Sat Jan 21 10:44:14 CST 2012
What I expected to happen: Sat, Jan 21, 2012. 10:44:14 CST (or similar
formatting)
When
Just updating to say this is still a problem in Natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/657901
Title:
linux-virtual depends on wireless-crda
To manage notifications about this bug go
For now I'm going to mark this bug as incomplete since so far it seems
like it could be a faulty drive, if you have any more information please
feel free to post it and keep everyone updated so we can try to help you
out further. Thanks.
** Changed in: linux (Ubuntu)
Status: Confirmed =
Can we get a filtered dmesg for the failing server and a bootdmesg for
both to compare? Your UFW is taking up valuable real estate in dmesg so
it might be fitting to attach log outputs without all the UFW cruft if
you can please.
--
You received this bug notification because you are a member of
I would much more prefer the output of dmesg |grep -v UFW and there
should be indicators in dmesg unless there is a random race condition,
but so far this seems like it might be the drive but we'll have to see
some logs to make an informed guess on that.
--
You received this bug notification
Please attach a patch so that I might apply it and test it to report
results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665944
Title:
System takes too long to activate wifi on resume
To manage
I haven't had a chance to look at the script yet, but after testing, it
seems that using the switch --allow-system-internal you will be able to
install the bootloader on a USB stick, I tested this with 11.04 making
an 11.04 startup disk to a PNY stick. Would one of you who reported
this also try
This bug is far wider than the original submitter had originally
assumed. After testing this bug for security (by recommendation) and
validating it to see if it should be closed, I soon discovered I was
able to delete /dev/null and /etc/ndiswrapper and any other directory I
chose to delete using
Belabela,
Publicly editable does not mean it's insecure. The Wiki does keep track
of all edits so that an audit can happen. By your theory the
information you linked to on Wikipedia is insecure as well, because I
can go and edit it freely and forge all kinds of information. HTTPS
does not make
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read How to report bugs effectively
Can we get a snapshot of /var/log/apt/history.log too if you don't mind
so that we can see if apt stopped logging actions too and to determine
if this is a bug in synaptics or a possible bug in apt. Thanks for
helping us narrow this down. You should see something like:
Start-Date: 2010-11-07
** Changed in: synaptic (Ubuntu)
Status: Incomplete = Confirmed
--
[Maverick] History missing
https://bugs.launchpad.net/bugs/672354
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have requested that this bug have an importance set since it is a
confirmed bug, I experienced it today while configuring several of our
new VM's on a new Xen server with PV-Grub. I was pretty surprised and
intrigued it required it at all. It should really be a recommend not a
requirement.
--
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, at this time this bug lacks some basic
information and is pretty general. Could you please try the following
to see if we can get more information on the error:
sudo service postgresql start
Does it
Hey Emada,
The error was located in DPKGTerminalLog.Txt.
** Changed in: postgresql-8.4 (Ubuntu)
Status: Incomplete = Invalid
--
package postgresql-8.4 8.4.3-0ubuntu9.10 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
Hello Joschi
dpkg -P is a purge. If a package is being uninstalled by apt, synaptics
or aptitude and does not properly purge the files, you should file a bug
against the respective package manager instead of against postgresql.
Thanks for taking the time to help make Ubuntu better.
** Changed
** Changed in: postgresql-8.4 (Ubuntu)
Status: New = Incomplete
--
package postgresql-8.4 8.4.5-0ubuntu10.04 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/665983
You received this bug notification
This was fixed in the final release.
** Changed in: fglrx-installer (Ubuntu)
Status: New = Invalid
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned) = Jordon Bedwell (envygeeks)
--
Patch required by fglrx but not supplied automatically
https://bugs.launchpad.net/bugs
Public bug reported:
Binary package hint: ruby1.9.1
Some people may opt to install ruby1.9.1 because it provides ruby1.9.2
which is known to be faster in benchmarks than Ruby1.8 however, it came
a surprise today when I installed ruby1.9.1 on a production system and
it provided gem which is
I'm pretty sure I implied it was included? And it's not too complicated
to remove. It took us mere minutes to remove it from the source and to
rebuild it. The least you could have done was ask it be moved upstream
instead of making up bad excuses and marking the ticket as invalid when
it's a
Still plaguing Maverick as well.
--
GDM login theme change when using accessibility features
https://bugs.launchpad.net/bugs/402017
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Is this bug still affecting you? As of today, after checking it appears
that hand installed software does get listed in the software centre. I
have tried this with skype, opera, GIMP PPA and Google Voice Plugin.
--
Downloaded .deb doesn't appear in Installed Software after installation
Public bug reported:
Binary package hint: fglrx
When a user attempts to install fglrx on Maverick via additional
drivers or even manually using apt-get they will receive: Error!
Application of patch use-cflags_module-together-with-modflags.patch
failed via apt-get or simply just get an error
** Description changed:
Binary package hint: fglrx
When a user attempts to install fglrx on Maverick via additional
drivers or even manually using apt-get they will receive: Error!
Application of patch use-cflags_module-together-with-modflags.patch
failed via apt-get or simply just
** Changed in: apport (Ubuntu)
Status: New = Incomplete
--
cannot report a bug of a root process
https://bugs.launchpad.net/bugs/641469
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
David,
This is not a bug, it's a feature. According to upstream you can disable
NX Bit using the kernel flag noexec=off and noexec32=off, if you still
have problems, disable it in your CPU too using your BIOS. Please also
refrain from making false statements about other operating systems on
David,
This is not a bug, it's a feature. According to upstream you can disable
NX Bit using the kernel flag noexec=off and noexec32=off, if you still
have problems, disable it in your CPU too using your BIOS. Please also
refrain from making false statements about other operating systems on
I was unable to replicate this and was able to run a report on a root
process using sudo. Are you sure that the process was still alive when
you were trying to run the report? Try doing: sudo ubuntu-bug 1 and
see if you still get that message so you can work out whether or not it
was simply an
*** This bug is a duplicate of bug 638085 ***
https://bugs.launchpad.net/bugs/638085
** Visibility changed to: Private
** Visibility changed to: Public
--
policyui.py crashed with GError in __init__()
https://bugs.launchpad.net/bugs/647291
You received this bug notification because you are
76 matches
Mail list logo
