I've tried to reproduce this bug on a Debian/unstable system (using the
Ubuntu .deb and dash as a shell instead of bash), but no luck. From
looking at the log file, the postinst script fails, but without an error
message. I'm not sure how this could happen at all, really.
** Summary changed:
- th
0.7.1 is packaged and shipped with karmic.
** Changed in: openttd (Ubuntu)
Status: New => Fix Released
--
Please update OpenTTD to 0.7
https://bugs.launchpad.net/bugs/364528
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Upstream reports that it is most likely this bug has been fixed in
0.7.1-RC3. I'm closing this bug, Please reopen it if the bug persists.
** Changed in: openttd (Ubuntu)
Status: New => Fix Released
--
Error: !Disconnecting road vehicle.
https://bugs.launchpad.net/bugs/368952
You received
I can't seem to change the status either, perhaps there is no
distinction between bugs and wishes?
I would like to note that, though OpenGFX is a graphics set that can be
used with OpenTTD, it is not yet finished and is not bundled with
OpenTTD (yet). Also, to be able to download it through the co
Hi Rufio,
this doesn't seem to be a Ubuntu/Debian specific bug, so it will
probably not fixed by us. To get the bug fix, you should report it
upstream, at the OpenTTD project itself: http://bugs.openttd.org.
I would have forwarded the bug myself, but your report does not specify
enough informatio
I've been having problems with the 8169 driver and RTL8111/8168B network
card as well. I'm not 100% sure if this is the same issue, but I suspect
it might be.
Anyway, the issue I was seeing was that the network card was properly
detected, but did not do proper link detection (no connection and no
Hi Eduardo,
is this reproducible? If you run dpkg --configure --pending (IIRC), or
remove openttd and install it again, does it happen again? Could you
post output from such a run?
If you can reproduce this, are you prepared to do some debugging, with
my directions? If so, let us know here, or pe
This bug was also reported (and fixed) for Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462604
--
Openttd Turkish Charset Error
https://bugs.launchpad.net/bugs/164954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
FYI, we uploaded 0.6.0-2 almost immediately after -1, to fix build on
some Debian buildd's.
--
Please accept openttd 0.6.0-1 in hardy
https://bugs.launchpad.net/bugs/210848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm kinda confused by this report, it seems like you used the bug
template for firefox instead of OpenTTD? Just to confirm, does this bug
actually apply to OpenTTD?
If so, could you supply your ~/.openttd/openttd.cfg file? Also, try
running "openttd -d 4" from a terminal, quit openttd immediately
Hmm, it seems I really need to take a look at how Ubuntu shows Debconf
messages. Apparently it misinterprets the (quite simple) debconf message
the openttd package shows somehow.
However, since this message will be removed from the 1.0 package
entirely, I might not go through the trouble (I don't
Hi Paul,
some comments. First of all, we're planning on getting rid of the dialog
alltogether and replacing it with a better approach with multiple
packages (Also hoping to package the OpenGFX free graphics for OpenTTD).
Also, this bug seems to be similar to Debian #524651
(http://bugs.debian.org
Hi,
could you explain a bit more what you were doing when this error
occured? In particular, were you trying to upgrade or install openttd?
Could you also try to reproduce this error? Try uninstalling and
reinstalling if you were installing, or trying downgrading and upgrading
again if you were u
Hi Giorgos,
Does this bug happen consistently for you? If so, could you answer my
original questions:
Could you supply your ~/.openttd/openttd.cfg file? Also, try running
"openttd -d 4" from a terminal, quit openttd immediately and attach the
resulting output here. Also, could you attach the outp
Awesome, thanks all :-D
--
sync openttd 1.0.0-1 from Debian unstable
https://bugs.launchpad.net/bugs/556593
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
*** This bug is a duplicate of bug 556593 ***
https://bugs.launchpad.net/bugs/556593
** This bug is no longer a duplicate of bug 553024
OpenTTD 1.0.0 is stable now - When it come Ubuntu repository?
** This bug has been marked a duplicate of bug 556593
sync openttd 1.0.0-1 from Debian uns
*** This bug is a duplicate of bug 556593 ***
https://bugs.launchpad.net/bugs/556593
Updating a package so late in the Lucid release cycle is a complicated
process. However, if everything turns out ok, openttd 1.0 should be in
Lucid very soon. See also bug #556593. I'm closing this bug in favo
I've just uploaded 1.0.0-2 to unstable which fixes upgrades from 0.7.5-1
due to an off-by-one error in the Replaces (upgrading from all other
versions already worked). Please use this version for Lucid, thanks.
--
sync openttd 1.0.0-1 from Debian unstable
https://bugs.launchpad.net/bugs/556593
Yo
I'm attaching a patch with the changes to the Debian packaging between 0.7.5-1
and 1.0.0-1. The most import changes are:
- openttd was moved from contrib to main
- openttd now uses the 3.0 (quilt) source format
- All maintainer scripts were removed, openttd no longer prompts about missing
data
*** This bug is a duplicate of bug 553024 ***
https://bugs.launchpad.net/bugs/553024
** This bug has been marked a duplicate of bug 553024
OpenTTD 1.0.0 is stable now - When it come Ubuntu repository?
--
Please update to new stable release
https://bugs.launchpad.net/bugs/553119
You receiv
Could you see if this problem is fixed (or rather, workarounded) by
installing libsdl1.2debian-pulseaudio ?
--
openttd eats all my cpu
https://bugs.launchpad.net/bugs/467179
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Funny that it doesn't happen again. Perhaps there was some other process
running that confused openttd in some way, or something else was
different in your environment? If you manage to reproduce it again, let
us know. If not, I'll probably close this report soon.
The debug output generated by ope
Public bug reported:
I'm not entirely sure this bug belongs in package xinput, but I'm
following the lead of #1275416, which describes the same symptoms (but
on other hardware, so likely a different underlying problem).
On this notebook, the touchscreen works well out of the box. But as soon
as I
** Description changed:
I'm not entirely sure this bug belongs in package xinput, but I'm
- following the lead of #1275416, which describes the same symptoms (but
- on other hardware, so likely a different underlying problem).
+ following the lead of
+ https://bugs.launchpad.net/ubuntu/+source/x
I dug around a bit, and found that the touchscreen can also be fixed by
reloading the ic2_hid module.
It also works to reinitialize just the hid driver for the touchscreen
(rather than reloading the entire module) by running:
echo 0018:06CB:77B2.000C > /sys/bus/hid/drivers/hid-multitouch/unbind
e
I also ran the i2c_hid module with debug enabled (`modprobe i2c_hid
debug=1`), which gives a bit of insight in what commands are sent to the
touch screen. On a suspend, it seems to send a sleep command. On a
resume, it sends a power on command, followed by a reset command (which
is properly acknowl
Good call, thanks!
This turns out to be fixed in the latest mainline kernel. Looking at the
git log for the i2c_hid driver, I found this commit which I suspect is
the fix for my problem.
https://github.com/torvalds/linux/commit/52cf93e63ee672a92f349edc6ddad86ec8808fd8
https://patchwork.kernel.org
It seems this fix also fixes the touch screen not working (no irq storm)
after a suspend on an Acer Aspire Switch 11 (and possibly also other
modules).
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796580
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is still an issue: Just started the disco -> eoan upgrade through
the GUI prompt I got, which broke on, I think, the second step (setting
up software sources IIRC). A systray icon showed up saying there was a
problem with the package manager (saying 'disco', which I have now
configured as the
Just finished the upgrade without problems, so just disabling the
default-release temporarily seems to be sufficient. Would be nicer if
the upgrade somehow handled this, even if just detecting that it was set
and bailing out before rather than during the upgrade and allow the user
to unset it manua
** Changed in: openttd (Ubuntu)
Status: New => 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/1731637
Title:
New upstream Version
To manage notifications about this bug go to:
ht
This is fixed in version (0.5.1-1), which is included in the Groovy
20.10 release. Only Focal 20.04 is still affected, since earlier
versions had older versions of Python that did not remove the deprecated
module yet.
Considering this bug completely prevents this package from working and
20.04 is
This is still a problem: I wanted to upgrade from eoan to focal and
forgot about this bug, so the upgrade failed again (I think it actually
crashed this time, the GUI window disappeared, but I accidentally
dismissed the "send report" prompt, so I'm not sure how exactly).
It seems the pattern is st
I just tried installing gdb-multiarch as a replacement for gdb-arm-none-
eabi for an Atmel SAMD target and an STM32 target, and that worked out
of the box. Maybe this issue can be closed?
A transitional package depending on gdb-multiarch might have been
useful, but since this package has been gone
This bug is reported and fixed upstream at
https://github.com/SpamExperts/pyzor/issues/74
Looks like the attached patch is essentially the upstream fix.
** Bug watch added: Debian Bug tracker #923077
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923077
** Also affects: pyzor (Debian) via
Public bug reported:
I'm running Ubuntu 19.10 and got a message prompting me to upgrade to
20.04. I clicked the "Upgrade now" (or something similar) button and
then nothing happens at all.
Looking in the journal, I see:
jun 22 08:19:00 grubby check-new-release-gtk[27508]: Checking for a new Ubun
AFAICS this is fixed in 2017.7.ubuntu1:
debian-archive-keyring (2017.7ubuntu1) bionic; urgency=medium
* Do not trust debian archive keys by default, and instead ship those
keys in usr/share/keyrings. On Ubuntu, this package is mostly used for
validating chroots when debootstrapping Debi
Public bug reported:
Since version 2017.7ubuntu1, the keys installed by the Ubuntu version of
debian-archive-keyring are no longer trusted by default. Coming from
Debian, this surprised me, but now I've found the changelog entry, I
understand the reasoning.
Initially, though, I had expected insta
Seems upstream diagnosed and fixed this bug in their master branch two
weeks ago, and the fix indeed got included in 3.32 (first in 3.31.92,
though it seems to have been omitted from their changelog/NEWS file).
Any chance of getting this fix backported into the Ubuntu cosmic
package?
--
You rece
Public bug reported:
I'm trying to upgrade from 18.10 to 19.04 by running `update-manager -c`
as instructed by https://wiki.ubuntu.com/DiscoDingo/ReleaseNotes. After
running it earlier to install pending package updates, I now get a
message saying there is a distribution upgrade available (see att
After this error, removing the Default-Release config and starting
`update-manager -c` again shows a popup "Failed to load the package
list". Clicking "ok" shows a spinner that takes some time and then
offers a partial upgrade, which looks reasonable (but has not finished
yet).
--
You received th
Public bug reported:
I just tried to upgrade my Ubuntu system from cosmic to disco, but it
seems the presence of the Default-Release configuration value breaks the
upgrade.
I have some Debian sources in my sources.list so I can occasionally
cherry-pick packages from there. To make sure these are
I'm also running into this bug (or at least something that looks like
it). Typically what happens for me is that I resume from suspend, get an
unlock prompt (the system is locked on suspend) and when I log in, the
unlock prompt stays visible (the password dots disappear, but I cannot
type anything
W00ps, seems I (Debian maintainer) missed that release. I'll try to
upload a package to Debian somewhere this or the next month.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731637
Title:
New upst
I just uploaded 1.7.1-1 to Debian unstable, so this should migrate to
Ubuntu at some point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731637
Title:
New upstream Version
To manage notifications
Public bug reported:
I just tried installing the Artful version (0.10.3-1) on a Xenial
install, and had some problems making it work. It seems that I needed
`Defaults env_keep+=SSH_AUTH_SOCK` (or, actually, I used `Defaults
env_keep+=SSH_*`) to let pam-ssh-agent-auth see the SSH agent and
connect
*** This bug is a duplicate of bug 489486 ***
https://bugs.launchpad.net/bugs/489486
I've marked this bug as a duplicate of #489486, which was fixed in
1.0.0-2 (by removing the dialog altogether).
** This bug has been marked a duplicate of bug 489486
package openttd 0.7.1-1 failed to insta
I can reproduce this on a Debian Jessie system. Bypassing pulseaudio
makes playback work normally:
pasuspender -- timidity up_on_the_housetop.mid -o hw:0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Similar observation at my end: It works through pulse to my intel_hda
sound card, but fails through pulse to my Terratec Aureon 5.1MKII USB
audio device. Perhaps a bug in the USB audio driver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
An ignore should probably be added for Arduino.org devices too (there's
two competing Arduino companies now, don't ask):
ATTRS{idVendor}=="2a03", ENV{ID_MM_DEVICE_IGNORE}="1"
And, while we are here, perhaps also ignore the Pinoccio Scout (arduino-
like device):
ATTRS{idVendor}=="1d50", ATTRS{idP
Actually, OpenTTD 1.2.0 was only released last weekend, and I (Debian
maintainer) just uploaded it to Debian yesterday, so it's not so weird
that it's not in Ubunut yet :-)
Having said that, I guess this would be a good time to pull the package from
Debian. I'm not sure about the procedure for th
On more thing: It might be useful to get 1.1.5 into Ubuntu 12.04, which is only
bugfixes compared to 1.1.4. Considering 12.04 is an LTS release, having the
1.1.5 release, which is (probably) the end of the 1.1 cycle, would be useful.
However, I'm not directly involved with Ubuntu, so I'll leave
In case any one else comes across this problem: I had exactly the same
symptoms and found out they were caused by xbindkeys that was started in
the background. Removing my .xbindkeysrc solved the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This was fixed upstream, by allowing opening the shield on any printable
character keypress, and entering that character into the password field,
so you can just type your password while the shield is still shown /
moving away.
https://bugzilla.gnome.org/show_bug.cgi?id=686740
According to git, t
This is fixed in BIOS version 1.70 (version 1.50 for E350M1/USB3).
** Changed in: linux (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/815980
Title:
Asrock just sent me a beta BIOS as well (version 1.60A), which seems to
fix the problem on the E350M1 board (half a dozen clean shutdowns so
far). I presume they'll be releasing BIOS version 1.70 soon with this
fix contained.
--
You received this bug notification because you are a member of Ubunt
It seems the BIOS version 1.50 works on the E350M1/USB3 board, but not
on the E350M1 board. I've just contacted Asrock about this issue as
well.
Note that I'm not using Ubuntu, but a Debian live image, so I suspect
this is something triggered by the upstream kernel, not an Ubuntu
specific bug.
--
I'm seeing a similar problem here. It didn't happen on a particular
upgrade, but it just stopped working (perhaps during a suspend, but I'm
not sure). I've found that rebooting to Windows actually fixed my
problem before (but my Windows install is broken right now, so I can't
see if it works again)
I (the Debian maintainer for OpenTTD) have just uploaded 1.3.0-1 to
Debian unstable, so it could be taken from there.
Note that to build OpenTTD 1.3.0, grfcodec 6.0.2 is needed, so that
would have to be updated from Debian unstable as well.
Finally, to get all the needed baseset sprites, openttd-
Given that raring has been released without 1.3.0, but that 1.3.0 has
been (automatically) imported into saucy, I think this bug can be
closed.
** Changed in: openttd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Given the age of the original report, I'm not sure if it's still worth
investigating this. It's likely that this bug has been fixed already in
newer OpenTTD versions.
If the bug still occurs for you, please reopen this bug or leave a
comment.
** Changed in: openttd (Ubuntu)
Status: New =>
I've packaged up openmsx for Debian a few weeks ago, it's now waiting in
NEW.
--
[needs-packaging] openttd-openmsx
https://bugs.launchpad.net/bugs/571687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
And after poking ftpmasters, it's in unstable now.
I'm also preparing an updated openttd package that recommends openttd-
openmsx (and expect a new openttd upstream release this month, which we
hope to get into squeeze together with openmsx).
--
[needs-packaging] openttd-openmsx
https://bugs.lau
Note that 1.0.1 is affected by CVE-2010-2534, while 1.0.0 is not. So the
patch for that CVE should either be backported to 1.0.1, or lucid should
be updated to 1.0.3.
See http://security.openttd.org/en/CVE-2010-2534 for details and a
patch.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.
I'm the maintainer of openttd & friends in Debian. Someone took up the
previous comment and sent me an email :-)
Looking at openmsx has been om my list for a while, but this was a nice
occasion to look a bit closer. I've filed ITP #591930 with Debian, I'll
try to get a package whipped up in the ne
Public bug reported:
This is really an upstream bug, but I found no upstream bug tracker or
contact address, so I'm hoping the upstream maintainer might be reading
along here (and it's a bug in the Ubuntu version as well, so not
entirely off here).
The problem is that when I set a debounce time o
Public bug reported:
This is an upstream bug that prevents using stlink devices with openocd
entirely with the jammy versions of openocd and libusb. This is a bug in
openocd that was exposed by a change in libusb-1.0.24.
Upstream has committed a fix for this already (intentionally small to
facili
Looks good, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820586
Title:
Should document keys are not trusted by default
To manage notifications about this bug go to:
https://bugs.launchpad
Public bug reported:
After upgrading from 21.04 to 21.10, my /etc/X11/Xresources/ directory
no longer loads on login.
Looking at the sources, I think this can be traced to:
- Switching from a custom Xsession file to the upstream Xsession file in
3.38.0-1ubuntu1, combined with
- An oversight in
Just tested, the above test solves the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955850
Title:
/etc/X11/Xresources no longer loaded, error in patch
To manage notifications abou
Hm, that patch is indeed old, that is not consistent with what I thought
was going on. So I looked a little closer.
> Looking at the sources, I think this can be traced to:
- Switching from a custom Xsession file to the upstream Xsession file in
3.38.0-1ubuntu1, combined with
- An oversight in
@Jack, I'm not sure about nvidia support, but I do think that it is
really unrelated to *this* particular bug (which is about a mistake in
the rules file that caused the nvidia-specific rules to be applied to
other systems, breaking wayland on non-nvidia systems, and which should
be fixed now).
If
Also, the bug that is described here is about things breaking on
*non*-nvidia systems. If you have problems on nvidia systems, please do
not add comments here, you are seeing another problem. See also
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/comments/37,
and if the bug referenced
Public bug reported:
I was happily using wayland so far on an Intel Tiger Lake laptop. Then I
did an upgrade, including upgrading gdm3 42.0-1ubuntu2 to 42.0-1ubuntu4,
rebooted, and got logged into an Xorg session.
Investigating, it seems this was caused by this patch, reverting in
manually locall
I just reported
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969250 which was
marked as duplicate of this bug (which it is), but do check that bug for
a bit more analysis on where the bug is. TL;DR: there are nvidia-
specific checks in 61-gdm.rules that are no longer guarded by a check
for
> I have no session menu at all after upgrading to Jammy today. Is this
the right bug report for it, or should I open a new one? It wasn't
entirely clear to me from the description.
Sounds like the same bug - if only one session is available, gdm hides
the menu entirely I believe (I also have no m
Jeremy, I'm not sure the fix is complete yet, did you test this? I
believe our added patch still removes the nvidia-only guard block
(leaving only the gdm_nvidia_end label, but no jump to it), so the
nvidia suspend checks are still applied to other machines (which will
not have e.g. /usr/bin/nvidia
I'm seeing the same (or at least a highly similar) problem on Ubuntu
22.10:
NetworkManager[1628]: [1718657963.8557] device (CC:21:19:DA:E8:EA):
Activation: starting connection 'Gambit Network'
(e2a0aeb8-c87f-4ac6-8972-1e0bfac16e91)
NetworkManager[1628]: [1718657963.8558] audit:
op="
w00ps, I mistyped in my last comment, I am running 23.10, not 22.10.
Still not the latest, so I'll try to remember to re-test and report back
when I upgrade to 23.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
79 matches
Mail list logo
