[Bug 1897784]
(In reply to Olivier Tilloy from comment #8) > This bug looks similar to > https://bugs.documentfoundation.org/show_bug.cgi?id=131083 Nice find. Summary of bug 131083: Happened reproducible for the user with LO Ubuntu build 6.4.0-0ubuntu7 and LO Tinderbox build 45ca47ac39c03df4de52d627a764f16068b1eab0 (7.0.0.0.alpha0+ is reported for all development builds before branch off / alpha1 / beta) and just with kf5 in KDE / Plasma 2, not with Xubuntu (Xfce? which VCL in About? I would assume gtk3). Happens with the empty / default document. Bug 131083 comment 13 states: "I'm testing both Kubuntu and Xubuntu in a VM environment (VirtualBox 6.1.4)." You can get a comparable (but not equal!) build to the Tinderbox one via https://bibisect.libreoffice.org/linux-64-7.0 commit fc089b4dda133f1fd03922b713708e53af6c16fa. Reproduce: 1. start Calc 2. mark F10/11 vertically 3. exit LO 4. choose not to save Questions for each point (which might be related or not): 1. How is Calc started? Desktop link, command line (which one?), via start center? Does it happen with non-default profile via -env:UserInstallation=file:///tmp/test? 2. How are the cells marked? Mouse only, keyboard? Which cell first? Does it crash with other cells? 3. Exit crash just happens via window decorations? Or also via menu? Or by using Alt+F4 or Ctrl+Q? Or also by closing the Calc document and then the start center? 4. Why does Calc think the document was modified? Point 4 is AFAIK already exposing the real bug. General question: any additional output in a terminal? New entries in ~/.xsession-errors? Is this just happening with the localized KDE (the reporter uses de-DE.UTF-8)? An other eventually related crash I found (fixed?) is bug 131533 in LO 6.4.4. The implemented fix / patch is just a workaround, as I couldn't come up with a minimal reproducer without LO. There are some additional comments (see last ones) with info in https://gerrit.libreoffice.org/c/core/+/90990. According to bug 131083 comment 15, an old LO profile doesn't seem to be the cause of this, as the crash could be reproduced after deleting the profile. Since it didn't crash with the first try, it still might somehow be related. Would still be nice to get a known crashing profile for testing / reference, in the case there is some setting in it, leading to the crash. Bug 131083 comment 26 states the problem to reproduce the bug. "Made the installed DEB packages identical" I guess just means the package list, like "dpkg --get-selections", not the exact versions. An other bug that just comes to my mind and which was actually fixed for 6.4.0 is bug 104717. That changes the selection / clipboard handling in Calc. Quoting from my commit message: "Calc also removes the system selection when clearing the selection. Other applications keep the primary selection valid, until the application or document closes, so do the same in Calc." So maybe this introduces some case, where the primary selection isn't correctly cleared on shutdown. This is not KDE specific, but the QClipboard handling / API is very different from either Gtk+ or X11, so there might be some broken case now, where we don't clean the selection on module shutdown. Can you see, if the Kubuntu crashes happen on KDE shutdown, AKA session management related? > In the errors.ubuntu.com tracker, the earliest version exhibiting the crash > is 6.4.3, and there are new reports daily with 6.4.6. The thing we definitely know is that the LO 1:6.4.6-0ubuntu0.20.04.1 build in combination with KDE makes the crash much more likely. It seems the original bug is older. Still we don't have any reproducer, just a huge amount of reported crashes from Kubuntu users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
FWIW: I have installed Ubuntu's LO 6.4.6 in my focal schroot. I'm running Debian Buster with KDE on the host in X11. I couldn't produce any crash with the LO in the chroot, doing Calc selections and copy and paste operations, D'n'D and also some external copy actions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
Created attachment 165976 rhbz#1847031 cleaned crash bt That whole bt looks broken. RH has no reproducer either, so the fix is just a guess. Version was libreoffice-6.4.4.2-2.fc32.x86_64, as you can see in the bt paths. The bt itself looks "wrong". The user did a right-click on a Calc cell, that would open the context menu, but at that point, when the Gtk event is processed, a lot more stuff is already "gone", like all the aGuard objects have nullptr, so no mutex in them. So I guess this is just for reference, but won't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
No. (In reply to Michael Weghorn from comment #2)
> The only relatively recent commit related to QMimeData handling (i.e. mostly
> copy & paste and drag'n'drop) is the fix for tdf#131533, but that fix is in
> 6.4.4 already.
>
> @jmux: Any ideas?
We know the fix for tdf#131533 is rather fishy and more of a workaround,
then a real fix. But if we have the same backtraces before 6.4.4 (and I
checked that libreoffice_6.3.3-0ubuntu1.debian.tar.xz doesn't carry that
fix), we can - kind of - rule that out. Also all the backtraces just
indicate Calc (ScSelectionTransferObj), not any other LO modules (at
least Writer), which is strange. Maybe an active selection in Calc is
just more common on shutdown, then in other applications? OTOH a copy in
Calc keeps the selection, even if you move the "cursor rectangle". There
is also nothing suspicious new on
https://crashreport.libreoffice.org/stats/version/6.4.6.2
And the only "fix" in vcl/qt5 between 6.4.2 and 6.4.3 is commit
1000169ebca79478a05b4c23e760d99bd77e739e ("Qt5 unify font attribute
conversions"), which I would also rule out as the origin of any bug
(famous last words).
There is also no other fix in vcl/ or sc/ since commit
cbac26c52ccbe59c51c6631cb8c4b0a314a9848a / 6.4.0, which looks suspicious
at all w.r.t. the backtrace at a first glance. And the whole lazy
clipboard stuff was already in 6.3. And your fix for tdf#129809 was
already in 6.4.2.
Still nothing would explain the current peak, I can see in
https://errors.ubuntu.com since
https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=libreoffice-
core&from=2020-08-24&to=2020-09-25, which matches the publishing date
from
https://launchpad.net/ubuntu/+source/libreoffice/1:6.4.6-0ubuntu0.20.04.1
.
So I checked the diff of the 6.4.6 fix range for sc and interestingly it
contains commit 8718d243edc9400b0e0131b096702af8d33df327 (rhbz#1847031
null-deref), which fixes a null-deref in ~ScTransferOb. That should
really just fix a bug, not cause one, but eventually this just papers-
over some real bug in the other fixes, which now hits Qt in some way.
Because ScTransferObj is part of libsclo, which can't exists with
"pScMod == nullptr".
$ git log --pretty=oneline
f2e448175cee92fc695413e7281223e9f23e30ee~1..origin/libreoffice-6-4-6 | wc -l
123
Now I really would like to have a reproducer, which eventually should
also happen on master... and tdf#130559 is the only additional thing in
sc that looks strange, but that's just 17 out of the 123 patches.
Someone from Kubuntu could "mine" the crash reports, if there is
anything reproducible in it. And I have to get the RHEL bug report from
someone (Caolan, eventually).
So while I first suspected something non-LO, it now smells like a LO
bug, independent of VCL, evetually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897784
Title:
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
Created attachment 165978 Kubuntu shutdown crash bt It appears that one can just DL the text with a Launchpad login. So this is just a copy from the BT as reference. For whatever reason the clipboard object is still active, while the module is already gone, which is causing the crash. An other question is, what other packages were published that day, just in the case it's eventually no LO bug (I still think it is). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738774]
This is the typical chicken-egg problem: LO's SVG rasterizer / icons broken => default to PNG. Everybody uses PNG (and some complain about blocky icons in HiDPI) => nobody fixes the LO's SVG rasterizer / icons. Some more background info is in bug 133877 comment 11. And OTOH people can manually select an SVG icon set, so the pressure to fix this isn't really high. While the SVG icons easily look better when scaled, the PNG icons definitely look better in 100% / non-scaled in Linux. And it also doesn't help that gtk3 always scales the rasterized icons, so you get the worse 100% SVG icons scaled to HiDPI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812101]
FYI KDE4 used to have its own auto-extension checkbox in the file open dialog, so the LO KDE4 integration used that KDE setting and skipped LOs' own handling. Probably that setting doesn't exist anymore, as file dialogs are now Qt5 based and now LO has to handle the file auto- extension on its own. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812101 Title: libreoffice-kde5 file dialog/picker doesn't add extension automatically To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1812101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications
** Bug watch added: Debian Bug tracker #911148 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148 ** Also affects: hash-it via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148 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/1798861 Title: Tooltips flicker constantly in GTK3 applications To manage notifications about this bug go to: https://bugs.launchpad.net/hash-it/+bug/1798861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772451]
Created attachment 145298 Just an example image from master build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772451 Title: Diacritical marks become visible only after changing view in Writer To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772451]
That image is from todays master… And yes - those two selections is just one done with a single cursor. Probably this should have been a new bug… Version: 6.2.0.0.alpha0+ Build-ID: b0eab4b2d2761139ecf5191252dfa8005cd29508 CPU-Threads: 64; BS: Linux 3.16; UI-Render: Standard; VCL: x11; Gebietsschema: de-DE (de_DE.UTF-8); Calc: threaded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772451 Title: Diacritical marks become visible only after changing view in Writer To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772451]
Created attachment 145299 The example document used for the screenshot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772451 Title: Diacritical marks become visible only after changing view in Writer To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769654] Re: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics
Just a FYI: I opened https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=907487 That won't result in a different binary package, but from my interpretation it's a bug in the patch. ** Bug watch added: Debian Bug tracker #907487 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907487 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769654 Title: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727
I did the same tests as in comment #3 and it works for me. Thanks. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745130 Title: Support rfkill-any led trigger for Fujitsu u727 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727
I can't test this 3.13 kernel, as it has multiple other problems. What I was talking about was the 4.4 Xenial kernel compiled with the Trusty config / compiler, so my modules will build against: Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack- protector-strong not supported by compiler. So on Trusty with HWE Xenial I get: $ grep CONFIG_CC_STACKPROTECTOR_STRONG /boot/config-4.4.0-111-generic # CONFIG_CC_STACKPROTECTOR_STRONG is not set while on Xenial I have $ grep CONFIG_CC_STACKPROTECTOR_STRONG /boot/config-4.4.0-112-generic CONFIG_CC_STACKPROTECTOR_STRONG=y Sorry for not being explicit enough. BTW: I manually compiled the Ubuntu kernel source with my attached patch, the config from /boot as .config and a make oldconfig etc. and it worked as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745130 Title: Support rfkill-any led trigger for Fujitsu u727 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727
Thanks a lot. After apw's comment on IRC I expected something in the next weeks :-) I can just tell you it boots and seems to work. When I tried to manually build my hw-support-dkms against the kernel I got: LANG=C ./r + pwd + make -C /usr/src/linux-headers-4.4.0-112-generic M=/home/glg/mod make: Entering directory `/usr/src/linux-headers-4.4.0-112-generic' Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler CC [M] /home/glg/mod/fujitsu-laptop.o gcc: error: unrecognized command line option '-fstack-protector-strong' make[1]: *** [/home/glg/mod/fujitsu-laptop.o] Error 1 make: *** [_module_/home/glg/mod] Error 2 make: Leaving directory `/usr/src/linux-headers-4.4.0-112-generic' So I guess this kernel was build on Xenial, which I don't have installed. I have Trusty and Bionic, which has the upstream patch included. But generally it looks ok'ish, as rfkill-any shows up: $ cat /sys/class/leds/input2\:\:capslock/trigger none rfkill-any kbd-scrolllock kbd-numlock [kbd-capslock] kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock AC-online CMB1-charging-or-full CMB1-charging CMB1-full CMB1-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 mmc0 rfkill0 rfkill1 phy0rx phy0tx phy0assoc phy0radio For a test I used the the caspslock led and manually set the soft rfkill, which triggers the led correctly: $ echo "rfkill-any" | sudo tee /sys/class/leds/input2\:\:capslock/trigger rfkill-any $ cat /sys/class/leds/input2\:\:capslock/trigger none [rfkill-any] kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock AC-online CMB1-charging-or-full CMB1-charging CMB1-full CMB1-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 mmc0 rfkill0 rfkill1 phy0rx phy0tx phy0assoc phy0radio => capslock led is on $ sudo rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo rfkill block 0 $ sudo rfkill block 1 => capslock led is off I tried all combinations of block and unblock. No stacks in the dmesg. So I guess it works as expected. If you can provide a Trusty based kernel, I'll test it tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745130 Title: Support rfkill-any led trigger for Fujitsu u727 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745130] [NEW] Support rfkill-any led trigger for Fujitsu u727
Public bug reported: I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both device driver currently provide a single rfkill trigger, so the led could just be assigned to one. As a result the upstream kernel got a new "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigger. commit 9b8e34e211b15af429b72388a8f2b3b1823d172e Author: Michał Kępień Date: Fri Jan 6 07:07:47 2017 +0100 rfkill: Add rfkill-any LED trigger Normally I would simply patch the affected modules using DKMS, like the i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW without messing with the kernel packages. I'm currently waiting for some reviews, like https://www.spinics.net/lists/platform-driver-x86/msg14606.html But the rfkill support is compiled in, so I can't patch it using DKMS. So my first proposed fix would be to include a backport of this patch. Alternatively rfkill can be compiled as a module, so I can patch it and provide an updated module. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-111-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 Date: Wed Jan 24 10:48:28 2018 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty ** Patch added: "Add rfkill-any as led trigger" https://bugs.launchpad.net/bugs/1745130/+attachment/5042221/+files/rfkill-any-4.4.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745130 Title: Support rfkill-any led trigger for Fujitsu u727 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1745130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
I can't bisect the problem, because for the two kernels I build, suspend was broken and the PC didn't wake up from 2nd suspend :-( I also tried 4.9-rc6 (albeit on an Arch Linux), which shows the same bug. ** Package changed: xorg (Ubuntu) => linux-lts-xenial (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
So I applied this "big hammer" solution of the patch to the Trusty (14.04) Xenial HWE kernel (4.4.0-47.68~14.04.1) and this fixes the bug. I'll give it some more testing, while bisecting v4.0 to v4.1. ** Bug watch added: freedesktop.org Bugzilla #98832 https://bugs.freedesktop.org/show_bug.cgi?id=98832 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=98832 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/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
$ git bisect log # bad: [89e419960fb6a260f6a112821507d516117d5aa1] Linux 4.1.4 # good: [c8bde72f9af412de57f0ceae218d648640118b0b] Linux 4.1.3 git bisect start 'v4.1.4' 'v4.1.3' # good: [e0cf83cc3de0341d8cabbb23097ad85f5ce97a11] drm/qxl: Do not leak memory if qxl_release_list_add fails git bisect good e0cf83cc3de0341d8cabbb23097ad85f5ce97a11 # bad: [9d680e03989324f000596be4862728a7c30f22c1] selinux: don't waste ebitmap space when importing NetLabel categories git bisect bad 9d680e03989324f000596be4862728a7c30f22c1 # bad: [510c99974fdbc18f143c41cbd461c522f5ad7164] tpm, tpm_crb: fix le64_to_cpu conversions in crb_acpi_add() git bisect bad 510c99974fdbc18f143c41cbd461c522f5ad7164 # bad: [8b941a43ea7709111d3cbea2bdfcc678975255da] drm/radeon: only check the sink type on DP connectors git bisect bad 8b941a43ea7709111d3cbea2bdfcc678975255da # good: [0f2bb042f21bdb28f20efcf1ff1c507e2f8b3caa] drm/i915: Declare the swizzling unknown for L-shaped configurations git bisect good 0f2bb042f21bdb28f20efcf1ff1c507e2f8b3caa # good: [1f977d7e942519127aea0a08e9d08437b363cf19] drm/i915: Use two 32bit reads for select 64bit REG_READ ioctls git bisect good 1f977d7e942519127aea0a08e9d08437b363cf19 # good: [7b49262b642511a16699cc63cf2a716739f0c43f] drm/radeon: SDMA fix hibernation (CI GPU family). git bisect good 7b49262b642511a16699cc63cf2a716739f0c43f # bad: [d1a4362d41e4feb52df6464f70fb64f21b894623] Revert "drm/radeon: dont switch vt on suspend" git bisect bad d1a4362d41e4feb52df6464f70fb64f21b894623 # first bad commit: [d1a4362d41e4feb52df6464f70fb64f21b894623] Revert "drm/radeon: dont switch vt on suspend" Just remember that good and bad is inverted, as I was looking for the commit which fixes my colour problem in v4.1.4. For me it fixes more then just the cursor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
Hmm - so I'm not sure what's going on here. I started bisecting v4.1 .. v4.2.8 and I couldn't find a working version in 6-7 bisects and when I checked rest of the commit set in the bisect, it couldn't find any commits to drivers/gpu?! So I decided to test Ubuntu mainline kernels a little bit more and the current status is: Broken: linux-image-4.1.3-040103-generic_4.1.3-040103.201507220129_amd64.deb Working: linux-image-4.1.4-040104-generic_4.1.4-040104.201508031330_amd64.deb So probably something was fixed and in a short time broken again during the v4.2 development cycle?! And probably I should check with other connectors too, as I currently run the monitor via DVI => VGA connector. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
So I downloaded some kernels from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D Working: linux-image-4.1.35-040135-generic_4.1.35-040135.201610241431_amd64.deb Broken: linux-image-4.2.7-040207-generic_4.2.7-040207.201512091533_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
While keeping the Xenial HWE stack on Ubuntu Trusty (14.04), I tried various installed HWE kernels. It seems it really broke with the Wily kernel (4.2.0.42.34). The Vivid kernel (3.19.0.74.56) has survived multiple resume cycles, while Wily instantly created the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
Now I tried all the Trusty HWEs and it seems to have started with Wily. xserver-xorg-video-radeon-lts-wily 1:7.5.0+git20150819-0ubuntu1~trusty1 linux-image-generic-lts-wily 4.2.0.42.34 xserver-xorg-core-lts-wily 2:1.17.2-1ubuntu9.1~trusty1 mesa-lts-wily 11.0.2-1ubuntu4~trusty1 I had once wrong colors with the Trusty initial stack (3.13), which I couldn't reproduce. And I was just told that disabling DPMS / monitor power management in KDE also prevents the problem, which might correlate with the fact, that running a DPMS "force off" / "force on" cycle also restores the colors correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
I couldn't reproduce the problem with Trusty (14.04) using its original HWE stack (AKA Kernel 3.13). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
This is just a display problem - a snapshot is correct, so it really looks like a radeon driver problem, instead of an xorg problem. The wrong colors are always different, so every cycle produces a different result. For a photo as background it almost looks like modern art ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] Re: Distorted colours after suspend / resume cycle
** Attachment added: "Correct Unity desktop" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+attachment/4781463/+files/photo_desktop_ok.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643843] [NEW] Distorted colours after suspend / resume cycle
Public bug reported: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu yakkety ** Attachment added: "Broken Unity desktop after resume from suspend" https://bugs.launchpad.net/bugs/1643843/+attachment/4781443/+files/photo_desktop_broken.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559051] Re: Instable DisplayPort with latest radeon driver
The reverted radeon patchset didn't help for long. Actually I don't know why it worked at all, but probably the HW was just breaking down slowly. What finally helped was replacing my DisplayPort to DVI adapter for a new one. This doesn't seem to be a software problem, as the latest kernel works again without a patch. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559051 Title: Instable DisplayPort with latest radeon driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559051] [NEW] Instable DisplayPort with latest radeon driver
Public bug reported: I'm using an external monitor on my notebook via DisplayPort => DVI adapter. After the latest Xenial updates, which included a kernel update to 4.4.0-13.29, I had massive problems, with black screen after reboot to black screen after suspend with the attached monitor. xrandr still showed the monitor correctly. Additionally I had graphic glitches. Sometimes I managed to re-enable the monitor by detaching it, changing some window in the KDE session and re-attaching it. But it didn't always work. dmesg had some entries like: [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed The 12.27 kernel contained a "Pull in upstream AMD code (amdgpu) in Xenial (LP: #1546572)", which also includes "drm/radeon: fix dp link rate selection (v2)" patch So I took the old radeon modules source from 11.26, compiled and installed it for 13.29, updated the initramfs and my problems are solved. I didn't yet test the explicit patch. as I don't know where the patchset was taken from. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-13-generic 4.4.0-13.29 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmg3642 F pulseaudio /dev/snd/controlC1: jmg3642 F pulseaudio CurrentDesktop: KDE Date: Fri Mar 18 12:34:15 2016 HibernationDevice: RESUME=UUID=9e70-bcd1-4a58-b700-4b47774178d3 MachineType: LENOVO 2550W4R ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-13-generic root=/dev/mapper/lenovo--username-root ro splash quiet radeon.dpm=1 nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-13-generic N/A linux-backports-modules-4.4.0-13-generic N/A linux-firmware1.156 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-03-04 (13 days ago) dmi.bios.date: 09/21/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 81ET44WW (1.20 ) dmi.board.name: 2550W4R dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr81ET44WW(1.20):bd09/21/2010:svnLENOVO:pn2550W4R:pvrThinkPadL512:rvnLENOVO:rn2550W4R:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2550W4R dmi.product.version: ThinkPad L512 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Patch added: "Diff from the radeon directory 11.26 to 13.29" https://bugs.launchpad.net/bugs/1559051/+attachment/4603101/+files/radeon-11.26--13.29.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559051 Title: Instable DisplayPort with latest radeon driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891199]
I just did a quick test and generally it works and sends the PDF to CUPS. So thanks again for this quick patch. I currently don't have time to turn this patch into a really useable version and I don't know if anybody will add enought priority to it and work on it (I'm leaving for a holiday at least until July). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891199 Title: Okular sends print jobs in PostScript format To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/891199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891199]
The initial patch would be great. We'll get this tested before production anyway and I can report back or probably even send patches, which fix stuff. It's not that we're not coding stuff ourself, but I thought it would be more work to get this coded, and we already buy Linux support, which patches upstream code, if we don't code the stuff ourself. Additionally I would add some option to okular to select the default printing format (PDF or PS - like LibreOffice) to really get this feature included upstream (defaulting to PS). We normally require upstream / master fixes before including a backport in our release, so we don't have to re-patch everything within our next major release cycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891199 Title: Okular sends print jobs in PostScript format To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/891199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236012]
Ups - I forgot to add the fdo prefix to the real fix, which is: http://cgit.freedesktop.org/libreoffice/core/commit/?id=6c7374f071d998f726cd4a5b67baf54e357d096b&h=master KDE4: prevent blocking in Display::Yield Will reword for 4.2, so it will be included in bugzilla. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236012 Title: [KUBUNTU] Calc freezes screen when using drag-and-drop on cells To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1236012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272725]
Ok - the LO shell doesn't see any events, because these are queued and no one is running the qt main loop. I'm currently looking into QTimer stuff. It looks like it blocks all Timers, if I open a Dialog from a timer event. There seems to be a race somewhere in the Qt event loop handling (wich is actually glib in Qt 4.8). The FormatCells dialog is huge compared to most other dialogs. If I block on any dialog with gdb and just press continue, the event handling / QTimers are dropped. This happens with all dialogs in gdb. So this change makes thuings definitly worse. If I won't find a workaround today for the strange QTimer handling, I'll revert them. BTW - for me LO just works fine, if you directly open any application and not the shell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272725 Title: [Upstream] LibreOffice Calc Format Cell Dialog is sometimes unusable To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1272725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272725]
Which build / version are you testing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272725 Title: [Upstream] LibreOffice Calc Format Cell Dialog is sometimes unusable To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1272725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290514] [NEW] LibreOffice KDE4 backend crashes in Qt4 recursive paint events
Public bug reported: Distribution: Kubuntu 12.04 Package: qt4-x11 4:4.8.1-0ubuntu4.6 Program: LibreOffice 4.3 (current master build). This bugs origin is a crash when using KDE4 native file picker dialogs from within LibreOffice [1]. There are several similar ones in all distributions. In the backtrace you can see, that LO calls the Qt event dispatcher, which processes a draw event, which - at some point - waits for the clipboard using the Qt / LO event loop, which processes another (now nested) draw event -> crash. This happens, because LO sets qApp->clipboard()->setProperty( "useEventLoopWhenWaiting", true ); because the X11 event processing in clipboardWaitForEvents would interfere with the LO X11 handling / locking. QX11Data::clipboardWaitForEvents (gui/kernel/qclipboard_x11.cpp:520) actually installs the correct clipboard event filter in the qapp, which should just handle Clipboard events. But actually the Qt internal glib event loop doesn't honor the QEventLoop::ExcludeSocketNotifiers (see src/corelib/kernel/qeventdispatcher_glib.cpp). Originally I opened [2], because I didn't want to deep dive into the Qt codebase. Since I didn't get any usable replies and all my implemented workarounds in LibreOffice didn't work I tried to understand the backtrace from [2] and realized the missing QEventLoop::ExcludeSocketNotifiers handling in the Qt glib code. I opened [3] and pushed a patch for Qt review as [4]. [1] https://bugs.freedesktop.org/show_bug.cgi?id=69002 [2] https://bugreports.qt-project.org/browse/QTBUG-34614 [3] https://bugreports.qt-project.org/browse/QTBUG-37380 [4] https://codereview.qt-project.org/#change,80528 ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: qt4-x11 (Ubuntu Precise) Importance: Undecided Status: New ** Affects: qt4-x11 (Ubuntu Saucy) Importance: Undecided Status: New ** Affects: qt4-x11 (Ubuntu Trusty) Importance: Undecided Status: Triaged ** Tags: kubuntu ** Attachment added: "LibreOffice backtrace of the crash." https://bugs.launchpad.net/bugs/1290514/+attachment/4017137/+files/bt-repaint-error.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290514 Title: LibreOffice KDE4 backend crashes in Qt4 recursive paint events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1290514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272725]
This looks like a KDE4 backend problem. Doesn't happen with we GNOME backend. For me not only this Window is transparent, but the whole application stops processing (internal?) X11 (paint?) events (just move the window). If I close the dialog by guessing the button or pressing ESC, everything continues to work fine... Actually for me it just happens, if LO has some content in the clipboard (probably again a QClipboard problem). And it just happens with this modal dialog. I've tested other dialogs, which using the same class (SfxTabDialog), but these don't freeze. Currently I'm investigating, what makes this particular dialog so special. All threads are actually Yielding, nobody seems to wit for a lock - very strange. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272725 Title: [Upstream] LibreOffice Calc Format Cell Dialog is sometimes unusable To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1272725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272725]
Can you please verify that the shortcut (Ctrl+1) and "Format -> Cells" always work correct? I just can test master, which has additional fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272725 Title: [Upstream] LibreOffice Calc Format Cell Dialog is sometimes unusable To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1272725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995330]
Created attachment 94350 Oxygen rendered background - top highlighting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995330 Title: [Upstream] Libreoffice has no border on menus (KDE) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/995330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995330]
I just added two images of the Qxygen themed menu to show the highlighting problem. Additionally the disabled menu entries are almost unreadable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995330 Title: [Upstream] Libreoffice has no border on menus (KDE) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/995330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995330]
Created attachment 94351 Oxygen rendered background - bottom highlighting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995330 Title: [Upstream] Libreoffice has no border on menus (KDE) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/995330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995330]
I did some research on this bug while thinking of a resolution for #74416. Currently the KDE4 backend works like this: * Get a control request * Generate a QImage with the requested size * Fill image with the QPalette::Window color * Draw the control with the theme style to the QImage * Blit / copy the image to the actual target This results in this - actually unstyled - dropdown menus. So for a test I changed the menu generation to a more Gtk+ backend approach: * Get the control request from vcl * Create a QMenu object * Resize the menu to the requested size * Copy the QMenu to a QImage using QImage(QPixmap::grabWidget(...).toImage()) * Draw the control with the theme style to the QImage * Blit / copy the image to the actual target This generates the correct background (yeah); but now I realized (to my increasing frustration), that the highlighting is actually drawn based on the background image with a different color. Probably just the opaque value is adapted - I didn't actually check the Oxygen code. To make the KDE theming using VCL even harder, Oxygen uses some kind of animation to fade the highlighting to the correct color, which won't work using the QImage based copy approach (and I also don't know how this actually works in the Oxygen Qt style engine). Additionally the QPixmap::toImage() call has additional drawbacks: "Note that for the moment, alpha masks on monochrome images are ignored." (http://qt-project.org/doc/qt-4.8/qpixmap.html#toImage) >From my current point of understanding of all the interaction, the only realistic way to fix the styling problems is to draw LO native widgets using a real Qt widgets stack and let LO draw it's specific objects. I guess this will result in a complete rewrite of the KDE4 backend based on a new architecture - if this is possible using VCL. And there is already an abstraction for (popup) menus, which uses the same approach (SalMenu). Now I need to get some feedback, if this approach is implementable at all. I would start a kde4v2 backend, but this is a lot more work then I have currently time for: GSoC 2014 anyone? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995330 Title: [Upstream] Libreoffice has no border on menus (KDE) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/995330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176577] Re: mei unexpected reset in kernel 3.8
I patched the source from 3.8.0-27.40 (there aren't any changes for the mei driver in any Ubuntu 3.8 kernels) and just build the module. The dmesg log still continues to fill with "mei reset" messages. Since the mei driver has changed a lot since 3.8, I tried to backport the mei driver from git AKA 3.11-rc5+ (commit dab9bf41b23fe700c4a74133e41eb6a21706031e) for a test. The backport patch is very minimal and stops the messages, but since I don't use the Intel AMT interface, I don't know if it's working as expected. ** Patch added: "Backport patch for the mei driver from kernel v3.11-rc5+ to v3.8." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176577/+attachment/3775052/+files/mei-bp-from-commit-dab9bf41b23.diff ** Bug watch added: Red Hat Bugzilla #917081 https://bugzilla.redhat.com/show_bug.cgi?id=917081 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=917081 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/1176577 Title: mei unexpected reset in kernel 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186976] [NEW] debmirror doesn't download translations for Ubuntu repositories since quantal.
Public bug reported: I'm on Ubuntu raring. In debmirror v2.13 translation downloading was changed from parsing i18n/Index files to using the file information from the distributions Release file. The Ubuntu repositories don't yet include the translation files in the Release files. As a result the translated Package description won't be mirrored since quantal (1:2.14ubuntu1), which is a real nuisance if you use a local mirror. The complete i18n/Index parsing code was dropped in the following Git commit: SHA: 2437646a9d8478b3a05aeaffdbcfd71fca99bf5f Subject: Fix downloading of translation files for sections contrib and non-free. The attached patch is against debmirror 1:2.14ubuntu1. ** Affects: debmirror (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "Use i18n/Index and Release information to find translations." https://bugs.launchpad.net/bugs/1186976/+attachment/3693604/+files/fix_i18n_index.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186976 Title: debmirror doesn't download translations for Ubuntu repositories since quantal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1186976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030858] Re: 0bda:8176 RTL8188CUS does not connect to wireless networks
*** This bug is a duplicate of bug 852190 *** https://bugs.launchpad.net/bugs/852190 ** This bug has been marked a duplicate of bug 852190 7392:7811 Edimax EW-7811Un USB dongle won't connect to networks (rtl8192cu module) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030858 Title: 0bda:8176 RTL8188CUS does not connect to wireless networks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1030858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030858] Re: 0bda:8176 RTL8188CUS does not connect to wireless networks
Just wanted to add a "me too". My hardware is: 050d:1102 Belkin Components F7D1102 N150/Surf Micro Wireless Adapter v1000 [Realtek RTL8188CUS]. The attached patch fixes the RealTek drivers (3.4.4.4749.20121105) for the Raring kernel v3.7.1-030701.201212171620. ** Patch added: "Convert kernel_thread => kthread_run." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1030858/+attachment/3465019/+files/use_kthread_run.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030858 Title: 0bda:8176 RTL8188CUS does not connect to wireless networks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1030858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] Re: Any access to an NFSv4 based NFSroot fails with "Not a directory".
** Patch removed: "1788ea6e.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+attachment/3245657/+files/1788ea6e.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] Re: Any access to an NFSv4 based NFSroot fails with "Not a directory".
** Patch added: "1788ea6e.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+attachment/3245657/+files/1788ea6e.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] Re: Any access to an NFSv4 based NFSroot fails with "Not a directory".
I attached the git patches with fixed offsets and fuzzy apply messages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] Re: Any access to an NFSv4 based NFSroot fails with "Not a directory".
** Patch added: "1788ea6e.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+attachment/3245656/+files/1788ea6e.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] Re: Any access to an NFSv4 based NFSroot fails with "Not a directory".
** Patch added: "16b1c1cd.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+attachment/3245655/+files/16b1c1cd.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] Re: Any access to an NFSv4 based NFSroot fails with "Not a directory".
** Patch added: "5ede7b1c.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+attachment/3245654/+files/5ede7b1c.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] Re: Any access to an NFSv4 based NFSroot fails with "Not a directory".
** Patch added: "0ef97dcf.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+attachment/3245653/+files/0ef97dcf.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] Re: Any access to an NFSv4 based NFSroot fails with "Not a directory".
I've just tested 3.5-rc6 [0]. Since neither unionfs or aufs are included in the packages the install fails. But now I get "read-only filesystem errors" and I can actually chroot into the NFSroot and open or execute commands without the "Not a directory" error. So I guess it's really fixed upstream. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc6-quantal/ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags removed: needs-upstream-testing ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] Re: Any access to an NFSv4 based NFSroot fails with "Not a directory".
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020870] [NEW] Any access to an NFSv4 based NFSroot fails with "Not a directory".
Public bug reported: I'm using NFSv4 and FAI to install Ubuntu LTS. Currently I'm on 10.04 with the linux-lts-backport-oneiric kernel. A week ago I have started to base a new release of our LiMux distribution (http://www.muenchen.de/Rathaus/dir/limux/english/index.html) on 12.04 and got NFSv4 access errors after mounting the NFSroot from the FAI installation. This is the last error from the NFSroot initramfs, before the kernels "can't find init' panic: run-init: /sbin/init: Not a directory The origin of this error is commit 1788ea6e in the kernel git repository: nfs: when attempting to open a directory, fall back on normal lookup (try #5) It was fixed in v3.5-rc1 by commit 0ef97dcf nfs: don't open in ->d_revalidate I was able to fix this error by either porting 0ef97dcf + 16b1c1cd + 5ede7b1c to the precise kernel, or reverting 1788ea6e. I would like to get the fix included into the Ubuntu kernel, so I don't have to rebuild the kernel for every security update. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-25-generic 3.2.0-25.40 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Date: Wed Jul 4 08:44:06 2012 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=de_DE:de:en_GB:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=48a800b7-5834-4135-bb1e-ebd4fe451010 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.2.0-25-generic N/A linux-backports-modules-3.2.0-25-generic N/A linux-firmware1.79 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020870 Title: Any access to an NFSv4 based NFSroot fails with "Not a directory". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1020870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 854018] [NEW] Postinst fails to migrate /var/run and /var/lock directories on upgrade from natty.
Public bug reported:
base-files.postinst contains the function migrate_directory, which
should replace /var/{run,lock} with symlinks to /run and /run/lock doing
a "rmdir; ln -s". This fails, as both directories are tmpfs mounts on
Natty and can't be simply rmdir'ed without umounting their tmpfs in
advance.
On next boot several services fail, because they write their data to
/run but look for the data in /var/run (dbus, rpcbind).
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: base-files 6.4ubuntu4
ProcVersionSignature:
Uname: Linux 2.6.38.2-jmg i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Mon Sep 19 18:41:07 2011
Dependencies:
ProcEnviron:
LANGUAGE=de_DE:de:en_GB:en
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: base-files
UpgradeStatus: Upgraded to oneiric on 2011-09-11 (8 days ago)
modified.conffile..etc.nsswitch.conf: [modified]
modified.conffile..etc.profile: [modified]
mtime.conffile..etc.nsswitch.conf: 2007-11-10T15:05:31
mtime.conffile..etc.profile: 2011-09-11T14:06:19
** Affects: base-files (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854018
Title:
Postinst fails to migrate /var/run and /var/lock directories on
upgrade from natty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/854018/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623844] Re: lockpref not honored in /etc/thunderbird/pref/thunderbird.js
** Bug watch added: Mozilla Bugzilla #440908 https://bugzilla.mozilla.org/show_bug.cgi?id=440908 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=440908 Importance: Unknown Status: Unknown ** Patch added: "Debian Patch from 3.1.9-2" https://bugs.launchpad.net/thunderbird/+bug/623844/+attachment/2182900/+files/0007-Allow-.js-preference-files-to-set-locked-prefs-with-.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/623844 Title: lockpref not honored in /etc/thunderbird/pref/thunderbird.js To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/623844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525154] Re: mountall for /var races with rpc.statd
The attached patch changes the rpc_pipefs upstart job to start on statd and also poll in the pre-start script for the directory /var/lib/nfs/rpc_pipefs for 120*0.5 seconds to become available. Fixes my problem booting a NFSv4 Lucid server and survives an "apt-get install --reinstall nfs-common nfs-kernel-server" of the patched nfs- utils packages. Hope that the /var fsck / mount never takes more then 60 seconds (didn't check that yet). ** Patch added: "Fixed rpc_pipefs upstart job." https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/525154/+attachment/1751215/+files/rpc_pipefs.conf.diff -- mountall for /var races with rpc.statd https://bugs.launchpad.net/bugs/525154 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.com/mailman/listinfo/ubuntu-bugs
[Bug 478392] Re: /tmp is not cleaned when on a separate partition
I'm seeing the same problem on my Lucid server. Guessing from my "mountall --debug" log the problem seems to be, that /usr is also on a seperate partition and mounted-tmp.conf uses find to clean /tmp, which is on /usr but mounts /tmp before /usr. I tried to use "start on (mounted MOUNTPOINT=/tmp and mounted MOUNTPOINT=/usr) but this deadlocks the boot process. Any idea how to prevent the deadlock? -- /tmp is not cleaned when on a separate partition https://bugs.launchpad.net/bugs/478392 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.com/mailman/listinfo/ubuntu-bugs
[Bug 636488] Re: cupsd crashed with SIGSEGV in cupsArrayFind()
** Bug watch added: Debian Bug tracker #549050 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549050 ** Also affects: cups (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549050 Importance: Unknown Status: Unknown -- cupsd crashed with SIGSEGV in cupsArrayFind() https://bugs.launchpad.net/bugs/636488 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.com/mailman/listinfo/ubuntu-bugs
[Bug 636488] Re: cupsd crashed with SIGSEGV in cupsArrayFind()
As you can see in the CUPS bug report, this is fixed in CUPS 1.4.4. I tested a Backport from Maverick, which doesn't crash on SIGHUP. -- cupsd crashed with SIGSEGV in cupsArrayFind() https://bugs.launchpad.net/bugs/636488 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.com/mailman/listinfo/ubuntu-bugs
[Bug 636488] Re: cupsd crashed with SIGSEGV in cupsArrayFind()
I've also opened http://www.cups.org/str.php?L3682+P0+S-2+C0+I0+E0+M20+Q -- cupsd crashed with SIGSEGV in cupsArrayFind() https://bugs.launchpad.net/bugs/636488 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.com/mailman/listinfo/ubuntu-bugs
[Bug 636488] Re: cupsd crashed with SIGSEGV in cupsArrayFind()
** Attachment added: "classes.conf" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/636488/+attachment/1648705/+files/classes.conf -- cupsd crashed with SIGSEGV in cupsArrayFind() https://bugs.launchpad.net/bugs/636488 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.com/mailman/listinfo/ubuntu-bugs
[Bug 636488] Re: cupsd crashed with SIGSEGV in cupsArrayFind()
** Attachment added: "Printers config" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/636488/+attachment/1648704/+files/printers.conf -- cupsd crashed with SIGSEGV in cupsArrayFind() https://bugs.launchpad.net/bugs/636488 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.com/mailman/listinfo/ubuntu-bugs
[Bug 636488] Re: cupsd crashed with SIGSEGV in cupsArrayFind()
After some investigation, I found that cupsd always crashes in cupsdDeleteAllPrinters (cups_array_find) when send a SIGHUP (cups reload) and I have setup a class. It always crashes with my attached config files. If I leave the classes.conf empty, it won't crash. As it crashes in cupsdFindPolicyOp I added a default Policy to cupsd.conf, but the crash persists. I've attached the config without the default policy. ** Attachment added: "cupsd.conf" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/636488/+attachment/1648692/+files/cupsd.conf -- cupsd crashed with SIGSEGV in cupsArrayFind() https://bugs.launchpad.net/bugs/636488 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.com/mailman/listinfo/ubuntu-bugs
[Bug 636488] Re: cupsd crashed with SIGSEGV in cupsArrayFind()
I'm using a Lucid cups backport to Hardy having the same issue. I rebuild my backport with --enable-debug and got a useful backtrace. I have a VM, with a reproducible test case. ** Attachment added: "bt full from 1.4.3-1ubuntu1.2~lhm1 (Backport for Hardy)" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/636488/+attachment/1648412/+files/backtrace.log -- cupsd crashed with SIGSEGV in cupsArrayFind() https://bugs.launchpad.net/bugs/636488 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.com/mailman/listinfo/ubuntu-bugs
[Bug 283192] Re: X start crashes i915GM LVDS graphics
This is not a Thinkpad-only problem - I'm using a Medion SIM 2100 / MD 95600, which is actually a rebranded MSI S260. -- X start crashes i915GM LVDS graphics https://bugs.launchpad.net/bugs/283192 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.com/mailman/listinfo/ubuntu-bugs
[Bug 283192] Re: X start crashes i915GM LVDS graphics
After some more reboots it seems that the 2.2.1 driver doesn't work reliable without ForceEnablePipeA. It seems it was just luck that it worked a few times consecutively. The log is still slowly filling up and I don't have any EE entries. -- X start crashes i915GM LVDS graphics https://bugs.launchpad.net/bugs/283192 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.com/mailman/listinfo/ubuntu-bugs
[Bug 283192] Re: X start crashes i915GM LVDS graphics
It's not really working as good as I thought. The 10 second connections polling process freezes the graphics about 1/2 second per poll, which makes watching video very skippy. The sound (pulseaudio) is fine during the freeze. -- X start crashes i915GM LVDS graphics https://bugs.launchpad.net/bugs/283192 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.com/mailman/listinfo/ubuntu-bugs
[Bug 283192] Re: X start crashes i915GM LVDS graphics
** Attachment added: "Log with working 2.2.1 intel driver on intrepid" http://launchpadlibrarian.net/18530913/Xorg.0.log -- X start crashes i915GM LVDS graphics https://bugs.launchpad.net/bugs/283192 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.com/mailman/listinfo/ubuntu-bugs
[Bug 283192] Re: X start crashes i915GM LVDS graphics
** Attachment added: "Log without ForceEnablePipeA but with ModeDebug on 2.4.1" http://launchpadlibrarian.net/18530865/Xorg.0.log-fail -- X start crashes i915GM LVDS graphics https://bugs.launchpad.net/bugs/283192 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.com/mailman/listinfo/ubuntu-bugs
[Bug 283192] Re: X start crashes i915GM LVDS graphics
** Attachment added: "Log with ForceEnablePipeA and ModeDebug on 2.4.1" http://launchpadlibrarian.net/18530832/Xorg.0.log-flicker -- X start crashes i915GM LVDS graphics https://bugs.launchpad.net/bugs/283192 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.com/mailman/listinfo/ubuntu-bugs
[Bug 283192] Re: X start crashes i915GM LVDS graphics
** Attachment added: "Currently working xorg.conf" http://launchpadlibrarian.net/18530762/xorg.conf -- X start crashes i915GM LVDS graphics https://bugs.launchpad.net/bugs/283192 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.com/mailman/listinfo/ubuntu-bugs
[Bug 283192] [NEW] X start crashes i915GM LVDS graphics
Public bug reported: After upgrading from Hardy to Intrepid X stopped working for me. The screen flickers two times and starts to show a RGBWB slideshow, i.e. the whole screen turns red, green, blue, white, black, ... and changes every second. X is running fine, as I can switch to console and press Ctrl+Alt+Del to reboot. The display just continues with the slideshow, so I have no visual feedback at all. Booting with an older custom kernel, which was working with Hardy into "init=/bin/bash" and starting X via startx results in the same error. The graphics kind of work, if I set ForceEnablePipeA, except that the whole screen flickers every few seconds, and the Xorg log is flooded with data, probably because teh driver tries to find connected devices on VGA and TV. Errors are: (EE) intel(0): tried to update DSPARB with both planes enabled! (EE) intel(0): underrun on pipe B! <== this is the LVDS The vesa driver is working fine. I also tried an older 2.3.2 ubuntu package, which was used with 1.4.x, recompiled against 1.5 Xorg, which fails with the same symptoms. Next I tried patched hardy driver sources - failed too. The only working version for me is the driver compiled from the vanilla 2.2.1 sources, where I don't need the "ForceEnablePipeA" option, but which also fills my Xorg.0.log with messages. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- X start crashes i915GM LVDS graphics https://bugs.launchpad.net/bugs/283192 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.com/mailman/listinfo/ubuntu-bugs
[Bug 259761] Re: usplash segfaults on shutdown when pulsating
** Attachment added: "Fix for the crash" http://launchpadlibrarian.net/16958802/usplash-segfault-while-pulsating-during-shutdown-fix.diff -- usplash segfaults on shutdown when pulsating https://bugs.launchpad.net/bugs/259761 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.com/mailman/listinfo/ubuntu-bugs
[Bug 259761] [NEW] usplash segfaults on shutdown when pulsating
Public bug reported: Binary package hint: usplash While testing my own usplash theme on debian using usplash 0.5.19, usplash was crashing when shutdown in pulsating mode, because the SIGALRM triggered while graphics were already shut down. The attached simple fix sets pulsating = 0 when exiting the main_loop(). BTW: is there a reason, why the timer isn't stopped and started, instead of setting pulsating? Toggling pulsating mode shouldn't happen that often... ** Affects: usplash (Ubuntu) Importance: Undecided Status: New -- usplash segfaults on shutdown when pulsating https://bugs.launchpad.net/bugs/259761 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.com/mailman/listinfo/ubuntu-bugs
[Bug 148618] Change in behaviour of gzreadline() caused debmirror to delete my whole mirror
Public bug reported: Binary package hint: libcompress-zlib-perl Everything about this bug is in http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=435656 . As the summery says it, the behaviour of gzreadline changed, which resulted in debmirror deleting my mirrors instead of updating :-( Please update the package at least to 2.005-2, better 2.007-1, which fixes some more compatibility issues with 1.x series. ** Affects: libcompress-zlib-perl (Ubuntu) Importance: Undecided Status: New -- Change in behaviour of gzreadline() caused debmirror to delete my whole mirror https://bugs.launchpad.net/bugs/148618 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
