I used telegram-desktop 3.1.1+ds-1~ubuntu20.04.1 on focal for two days
now and the package is back into a functional state for me. No issues
observed whatsoever. I cannot say anything about libtgowt but it is my
understanding that this is "just" a build dependency for audio/video
call that is
lp:1477106 is another bug where this is being discussed (but didn't get
much attention). I agree that this is due to somewhat broken behaviour
of gtk3 and not cups-filter or avahi. In any case, an updated GTK 3
patch for Focal is available in the following for those who came here
with this
Since the bug report is very old, the original cause for what is
described here may have changed. But on a focal system, the gtk print
dialog populates the printer list on its own. Even if cups is not
running locally, it queries avahi-daemon and produces a list of
printers. This is causing a
Hello
Yes I am still around and you probably got lucky because I need this fix
for a class I am teaching once a year and I am currently preparing that
class. I have not touched the tiemu part yet, though.
It has to be said that this fix is not complete at all, it is more of a
hack to allow me to
Jammy,
I'm attaching a dump of the DSDT on my EliteBook 8530p. On a side note,
I'm interested in what you will do to check whether a BIOS bug may be
responsible for the issue. Can you maybe outline your procedure?
As for the Fan aways ON setting, I keep that one disabled anyway.
Regards and
Alberto,
As requested, I checked the status on karmic, and unfortunately, the bug
persists (2:8.660-ubuntu2 and a fully updated, fresh install of karmic
beta.)
However, --acpi-services=off is still applicable as workaround.
Regards
Matt
--
[HD 3650] fglrx versions newer than 8.543 cause
Georges,
How is this related to the bug? Just for the record, the mobility radeon
3650 mentioned in the initial posting is not one of the older cards
not supported anylonger since fglrx 9.4. However, these cards are
supposed to be supported by the open source driver - the efforts AMD has
done to
*** This bug is a duplicate of bug 221332 ***
https://bugs.launchpad.net/bugs/221332
** This bug has been marked a duplicate of bug 221332
The tiemu package is heavily outdated
--
update the version of tiemu pls
https://bugs.launchpad.net/bugs/341779
You received this bug notification
I packaged tiemu 3 because I had to fix some annoying bugs. My packages
are available in my PPA:
https://launchpad.net/~launchpad-weyland/+archive/ppa
Feel free to use some of my work to create an official package. I'm
about to comment on the bugs I just fixed in LP #373767.
Matt
--
The tiemu
This is because of the way tiemu handles key press and releases. The
mapping for hardware keycodes is hardcoded in src/gui/calc/pckeys.h.
Unfortunately, this mapping may differ. That's why certain keys are not
working. Furthermore, on my swiss german keyboard, y and z is swapped.
Unfortunately,
Problem persists with fglrx version 9.3 released today. See
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/346372
for my bug report which apparently is the same than the problem
described here.
--
fglrx versions newer than 8.543 cause system hang and panic
*** This bug is a duplicate of bug 346028 ***
https://bugs.launchpad.net/bugs/346028
Hello Michael
I don't agree that this is a dup of #346028 because of mismatching
symptoms. However, it's none of my business how duplicates are handled
and I'm leaving it up to the maintainers.
However, I'm
*** This bug is a duplicate of bug 346028 ***
https://bugs.launchpad.net/bugs/346028
Sorry, I posted the wrong link. I was referring to this bug instead:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/314600
In my opinion, this bug should either be marked as duplicate of
Public bug reported:
I installed fglrx 8.600 using jockey on a current jaunty 32bit
installation. After shutting the system down and starting the laptop (hp
elitebook 8530p) again, I get a black screen instead if GDMs login
screen. The laptop freezes; it's not even possible to log in via ssh
from
** Attachment added: xorg.conf
http://launchpadlibrarian.net/24189371/xorg.conf
--
Freeze on X startup with Mobility Radeon HD 3650
https://bugs.launchpad.net/bugs/346372
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Xorg.0.log of failed attempt
http://launchpadlibrarian.net/24189384/Xorg.0.log
--
Freeze on X startup with Mobility Radeon HD 3650
https://bugs.launchpad.net/bugs/346372
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Xorg.0.log of an old fglrx version which works (see bug
description)
http://launchpadlibrarian.net/24189486/Xorg.0.log
--
Freeze on X startup with Mobility Radeon HD 3650
https://bugs.launchpad.net/bugs/346372
You received this bug notification because you are a member
** Attachment added: kern.org of the crash
http://launchpadlibrarian.net/24189455/kern.log
--
Freeze on X startup with Mobility Radeon HD 3650
https://bugs.launchpad.net/bugs/346372
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: /var/log/messages of the crash
http://launchpadlibrarian.net/24189474/messages
--
Freeze on X startup with Mobility Radeon HD 3650
https://bugs.launchpad.net/bugs/346372
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I found these maybe-related bug reports on phoronix and in the
Unofficial ATI Linux Driver Bugzilla:
http://www.phoronix.com/forums/showthread.php?t=15215
http://ati.cchtml.com/show_bug.cgi?id=1475
--
Freeze on X startup with Mobility Radeon HD 3650
https://bugs.launchpad.net/bugs/346372
You
I tried it on amd64 - same problem. I installed alpha6, upgraded all of
the packages, ran jockey, installed the proposed driver, shut the
computer down and started it again and ran into the very same black
screen.
--
Freeze on X startup with Mobility Radeon HD 3650
Just for the record: This is supposed to be fixed in new upstream
version. So this bug can be closed after a check that it really is
working now. (I had no time to do that yet)
--
timeline with multiple categories messed up
https://bugs.launchpad.net/bugs/152252
You received this bug
I'm sorry this comes late, launchpad was very slow yesterday. Here comes
the patch to fix it.
** Attachment added: fix
http://launchpadlibrarian.net/9979163/patch_categories
--
timeline with multiple categories messed up
https://bugs.launchpad.net/bugs/152252
You received this bug
** Attachment added: screenshot of problem
http://launchpadlibrarian.net/9979171/broken.png
--
timeline with multiple categories messed up
https://bugs.launchpad.net/bugs/152252
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: how it should look
http://launchpadlibrarian.net/9979175/fixed.png
--
timeline with multiple categories messed up
https://bugs.launchpad.net/bugs/152252
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: ploticus
ploticus version 2.33 has a bug which makes multi-dimension timelines
impossible to draw. The outline of one bar is always extended to the
longest bar. Example:
#proc getdata
data:
2 5 6 963
1 1 2 1327
2 3 4 962
#proc categories
Hi
I just followed the advice of disabling the cdrom in the list of boot
devices as described above, but the problem persists. At least for me,
it's not solved yet :(. I'm wondering what others are experiencing,
especially those with asus notebooks (mine is asus, specs see above).
regards, Mat
Hi
Just for the case that anyone tries the workaround fior Samsung drives
described in a duplicate of this bug: Crossflashing the ASUS drive with
the Samsung firmware (version 03 or something) didn't work. After re-
flashing it with the original firmware, things went back to
normal/buggy.
Hi Patrick
I perfectly agree with you that my problem and yours are quite
different. However, I believe that several people who committed to this
bugreport are experiencing the same or a very similar problem than I do.
I am going to disable the ondemand governor as soon as I have time to
Hi
I have exactly this problem (Asus A6000, i386 feisty clean install) and
it still happens after installing libdvdcss. Please not that it also
happens while I'm not watching DVD and with CD roms or audio CDs in the
drive. This indicates that it is not related to libdvdcss. It didn't
lock up
I'm attaching the relevant part of /var/log/messages
Some information about the drive:
[EMAIL PROTECTED]:~$ dmesg |grep hdb
[3.184990] ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA,
hdb:DMA
[3.926314] hdb: TSSTcorpCD/DVDW TS-L632D, ATAPI CD/DVD-ROM drive
[6.064000] hdb:
** Visibility changed to: Public
--
root console with broken /etc/fstab
https://launchpad.net/bugs/52892
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
32 matches
Mail list logo
