Really? After all those years you ask _me_ to figure out if it is still the
case?
Just close the issue if you are not interested in fixing it
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
After all those years you are asking _me_ to test if it is still an
issue?! Bye!
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/131
** Also affects: os-prober via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688336
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294638
Title:
o
A workaround (at least fix the frozen desktop) without restarting,
ending sessions, etc. is to switch to another tty (eg tty1 with CTRL-
ALT-F1) and type:
DISPLAY=:0 kwin_x11 --replace &
When switching back to the desktop, it is seen restarting and everything
is working again.
--
You received t
First of all, thanks for your work on this!
When I try to install your packages on Utopic I have dependency
problems. For example:
$ sudo apt-get install libgazebo3
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed
I marked this bug report as 'fix released' as this problem seems to be
fix upstream (a while ago already) and the report is marked incomplete
for over 2 years as the OP does not respond anymore.
** Changed in: akonadi (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug no
I marked this bug report as 'fix released' as this problem seems to be
fix upstream (a while ago already) and the report is marked incomplete
for over 2 years as the OP does not respond anymore.
** Changed in: akonadi (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug no
I am seeing exactly the same behavior as Sergio described again. For me
it was also fixed for a while, but the problem came back. (Kubuntu 14.04
KDE 3.13.3)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I do not think the KDE linked bugs are relevant:
* They describe other function that crash, instead of
gtk_tree_view_get_background_area+0x8a
* The KDE bug report say that the problem is fixed (half a year ago) and I
still have the same problem
Also adding "gtk-enable-animations=0" to $HOME/.g
** Also affects: eclipse via
https://bugs.eclipse.org/bugs/show_bug.cgi?id=421073
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1223181
Title:
After
It is still an issue with Ark 2.19 on KDE 4.13 (Kubuntu 14.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/635384
Title:
ark crashes while loading a big archive
To manage notifications about this
I closed it, because there is a (simple) option to disallow the use of
TLS, which fixes the problem as I mentioned in comment 2
Furthermore, this is a gnutls problem, I suppose, not a mercurial one..?
I'll leave it open and let 'Ubuntu Developers' (they are the maintainers
of this package) decide
I found this undocumented feature to force using SSL (instead of TLS,
which is supposedly not supported by the server..?):
http://selenic.com/repo/hg/rev/47ff9d1abfa9
One can activate it by adding 'tls = False' to ~/.hgrc
Sorry for the noise, I'll close this issue.
** Changed in: mercurial (Ubu
Additional information: Downgrading to version 2.6.3-1 (Saucy) solves
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/1312108
Title:
SSL routines:SSL3_GET_RECORD:wrong version number
To ma
Public bug reported:
I upgraded to Trusty (fresh install) and since then mercurial gives this
error when trying to connect to the remote server:
$ hg clone https://hg.ce.utwente.nl/TERRA
abort: error: _ssl.c:510: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
version number
When I boot from
I *do* know that Windows XP is not supported. That particular partition is
'left over' and is not used for over a couple of years, I guess I'll put
something else on it eventually. It is not part of the problem (ubiquity
handles that partition just fine).
I also *do* know that the problem is tha
Public bug reported:
After copying and installing all content (Kubuntu 14.04), ubiquity tried
to install GRUB. This failed (wrong/non-existing partition in my
RAID/LVM setup) and a crash handling dialog showed.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.7
ProcVersionSigna
I have the same problem with my extended LVM volume groups.
https://bbs.archlinux.org/viewtopic.php?pid=1289321#p1289321 describes
how to trigger this bug and provides some more information
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
The updated version of the package (to version 1.0.28) solves the second
(major) bug, the first bug is still present though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/490015
Title:
python-pydot
I have updated the package to 1.0.28 and all seems to be working.
In my PPA (ppa:veger/ppa) is a build version of the package after this update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987934
Ti
Public bug reported:
In order to get the details of volume groups, physical volumes and
logical volumes for the variety of LVM commands the bash completion
script uses vgscan, pvscan and lvscan respectively.
These commands require root permissions, so the auto completion does not
work.
Test case
I tried to install Trusty to see if I could reproduce the issue and then send
the collected data.
But I could not due to the installer crashing (bug #1267629), so I'll have to
come back to this later when the installation problems are solved.
--
You received this bug notification because you ar
The newest mainline kernel (for saucy) 3.11.0-15 does not show the
problem... So I guess it does not make sense to open a new report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/582145
Title:
Virt
I do not know... I have this problem as long as I can remember. At a certain
point I got fed up with it and filed the report.
Unfortunately I do not have any Quantal installations available. But II
*suspect* it was already there in Quantal, whether I already had it when I used
fglrx-* or not I d
Comment #11 is about my current installation comment #13 is about the
live environments (booted from USB):
In summary:
I could *not* reproduce it in the live environments of Kubuntu 13.10 and 14.04.
But I 'suffer' from this problem on my currently installed machine (Kubuntu
13.10). It does not ma
On my search to a solution of slow scrolling in my terminals (tty) I
stumbled upon this report.
After upgrading from 3.12.4 to 3.13-rc7 the problem is gone (without
blacklisting additional fb modules).
Note: I'll leave the tags are report status for the Andreas
--
You received this bug notifica
I used already the Kubuntu 13.10 and Kubuntu 14.04 live environments in
the test of my previous commit...
I just create a new user account to see whether the issue is (user)
configuration dependent. But this new user account has the same problem.
So I guess it does not have anything to do with the
I tried both 14.04 and 13.10 live USBs. I cannot reproduce the problem on
either one.
On the other hand, my current installation (as well as previous ones) does have
the problem.
So I guess it is due the configuration of my user account? Or something I
installed? (and had installed in previous
I have had the same issues, but I must say that lately (I do not know
when exactly) I did not experience this issue anymore... So maybe it got
fixed at some point?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I still have the problem using Kubuntu 13.10, nothing really changed
compared to previous versions/reports.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1071722/+attachment/3940705/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071722
apport information
** Tags added: apport-collected saucy
** Description changed:
I have attached a external monitor to my laptop. When I my the mouse
from the primary display (my laptop screen) to the secondary display
(external monitor), the mouse cursor image gets duplicated.
On the
If I disable the 'Nepomuk File Indexer', virtuoso seems to stop crashing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264865
Title:
Virtuoso crashes frequently (about every 10 seconds)
To manage
Public bug reported:
Virtuoso crashes and restarts frequently. WHen I look in /var/log/syslog
it seems that it crashes about every 5-10 seconds..! (which is really
insane)
I have ran apport-retrace using the dump I found in /var/crash. I have
put this first part below, the complete retrace file i
Public bug reported:
I am currently trying LVM. My motherboard has hardware RAID controller,
which combines two harddisks (RAID0 I believe, but that does not really
matter)
After circumventing bug 1038522, the installer finished, but when I
booted into the freshly installed system, some LVM parti
This bug is still present in the Kubuntu 13.10 installer
The patch/workaround provided in comment #23 helped me finish the installation.
I never had any problems while using multiple partitions during the
installation. The thing that got changed is that I (partially) use my
harddisks in a LVM setu
** Also affects: muon via
https://bugs.kde.org/show_bug.cgi?id=326256
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245418
Title:
Muon updater does
Public bug reported:
When the system tray shows that there are updated available (with the 'gear
icon'), the Muon updater (that is opened when clicked on the gear icon) does
not show the available updates.
Instead it tells when the last check of updates occurred.
When opening Muon itself and se
Thank you for your clarification! It seems reasonable enough to keep the
behavior of apt this way.
** Changed in: apt (Ubuntu)
Status: Opinion => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I read the manpages, but I guess I did not understand them completely...
And I do know that pinning is a highly advanced feature. But when using
experimental packages/PPAs, not using pinning also might break your
system... Hence I wanted to use pinning to prevent automatic updating of
such experime
Public bug reported:
When some pinning rules are added in /etc/apt/preferences.d/ the
priority values of the rules that matches first are used.
Take this example:
Package: *
Pin: release n=raring
Pin-Priority: 990
Package: *
Pin: release o=LP-PPA-my-raring-ppa
Pin-Priority: 50
Results in all p
Upstream report got marked as duplicate of this report
** Bug watch added: KDE Bug Tracking System #258431
https://bugs.kde.org/show_bug.cgi?id=258431
** Changed in: kdegraphics
Importance: Medium => Unknown
** Changed in: kdegraphics
Status: Invalid => Unknown
** Changed in: kdegr
The Configure KSudoku menu option properly open the setting dialog in version
1.2.
I guess it is fixed some time after this report was last updated.
Please update to a newer version of KSudoku and report back if the
problem still manifests (or is solved).
** Changed in: ksudoku (Ubuntu)
S
Public bug reported:
I am trying to install both the 32-bit and the 64-bit version of libswt-
gtk-3-jni, but both packages seem to be conflicting.
$ sudo apt-get install libswt-gtk-3-jni:i386 libswt-gtk-3-jni:amd64
Reading package lists... Done
Building dependency tree
Reading state inform
The actual (related) error from Termlog is:
(...)
Setting up libswt-gtk-3-java (3.7.2-2) ...
update-alternatives: error: alternative path /usr/share/java/swt-gtk-3.7.jar
doesn't exist.
dpkg: error processing libswt-gtk-3-java (--configure):
subprocess installed post-installation script returned
*** This bug is a duplicate of bug 990097 ***
https://bugs.launchpad.net/bugs/990097
** This bug has been marked a duplicate of bug 990097
package libswt-gtk-3-java 3.7.2-2 failed to install/upgrade: ErrorMessage:
subprocess installed post-installation script returned error exit status 2
I do not know whether it is relevant, but attached is a test file that
triggers the crash.
** Attachment added: "my_file.svg"
https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1175949/+attachment/3663527/+files/my_file.svg
--
You received this bug notification because you ar
Public bug reported:
When I start inkscape I get a warning
$inkscape my_file.svg
(inkscape:2983): Gtk-WARNING **: Theme file for default has no
directories
When I try to change the dash pattern of a line, the menu directly closes and
the terminal shows:
(inkscape:2983): Gdk-WARNING **: /build
** Summary changed:
- 软件包“ubuntu-desktop-nanjing-natty”标记可移除，但他以在移除黑名单为
+ The package 'ubuntu-desktop-nanjing-natty' is marked for removal but it's in
the removal blacklist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Summary changed:
- An unresolvable problem occurred while calculating the upgrade:
软件包“ubuntu-desktop-nanjing-natty”标记为可移除，但它已在移除黑名单中
+ An unresolvable problem occurred while calculating the upgrade: The package
'ubuntu-desktop-nanjing-natty' is marked for removal but it's in the removal
bla
** Bug watch added: Debian Bug tracker #692237
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692237
** Also affects: subversion via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692237
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Do you have any other packages (that you know of) installed or not
installed compared to your previous installation which might have been
related to the problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
It looks like it is not a ati problem, so I changed the package to xorg
** Package changed: xserver-xorg-video-ati (Ubuntu) => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071722
Titl
Note: am example build (for quantal) is available in ppa:veger/ppa (the
only change compared to this one is the version and quantal build
modification)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/107
** Description changed:
Debian provides version 0.213 of pbuilder, upgrading to this version
should fix bug #1060101
+
+ The Debian changelog:
+ pbuilder (0.213) unstable; urgency=low
+
+ [ Beatrice Torracca ]
+ * Bug#686004: [INTL: it] Italian translation of debconf messages - pbuilder
** Attachment added: "Ubuntu changes"
https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1075347/+attachment/3425134/+files/ubuntu_changes.debdiff.gz
** Changed in: pbuilder (Ubuntu)
Status: In Progress => Confirmed
** Changed in: pbuilder (Ubuntu)
Assignee: Ma
I have updating pbuilder to 0.213. I rebuild the pbuilder package after
installing a test build without problems, so it (still) seems to be
working
Attached are the debian and ubuntu changes
** Attachment added: "Debian changes"
https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1075347/
Public bug reported:
Debian provides version 0.213 of pbuilder, upgrading to this version
should fix bug #1060101
** Affects: pbuilder (Ubuntu)
Importance: Undecided
Assignee: Maarten Bezemer (veger)
Status: In Progress
** Changed in: pbuilder (Ubuntu)
Status: New
** Changed in: networkmanagement (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/422174
Title:
cannot connect to hidden ssid
To manage notifications
Public bug reported:
I have attached a external monitor to my laptop. When I my the mouse
from the primary display (my laptop screen) to the secondary display
(external monitor), the mouse cursor image gets duplicated.
On the primary screen it freezes its last location (so moving the mouse more
** Changed in: kdepim (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdepim in Ubuntu.
https://bugs.launchpad.net/bugs/643248
Title:
kmail problems with kaddressbook - what is used for autoc
I have exactly the same problem. I use Kubuntu 12.04 (but I experience
the problems for years already), KDE 4.9.2, ATI Radeon HD 5870, fglrx
driver.
On my primary monitor the mouse cursor is corrupted sometimes and on the
secondary monitor it is always looking good.
So by moving the mouse from th
Public bug reported:
I decided to try lightdm-kde using version 0.1.1-0ubuntu0.1 from
precise-updates repository(on Kubuntu 12.04, KDE 1.9.2), so I logged
out, stopped kdm and started lightdm
It all worked, besides that the login screen/dialog was in the middle of
my dual-screen setup, one half o
** Attachment added: "Screenshot of useless window"
https://bugs.launchpad.net/bugs/1048559/+attachment/3305226/+files/screenshot1.png
** Summary changed:
- Password is asked on wireless reconnect
+ Password is needlessly asked on wireless reconnect
--
You received this bug notification bec
Public bug reported:
First, I tried to use ubuntu-bug -w and clicked on the window (see
attachment) to report this bug, but it complained about non-official
packages, hence my manual report. So please let me know if there is not
enough information.
The actual report: When I use a wireless connect
** Changed in: debianutils (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/16598
Title:
/sbin/installkernel doesn't work
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/432369
Title:
Too many network OSD notifications when resuming from sl
Set to confirmed, as people (still) have this problem.
** Changed in: wpasupplicant (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/377430
Title:
Can't
You are right, I thought the issue was about the back and forward
buttons on Dolphin.
I indeed can confirm that the back and forward buttons of my mouse (I
never use them so I did not think of those) are not working (and that
they are working in other applications)
--
You received this bug notif
** Summary changed:
- Upgrading Hardy desktop to Lynx desktop crashes, when multiple graphic cards
are present
+ Upgrading Hardy desktop to Lucid desktop crashes, when multiple graphic cards
are present
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
You indicate that you have a slow internet connection, but your video showed
that is was downloading quite fast (or did you remove a part?), are you sure
that it is not just grabbing the update from your CD?
I could image that the message telling you that 943M needs to be downloaded, is
intended
Remove the lock file by typing:
sudo rm /var/cache/apt/archives/lock
After that retry removing the java package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684520
Title:
E: sun-java6-jre: Packa
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
This bug report is being closed due to your last comment regarding this being
fixed and the age of this bug making it very hard to do something useful with
it.
For future reference you can manage the status of your own bugs by clicking on
the current status in the yellow line and then choosing a
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command, as it will automatically gather
debugging information, in a terminal:
apport-collect 584491
When reporting bugs in the future please use apport by using 'ubuntu-bug' and
the
** Package changed: ubuntu => empathy (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011676
Title:
empathy-chat crashed with SIGILL in JSC::Interpreter::executeCall()
To manage notificatio
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and the downloads you gave in the
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"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
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"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
I am closing this report due to its age and your last comment that the newer
PPA (probably in the regular repositories at this moment) packages solve your
problem.
Next time, please file translations errors/problems with the package that is
having the problem, if possible. So the respective deve
As you describe that your update was (at last) successful and you did not add
any logs or other additional information, it is going to be hard to find out
what was wrong. Especially since it has been a long time ago and you (probably)
do not have any remaining logs left.
Therefore, I am closing
I am closing this report due to the lack of information and the lack of
responses over time (does not seem too serious).
** Changed in: update-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
Thank you for reporting this bug to Ubuntu. Both Jaunty and Karmic reached EOL
(on October 23, 2010 and April 30, 2011).
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
If you still have this issue when trying to upgrade your installation,
it would be
Thank you for reporting this bug to Ubuntu. Both Jaunty and Karmic reached EOL
(on October 23, 2010 and April 30, 2011).
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
If you still have this issue when trying to upgrade your installation,
it would be
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
1 - 100 of 924 matches
Mail list logo
