Not to be overly repetitive, but this is still an issue 8 years later...
While the solution discussed above (pulling the release name from /etc
/lsb-release) would certainly be nice, there's no reason this really
needs a fix that complicated. Every instance of the word "Ubuntu" can
be avoided by
This is still happening as of Trusty. We're still forced to fork the
package...
** No longer affects: usb-creator (Nexradix)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/321937
Title:
The package update in question does not appear to have fixed this, at
least not for me. Running Precise, I upgraded software-center to
version 5.2.9, then ran sudo update-apt-xapian-index -vf. I got the
same results as reported originally, with the workaround I posted
(though now on line 166)
I just installed version 6.01, and still don't see the memory functions,
in any of the modes. I don't see how this has been fixed. Am I
missing something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes. I can confirm this bug still present 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/682233
Title:
Copy disc progress dialog box should be able to be minimized
To manage
Public bug reported:
When software-center is installed on an Ubuntu derivative (in our case,
Nexradix), update-apt-xapian-index fails.
When run, a python error indicating that no module Nexradix is found
When I replace lines 112-114 in /usr/share/software-
Public bug reported:
Binary package hint: gnome-session
Since Maverick, gnome-session has changed the names of the default GNOME
sessions to refer specifically to Ubuntu. This requires downstream
distros based on Ubuntu to fork the gnome-session package simply to
remove the Ubuntu branding.
I
Is my previous comment sufficient to remove the incomplete status? Or
do you need more info? I'd be glad to help if that's the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/570592
Title:
It's been six months now with no response. Surely someone can at least
give me a general idea? Ubiquity has almost no useful documentation
that I've found, and I've gotten virtually nowhere with trial and error.
I'd be willing to pay a reasonable bounty to see this feature
implemented.
--
You
I can confirm that this is still an issue on Maverick. Tested with an
MKV with embedded subtitles -- I get the italics tag instead of text
displayed in italics. If I use mkvextract to extract the subtitles to
an external .srt file, and then select this file in Totem, the subtitles
display
I can confirm this is still an issue in both lucid and maverick. I can
also confirm that the solution from post #3 works for me.
I'm not sure this is an upstream issue -- if Calibre requires a
customized version of pypdf, then it makes sense that such a customized
version be provided in the
Public bug reported:
Binary package hint: brasero
Currently, the dialog box that provides the progress indicator during a
disc copy cannot be minimized. Given the fact that it is always on top
of any nautilus window, it is particularly difficult to get work done
while the copy is active.
A
Wow, sorry for the slow response. Totally forgot about this one.
I'm currently on Lucid. I'll try Maverick to see if it has been fixed
there.
Meanwhile, it seems that Jacob Nevins is correct: my bug is indeed a
duplicate of #463029, and as such can be closed.
--
GDM requires you to hit an
Would anyone mind taking a look at this for me? I've spent a few hours
digging around Ubiquity's code, but can't seem to find exactly what I
need to change to get this working.
--
Cannot preseed manual partitioning mount points
https://bugs.launchpad.net/bugs/617607
You received this bug
Any news on if anyone else has confirmed my fix in post #40?
--
no second attempt and no feedback when wrong password entered
https://bugs.launchpad.net/bugs/298217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I believe I have found the solution to users that have upgraded from
previous versions to Lucid:
arab80ps reported above that typing gksu natuilus and entering the
wrong password returned the following for him:
GNOME_SUDO_PASSSorry, try again.
sudo: 3 incorrect password attempts
For me, it
As stated by myself and Jean-Peer Lorenz, this bug is NOT fixed on Lucid
systems that have been upgraded from previous versions.
What other info do you need from us to help fix this?
--
no second attempt and no feedback when wrong password entered
https://bugs.launchpad.net/bugs/298217
You
Indeed, the correct package is installed according to dpkg -l
libgksu2-0
The results of gksu -d whoami is attached.
** Attachment added: gksu-results.txt
https://bugs.launchpad.net/ubuntu/+source/libgksu/+bug/298217/+attachment/1654055/+files/gksu-results.txt
--
no second attempt and no
I just tested the libgksu package from lucid-proposed (now that it is
there for real...). It fixed the issue on a fresh install of lucid, but
on two of my machines with existing installs, the problem persists.
Any idea where the inconsistency could be? Both of the existing
installs were
I experience this issue when using Remastersys on the standard Ubuntu --
Ubiquity will crash when run from the generated ISO and encrypted home
directory support is chosen.
The patch listed by Arthur Lutz on comment #4 appears to have fixed the
issue for me as well.
--
ubiquity crashes with
Public bug reported:
Binary package hint: grub2
Setting a numerical value for GRUB_HIDDEN_TIMEOUT in /etc/default/grub
properly sets a delay during boot that allows the user to press shift
to display the Grub menu. However setting
GRUB_HIDDEN_TIMEOUT_QUIET=false no longer displays a countdown
I compiled libgksu 2.0.13~pre1-1ubuntu5 from source on Lucid, and the
problem persists.
--
no second attempt and no feedback when wrong password entered
https://bugs.launchpad.net/bugs/298217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: gdm
When one disables the user list browser using the disable_user_list
gconf key, GDM shows a login button prior to allowing you to type in
your username. This is completely unneeded, and adds unnecessary time
to the login process. GDM 2.20 would
This behavior should be configurable, rather than forced. While I agree
that the default should be to forbid a root login with GDM, one should
be able to enable such functionality if they so choose.
--
GDM allows root logins
https://bugs.launchpad.net/bugs/484317
You received this bug
I'd like to help impliment this feature, if possible. Can anyone point
me in the right direction of where to start?
--
Cannot preseed manual partitioning mount points
https://bugs.launchpad.net/bugs/617607
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Since gdm-2.20 is no longer in the repositories, I suppose this can
probably be closed, unless there is hope that it will return for
Maverick (which I hope it will).
--
[needs-packaging] needs-packaging: gdm-guest-session-0.8
https://bugs.launchpad.net/bugs/501492
You received this bug
Public bug reported:
When adding a PPA using the sudo add-apt-repository ppa:ppa-name
command, the distribution codename specified in /etc/lsb-release is used
when adding the entry to /etc/apt/sources.list. Unfortunately, this
has the side effect of causing the add PPA functionality to not work
Public bug reported:
Binary package hint: ubiquity
Normally, when one chooses manual partitioning, Ubiquity presents a disk
configuration based on the current configuration. However no mount
points are selected by default. We are attempting to preseed an
installation that takes advantage of
Yep, still in Lucid. I can confirm that the previously mentioned
solution works with the Lucid version of nautilus, but it does (as
mentioned) require recompiling. I'd very much like to have this fixed
for Maverick... if nothing else, why not just make the fix listed above
the default until a
Looks like the wording of my original bug could have been better, sorry.
The appending of digits after the brasero file name was my idea of a
stop-gap solution so the program would still be usable. But my actual
request was to use the volume name of the disc as the file name as
To answer your question: It seems to me that given how many distros are
based upon Ubuntu, making things easy to rebrand makes the most sense
for everybody. There is no particular reason printer test pages need to
be branded at all, regardless of what the distro branding is.
But if that's
I'm still getting this in Lucid. I don't have a screenshot this time,
but the message looks basically identical.
If this is to be filed as a wishlist item instead of a bug, I assume
it likely won't be fixed any time soon. Would someone mind pointing me
in the right direction as to where I
Any chance this is still being considered? Not only would it fix the
bug I described in #4, it would also be a very useful feature for
installing .deb packages locally. Currently, there is no easy way to
install multiple local deb files, except by using the command line.
--
gdebi does not
This is still happening as of Lucid. Any chance of it being fixed for
Maverick?
--
Installation Complete message text contains reference to Ubuntu rather than
using the current distro name
https://bugs.launchpad.net/bugs/499334
You received this bug notification because you are a member of
Good to know the appending of the number issue has been fixed -- how
about using the volume name as the file name instead of brasero? Or
should I just open a separate bug for that, since this one seems to be
closed?
--
Copy disc to ISO image always uses brasero.iso by default
This is not a bug in gksu, at least not as of Lucid. It is a bug in
sudo. Downgrading sudo to the version in the Karmic-Updates repository
fixes this problem. However downgrading the gksu package does not fix
it, indicating the issue is with the sudo package alone.
--
no second attempt and no
Reported upstream as requested:
https://bugzilla.gnome.org/show_bug.cgi?id=612980
** Bug watch added: GNOME Bug Tracker #612980
https://bugzilla.gnome.org/show_bug.cgi?id=612980
--
Copy disc to ISO image always uses brasero.iso by default
https://bugs.launchpad.net/bugs/505341
You received
Bug filed upstream as suggested:
https://bugzilla.gnome.org/show_bug.cgi?id=612982
** Bug watch added: GNOME Bug Tracker #612982
https://bugzilla.gnome.org/show_bug.cgi?id=612982
--
can't catch $USER in /etc/gdm/PostLogin/Default
https://bugs.launchpad.net/bugs/463376
You received this bug
I see your point about the branding, but as far as I know, no one
currently gets confused when someone asks Is X available in Synaptic
Package Manager, despite the fact that many different distros use it.
However, provided that the title becomes dynamic as you suggest, that
becomes a moot point.
True, but it seems to happen pretty often. For example ubiquity and
ubiquity-frontend-gtk depend on one another...
Either way, both dpkg and Synaptic have no problems with this, so
neither should gdebi.
--
gdebi does not support multi-package installations
https://bugs.launchpad.net/bugs/37649
This does not appear to be fixed upstream. I have the exact same issue
using Totem in Karmic. I also tried using the version of Totem from
karmic-updates, but the issue persists.
When launching Totem from a terminal, I get the following error when
trying to play the file:
** Message: Error:
Public bug reported:
Binary package hint: gnome-system-tools
shares-admin does not currently allow the restricting of a share to a
set of specific users. While you can restrict global share access to
users on the list via the users tab, there is no way to set certain
shares as accessible only
I can confirm this. When installing via PXE boot using a Karmic Desktop
Install CD, the installed system does not properly connect to the
network automatically the way the live environment did. Running sudo
dhclient gets an address, and it then connects fine, but when you
reboot it is back to
Public bug reported:
Binary package hint: system-config-printer
Currently, the test prints are branded with a huge Ubuntu logo at the
top. This is unnecessary, and provides no additional functionality, as
the end user is unlikely to do anything substantial with the test page
after it has been
Using gparted to format first does seem to work, but that's not a
realistic workaround for end-users, who would never figure this out on
their own.
What's makes things worse is that usb-creator's attempt to format the
drive leaves it with a corrupted formatting, causing it to be useless
until you
** Also affects: usb-creator (Nexradix)
Importance: Undecided
Status: New
** Changed in: usb-creator (Nexradix)
Importance: Undecided = Medium
** Changed in: usb-creator (Nexradix)
Assignee: (unassigned) = Twisted Lincoln, Inc. (twistedlincoln)
** Changed in: usb-creator
This seems like a no brainer to me. If one wants to remove all traces
of a package (including config files), it makes perfect sense that
they'd want to do the same for the dependencies. Make it a preferences
option if nothing else...
As it stands, one has to go back and purse the dependencies
While this isn't a situation that happens often, it is certainly a bug
that should be addressed. Any chance to get this in for Lucid?
--
Should run dpkg --configure -a automatically
https://bugs.launchpad.net/bugs/19021
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: synaptic
There is no point in offering the user the option to completely remove
a package when it has no configuration files to completely remove. It
would make sense to keep this option unselectable when selecting a
package that has no config files.
I'd love to see this fixed. As it stands, if two packages depend on
each other, gdebi can't install either of them, as with each package, it
expects the other to be installed first.
--
gdebi does not support multi-package installations
https://bugs.launchpad.net/bugs/37649
You received this bug
I'd be willing to sponsor the addition of this feature if a developer is
willing to add it for a reasonable fee. Feel free to contact me
directly via the address on file with Launchpad.
--
gdebi-gtk - Include uninstall button
https://bugs.launchpad.net/bugs/74042
You received this bug
Public bug reported:
Binary package hint: software-center
Software-center is currently branded as Ubuntu Software Center in
several places. This requires downstream distros to fork the package
in order to remove the Ubuntu branding.
Instead, software-center should look to the current distro
Public bug reported:
Binary package hint: brasero
Brasero's predecessor (nautilus-cd-burner) would automatically name ISO
images the same as the volume name of the disc being copied.
Brasero always uses brasero.iso as the default name, forcing you to
manually change the name when ripping
I can't confirm of deny Imre's comment (I am no longer running nautilus
2.28 because of this bug), but I can say that yes, this bug really is
that annoying. Even if his fix works, users should NEVER be expected
to do something as tedious as uncheck a check box every time they wish
to move an
Public bug reported:
Binary package hint: ubiquity-slideshow-ubuntu
The ubiquity-slideshow-ubuntu package has no dependencies. While it
should be fairly obvious that you need Ubiquity for it to do you much
good, it is not at all obvious that it needs python-webkit installed in
order to actually
As Zoltan Tesch indicated, this is not a general Ubuntu bug, but instead
an issue with GDM.
** Package changed: ubuntu = gdm (Ubuntu)
--
can't catch $USER in /etc/gdm/PostLogin/Default
https://bugs.launchpad.net/bugs/463376
You received this bug notification because you are a member of Ubuntu
Downgrading to 2.26.2 will solve the problem, however that version won't
run in Karmic without displaying a bug that causes Nautilus to crash
whenever you display the preferences window
(https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/422282).
--
'Keep Aligned' option always resets to
I know we're waiting on an upstream fix, but if anyone knows of a
temporary workaround or hack (even if it requires recompiling from
source), please post it...This is absurdly annoying.
--
'Keep Aligned' option always resets to 'true' after desktop reload
https://bugs.launchpad.net/bugs/399974
Using xset dpms force standby works properly for me once the
screensaver is completely disabled. Otherwise, I have the same issues
reported here.
--
display doesn't go to DPMS sleep
https://bugs.launchpad.net/bugs/203513
You received this bug notification because you are a member of Ubuntu
If Move to Trash is changed to Delete (which, as I stated above, it
shouldn't be), PLEASE make this a changeable text via gconf. That way
those of us who have users that do understand the distinction between
delete and move to trash don't have to deal with an unintuitive and
inconsistent
Public bug reported:
Binary package hint: gdm-guest-session
gdm-2.20 is packaged for Karmic and Lucid for users that do not want to
upgrade to 2.28. Unfortunately, the new gdm-guest-session package
only works with gdme 2.28. As a result, gdm-guest-session 0.8 should be
packaged as
Public bug reported:
Binary package hint: ubiquity
When Ubiquity is finished installing, it presents a message indicating
that Installation is Complete. The text in this message reads:
Installation has finished. You can continue testing Ubuntu now, but
until you restart the computer, any
While this can easily be fixed by changing the /etc/gdm/gdm.conf file
manually, if it is not fixed by the next package update, users could
upgrade and find their system won't start X upon the next reboot...
--
Wrong path to X server in gdm.conf
https://bugs.launchpad.net/bugs/445256
You received
[This is an automated message. Apologies if it has reached you
inappropriately; please just reply to this message indicating so.]
I'm not sure how any of those logs have any relevance to this issue.
The concern isn't how failsafe mode comes to be started, but instead
what is displayed once it is.
** Attachment added: lspci -vvnn from Ubuntu 9.04 (Jaunty) running in
VirtualBox
http://launchpadlibrarian.net/36702473/lspci.txt
--
Failsafe mode uses Ubuntu specific branding unnecessarily
https://bugs.launchpad.net/bugs/495253
You received this bug notification because you are a member
** Attachment added: /var/log/Xorg.0.log from Ubuntu 9.04 (jaunty) running in
VirtualBox
http://launchpadlibrarian.net/36702494/Xorg.0.log
--
Failsafe mode uses Ubuntu specific branding unnecessarily
https://bugs.launchpad.net/bugs/495253
You received this bug notification because you are a
** Attachment added: Custom /etc/X11/xorg.conf used to invoke failsafe mode in
VirtualBox (since no nvidia driver is installed)
http://launchpadlibrarian.net/36702509/xorg.conf
--
Failsafe mode uses Ubuntu specific branding unnecessarily
https://bugs.launchpad.net/bugs/495253
You received
This was taken from a fresh Ubuntu 9.04 install, having invoked the
failsafe mode using the xorg.conf file previously attached. The exact
same dialog occurs in Nexradix 1.16 (which is directly based on Ubuntu
9.04, and uses the same Xorg packages), indicating that the failsafe
mode does not
After hitting ok at the first dialog, this menu is presented. It also
improperly uses Ubuntu rather than the distro name in question, or a
distro-neutral statement.
** Attachment added: Run Ubuntu in low-graphics mode for just one session.
Ok, I've attached the requested files after reproducing the issue on
Ubuntu 9.04 using VirtualBox. I'll also attach the screenshots of the
exact dialogs in question that have the unnecessary branding.
--
Failsafe mode uses Ubuntu specific branding unnecessarily
Sadly, I can't seem to force the failsafe mode in 9.10 in order to post
screenshots from it. I tried using the same xorg.conf file, but all I
get is a quickly flickering console login prompt, no failsafe menu. I'm
not sure if this is because I am running within VirtualBox or not.
I don't have
This is a pretty huge regression. I don't get how new final versions of
Ubuntu keep getting released with major features that were present in
prior versions completely missing. There should be a no feature
regression policy when a new release comes out -- if a new version of
an app doesn't have
Public bug reported:
Binary package hint: xorg
The failsafe mode currenty greets the user with Ubuntu is running in
low graphics mode, and offers the user options on how to proceed.
These dialogs all specifically reference Ubuntu, rather than the
distro name noted in /etc/lsb-release.
This
We forked the Jaunty version for Nexradix, and it works just fine,
despite that the name in /etc/lsb-release isn't Ubuntu. The only thing
we actually changed was the menu labels in the interface so that they
were distro-neutral.
So unless something has changed in the Karmic version, there aren't
@ brodiepearce: I completely agree. While server admins might be
expected to be advanced enough to add the bootwait option, average
users cannot be expected to magically know this, let alone actually do
it.
I'd understand taking the position that the new boot process is superior
and shouldn't be
While it looks like I'm a bit late, I'd strongly suggest making the
launcher distro-neutral such as Install to Hard Drive rather than
mention Ubuntu specifically. Otherwise downstream distros will have to
fork Ubiquity just to change the branding.
--
Ubuntu LiveCD Install icon confusing
If this gets impliemented, I'd strongly recommend making this change
easily removable with its own package (or part of an existing Ubuntu
branding package). That way downstream distros won't have to fork
nautilus just to change the branding...
--
Place an Ubuntu icon/emblem on the system
** Changed in: iceweasel (Nexradix)
Status: Confirmed = Fix Released
--
[MASTER] right click (with button release) might activate random popup-menu-item
https://bugs.launchpad.net/bugs/187313
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Any chance this will be fixed for Karmic?
--
usb-creator has hard-coded references to Ubuntu
https://bugs.launchpad.net/bugs/321937
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I totally disagree. First off, there are are good number of people in
the Windows world that think delete means gone forever. I've seen
quite a few people that have no idea what the recycle bin does, and are
shocked to find their files are still there. We don't want to have the
same issues
That would probably be easier, certainly. In fact, that's exactly what
I did when I modified usb-creator for inclusion in Nexradix. I changed
the intro label up top to read:
NOTE: To boot or install from a USB disk, it needs to be set up as a
startup disk. Make sure your system's BIOS is set
Any chance of any of these issues being fixed for the final Jaunty
version of Ubiquity? I'd love to avoid continuing to fork Ubiquity in
our next version of Nexradix.
--
Ubiquity uses hard-coded references to Ubuntu rather than looking to
/etc/lsb-release
https://bugs.launchpad.net/bugs/322174
Any progress on this? It would be great to not have to fork usb-creator
anymore for Nexradix.
--
usb-creator has hard-coded references to Ubuntu, rather than using the distro
in /etc/lsb-release
https://bugs.launchpad.net/bugs/321937
You received this bug notification because you are a member
Lincoln, Inc. (twistedlincoln)
--
[MASTER] right click (with button release) might activate random popup-menu-item
https://bugs.launchpad.net/bugs/187313
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Didn't realize that adding to the original bug would reopen it on your
end. My apologies --I should've been paying more attention.
Tony Lovasco
Twisted Lincoln, Inc.
John Vivirito wrote:
Why did you open this bug back up? If fix released upstream than we will
get it and patch it for us
Public bug reported:
Binary package hint: gfxboot-theme-ubuntu
When one uses the usb-creator package to create a bootable USB drive
from an Ubuntu Desktop Live CD, the resulting boot menu shows expert
mode upon hitting F6. It is my understanding that this mode is only
functional with the
Public bug reported:
Binary package hint: usb-creator
usb-creator mentions Ubuntu directly in the interface, as does many
other apps. However unlike most other apps that come with Ubuntu, it
does not display this by using the current distribution listed in the
/etc/lsb-release file. As a
Public bug reported:
Binary package hint: ubiquity-frontend-gtk
Ubuntu derivative distributions (such as Nexradix, the GNU/Linux distro
we maintain) have to modify Ubiquity before deployment in order to
remove references to Ubuntu from code.
Currently, line 1183 in gtk_ui.py
** Attachment added: Replacement Ubiquity icon without the Ubuntu logo
http://launchpadlibrarian.net/21700488/ubiquity.png
--
Ubiquity uses hard-coded references to Ubuntu rather than looking to
/etc/lsb-release
https://bugs.launchpad.net/bugs/322174
You received this bug notification
Public bug reported:
Binary package hint: yelp
In Yelp's table of contents page, as well as the description of the
program via it's GNOME launcher, Ubuntu is referenced specifically
(usually in the form of Get help with Ubuntu).
There is no reason to specifically reference Ubuntu at all in yelp
Public bug reported:
Binary package hint: ubiquity
NOTE: tested using Intrepid (8.10)
When using oem-config mode (oem-config/enable=true) along with a preseed
file, you cannot preseed all options of Ubiquity. The page in which you
would normally select the oem user's password, and the system's
91 matches
Mail list logo
