Hi Paul
Sorry for a late response.
I'm sure the bug can be recorded as closed.
/*Alaric*
using Ubuntu 16.04.4 LTS/
On 24/07/18 11:13, Paul White wrote:
> Alaric, we are sorry that we do not always have the capacity to review
> all reported bugs in a timely manner. You reported th
Hi Paul
I can't even no remember what the problem was, but given that I was
using 14.04 LTS at the time, now on 16.04 LTS and about to migrate to
18.04 LTS, then I'm happy to call it closed.
/*Alaric*
using Ubuntu 16.04.4 LTS/
On 23/07/18 12:49, Paul White wrote:
> We are sor
It was an automated report from the system. The PC will not shut down
and has to be 'hard-crashed' to switch off. On reboot it asked me to
submit this bug report - along with several others - so I did.
*Alaric Cundy*
alaric.cu...@btinternet.com or ala...@mountnessingbridgeclub.o
This particular desktop PC refuses to shut down (or to restart). Not
even Alt+SysReq + etc works. Once, on restart after crashing out by
holding down the Power button, it invited me to submit a whole host of
bug reports that appeared to be linked to the failure to shut down - so
I submitted them!
This particular desktop PC refuses to shut down (or to restart). Not
even Alt+SysReq + etc works. Once, on restart after crashing out by
holding down the Power button, it invited me to submit a whole host of
bug reports that appeared to be linked to the failure to shut down - so
I submitted them!
This particular desktop PC refuses to shut down (or to restart). Not
even Alt+SysReq + etc works. Once, on restart after crashing out by
holding down the Power button, it invited me to submit a whole host of
bug reports that appeared to be linked to the failure to shut down - so
I submitted them!
Public bug reported:
PC will not shut down or restart 14.04
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: dkms 2.2.0.3-1.1ubuntu5.14.04
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubunt
Public bug reported:
PC does not shut down or restart 14.04
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: dkms 2.2.0.3-1.1ubuntu5.14.04
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubunt
Public bug reported:
PC will not shut down or restart 14.04
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: coreutils 8.21-1ubuntu5.1
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.7
Public bug reported:
PC will not shut down or restart 14.04
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cpp-4.8 4.8.2-19ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.7
A
Public bug reported:
PC will not shut down or restart 14.04
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gcc-4.8 4.8.2-19ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.7
A
Public bug reported:
PC will not shut down or restart 14.04
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: dash 0.5.7-4ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.7
Archi
Public bug reported:
PC will not shut down or restart
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: binutils 2.24-5ubuntu3.1
ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.7
Archit
Public bug reported:
desktop machine fails to shut down
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pm-utils 1.4.1-13ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.7
Ar
Public bug reported:
Could use a guide to help ensure all partitions are assigned for uefi to
boot properly. From what I've seen online I have created a proper BIOS
boot partition, but failed to create an EFI partition.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity 2.15.26
ProcV
Public bug reported:
Error message keeps popping up spontaneously
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: ndiswrapper-dkms 1.57-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-28.48-generic 3.5.7.9
Uname: Linux 3.5.0-28-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
I am not in control of these things - but I would hope so!
I keep getting messages to say that it is a duplicate of some other bug
that has already been reported, so it sounds as though it is being taken
seriously.
Alaric Cundy (alaric.cu...@btinternet.com or
ala
*** This bug is a duplicate of bug 1101167 ***
https://bugs.launchpad.net/bugs/1101167
Public bug reported:
I was applying a normal routine system upgrade via 'software updater'
when this happened
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: ndiswrapper-dkms 1.57-1ubuntu1
ProcVe
*** This bug is a duplicate of bug 1090675 ***
https://bugs.launchpad.net/bugs/1090675
Public bug reported:
Appeared as part of a routine software update on 19/12/2012
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: ndiswrapper-dkms 1.57-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-
*** This bug is a duplicate of bug 856205 ***
https://bugs.launchpad.net/bugs/856205
I can confirm this bug. I realize it may not be high priority or a
"blocking" issue, but this bug is severely aggravating. I've had to
replace the dashboard as my default alt+f2 option. The reason power
use
Unfortunately I got it working through apt-get before receiving this
message. I'm convinced that most of the problems were caused by the fact
that the 3.0.0 kernel sources and headers were not a dependency of the fglrx
or fglrx-updates packages. After installing them the apt-get commands you
sugg
The installation of the post-release updates through jockey failed. I've
attached the new log. Attempting to revert to the original package.
Jockey claimed to revert to the original driver successfully, but I was
unable to test the jockey based installation due (I believe) to some
unreleated pro
After installing linux-source-3.0.0 and linux-headers-3.0.0-12-generic, the
apt-get completed successfully and jockey is currently displaying a green
"activated" icon besides the (non post-update) fglrx driver. I haven't
tried restarting to test it yet because I'm going to install the
post-release
I'm not sure if this is because of my chroot environment or not, but while
attempting to reinstall fglrx with the command you suggested, I get several
hundred lines of this:
FATAL: Could not load /lib/modules/2.6.35-30-generic/modules.dep: No such
file or directory
Followed immediately by
Loadin
Also, Let me add that the entire build folder appears to be empty.
alaric@Hercules:/media/sdb7/var/lib/dkms/fglrx-updates/8.881/build$ ls -a
. ..
On Wed, Oct 12, 2011 at 9:29 AM, jro...@gmail.com wrote:
> Hey,
>
> Sorry for the late response. I was on an extended vacation. I w
vided on Sunday.
Unfortunately, it didn't find anything. I can only assume that the files
were cleared when I shut down the computer? What do I need to do to
correctly generate that log file?
alaric@Hercules:/media$ sudo mount /dev/sdb7 sdb7
alaric@Hercules:/media$ cd sdb7
alaric@Hercules:/medi
** Attachment added: "My Jockey.log"
https://bugs.launchpad.net/bugs/871344/+attachment/2532760/+files/jockey.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871344
Title:
Jockey cannot install
card is an AMD Radeon 6670 HD.
01:00.0 VGA compatible controller: ATI Technologies Inc Turks XT [AMD
Radeon HD 6600 Series]
Regards,
Alaric
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu10
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12
Sorry, I'm no longer certain this is the right location for this post,
as I am utilizing the xorg-edgers repository.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737644
Title:
xserver-xorg-video-ra
It appears that this problem now affects the package "xserver-xorg-
video-radeonhd". Could you please attempt to install the same patch on
this package so that I can test my Radeon 6670HD?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
am first put into maintenance, but when I close
maintenance mode, it crashes. Here's relevant terminal output.
ala...@alaric-laptop:~$ lsb_release -rd
Description:Ubuntu maverick (development branch)
Release:10.10
ala...@alaric-laptop:~$ apt-cache policy mesa-utils
mesa-
Confirmed fixed in Lucid.
--
Connect to Hidden...select Saved Secure Connection; Connect not possible
https://bugs.launchpad.net/bugs/446394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
I'm running Ubuntu 10.04 beta and this appears to be affecting a clean
install. When I attempt to add a printer it prompts me for the root
password that does not exist. I can also confirm that running gksudo
rectifies the problem. For this reason, I feel system-config-printer
(mine is version 1.
Confirmed. Fix is in the repositories. Thanks for your quick work guys
:)
On Wed, Mar 31, 2010 at 6:17 AM, Mark wrote:
> Ran into this bug, updated packages, and can now launch Appearance
> Preferences.
> Thanks for the quick fix!
>
> --
> gnome-appearance-properties crashed with SIGSEGV in
>
Confirmed that using the appearance manager as root does not crash.
Will not allow us to change settings for the primary user account though
and therefore most settings are not changeable for the average user.
--
gnome-appearance-properties crashed with SIGSEGV in
g_cclosure_marshal_VOID__VOID()
This problem is incredibly aggravating for average users. When is this fix
going to hit the common repositories? I'm running a few fully upgraded
karmic machines and all of them are experiencing these problems stemming
from a release of network-manager from October (the newest available in the
re
Still an issue, fully upgraded.
--
'Keep Aligned' option always resets to 'true' after desktop reload
https://bugs.launchpad.net/bugs/399974
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Here's the attachment
** Attachment added: "wireless-dialog.c"
http://launchpadlibrarian.net/34379795/wireless-dialog.c
--
[karmic] Connect-to-Hidden... doesn't work for saved connections
https://bugs.launchpad.net/bugs/449287
You received this bug notification because you are a member of Ubu
For more experienced users desperate for a quick fix, exchanging this
attachment for the default file within the network-manager-gnome source
file /src/wireless-dialog.c will allow you to edit the hidden network
settings. Please keep in mind that (as you probably noticed) I have no
affiliation wit
Same here. Unable to connect to hidden wireless networks.
Device Information
Inspiron 1545
Network Card BCM4312 802.11b/g [14e4:4315]
Network Information
Security: WPA/WPA2 - Enterprise
Authentication: PEAP
Anonymous Identity: None
CA Certificate: Thawte_Premium_Server_CA.pem
Peap Version: Autom
B43 disappears because it is uninstalled by Jockey when switching to
STA. It can be reinstalled and loaded, but will not work with network
manager, and is not a bug in Jockey. STA requires a restart to update
network-manager. Inspiron 1545 users, use STA, although it does still
have a few bugs o
Run apt-cache show jockey-common and post the results here. The update
just hit my repository. Ran the update process about 6 hours ago and
there was nothing, then a minute ago it updated jockey to the version
listed above. I've also got a Inspiron 1545 and I'm about to test
whether this will fi
42 matches
Mail list logo