Not seeing this with a machine updated today (2012-09-18) which should
have the new stack by now. So probably fixed along the process. Closing.
** Changed in: xorg (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Desktop
Ok, seems that the problem is somewhere in the radeon driver in the
kernel as installing a 3.2 kernel would boot with usable graphics.
Though frankly that is still X guys kinda domain to me.
** Attachment added: dmesg from 3.2 (12.04 kernel)
Things also became better with the Cirrus driver and VMs. After being able to
login I noticed that my KVM VM (which runs on a rather power efficient, iow not
too fast, machine) still has occasional crashes of this type. And there you can
see (and have to wait) every graphical goodness like
After upgrading to the proposed version jockey-text -l (for example)
starts failing for me. The 0.9.7-0ubuntu7.4 version does work.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Desktop
Packages, which
.tmp.unity.support.test.0:
ApportVersion: 2.0.1-0ubuntu15
Architecture: amd64
CompizPlugins:
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
apport information
** Attachment added: .var.log.jockey.log.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441886/+files/.var.log.jockey.log.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441889/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: BootLog.gz
https://bugs.launchpad.net/bugs/1080588/+attachment/3441888/+files/BootLog.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: Devices.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441890/+files/Devices.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441893/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441894/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1080588
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441895/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1080588
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441892/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441891/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441898/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441896/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441897/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441899/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441900/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441901/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441902/+files/UdevLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441903/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: XorgConf.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441904/+files/XorgConf.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441907/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441908/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441905/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441906/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
While I did not find the package uploaded to proposed, yet, I took the
packages from the link posted in PM and can confirm that it fixes the
regression I saw.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
Here you go...
** Attachment added: Xorg.0.log.old
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1086345/+attachment/3451966/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
** Attachment added: Screenshot taken
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/842066/+attachment/2358224/+files/Screenshot%2520at%25202011-09-05%252020%253A44%253A47.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
I find that the following scenario gives weird behaviour:
1. music files are on another host running forked-daapd (precise)
2. daapd source added locally to rhythmbox and playing
3. pause playback (indicator or application)
4. wait (not sure about the minimum here, about 1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/950717
Title:
rhythmbox: Problems when unpausing a daapd source after long pause
Status in “rhythmbox” package in Ubuntu:
New
Bug
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/941846
Title:
Duplicate entries in keyboard shortcuts for screenshots
Status in “gnome-settings-daemon” package in
** Attachment added: Screenshot at 2012-02-27 11:12:00.png
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/941846/+attachment/2787407/+files/Screenshot%20at%202012-02-27%2011%3A12%3A00.png
--
You received this bug notification because you are a member of Desktop
That was actually a bug in udev (now part of systemd) which dropped an
upstart script for the case of alternate graphics devices. This was
fixed now.
** Changed in: lightdm (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
** Package changed: ubuntu = ibus (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1369575
Title:
Regression/Trusty: Ultron un-1 most keys no longer recognized
Status in “ibus”
Public bug reported:
Could be a duplicate of bug #873495 which has not, yet, gone past
triaged status. But it has not been updated since last year and this
just happened to me trying 14.10 (Utopic).
Before installing the binary drivers, the nouveau driver was in use and
lightdm started
Public bug reported:
Needs more investigation but the system feels sluggish (video operations not
always smooth). This morning I had a crash in firefox (may not be related) and
it does not always seem to be reproducible. Yesterday I was able to run
glxgears and play a video stream through
[ 6732.868007] mce: [Hardware Error]: CPU 0: Machine Check Exception: 4 Bank 4:
b2070f0f
[ 6732.868007] mce: [Hardware Error]: TSC 71912a367e5
[ 6732.868007] mce: [Hardware Error]: PROCESSOR 2:10ff0 TIME 1412263116 SOCKET
0 APIC 0 microcode 41
[ 6732.868007] mce: [Hardware Error]: Run
After a cold boot today. Things looked relatively good for quite a while
(menus, youtube and glmark2). But while running glmark2 (for several
iterations):
[ 5792.435913] nouveau E[Xorg[1377]] cal_space: -16
[ 5792.515102] nouveau E[Xorg[1377]] cal_space: -16
[ 5792.597439] nouveau E[Xorg[1377]]
Ok, so the same happens when running a glmark2 loop with a 3.13 kernel.
So not related to the problem I initially had. I would say that was
quicker to trigger and seems to be gone with the latest kernels in
Utopic.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New = Fix
Hi Patricia, that was only the release-notes task. So we just noted
wrote down there that this can happen and how to work around it. I have
not seen or heard anyone fixing (or even looking at) the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which
Setting package to rhythmbox to have a starting point. It probably is
wrong and should be some part of the gstreamer set. But I don't know
which one.
** Package changed: ubuntu = rhythmbox (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is
apport information
** Tags added: apport-collected trusty
** Description changed:
Up-to-date 14.04 (Trusty) desktop installation (64bit), used enable 3rd
party software when installing
Testcase: Using rhythmbox to extract audio tracks from a audio CD into
the library as mp3. The GUI
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1342094/+attachment/4153332/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
apport information
** Attachment added: GstreamerVersions.txt
https://bugs.launchpad.net/bugs/1342094/+attachment/4153329/+files/GstreamerVersions.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1342094/+attachment/4153331/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
apport information
** Attachment added: LogAlsaMixer.txt
https://bugs.launchpad.net/bugs/1342094/+attachment/4153330/+files/LogAlsaMixer.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
Reading that file it looks like I would be unsure again whether it is a
problem with the interface or other. Though both options seem to
keep the bug reported against rhythmbox. So in doubt I ran apport-
collect and selected other.
--
You received this bug notification because you are a member
Public bug reported:
In Raring, the following link (http://mp3-live.swr3.de/swr3_m.m3u) added
as a radio station will show (paused) in the title as soon as playback
is pressed (32bit and 64bit). This did work at least back in Precise.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package:
Just to confirm that the work-around described in the upstream bug (set
MESA_GL_VERSION_OVERRIDE=1.4 in /etc/environment) works on my GMA950
based netbook).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
After a fresh install, adding any source that is in mp3 encoding, the
dialog that offers to download the plugin will fail to find it. Manually
installing gstreamer1.0-fluendo-mp3 does make mp3 sources play.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rhythmbox
Public bug reported:
Starting to report this against unity, feel free to re-assign against
the correct package (the xserver or llvm-pipe?). With the current Trusty
image (64bit) installed into a VM (KVM or Xen) that uses the default
Cirrus graphics (using virt-managers VNC viewer), I see at least
Public bug reported:
This is on updated 12.04.4 (Precise) 64bit. Not sure exactly since when
but it had been working at some point.
Testcase: Open a pdf document in Firefox with the browser set to
embedded display (so Firefox uses its own viewer). Select print (either
the toolbar in the viewer
Same happens on an updated 14.04 system. So very much related to the
Firefox version.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1319061
Title:
Printing pdf documents from
Verified with a current Trusty iso. Looks to be fixed now.
** Changed in: rhythmbox (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
** Summary changed:
- Duel screen greeter can break 3D acceleration
+ Dual screen greeter can break 3D acceleration
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1292467
Title:
Should we add something to the release notes? Maybe like this:
Some laptops or netbooks with older graphics can experience bad
graphical performance when starting with a high resolution external
monitor attached. The reason for this is that some graphics cards (like
the Intel 945GSE for example)
** Description changed:
When booting with two screens (internal LVDS and VGA), lightdm comes up
in a mode where it displays separate screen content on both displays (so
no mirror mode). These screens seem to be arranged side-by-side
regardless of the fact that (like in my case) the
And oddly its only gnome-term. Xterm is ok.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1298517
Title:
Rendering issues in unity with xserver-modeset
Status in “mesa” package in
I tested today with Xen and cirrus or svga and both show the same bug.
** Attachment added: Screenshot from 2014-04-16 18:37:17.png
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1298517/+attachment/4085585/+files/Screenshot%20from%202014-04-16%2018%3A37%3A17.png
--
You received this
Public bug reported:
Release: Trusty (updated 2013-03-13 11:00 UTC)
Architecture: amd64
Testcase: Start virt-manager and launch a VM guest. While the VNC
graphical terminal is active, the menus do not work (neither top bar,
nor window bar). When switching away from graphical screen (the window
Public bug reported:
The latest updates cause a short-cuts dialogue to appear automatically
on the next login. Unlike the similar box which appears on holding the
super key long, this one has a decoration that looks like a dismissal
button. But it does nothing when clicking to it. It seems the
Public bug reported:
When booting with two screens (internal LVDS and VGA), lightdm comes up
in a mode where it displays separate screen content on both displays (so
no mirror mode). These screens seem to be arranged side-by-side
regardless of the fact that (like in my case) the combined width
** Changed in: lightdm (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1292467
Title:
Lightdm on dual-screens can break 3D acceleration
Alberto is rolling this back into older releases over time. To be fair
it is an annoying issue but not one that is so fatal one would not be
able to recover a system. In the majority of cases this ends up being
just a false system issue notification. Because on kernel update the
parallel builds
Since a simple work-around exists I think the importance can be lowered.
** Summary changed:
- Ubuntu 14.04 LTS, 14.10, 15.04, 15.10 guests do not boot to Unity from
QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts
+ llvmpipe i386 crashes when running on qemu64 cpu
** Description changed:
*** This bug is a duplicate of bug 1448985 ***
https://bugs.launchpad.net/bugs/1448985
Or actually kvm64 as model. I would be duping this bug report against
the one I was looking into before as I think we got more details in that
by now.
** This bug has been marked a duplicate of bug 1448985
Public bug reported:
When converting the example svg file into pdf on i386 there is a bug
which causes the resulting MediaBox element to have an incredibly large
height (looks like this might be an integer overflow). The expected
height is around 423 which the 64bit test run is correctly
** Changed in: ubuntu-fan (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-fan (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-fan (Ubuntu)
Assignee: (unassigned) => Stefan Bader (smb)
--
You received this bug notification because you are
** Changed in: ubuntu-fan (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs
Since we no longer produce i386 images, this would be hard to reproduce.
I could imagine the issue still exists but nobody is or will care.
Essentially a difference of what features are reported via cpuid and
what actually is implemented in the cpu emulation. Will close at least
the Ubuntu side.
test_wpa2_ip4 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv4 ... ok
test_wpa2_ip6 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv6 with only RA ... ok
test_auto_detect_ap (__main__.Hotplug)
new AP is being detected automatically within 30s ... expected failure
test_auto_detect_eth (__main__.Hotplug)
new
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/n/network-manager/20180323_105026_adff0@/log.gz
** Affects: network-manager (Ubuntu)
Importance: Undecided
Above is from apt upgrade log. So both went from 1:52.9.* to 1:60.2*
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1798090
Title:
Xenial update of thunderbird seems to have
I am not convinced this is a ducplicate of bug #1797945. If I read that
report correctly it is about upgraded Thunderbird with the external add-
ons used. I *do* have both lightning and gcal provider from the Ubuntu
archive (repeating from the description):
xul-ext-lightning:amd64
Public bug reported:
After an update this morning (1:52.9.1+build3-0ubuntu0.16.04.1,
1:60.2.1+build1-0ubuntu0.16.04.4) I seem to no longer have access to
google calendars from lightning (both also upgraded)
xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1,
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
I did at least check the dkms install step on a trusty VM with lts-
xenial kernel installed and the nvidia-304 driver installed. That did
succeed. Similar testing for nvidia-340 and -384 but those were done for
xenial VMs.
--
You received this bug notification because you are a member of Desktop
Confirmed to be fixed. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1862169
Title:
rhythmbox crashed with SIGSEGV in build_flavored_key()
Status in grilo-plugins
Public bug reported:
Fresh Focal installation (amd64 deCusktop), after enabling the grilo
framework from the plugins dialog. Currently every attempt to start
rhythmbox again results in an immedate crash.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: rhythmbox 3.4.4-1ubuntu1
** Tags added: champagne
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1862169
Title:
rhythmbox crashed with SIGSEGV in build_flavored_key()
Status in rhythmbox package in
I am adding the block-proposed-bionic before this falls in between
cracks. Right now we ended up in a situation where the nvidia-440
modules were added to the kernel lrm package build but the version used
for the nvidia-390 modules was not updated to the proposed version. The
hope is that having
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1971418
Title:
network-manager/1.36.4-2ubuntu1
mmy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notif
Public bug reported:
This is a scripted bug report about ADT failures while running network-
manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by
the dep8 tests of the tested source or the kernel has yet to be
determined.
Testing failed on:
amd64:
This seems to be related to: "rfkill: make new event layout opt-in" in
the -28 kernel. When I revert that a local reproduction run starts to
work again. However I never got the same error pattern as in the ADT
logs (those seem to get random data back from trying to read the MAC
address). So a
With the revert, the network-manager ADT tests work again.
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/n/network-manager/20220505_053118_fb2db@/log.gz
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug
89 matches
Mail list logo
