P1.70
04/21/2015
As I was saying before, this only happened since updating to 15.04 from 14.10.
It has more to do with my television not specifying a resolution that is
compatible with modeset. For example, it may say that it's 720p tops instead
of 1280 x 720 but I'm not sure. I do know that
** Changed in: xorg (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448574
Title:
Have to use nomodeset for install (new problem for new distro)
To ma
Public bug reported:
I haven't had this problem since around version 12.04 or before (can't recall
which one precisely) where, during installation, I have to use nomodeset in
order to get my Samsung television to stop turning on and off repeatedly during
modeset problems. I would like to menti
Relax, the bug is only sporadic and the slowdown on boot may be overcome with
inode updates and defrags which may or may not occur automatically with the
BTRFS file system. While it may happen with one system, it may not with
another. While it may happen at one time with a system, it may not a
I concur!
Though, I think the problem is more-so that there is a race in the first place
instead of a march which is what I'm hoping we can fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969489
T
Seven months have passed with no fix in place. I have removed the
assigned user so that another may step-up in their place to resolve the
issue.
** Changed in: lightdm (Ubuntu)
Assignee: Dalmer Vieira (dalmer-vieira) => (unassigned)
--
You received this bug notification because you are a m
*** This bug is a duplicate of bug 969489 ***
https://bugs.launchpad.net/bugs/969489
** This bug has been marked a duplicate of bug 969489
lightdm tries (and fails) to start too early?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
We need to apply a fix in the startup which performs a while statement to check
if dependencies are not yet loaded. This will mitigate against problems with
varying sleep times which may or may not work for users.
Alternatively, having a list of dependencies to run inline may be a better
option
This bug is a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/969489
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410
This bug has not been resolved as of yet and has affected Ubuntu distributions
ever since, at most, 12.10. Not sure before that.
Though this p
Sorry, I did get a little confused over the sectors thing. The 63rd LBA sector
is the starting point for the 0MB boundary of partitions usually. I wasn't
thinking straight. I'm used to using the MB settings for partitioning instead.
Anyhow, the normal Grub2 install for any partition that's n
Sorry, I was talking about an MBR system, not a UEFI. Core.img is too
large to fit into the first 64 sectors (starting from 0). And, so, the
next best place to start would be the 127 - 128 boundary. Also known as
the 2MB boundary.
--
You received this bug notification because you are a member
Actually, Phillip, BtrFS requires 2MB for a Grub2 installation. So, while you
are correct that it does start at 1MB, the partitioner does have an error in
not including that the rules for BtrFS are different. The normal 1MB is a part
of the normal MBR rules. Since Grub2 requires some extra in
There is no need to reformat with Ext4. If you wish to use BtrFS for the Boot
partition, it's recommended. Just tell the partitioner to start at the 1MB
boundary instead of the first sector. To reiterate, you need an empty 1MB at
the beginning of your drive to write to. I would call this an
I've come to find that it's because Ubuntu doesn't include the files and
work-around necessary to allow installation to btrfs filesystem. I
recommend including a check/prompt to ensure that 1 MB exists at the
beginning of the drive to allow the use of btrfs as the root file system
as not having it
Public bug reported:
All information pertaining to this error has been uploaded
automatically.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.12.16
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu3
Architectur
Well gdm it, if they repeated the process they would have exactly the info they
need. It crashes on more than one system if you try to switch to guest while
logged into another user and then back. It does it ever so often, so if it
fails once, try it again. That should be enough info.
Other t
Eh, I'm not sure. But I'll go with it.
** Package changed: ubuntu => xserver-xorg-driver-ati
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032900
Title:
Display crash on user change
To manage no
Public bug reported:
After being logged in as a user, if another user decides to attempt to change
user as guest instead of entering a password, the display will sometimes go
black and fail to respond resulting in no signal to the monitor. The only
known way of fixing the problem is by restart
Public bug reported:
GDM has crashed on me twice using the same system. The first time, my sister
had changed the user while my screen had locked itself to utilize the guest
account due to her not knowing my password. It crashed once I logged out of
the guest account and I couldn't get startx
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573202/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/754284
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573212/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573211/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/754284
Tit
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573210/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/754284
Title
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573209/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/754284
Title
apport information
** Attachment added: "PulseSources.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573208/+files/PulseSources.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "PulseSinks.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573207/+files/PulseSinks.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/7542
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573206/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/75
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573205/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573204/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/75
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573203/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573201/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/754284
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573200/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/754284
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573199/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "Card1.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573198/+files/Card1.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.lau
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573197/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.lau
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573196/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launc
apport information
** Attachment added: "ArecordDevices.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573194/+files/ArecordDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/b
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573195/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/754284
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573193/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/754284/+attachment/2573192/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/75
apport information
** Tags added: oneiric
** Description changed:
This problem was fixed in 10.10 with an update. While not using nomodeset,
sometime incorrect commands would be sent to the display causing errors such as
entering low-power mode, flickering or simply going blank. In particu
Problem still exists.
** Changed in: linux (Ubuntu)
Status: Expired => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/754284
Title:
Modeset code fixed with update in 10.10
Oops, forgot to attach...
** Attachment added: "The results of utilizing mdadm"
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/666577/+attachment/2098780/+files/mdadm%20results.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
As you wish. Attached are the files Examine, Detail and even Detail-
Platform so you know specifically what I'm working with. Unfortunately,
since my main RAID 5 array became corrupted, I decided it was time to
consolidate both arrays into one so I won't be able to verify any fix of
the code that
So it hasn't been fixed and it still allows issuing of low-level
commands to monitors which can eventually render them inoperable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/754284
Title:
Modeset
apport information
** Tags added: apport-collected natty ubuntu
** Description changed:
This problem was fixed in 10.10 with an update. While not using nomodeset,
sometime incorrect commands would be sent to the display causing errors such as
entering low-power mode, flickering or simply go
Honestly, I don't know why or how it worked, but it did. I used the --examine
--scan to see if it would even recognize the array. Once I realized it
recognized it, I told it to scan and run the array. It told me there were no
super blocks, but it loaded it right up and I was able to mount my
I've done some investigating on my second array by poking around with mdadm.
It seems that there was a slight offset with the partition allignment that
COULD have been the problem. It was offset by 33280 bytes. mdadm seems to
allow me to access both of the arrays correctly though. So I can't
I believe the problem we're going to have with fixing this is
determining how many disks were in the array to begin with. It requires
reading specific data from the arrays descriptors and matching it to the
drives listed. I would also recommend getting sector specific on the
fix so that drives sh
Have you attempted to reinstall dmraid to verify that it is not present
in the package or try running dmraid from the terminal? I'm having a
similar issue, but mine is with dmraid installed and not recognizing my
array right off the liveCD then freezing when it doesn't know how to
handle it.
--
dm-raid45 doesn't work correctly in 11.04 with the default module. It
will not load my RAID arrays. I believe it may have difficulty
distinguishing between the two RAID 5 arrays which both share 3 drives.
As for the one I attempted to compile, that was back in 10.10 when the
module still didn't
This bug also affects Ubuntu 11.04 currently in Beta production.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666577
Title:
dmraid hangs trying to start ICH9R RAID 5
--
ubuntu-bugs mailing list
u
I would love to add it to the other bug and I tried, but I can't seem to
find any setting that says "Also affects 11.04". So I had little choice
but to create this new bug report for 11.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Excuse me, but why have you changed the security vulnerability status to
no when this bug allows direct, unauthorized access to the internal
hardware settings of the monitor enough to literally power it on and off
with commands through HDMI? Direct hardware access by anyone but the
administrator s
Sure, I'll give you the steps from both installed and CD-based.
CD:
Step 1: Turn on computer
Step 2: Insert Ubuntu Live CD or DVD
Step 3: Wait for menu
Step 4: Press enter to use Live CD or DVD based Ubuntu
Step 5: Observe as your screen goes blank, flickers or begins turning on and
off depe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/754274
Title:
dmraid fails to start when 3 drives share 2 RAID-5 arrays
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
Public bug reported:
Binary package hint: dmraid
dmraid absolutely refuses to work at start when I have 3 hard drives sharing 2
RAID-5 arrays on my Intel ICH9R chipset. This error also occurs in 10.10 and
10.04. Phillip Susi had been working with me on this problem, but we haven't
come to a
What I was attempting to compile above was the Ubuntu kernel from the
sources provided by Synaptic. Once it hit the experimental Ubuntu dm-
raid4-5 driver you mentioned, it errored very specifically on the dm-
region-hash.c file. Looking at the compilation output, it seems that
most, if not all o
What I'm trying to get at is that I'm pretty certain that the source of the
leak is in the ubuntu patches. Specifically,
../ubuntu/dm-raid4-5/dm-region-hash.c
Mr. Susi, if you could please take a look at my compilation output from above
and see if that helps track the error, I would appreciate
Consider yourself verified. Also, see my previous comment about my
attempt at recompiling my kernel and how it failed at the ../ubuntu/dm-
raid4-5/dm-region-hash.c file. It's comment #5 to be exact.
Dec 30 03:05:11 ubuntu kernel: [ 22.205128] hda-intel: IRQ timing workaround
is activated for
As requested sir, here is your metadata.
** Attachment added: "Metadata of RAID 2 (Darkness)"
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/666577/+attachment/1773416/+files/metadata.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Actually, I don't have the array itself divided into two volumes, I have
the three drives divided into two raid 5 arrays. Darkness doesn't get
used as much as it used to be my XP partition. However, I found that I
used my Vista and, later, Win 7 more often so I removed XP and left it
as a partiti
I've found the problem and a work-around. dmraid is incapable of
handling metadata which is written into RAID arrays by Intel's Matrix
program. dmraid errors on the metadata and crashes. If someone would
be so kind as to code something into dmraid to either ignore or utilize
the metadata, it wou
I'm guessing nobody's going to be working on this anytime soon. For
some reason, it's still having trouble identifying my isw drive. I
think we might need to go about a different means of identifying and
adapting to it.
--
You received this bug notification because you are a member of Ubuntu
Bu
I'm compiling it using the source from synaptic. But this bug isn't
about compilation errors; it's about the startup error. I only put the
compilation error there as a point of reference should the source need
to be looked at.
--
dmraid fails on start with ICH9R under RAID 5
https://bugs.launch
Here is the output of dmraid from my terminal:
er...@ubuntu:~$ sudo dmraid -ay - -
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sde: asr discovering
NOTICE: /dev/sde: ddf1discovering
NOTICE: /dev/sde: hpt37x discovering
NOTICE: /dev/sde: hpt45x discovering
NOTICE: /dev/sde:
Did you recompile or use a non-standard kernel than what came with
Ubuntu?
--
dmraid fails on start with ICH9R under RAID 5
https://bugs.launchpad.net/bugs/666577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Well, I finished (sort of) and it wasn't pretty to say the least.
Basically, it needs to have a few punctuations moved and needs to have
the code refined quite a bit. There's also a problem with incompatible
types in one of the declared variables. If someone that knows what
they're doing would fi
Okay, I'm going over the code now. I'm a novice so I might be wrong
here. But, I've changed uint32_t to unsigned long int and I've added a
LOT of semi-colons to void and struct statements. I think a number of
structs could have been changed to typeref, but I'm not a programmer.
If someone would
Okay everyone, it goes deeper! I tried recompiling the Linux kernel to
incorporate a few changes and to see if I could get dmraid to work
correctly. The following is my result:
ubuntu/built-in.o: In function `dm_rh_dec':
/home/erick/Desktop/linux-source-2.6.35/ubuntu/dm-raid4-5/dm-region-hash.c:
Update to messages: When I try to run ubuntu without the nodmraid
option and quiet enabled, I receive a message "device-mapper: table
252:5: raid45: Invalid RAID device offset parameter". Something tells
me that the problem isn't so much in dmraid itself as much as the RAID45
module.
--
dmraid
I mean that it failed to mount my raid arrays. Using sudo dmraid -ay only
causes it to set there on the terminal with a blinking cursor doing nothing. I
can type in it like it's waiting for something, but it's to no avail.
As for ls /dev/mapper, it only shows the file control.
--
dmraid fails
--
dmraid fails on start with ICH9R under RAID 5
https://bugs.launchpad.net/bugs/666577
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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
Public bug reported:
Binary package hint: dmraid
Description:Ubuntu 10.10
Release:10.10
PKG Version: 1.0.0.rc16-3ubuntu2
Expected: Raid to be recognized as RAID 5 array and the 3 partitions to
be available for access by Ubuntu.
Happened: udev-work[122]: inotify_add_watch(6, /dev
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27382160/Dependencies.txt
** Attachment added: "DpkgTerminalLog.txt"
http://launchpadlibrarian.net/27382161/DpkgTerminalLog.txt
--
acpid
https://bugs.launchpad.net/bugs/382559
You received this bug notification because
Public bug reported:
Binary package hint: acpid
Sadly, it affects Ubuntu-Desktop and Acpi capability
ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: acpid 1.0.6-9ubuntu4.9.04.3
SourcePacka
Yeah, what they said...Ran it with Alleyoop to find memory leaks in
liquidwar (25 of them by the way) and it crashed.
** Attachment added: "Valgrind crash involving memcheck"
http://librarian.launchpad.net/6440738/_usr_lib_valgrind_x86-linux_memcheck.1000.crash
--
valgrind crashes on memchec
Ditto here, was blowing myself up on level 6, picked up the goodies left
behind and "Poof!"
** Attachment added: "Poof! Screen went bye-bye."
http://librarian.launchpad.net/6414959/_usr_games_chromium.1000.crash
--
chromium crash during gaming
https://launchpad.net/bugs/68349
--
ubuntu-bug
78 matches
Mail list logo
