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
** 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
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
** 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.
--
** 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
** 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,
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
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
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
** 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
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
** 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
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
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
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
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)
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
** 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
** 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
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
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
** 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()
** 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:
** 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:
** 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:
** 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:
** 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:
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.
** 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:
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
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
*** 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
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
--
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:
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
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.
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 /
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
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
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
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
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
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
Ups - I forgot to add the fdo prefix to the real fix, which is:
http://cgit.freedesktop.org/libreoffice/core/commit/?id=6c7374f071d998f726cd4a5b67baf54e357d096bh=master
KDE4: prevent blocking in Display::Yield
Will reword for 4.2, so it will be included in bugzilla.
--
You received this bug
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
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
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
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
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.
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
$ 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
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
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
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
** 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.
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
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 /
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
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
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
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
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
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
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
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.
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.
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;
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
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
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
** 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
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
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
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
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
(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
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
77 matches
Mail list logo
