** No longer affects: glib
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1155327
Title:
skype crashed with SIGSEGV in malloc@plt()
To manage notifications about this bug
** Changed in: qtwebkit-source (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: qtwebkit-source (Ubuntu Raring)
Status: Confirmed => Invalid
** Changed in: nvidia-graphics-drivers-304 (Ubu
> Reopening the skype tasks, since we now have an opportunity
> to get rid of the temporary fix in the archive.
Re-closing; this bug is no longer present, and I've already uploaded
removing the workaround.
** Changed in: skype (Ubuntu Raring)
Status: Triaged => Fix Released
** Changed in:
This bug was fixed in the package xdiagnose - 3.2.4
---
xdiagnose (3.2.4) quantal-proposed; urgency=low
* bin/xdiagnose: Exit with error if run as non-root. Otherwise, the
program will crash when it tries to write a new grub configuration.
(LP: #769419)
-- Bryce Harringto
This bug was fixed in the package xdiagnose - 2.5.3
---
xdiagnose (2.5.3) precise-proposed; urgency=low
* bin/xdiagnose: Exit with error if run as non-root. Otherwise, the
program will crash when it tries to write a new grub configuration.
(LP: #769419)
-- Bryce Harringto
This does seem to be fixed in Raring, albeit by an exhaustive list of
conflicts/replaces.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1076414
Title:
Transitioning between nvidia dr
Hello Tormod.
I finally found some time to collect the backtrace.
Jumping to 0x is unhealthy ...
---
#0 0x in ?? ()
#1 0xb6fda380 in MGACrtc2FillStrip (pScrn=pScrn@entry=0xb7ff6838) at
../../src/mga_driver.c:3170
#2 0xb6fdba2a in MGAScreenInit
Public bug reported:
When my system upgraded to 304.88-0ubuntu0.0.2 I started having sporadic
black window decorations. I also started having windows open up with
completely blank (black) contents. Often closing and reopening would
fix it.
Downgrading back to 295.40-0ubuntu1 has completely fixed
Reopening the skype tasks, since we now have an opportunity to get rid
of the temporary fix in the archive.
** Changed in: skype (Ubuntu)
Status: Fix Released => Triaged
** Changed in: skype (Ubuntu)
Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)
** Changed in: skype (Ubuntu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1182666
Title:
fglrx-updates 2:9.000-0ubuntu0.3: fglrx-updates kernel module failed
to b
Public bug reported:
Crash on initial login after Update Manager run and reboot.
ian@nanny-ogg ~$ lsb_release -rd
Description:Ubuntu 13.04
Release:13.04
Crash report detected appeared on top left toolbar, rest of desktop seems OK.
ProblemType: Package
DistroRelease: Ubuntu 13.04
Packa
Skype 4.2 for Linux has been released:
http://blogs.skype.com/2013/05/20/skype-for-linux-4-2/
I couldn't help testing, so I removed the skype and skype-bin packages,
downloaded the provided .deb file and installed it.
It works. :) Without a need to downgrade libqtwebkit4 or apply 'the
LD_PRELOAD
my guess is the lack of anti-bounce software cleaning the signal as others have
suggested. Here's a fellow who cleaned the contact points with a cleaner.
http://www.tomshardware.com/forum/59113-3-fixing-razer-naga-mouse-double-clicking-problem-walkthrough
others have adjusted the return spring.
Landed in Saucy
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/599068
Title:
[g
Landed in Saucy.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1001332
Title:
Landed in Saucy.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1051403
Title:
Users experiencing issues similar to those described here, may also want to see
https://bugs.kde.org/show_bug.cgi?id=319065
Affects screen resolution of NX sessions through x2go, on Kubuntu 13.04.
** Bug watch added: KDE Bug Tracking System #319065
https://bugs.kde.org/show_bug.cgi?id=319065
Public bug reported:
Directly related to this:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1182366
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
Uname: Linux 3.8.0-21-generic x86_64
NonfreeKernelModules: wl
Unfortunately the issue remains... I had new crashes/freezes, which
required hard resetting the computer...
I'll send the bug in a few minutes. In the meantime, this is the log for
Xorg.0.log.old:
[24.038]
X.Org X Server 1.13.3
Release Date: 2013-03-07
[24.038] X Protocol Version 11, Re
The issue with my screen flashing got so bad I had to downgrade back to
12.10 and the 3.5 kernel. I'm still having issues with the external
monitor switching configurations (resolution, position, and mirror-
displays switches every several minutes).
--
You received this bug notification because
No thanks to Ubuntu support (or lack thereof), a fellow owner of a Dell
3000 / Intel-865G provided me the solution:
Create / edit / save this file ('vi', notepad, et al):
/usr/share/X11/xorg.conf.d/00-xorg.conf that contains the following
content:
Section "Screen"
Identifier "Default Screen
I certainly didn't think that bug was surveillance. In fact, they haven't
been around in quite a while. But it has happened and it's pretty obvious
when it did happen.
]
But I've decided to deal with it in a better way. George Orwell once wrote
that the most hated man in England was Nosey P)arke
What you say may be true on a micro scale, but on a macro scale,,,
such as when the person goes into my SSL certificates area and leaves
notes talkng about how useless SSL is and he knows how can beat it,
(and I don't have a clue as to whether he changed the security of the
whole machine any more t
I tried kernel version 3.9.2 and official 3.5.0-30 with no success. I have
still the random freezes.
Because of this posting: http://www.thinkwiki.org/wiki/Intel_HD_Graphics
I tried also the kernel options:
i915.semaphores=1 i915.i915_enable_fbc=0
but also with no effect.
--
You received this
Ah right, turning from "invalid" to "fix released" then, sorry.
** Changed in: udev (Ubuntu)
Status: Invalid => Fix Released
** Changed in: udev (Ubuntu Raring)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscrib
Great! Thanks for the clarification.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/408903
Title:
Does not handle microphone mute button (KEY_MICMUTE)
To manage notification
@James: we have the new udev in saucy since today:
https://launchpad.net/ubuntu/+source/systemd/202-0ubuntu6
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/408903
Title:
Does
Hi Martin,
I don't think we should close it just yet. The key still maps to micmute
(as you mention), and upstream udev and X and gnome-settings-daemon all
agree on f20. I can prepare a bzr branch if it makes things easier.
Alternately we could just wait for udev v199 or greater to land in the
dis
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1182514
Title:
nvidia-304-updates 304.88-0ubuntu2: nvidia-304-updates kernel m
Public bug reported:
dual monitors
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: nvidia-304-updates 304.88-0ubuntu2
Uname: Linux 3.9.2-999-i7 x86_64
NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 3.9.
Christopher, I never checked the BIOS version, as this laptop is from
the company I work for, but it was very old (about 2 years old), it was
F.08. The latest is F.40 and I updated BIOS a few minutes ago.
The output of the command you said now is:
68SCE Ver. F.40
03/13/2013
I'll be using this sys
*** This bug is a duplicate of bug 1076414 ***
https://bugs.launchpad.net/bugs/1076414
** This bug is no longer a duplicate of bug 1061707
package nvidia-settings 304.43-0ubuntu1 failed to install/upgrade: trying to
overwrite '/usr/bin/nvidia-settings', which is also in package
nvidia-set
Luís Nabais, thank you for reporting this and helping make Ubuntu
better. As per
http://h2.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=5045596&prodTypeId=0&prodSeriesId=5045594&swLang=13&taskId=135&swEnvOID=4060#120
an update is available for your BIOS (F.40).
*** This bug is a duplicate of bug 1076414 ***
https://bugs.launchpad.net/bugs/1076414
** This bug is no longer a duplicate of bug 1061707
package nvidia-settings 304.43-0ubuntu1 failed to install/upgrade: trying to
overwrite '/usr/bin/nvidia-settings', which is also in package
nvidia-set
** Also affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-settings (Ubuntu)
Status: New => Triaged
** Changed in: nvidia-settings (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1076414 ***
https://bugs.launchpad.net/bugs/1076414
** This bug has been marked a duplicate of bug 1076414
Transitioning between nvidia drivers (updates, 304, 310) results in install
failure due to conflicting nvidia-settings
--
You received this bug no
*** This bug is a duplicate of bug 1076414 ***
https://bugs.launchpad.net/bugs/1076414
** This bug has been marked a duplicate of bug 1076414
Transitioning between nvidia drivers (updates, 304, 310) results in install
failure due to conflicting nvidia-settings
--
You received this bug no
*** This bug is a duplicate of bug 1076414 ***
https://bugs.launchpad.net/bugs/1076414
** This bug has been marked a duplicate of bug 1076414
Transitioning between nvidia drivers (updates, 304, 310) results in install
failure due to conflicting nvidia-settings
--
You received this bug no
*** This bug is a duplicate of bug 1076414 ***
https://bugs.launchpad.net/bugs/1076414
** This bug is no longer a duplicate of bug 1062360
package nvidia-settings (not installed) failed to install/upgrade: trying to
overwrite '/usr/bin/nvidia-settings', which is also in package
nvidia-set
Public bug reported:
Problems occuring during compilation of new kernels using "make-kpkg
--append-to-version "-amd64-130515" --initrd --us --uc buildpackage ".
The errors during kernel compilation seem to occur with dkms and are reproduced
with "/usr/src# /etc/kernel/header_postinst.d/dkms 3.9.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1182368
Title:
fglrx 2:9.010-0ubuntu3: fglrx kernel module failed to build
To manage notification
Christopher M. Penalver, I thought I already sent the bug report,
however it seems I didn't. That issue happened again a few minutes ago.
After hard resetting the computer again, I reported the bug using
ubuntu-bug as you requested.
Thanks a lot
--
You received this bug notification because you
Public bug reported:
Computer: HP ProBook 6460b Laptop
VGA: Intel HD 3000
OS: Ubuntu 13.04 64-bit
Log: Xorg.0.log.old (the one kept before needing to hard reset the computer)
[24.456]
X.Org X Server 1.13.3
Release Date: 2013-03-07
[24.456] X Protocol Version 11, Revision 0
[24.456] B
** Package changed: udev (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/763952
Title:
X200 tablet after screen rotation pointer x and y axis not changed
Closing udev task. As far as I can see, KEY_MICMUTE is being emitted
correctly, but X.org cannot handle this key.
** Changed in: udev (Ubuntu)
Status: Triaged => Invalid
** Changed in: udev (Ubuntu Raring)
Status: Triaged => Invalid
--
You received this bug notification because yo
You have been subscribed to a public bug:
Binary package hint: udev
This is not like this bug:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/702426
The keys actually works, at least one for rotation. But, after rotating,
the inputer device is unchanged, meaning, when the screen is on the
I have reported the bug to the synaptic driver
(https://bugs.freedesktop.org/show_bug.cgi?id=64103) and Peter Hutterer replied:
"Not sure how to fix this without some larger rework in the smoothing code.
Play around with the noise cancellation though, maybe you can find a setting
that makes it be
47 matches
Mail list logo
