Public bug reported:
I run Ubuntu on a laptop. Recently I have experienced crashes of the
desktop after opening up the laptop and mousing over the Launcher. I
have the Launcher set to auto hide. The Launcher is longer then the
window so normally scrolls when mouse get to the bottom of the
Public bug reported:
For the past week or so, I've been getting 2 or 3 X server crashes a day
on my computer. After the crash, I normally get an apport popup and
walk through the dialogs in an attempt to report the crash. Based on
what I've read, the 12.04 release process is supposed to report
Public bug reported:
I upgraded my system to 12.04 today. After reboot and login, my desktop
initially displayed then a slow black screen wash happened from top to
bottom. I waited several seconds and eventually the desktop came back
with no panel or launcher. I received a crash popup and
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995239
Title:
compiz crashed with SIGSEGV in _wordcopy_fwd_aligned()
To manage notifications about this bug go to:
I couldn't disagree more with this bug. The session commands (logout,
restart, shutdown, etc) definitively belong in the application lens.
The whole point of the lens is to provide a single point of entry to the
system. You hit super, start typing, and hit enter when you choice
becomes the first
The 3.2.0-22-generic kernel works for me as well. No Oops on boot and
Suspend/Resume work properly. Bug seems to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/970286
Title:
Kernel Oops
I'm not able to perform the bisect. I restarted from scratch and tried
to build the most recent kernel before attempting any bisect operation.
The build is running on my computer, but it is going quite slow. I let
it run for 1.5 hours the first night before I had to stop it to
shutdown. I then
Andrew, I tried the kernel you requested ( 3.2.14-030214-generic). I
do not receive any Oops on boot and Suspend/Resume work properly, so
that version is working for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I wasn't sure which version to check. I used the link to the most
current version in the Mainline Kernel Mapping section. The resulting
version is:
uname -a
Linux dpwegener-laptop 3.4.0-999-generic #201204010405 SMP Sun Apr 1 08:12:57
UTC 2012 i686 i686 i386 GNU/Linux
There was no Oops on
+ Does this oops impact using the computer in anyway?
It prevents the computer from successfully entering Suspend mode. Attempting
to enter Suspend mode locks up the computer and the computer must be hard
powered off. (see comment #4)
+ Did you test this in a prior release and did it oops?
The
I can give it a try. I have built kernels in the past but that was many
years ago. I'm running on a netbook, so I don't have a great deal of
CPU power so I can't guarantee anything or give an estimate on when I
can complete the process.
--
You received this bug notification because you are a
I'm starting to get lost. I'm not sure I'm doing the bisect correctly.
It appears to have picked a version outside of the versions I'm trying
to bisect. I'm also getting a build error when trying to build the
kernel that bisect picked.
check-config:
*** This bug is a duplicate of bug 946674 ***
https://bugs.launchpad.net/bugs/946674
This issue has been marked as a duplicate of a private bug. That
prevents me from looking at the bug to confirm it is a duplicate or to
see any comments/status of the bug to determine when it might be fixed
Public bug reported:
With the latest Precice kernel, I'm receiving an oops on boot in the
asus_wmi module. Here are details from dmesg:
[ 19.317421] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 19.317608] IP: [f8176f09] asus_new_rfkill+0x99/0xf0 [asus_wmi]
[
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/970286
Title:
Kernel oops:BUG: unable to handle kernel NULL pointer dereference at
(null) module asus_wmi
To manage notifications about this bug go
Here are the dmesg lines immediately before the oops showing additional
logging from the asus_wmi module:
[ 19.306175] asus_wmi: ASUS WMI generic driver loaded
[ 19.307860] asus_wmi: Initialization: 0x0
[ 19.307982] asus_wmi: BIOS WMI version: 0.6
[ 19.308992] asus_wmi: SFUN value: 0x0
[
lspci output
** Attachment added: lspci-vvnn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/970286/+attachment/2977627/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have also noticed that suspend no longer works on netbook where this
error occurs. When invoking suspend, screen blanks out, but system
doesn't seem to completely suspend. Fan continues to run. System won't
come out of suspend. I have to hard power off system.
--
You received this bug
Booting up in
uname -a
Linux dpwegener-laptop 3.2.0-20-generic #33-Ubuntu SMP Tue Mar 27 16:45:08 UTC
2012 i686 i686 i386 GNU/Linux
doesn't have the bug and allows suspend/resume to work correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In my case, I can get the Dash to come once using Super if I wait for
all processing to settle down after login. But I can't get Super to
bring up the Dash after that. In fact, Super won't close the Dash. I
have to use ESC to close the Dash. I'm running System Load Indicator in
the panel and I
Based on comment #36 and textures, I notice that my .xsession-errors
file contains some messages regarding compiz having problems binding a
texture:
compiz (decor) - Warn: failed to bind pixmap to texture
compiz (decor) - Warn: failed to bind pixmap to texture
compiz (decor) - Warn: failed to
Additional update. Tonight I installed new updates and Unity
5.6.0-0ubuntu3 was installed. Now, the first time I press/release the
Super key after login, the Dash is brought up. Subsequent attempts to
bring up the Dash using the Super key are un-successful. The Dash is
only brought up on the
I've tried tapping at various different speeds. Hit and immediately
release all the way to hit till Launcher is displayed and release. It
doesn't matter, the Dash doesn't show after first time following a
login.
Super-a brings up the Application lens, Super-f brings up the files
lens, Super-m
Public bug reported:
With the latest Unity version, the Super key no longer brings up the
Dash. If you hold the Super key down long enough, the launcher is
displayed, but still no Dash.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.6.0-0ubuntu1
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953634
Title:
Super key doesn't bring up Dash
To manage notifications about this bug go to:
Public bug reported:
After the latest Unity upgrade, the mouse isn't able to bring up the
launcher when moved to the left edge. I have Auto Hide set for the
launcher. No matter how hard I push the mouse against the left edge of
the screen, the launcher does not display. The only way to get the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953639
Title:
Mouse won't bring up launcher when auto hidden
To manage notifications about this bug go to:
No, it doesn't appear when releasing the Super key. It doesn't matter
how long I hold the key down. I've tried quickly tapping as well as
holding it down till the Launcher appears and then release the key. It
never shows.
I've found the launcher Super-Tab sequence that goes through the
** Changed in: unity (Ubuntu)
Status: Opinion = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928826
Title:
Autohide broken (always hides)
To manage notifications about this bug
I'm very disappointed that this feature has been redacted by Mr.
Shuttleworth. I decided to accept Unity on my netbook specifically
because of this feature.
I'm tired of Mr. Shuttleworth constantly trying to make my desktop
look/behave like his. These constant disruptions to the desktop
Public bug reported:
Version 5.2.0-0ubuntu3 broke the auto hide behavior of the launcher.
With auto hide turned on, the launcher will only appear when pushing
the mouse against the left edge. It is no longer displayed if there are
no windows in the launcher area of the screen. If auto hide is
Public bug reported:
After one of the recent Precise updates, I have noticed that the first
character in the Unity panel is distorted. It almost looks like the
character is being partially offset by a couple of pixels. A similar
issue shows up in the popups on icons in the Unity launcher when
** Attachment added: Left character distorted. The U in Ubuntu shows a
distortion on the left.
https://bugs.launchpad.net/bugs/927441/+attachment/2718309/+files/Screenshot%20at%202012-02-05%2022%3A10%3A41.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Distortion in Launcher popup. Notice the G in Google.
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/927441/+attachment/2718340/+files/Screenshot%20at%202012-02-05%2022%3A11%3A40.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Window close icon with distortion. Notice the left edge
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/927441/+attachment/2718341/+files/Screenshot%20at%202012-02-05%2022%3A16%3A12.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I am experiencing the problem after upgrading from 3.2.0-11 to 3.2.0-12.
Booting back into the 3.2.0-11 kernel fixes the problem so it appears to
be an issue introduced in 3.2.0-12.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested the kernel you referenced in comment #30. The Wireless card is
working with this kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/923512
Title:
ath9k wireless stopped working after
Public bug reported:
Tonight I updated my 12.04 install with the latest kernel image (linux-
image-3.2.0-12-generic). After a reboot, my network card couldn't
connect to my wireless router. Tried rebooting a couple of times
without success. Removed network definition and tried re-adding but
** Attachment added: lspci output for the network card
https://bugs.launchpad.net/bugs/923605/+attachment/2700679/+files/lspci.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/923605
Title:
The package is provided by Lexmark for their printers. It is licensed
by them and I'm not sure I'm allowed to post it here. The version I had
installed no longer appears to be available on their support site.
I could probably send the file to you directly, but I don't think I'm
allowed to post
Here is the control file from the package with the description
** Attachment added: Control file with blank line in description
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/916799/+attachment/2677491/+files/control
--
You received this bug notification because you are a member of
Last 50 lines of term.log file from dist-upgrade when failure occurred.
Failure is right after dpkg was upgraded from 1.16.0.3ubuntu5 to
1.16.1.2ubuntu5
** Attachment added: distupgrade-error.txt
Public bug reported:
While attempting to upgrade from 11.10 to 12.04 the version of dpkg used
by Ubuntu was upgraded. The new version was unable to parse my
/var/lib/dpkg/status and /var/lib/dpkg/available files. Under 11.10, I
had installed a package from Lexmark for a printer driver that had
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916799
Title:
Blank line in previously installed packagedescription causes 12.04
upgrade failurt
To manage notifications about this bug go to:
Its unfortunate that Canonical hasn't fixed this problem yet. I'm
unable to purchase software in the software center because of this bug.
Canonical is giving up revenue for themselves as well as the developers
who are trying to make some money off of their work.
--
You received this bug
I'm very disappointed that the Ubuntu developers allowed this release to
proceed with such a basic requirement missing. Not allowing users to
customize their desktop is unacceptable. Because of this regression, I
will not be upgrading to the 11.10. In a number of the related bugs, a
claim is
Public bug reported:
The Oneiric beta release has the ability to select different themes.
However, this version of Ubuntu no longer has the ability to customize
the theme. Natty had the ability to select things like the
background/foreground color of tool tips, windows, etc. It is important
to
Multi-finger now detected on Asus 1005PE with the latest patch.
Synaptics Capabilities (292): 1, 0, 1, 1, 1
synclient -m reporting multiple fingers
7.001 3396 3521 84 2 5 0 0 0 0 0 0 0 0 0 0
8.002 3393 3503 84 2 5 0 0 0 0 0 0 0 0 0 0
9.002
I am using Eclipse on a netbook and would like to use the indicator
appmenu so save screen real estate. When running Lucid, it was possible
to get menus to display by pressing Alt-F for file, etc. Once
displayed, the menu items would remain until Eclipse was restarted.
Under Maverick, it isn't
It does look to be a FaceBook bug. 11:53 PM CDT and it is working
again. FaceBook is returning the comment_list as an array again.
--
facebook is always a day or two OLD
https://bugs.launchpad.net/bugs/572011
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Problem appears to be that the facebook.py is expecting comments to be
returned as a list and they are actually being returned as a dictionary.
I have been able to fix the problem by changing the comment parsing loop
to use values() for the dictionary. Here is the original code:
if
The comment_list element of comments now appears to be a dictionary
instead of a list. I have provided a patch for bug #572011
(https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/572011) that
fixes the problem.
--
Gwibber-service Failing to update facebook
I found a post on the Facebook developer forum where someone reported
that the comment_list had changed from the documented array to a
dictionary. May need to confirm with Facebook whether they intended to
make this change, or if it is a bug.
Attaching error output for gwibber-service -d -o
** Attachment added: stderr for gwibber-service -d -o
http://launchpadlibrarian.net/49177388/gwibber.err
--
facebook is always a day or two OLD
https://bugs.launchpad.net/bugs/572011
You received this bug notification because you are a member
Public bug reported:
Binary package hint: ubuntuone-client
Since setting up the ubuntuone client the first time on a Lucid Beta
install, I'm now unable to connect to the Ubuntu One servers. When ever
I try to connect, the ubuntu-preferences app shows Synchronization in
progress, but the
** Attachment added: Here is the oauth-login.log file
http://launchpadlibrarian.net/43329007/oauth-login.log
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43328187/Dependencies.txt
** Attachment added: UbuntuOneClientPackages.txt
I'm receiving the same error when attempting an install using the Lucid
Netbook Live Beta iso image from a USB drive.
--
Installer crash (Lucid beta 1 DVD installer)
https://bugs.launchpad.net/bugs/549879
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Xorg log from attempt with blacklist=vga16fb
http://launchpadlibrarian.net/41669856/Xorg.0.log.old
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Added blacklist=vga16fb as a boot option. This didn't help. System
still behaves the same. Screen becomes corrupted instead of showing the
desktop. I am attaching the dmesg and X org log file from the attempt.
** Attachment added: dmesg file from attempt with blacklist=vga16gb as boot
option
Adding blacklist=vga16fb nouveau.noaccel=1 works. Desktop is up and
running. I'm using FireFox now to update the comment.
The transition from the splash (plymouth? Ubuntu with the dots
underneath) to desktop wasn't an issue. Screen went black for a couple
of seconds and then desktop appeared.
** Attachment added: Xorg log for blacklist=vga16fb nouveau.noaccel=1
http://launchpadlibrarian.net/41682024/Xorg.0.log
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here are the requested log files. Note that these files were only able
to be collected after a successful boot to the desktop. The failed boot
did not provide any opportunity to collect the files. I've included
both Xorg.0.log and Xorg.0.log.old.
** Attachment added: Xorg log file
** Attachment added: Xorg log from failed startup
http://launchpadlibrarian.net/41524692/Xorg.0.log.old
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: dmesg of successful startup
http://launchpadlibrarian.net/41524803/dmesg
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: dmesg of failed startup
http://launchpadlibrarian.net/41524854/dmesg.0
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: output of lspci -vvnn command after successful startup
http://launchpadlibrarian.net/41524982/lspci.out
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: xorg
I'm testing out the Lucid beta by booting from a USB drive. Initial
splash screen displays progress. When boot up sequence switches to the
X display, the screen becomes corrupted. There are portions of the
screen from the last time the system
Additional info
Adding nomodeset as a boot option allows X to startup and I'm able to test out
the beta.
--
Screen corruption on startup
https://bugs.launchpad.net/bugs/542950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I started experiencing this today after applying the latest xserver
updates for Karmic (1:7.4+3ubuntu10). If you cancel out of the low
graphic mode dialog quickly enough, kdm will restart and run normally.
The problem results in the following messages in the kdm.log file:
Fatal server error:
I started experiencing something similar today after enabling Karmic
proposed repositories and performing an upgrade. The upgrade pulled in
updates for xserver. The updates seem to be related to the failsafe
server. Reverting to the Karmic released versions of the xserver
packages resolves the
I think I'm starting to figure this package thing out a little. I've
created a debdiff for the fix. I also have an updated
02_microblog_default_configuration.diff. I'm not sure whether one or
both are needed to address the fix, so I'll attach both.
** Attachment added: debdiff after fix
** Attachment added: Updated quilt patch file including fix.
http://launchpadlibrarian.net/34508081/kubuntu_02_microblog_default_configuration.diff
--
KDE Microblogs plasmoid does not show friend timelines nor public timeline
https://bugs.launchpad.net/bugs/414572
You received this bug
It would really be nice for this bug to be fixed prior to the release of
Karmic. Kubuntu Karmic is being advertised as social from the start.
The twitter support is a integral part of Kubuntu. I've posted the code
that fixes the problem a couple of times. Can someone give me some
advice on how
** Changed in: kdeplasma-addons (Ubuntu Karmic)
Status: Fix Released = Incomplete
--
KDE Microblogs plasmoid does not show friend timelines nor public timeline
https://bugs.launchpad.net/bugs/414572
You received this bug notification because you are a member of Kubuntu
Bugs, which is
The fix does not solve the problem of missing friend tweets. The wrong query
string is still being used in the downloadHistory method in microblog.cpp. The
code should look something like this.
if (m_password.isEmpty()) {
query = Qstring(NoAuth:%...@2);
} else if (m_includeFriends) {
Here is the output for devkit-disks-part-id:
sudo /lib/udev/devkit-disks-part-id /dev/block/8:21
Entering MS-DOS parser (offset=0, size=120034123776)
MSDOS_MAGIC found
looking at part 0 (offset 32256, size 254951424, type 0x83)
new part entry
looking at part 1 (offset 254983680, size 119776527360,
** Attachment added: udevadm output
http://launchpadlibrarian.net/33467015/udev.txt
--
devkit-disks-part-id crashed with SIGSEGV in v4l1_open()
https://bugs.launchpad.net/bugs/441088
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: devkits-disks output
http://launchpadlibrarian.net/33466954/dkd.txt
--
devkit-disks-part-id crashed with SIGSEGV in v4l1_open()
https://bugs.launchpad.net/bugs/441088
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ouput to commands attached. During the upgrade process from Jaunty to
Karmic, I couldn't get my system to boot and performed a clean install
of Karmic. This completely changed my partitions defined/used on my
hard drives. This output is based on the current configuration of the
hardisks. I
Additional information. It seems to have something to do with the
kubuntu_02_microblog_default_configuration.diff. This diff appears in revision
29 of the lp:~kubuntu-members/kdeplasma-addons/ubuntu branch. The following
code in the downloadHistory method was changed:
+-if
After performing an apt-get -compile on the source package, the
resulting plasma-widgets-addons deb package contains a
plasma_applets_microblog.so that doesn't work. The packaged library has
been stripped as part of the package build process. However, the shared
library built in the output
This looks to be a problem with the binary build. I tried to debug this
problem using gdb. The source code for the package doesn't match the
plasma_applet_microblog.so and plasma_engine_microblog.so from the
binary packages. Manually building from source produces libraries that
work.
--
KDE
*** This bug is a duplicate of bug 388923 ***
https://bugs.launchpad.net/bugs/388923
The duplicate status is wrong. This particular bug appears to be a
duplicate of 385478 or 78478.
--
package linux-image-2.6.28-13-generic 2.6.28-13.45 failed to install/upgrade:
subprocess
Details from the Synaptic installation include:
The provided postinst hook script [/sbin/update-grub] could not be run.
I have upgraded my system to use Grub 2.x
--
package linux-image-2.6.28-13-generic 2.6.28-13.45 failed to install/upgrade:
subprocess post-installation script returned error
Creating a symlink from /sbin/update-grub to /usr/sbin/update-grub
allows the installation to complete.
--
package linux-image-2.6.28-13-generic 2.6.28-13.45 failed to install/upgrade:
subprocess post-installation script returned error exit status 2
https://bugs.launchpad.net/bugs/395256
You
85 matches
Mail list logo
