Public bug reported:
Upgraded to beta release of 20.4 and Nautilus file manager now is
exhibiting a problem reported in older versions. When clicking on
folders in the left side window the folder will be dragged to where ever
the mouse is moved. The work around is to click once move slightly
I have had this problem for awhile. It got worse when I upgraded from
14.04 to 16.04. I haven't tried all the workarounds above yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579542
Title:
My
** Branch linked: lp:~returntoreptar/curtin/removable-drive-fixes
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1532062
Title:
Drives mistakenly reported as removable
To manage
** Branch linked: lp:~returntoreptar/curtin/removable-drive-fixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532062
Title:
Drives mistakenly reported as removable
To manage notifications about
Sure no problem! I have attached the output of sudo lshw as a file,
since it was a bit long.
** Attachment added: "Output of lshw on system with "removable" drives."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1532062/+attachment/4548195/+files/lshw-output-anakin
--
You received
Sure no problem! I have attached the output of sudo lshw as a file,
since it was a bit long.
** Attachment added: "Output of lshw on system with "removable" drives."
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1532062/+attachment/4548195/+files/lshw-output-anakin
--
You received
Sounds good, here is the output from: lsblk --pairs "--output=$full" /dev/sda
ALIGNMENT="0" DISC-ALN="0" DISC-GRAN="0B" DISC-MAX="0B" DISC-ZERO="0" FSTYPE=""
GROUP="disk" KNAME="sda" LABEL="" LOG-SEC="512" MAJ:MIN="8:0" MIN-IO="512"
MODE="brw-rw" MODEL="main" MOUNTPOINT=""
Sorry I should've known that wouldn't format correctly once I posted, I
have tried to structure the lsblk -l output here:
http://pastebin.com/hQktMbXg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sure, output is below (sorry its a bit hard to structure it in an easy
to read manner here):
lsblk --bytes --pairs --output=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX
,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-
IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY-SEC,RM,RO,ROTA,RQ-
Public bug reported:
I have multiple servers which report their drives are removable, even
though the drives are the main drives in the device (/dev/sda, /dev/sdb,
etc). One of such machines (an IBM system x3650 M1) I have pulled a
report from lsblk and lshw below and included them. These are
Public bug reported:
Upgrade fro 14.04 to 14.10 (32bit) via upgrade-manager -d
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: sysv-rc 2.88dsf-41ubuntu18
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic i686
ApportVersion: 2.14.1-0ubuntu3.3
I've just read through this thread with a view to wether we should
release a related OSSN.
From what I can tell, no fix was ever agreed on, is this likely to
change?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
I've just read through this thread with a view to wether we should
release a related OSSN.
From what I can tell, no fix was ever agreed on, is this likely to
change?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am also seeing this behavior with a logitech HD Webcam C310. I am
running ubuntu 12.10 and am receiving the same initialization failed
error. As soon as I unplugged my webcam I regained the ability to use my
speakers, and that ability remained even after plugging the webcam back
in.
--
You
I installed the latest nvidia driver NVIDIA-Linux-x86_64-304.37, and now
chrome does NOT crash, but thunderbird does.
This bug needs to be moved from chromium-browser category to Xorg
category.
Stack trace looks similar to the one that I provided earlier.
[ 4995.657] (EE) Backtrace:
[
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037208
Title:
Public bug reported:
Regardless of Window Manager used: Gmome, KDE, or Unity, starting up
chromium-browser crashes the WM. When crah occurs,
I get the login prompt. I do not see this issue with firefox or Thunderbird.
[ 20451.022] (**) NVIDIA(0): enabled on all display devices.)
[
** Attachment added: Complete Xorg log file
https://bugs.launchpad.net/bugs/1037208/+attachment/3262547/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037208
Title:
File attachement is from:
dmidecode SysInfo.txt
** Attachment added: Output from dmidecode
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1037208/+attachment/3262548/+files/SysInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
- Regardless of Window Manager used: Gmome, KDE, or Unity, starting up
chromium-browser crashes the WM. When crah occurs,
- I get the login prompt. I do not see this issue with firefox or Thunderbird.
-
+ This Window manager crash occurs in Quantal release (12.10)
+
openssl s_client is typically used for testing / verify certificates -
as it states in the man pages, this should only be used for testing.
There's no use case that I can see for using s_client without at least
one CA certificate. The default behaviour of openssl in fedora is to use
the system
I added the following 2 lines to /etc/security/limits.conf file, and I
have not experienced the 100% CPU saturation issue with dbus_daemon for
17 days:
* softnofile 65536
* hardnofile 65536
--
You received this bug notification because you are a
This appears to be a nVidia driver bug. The work around is to add the
following lines to the xorg.conf file until the driver bug is fixed by
nVidia.
Section Extensions
Option Composite Disable
EndSection
# Xorg.0.log fragments
Please don't close this bug! I have the latest natty packages installed and
the bug is still present.
I am able to reproduce at will by simply resizing a konsole window, or a
xterm window, or a gnome-terminal, or a System Monitor using TwinView.
Please let me know what debug information I can
I am experiencing the same issue. I have the latest KDE/natty installs,
and I believe this 100% CPU saturation was triggered, when I was moving
between folders in Thunderbird 3.10, thunderbird had hung. Yup, sure
enough I just killed thunderbird, and dbus-daemon is no longer at 100%
CPU
Following up on the previous comment of mine. As I was closing down
google-chrome, firefox Tomboy with Thunderbird 3.10 still running, I
noticed the the dbus-daemon utilization had returned to near 0% I don't
think that the other Apps shutting down had anything to do with the the
dbus-daemon
Yes,
I'm not able to run apport-collect at this time, as I am using the machine
at work, and it is not a good time to do this. Below is more information
about the bug that may help in debug. The Xorg.5.log file is attached.
The manifestation of the bug has changed in that, I am able to use KDE
Also seeing this in Alpha 3 kubuntu on three machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726343
Title:
on login to xfce desktop, orca opens a terminal window with an error
message
--
Hi Jeremy,
Thanks for responding to this bug.
I have not had time to get the upstream kernel. I will try
the 2.6.38-5-generic kernel this evening, and see if that works.
Robert
On Tue, Feb 22, 2011 at 8:07 AM, Jeremy Foshee 721...@bugs.launchpad.netwrote:
Hi Robert,
If you could also
Public bug reported:
Ubuntu natty release 11.04 Alpha2; uname -a output:
Linux zac-laptop 2.6.38-4-generic #31-Ubuntu SMP Wed Feb 16 23:44:48 UTC 2011
i686 i686 i386 GNU/Linux
Starting the Cisco VPN client with:
/etc/init.d/vpnclient_init start
will instantly crash the kernel.
The Cisco VPN
** Attachment added: kern.log file showing the stack and boot messages
https://bugs.launchpad.net/bugs/721921/+attachment/1860701/+files/cisco_vpn_crash_kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Upgrading from 10.10, and subsequent apt-get calls exhibit this issue.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: python3 3.2~b2-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
Date: Thu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/705747
Title:
package python3 3.2~b2-2ubuntu1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
Public bug reported:
I have the latest natty Alpha update, and when I open /usr/bin/xterm
with compiz enabled under the classic Ubuntu Desktop, the xterm opens
up with a title bar and a border, and the test area shows my background
un-obscured. I do not see a shell prompt, and typing exit does
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/bugs/701160/+attachment/1790353/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/701160
Title:
/usr/bin/xterm is not
Public bug reported:
This error occurred when running update-manager.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7
Uname: Linux 2.6.37-11-generic i686
NonfreeKernelModules:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/699915
Title:
package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu1 failed to
install/upgrade: bcmwl kernel module failed to build
--
ubuntu-bugs
Public bug reported:
Binary package hint: aptdaemon
Crash occurred when running Update Manager.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: aptdaemon 0.40+bzr529-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7
Uname: Linux 2.6.37-11-generic i686
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/698170
Title:
class 'aptdaemon.lock.LockFailedError':
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: xorg
The bug causes the KDE window manager to crash, and the gdm login screen
to appear after the crash. Running the exact set of applications under
Gnome does NOT crash. Therefore this bug is specific to KDE, and may be
related to using dual displays
** Attachment added: xsession-errors
https://bugs.launchpad.net/bugs/677148/+attachment/1737486/+files/xsession-errors
--
KDE crash occurs randomly within minutes of login
https://bugs.launchpad.net/bugs/677148
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Xorg.0.log.old
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/677148/+attachment/1737511/+files/Xorg.0.log.old
** Summary changed:
- kded4: Fatal IO error: client killed
+ KDE crash occurs randomly within minutes of login
--
KDE crash occurs randomly within
I have removed all of the obex modules, but KDE still crashes at login.
If it matters, I'm running a Win7 64 ultimate VirtualBox 3.2.8 host,
with Meerkat. Meerkat is at the latest release as of 2010.09.18
--
kded crashes at login
https://bugs.launchpad.net/bugs/641297
You received this bug
Please find attached the .xsession-errors file that was rename to
KDE_xsession_errors.
** Attachment added: KDE_xsession-errors
https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/641297/+attachment/1604054/+files/KDE_xsession-errors
--
kded crashes at login
The bug appears to have been fixed after I updated today (2010.09.14).
The most significant update appeared to be the kernel, but I don't know
if this was the root cause.
This bug report can be removed/deleted.
Thanks!
--
KDE freezes when starting gvim
https://bugs.launchpad.net/bugs/620015
With the Beta release of Ubuntu 10.10, the KDE crash behavior has
changed with regard to this bug.
This bug is NOT specific to gvim/vim under Ubuntu 10.10/KDE. It is
easily reproducible as follows:
Start KDE, and run ANY client X application (xterm, konsole, gvim, )
that resides on a Red Hat
The work around here is to start gvim with the --nofork option.
--
KDE freezes when starting gvim
https://bugs.launchpad.net/bugs/620015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: vim
When I start the gvim application under KDE, the screen turns black, and
only the mouse pomter is visivble.
To resolve the issue, I have to ssh in, and sudo /etc/init.d/gdm
restart twice. Killim the gvim process does NOT solve the problem.
I have
No commands needed. Just attach the 2 files that Martin requested.
=Robert
On 4/16/07, Mark Anton [EMAIL PROTECTED] wrote:
I will be happy to, but I won't be able to until tonight when I get home
to
that computer. To get that info for you, I guess I need to type those
commands in the
My previous comments stating that this bug was fixed, were premature.
Apparently a recent update has caused the issue to return.
I have the latest updates, and the original problem has re-appeared.
Additional information, which may require separate bug reports:
1) my Gigabit PCMCIA card, a
This issue was apparently fixed through one of the feisty updates. I
have not had any Ethernet configuration at startup up issues for over a
week now.
I consider this bug Fixed. Thanks Ubuntu Team!
--
Ethernet interface not configured at boot time
https://bugs.launchpad.net/bugs/94095
You
I do not see this problem if fsck runs at boot time. This leads me to
believe that this is a timing problem at boot time. I'm aware that
changes were made to improve boot times in feisty. Since I never saw
this problem in edgy, suspect the boot optimization(s) in feisty is
causing the problem.
I
Public bug reported:
I recently did an upgrade from Ubuntu 6.10 to Ubuntu 7.04, and after booting or
rebooting, my network
is not configured. With 6.10, I had no issues with Wired or Wireless interfaces.
For this bug report, only the wired interface is installed in my DELL
Inspiron 5000e.
53 matches
Mail list logo
