I'm upstream. I saw the removal first in the release notes. Yet I'm
not surprised by removal. The contributions to pptp and pptpd have
declined, so the release cadence has slowed as well (1.4.0 in 2013, but
a few commits in git since). Number of people asking for help has also
declined. Some
by setting
GTK_THEME to adwaita in the package sugar-write-activity. This
perturbs the timing just enough to prevent the problem on our
supported hardware.
For our upcoming Bionic build, the abiword 3.0.2-6 package doesn't
show the problem.
--
James Cameron
http://quozl.netrek.org/
--
You received
Any chance of a fix in Ubuntu 16.04 LTS Xenial?
As a derivative, I'm carrying a custom package, which is fine
technically, but is hard to explain.
Ubuntu 18.04 beta is unaffected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Summary; my own rtl8821ae frequent connection lost problem was fixed by
upstream patch b8b8b16352cd ("rtlwifi: rtl8821ae: Fix connection lost
problem") merged for 4.14-rc4.
I've recently fixed a problem very much like the problems reported in
this bug. In particular the loss of WiFi scan
Summary; my own rtl8821ae frequent connection lost problem was fixed by
upstream patch b8b8b16352cd ("rtlwifi: rtl8821ae: Fix connection lost
problem") merged for 4.14-rc4.
I've recently fixed a problem very much like the problems reported in
this bug; and during my tests I saw the cycling ping
This bug should close because the configuration has been disassembled,
we can hardly expect hotellina to change the wireless card back to what
it was just so that the bug can be solved. ;-)
However, several of the problems in this bug were fixed by upstream
patches, in particular b8b8b16352cd
Dave, Lwfinger is Larry Finger, the maintainer of the rtl8821ae driver
already in Ubuntu 16.04. When you used his GitHub driver, you had
undone a change by Realtek, and that's why it worked. The Realtek
change was 40b368af4b75 ("rtlwifi: Fix alignment issues") and caused the
connection loss.
Sorry Simon, I had already tested my patch with my own local package, I
didn't think you'd need me to test your package of it, and I'm hoping to
hear if anybody else has tested it. ;-)
On a 17.10 Artful VM with Sugar, the Sugar desktop does not appear, some
other problem, so I'm not able to test
Thanks. Reviewed abiword_3.0.2-3_3.0.2-3ubuntu1~ppa1.diff.gz ... looks
right to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574278
Title:
AbiWord text cursor starts to flicker after adding
Thanks for the bump, I'd forgotten to update this bug.
I found the cause of the problem and fixed it for systems using Xorg.
It was a race condition, and is affected by speed of computer, speed of
graphics, other processes, and theme drawing. That's why it may not
happen for some people. You
> GTK_THEME=Abiword solves the problem, no more flickering
Does not solve for me on Artful 17.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574278
Title:
AbiWord text cursor starts to flicker
For your interest, the package dropped the reiserfs module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691180
Title:
linux: 4.4.0-79.100 -proposed tracker
To manage notifications about this
G'day Brian. Good to hear. For local testing, the signing can be
ignored; there's an option to skip it. The warnings sound familiar,
but are normal. For me, the patch did fix the flickering of the whole
screen, but did not fix the flickering cursor. Guess next steps
upstream involve reproducing
G'day Brian. The patch command automatically applies a patch to a set
of files. The particular patch has a sacrificial path element so the
--strip 1 option should be used. The --dry-run option is also useful
for testing. So it would be "patch --strip 1 --dry-run < file.patch",
where file.patch
G'day Brian. Yes, it needs to be compiled in. Download the Ubuntu
source package, apply the patch, build the package, then install it. If
you've not done that before, you may find it quite complicated. You
might enable deb-src entries in your /etc/apt/sources.list file, then
"apt-get update",
G'day Brian! Yes, the theme workaround began not working for me with
17.04. Yes, the problem can come and go with any changes to the
hardware, kernel, X server, or libraries. There is a fix that makes the
situation a lot better, see my post last week on the upstream bug
Bug also affects me. I've isolated it to a specific kernel patch and
updated the upstream bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1406810
Title:
[iMac11,1] Unable to boot
To manage
I'm having problems playing videos after this fix. (LP: #1648721)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643467
Title:
Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
I'll attach a stream that causes the problem. It is from a DVB-T card,
filtered by pid.
The package with regression is libavcodec54.
Previous working version before updates was
https://launchpad.net/ubuntu/trusty/amd64/libavcodec54/6:9.18-0ubuntu0.14.04.1
A workaround, downgrade only this
Public bug reported:
Since the security update to 6:9.20-0ubuntu0.14.04.1 triggered today by
#1643467, vlc and mplayer do not play mpeg transport streams that were
previously playable. Other types of stream are unaffected.
Description:Ubuntu 14.04.5 LTS
Release:14.04
libav-tools
@asavah, you wrote "It's a SHAME that such a good fix is not yet in the
"official" package."
I'm laughing like anything. I'm the upstream and I make the official
package, yet this fix has NEVER come to me. I just happen to notice it
now, here. Next time, make sure you talk to upstream before
Is caused by missing wpa_supplicant.
Alternate workaround is to start it manually;
systemctl start wpa_supplicant
After this, wireless can be used. The reason reboot worked was that it
did the same thing.
According to syslog, when the host name changes from oem-INVALID to user
preference
Also seen with sugar-browse-activity package.
(gdb) bt
#0 JSC::JSCell::getPrimitiveNumber (this=this@entry=0x0,
exec=exec@entry=0x7f8e28d43ab0,
number=@0x7ffdcedc13e0: 9.8813129168249309e-324, value=...) at
../Source/JavaScriptCore/runtime/JSCell.cpp:134
#1 0x7f8e85accbdc in
Uwe, do you have a method to reproduce flickering with the
GTK_THEME=adwaita?
Even so, the workaround is a major improvement, and the best we have, so
I'll add it to my OLPC derivative of the Ubuntu sugar-write-activity
package. http://dev.laptop.org/~quozl/y/1bkIWb.txt
--
You received this
Reproduced on a derivative. Using 16.04.1 ISO remastered with the Sugar
desktop. Used to work with 14.04.3. Log out and log in makes no
change. Workaround is to reboot.
Can supply additional information if required. Let me know.
--
You received this bug notification because you are a
Public bug reported:
Using Ubuntu Xenial 16.04 with xenial-updates applied.
Installed gir1.2-maliit-1.0 0.99.1+git20151118+62bd54b-0ubuntu3 and
dependencies.
Expected: successful import of Maliit via GObject Introspection API
using python "from gi.repository import Maliit",
Observed: failure
Raised upstream as http://bugzilla.abisource.com/show_bug.cgi?id=13791
** Bug watch added: AbiSource bug tracker #13791
http://bugzilla.abisource.com/show_bug.cgi?id=13791
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Impacting OLPC.
Reproduced using Ubuntu 16.04 Xenial amd64 iso booted as live-image,
plus universe, with abiword_3.0.1-6ubuntu0.16.04.1 from xenial-updates.
Workaround: switch from Ambiance to High Contrast theme.
Also affects package sugar-write-activity_97-5 which depends on package
Public bug reported:
in what-utils-1.3-0ubuntu1 /usr/bin/what-repo uses col2, so it doesn't
work.
on xenial, col2 is provided by package byobu.
on trusty, col2 is available in package bikeshed.
however, it would be simpler if col2 were replaced by an equivalant awk.
e.g.
{{{
---
The fix made in this bug broke production systems for me. Same symptom
as in comment #4. Which bug is tracking the regression? Meanwhile, I
downgrade kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, it is still a problem. If you don't want to remain subscribed to
the bug, feel free to remove yourself.
** Changed in: ubiquity (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Brian.
I'm not part of Ubuntu, but I am a developer at One Laptop per Child.
In my situation, the same problem happened without any Windows involved
at all, so I'm looking at what is common between us.
Your system logs show two SATA drives of 64 GB each, a USB CD-ROM drive,
and a
Reproduced three times.
My ubiquity syslog shows grub install is attempted on the installation
media instead of the target media.
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1483004/+attachment/4442490/+files/syslog
--
You received this bug
After several more attempts, I found that the kernel discovery order of
the drives was critical. When the install media is detected as /dev/sda
the problem occurs. When the target media is detected as /dev/sda the
install is successful. There's no obvious way to control the discovery
order.
--
Thanks. But it is not resolved for me. There was no option to turn on
or off RAID. In the Installation Type dialog, I chose Erase disk and
install Ubuntu. Where was this alternate menu of which you speak?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On my system after upgrade from 13.04 to 13.10 and then to 14.04, custom
shortcuts didn't work because the wrong keysyms were being generated,
according to xev, despite my use of xmodmap in .xsession called by nodm.
I fixed it by delaying the xmodmap by two seconds. I speculate that the
X server
Thanks Joseph. The module version and source version are identical (see
below), but the kernel version is not ... because I am running the
latest kernel that works for me. I will schedule downtime and carefully
boot the new kernel, in order to avoid losing control of the system
again. I would
Joseph, -22.33 did _not_ fix the problem for me.
Are there any further tests you would like me to make?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182868
Title:
tg3 driver 1.28 does not
3.8.0-22.3 boots, but the ethernet device is not detected, and I've lost
USB as well. I can't get in to even get a dmesg. I'll try talking grub
into downgrading.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I upgraded from 3.8.0-20.31 to 3.8.0-22.33 on my Macmini6,1 and the
ethernet device went away again as per #1162665, judging by my gkrellm
on nodm display. USB also went away, preventing further easy
diagnosis. Grub would not respond to a held down shift key.
I was able to boot from an
G'day Joseph, thanks for the bug reference, I've posted an update to bug
#1182868.
Summary: 3.8.0-20.31 works fine, but 3.8.0-21.32 and 3.8.0-22.33 do not
detect the tg3 ethernet device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
For me on 13.04, although the error message in Xorg.log was the same, it
turned out to be caused by #714492 (plymouth).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070677
Title:
Xorg fails to
For me on 13.04 an alternate workaround was to configure
/etc/default/nodm to start on vt8, although this leaves plymouth active
on vt7, whether or not the splash option is on the kernel command line.
The workaround to add plymouth --wait --quit || true to
/etc/init.d/nodm worked fine for me.
After an update, linux-image-3.8.0-21-generic 3.8.0-21.32 was installed
from raring-security, and this problem has come back. Will downgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162665
This bug #1024533 would appear to be a duplicate of bug #943195, and bug
#943195 has way more information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024533
Title:
xpdf.real crashed with
Did install from ubuntu-13.04-desktop-amd64+mac.iso on Macmini6,1 and
built-in ethernet did fail, symptoms matched as above in this ticket.
Did add USB ethernet, enable proposed, install new kernel -20, remove
USB ethernet, reboot, and the built-in ethernet was enabled.
Did several scp of large
I see the same Xorg.0.log output, but it happens every boot, and it
began yesterday, after applying updates, on 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070677
Title:
Xorg fails to
Also affected, on iMac11,1 27 i7 ATI M98L HD 4850 with Ubuntu 10.04
amd64. Have fglrx package installed. Backlight is turned off by DPMS
idle timer fine. Backlight stays at a default brightness since boot
despite DPMS activation. Backlight goes to maximum brightness on resume
from suspend.
@Payall: on Mac mini 2010 with internal 320Gb SATA drive, performance is
low, about a tenth of expected. About 7 MB/sec on Ubuntu 10.04 using
the above kernel, versus about 55 MB/sec on Mac OS X as shipped. Better
than the 0 MB/sec before this fix was available.
(Test method on Ubuntu; ensure
Fantastic. I also confirm that the test ISO ubuntu-10.04-desktop-
amd64-macbook71.iso 7b4cc590c28f8a5d31a411562dc4ff11 works on
Macmini4,1. ~~ qu...@laptop.org
--
[MacBookPro 7,1]mcp89 sata link reset fails, no disks detected
https://bugs.launchpad.net/bugs/576601
You received this bug
@Damien, my partitioning was everything in one place and ext3 rather
than ext4, but even during creation of ext3 filesystem the progress was
unremarkable. It was difficult to tell if it was hung. I used top(1)
and cat /proc/diskstats in a terminal to verify things were still
happening. No disk
It's in the TODO file in the source repository and should be in the
.tar.gz, please check?
--
Only a single PPTP-Linux VPN connection allowed
https://bugs.launchpad.net/bugs/155945
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm upstream.
My opinion is that the original poster's problem is a combination of the
incomplete implementation of pptp on Linux, and external devices that
were never intended to be operated in that fashion.
We have a feature request logged in our system (TODO) dated 23rd
December 2000 to fix
Micke, what you describe has nothing to do with the original bug report
... which was an issue with the verbosity of the logs. But I can
suggest some actions you can take.
1. Please downgrade temporarily to 8.04 if possible to verify for sure
that it is the transition from 8.04 to 8.10 that
The --loglevel option for pptp was added in 2003 for this purpose, and
was present from version 1.4.0-rc1 and onwards. The messages you show
in this bug report are not printed if the --loglevel is reduced from the
default 1 to the low 0. The messages indicate you have packet loss, and
for
Upstream code follows the RFC, and does not imitate the competing
implementations exactly, therefore some routers do not handle the
simultaneous connections properly, because the routers were coded and
tested against other implementations.
Upstream will accept patches that seek to make the
56 matches
Mail list logo
