Bug #1787698 was reported to be useless, possibly because the machine
was not up-to-date, which isn't the case because mine was; so I can't be
more helpful here...
Thanks,
MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The newly created crash report is #1787698.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load without nomodeset
To manage notifications about this bug go to:
Thanks, I did step #2 (#3 was useless because #2 didn't fail) and the
newly-created bug report is #1783999.
Thanks,
MZ
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
Based on my comment #6, could this be related to #1782347 in any way, as this
only happens when graphics is involved?
Please note however that #1782347 is about Ubuntu only, while this bug is about
both Ubuntu and XUbuntu.
Thanks,
MZ
--
You received this bug notification because you are a
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1782347/+attachment/5168072/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Description changed:
Both with the livecd (usb drive) and the installed version, I must boot with
the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the
screen will keep on flashing in semi-textual mode, with a white mouse arrow
stuck).
This,
Isn't it the same logs I provided with apport-collect before?
Thanks,
MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load without nomodeset
To manage
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1782347/+attachment/5168073/+files/ProcEnviron.txt
** Attachment removed: "ProcEnviron.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5168073/+files/ProcEnviron.txt
**
Public bug reported:
The 'beep' command does not beep: I get no errors, not even in log files or
dmesg, but no sound can be heard.
The beep volume is ok (checked and unmuted with 'alsamixer').
This used to work in 16.04, so it is a regression.
'lsmod' shows that the 'pcspkr' module is loaded.
** Attachment added: "dmesg_noquiet_nomodeset.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167533/+files/dmesg_noquiet_nomodeset.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "journalctl_noquiet_nomodeset.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167534/+files/journalctl_noquiet_nomodeset.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Forgot to add: the system reboots/shutsdown fine when running in
'single' mode, i.e.: without switching to graphics mode first.
Thanks,
MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781889
Nothing crashed, so I skipped Your points #2 and #3.
As for #1, here's the log:
* when booting with 'noquiet nomodeset'
* and when booting with 'noquiet single' (I must add 'single' because starting
gdm without 'nomodeset' halts the machine).
Thanks,
MZ
** Attachment added:
** Attachment added: "journalctl_noquiet_single.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167536/+files/journalctl_noquiet_single.txt
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status:
** Attachment added: "dmesg_noquiet_single.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167535/+files/dmesg_noquiet_single.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, no improvements.
I booted the live cd in single mode, modified /etc/gdm3/custom.conf as
follows, then exited the single mode and continued the normal boot
process.
1) First attempt:
#WaylandEnable=false
I can see the purple background for a moment, then I'm sent back to text
mode and the
apport information
** Tags added: apport-collected
** Description changed:
Both with the livecd (usb drive) and the installed version, I must boot with
the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the
screen will keep on flashing in semi-textual mode, with a white
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1782347/+attachment/5165239/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Logs were taken when booting with 'nomodeset'; otherwise the machine is
unbootable.
Thanks,
MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load without
apport information
** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
https://bugs.launchpad.net/bugs/1782347/+attachment/5165240/+files/modified.conffile..etc.gdm3.custom.conf.txt
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Public bug reported:
Both with the livecd (usb drive) and the installed version, I must boot with
the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the
screen will keep on flashing in semi-textual mode, with a white mouse arrow
stuck).
This, however, prevents me from
Marked as requested, as it also happens with the latest upstream kernel.
Also, booting without acpi=off takes a very long time (1 minute?) before my
passphrase is asked (the logical volume is not found at first, and the system
has to perform a lot of scanning). With acpi=off, the question is
Seems solved on Ubuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574667
Title:
Mouse pointer occasionally jumps to the bottom-left corner
To manage notifications about this bug go to:
Seems solved in 18.04.
** Changed in: plymouth (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651139
Title:
plymouth needs 'nomodeset', otherwise it
Public bug reported:
Using default GRUB parameters ("quiet splash" or even "noquiet"), I'm
unable to reboot or shutdown: the Plymouth circle starts spinning, then
it stops and the system is frozen (altgr+sysrq won't work either).
If I use "acpi=off", I can reboot but obviously the system will
This also happens on the live cd, and in Ubuntu 18.04 too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781889
Title:
System freezes on restart or shutdown
To manage notifications about this bug
Robert, thanks for letting us know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574667
Title:
Mouse pointer occasionally jumps to the bottom-left corner
To manage notifications about this bug
@tinga: What exactly didn't work for you?
For me, replacing synaptics with libinput (as in #32) did the trick.
Then I also had to write a little bash script to reduce the speed:
#!/bin/sh
xinput -set-prop 11 281 -0.75
exit 0
or you could set this in 90-libinput.conf, as in #38 and #39.
--
You
Thanks Juan, your fix seems to work actually!
I confirm the pointer speed is very high, but a "xinput -set-prop 11 281
-0.5" command solved the issue (281 stands for "libinput Accel Speed"
and 11 is the proper device i.e. "DLLC6B2:00 06CB:75BF Touchpad").
Thanks,
MZ
--
You received this bug
Public bug reported:
If booting without 'nomodeset', Plymouth hangs very ofter right after
the Grub page, before the splash screen, leaving me to a useless black
screen.
(However, when booting with 'nomodeset' Unity icons can't be resized any
longer: see
Public bug reported:
When booting with the 'nomodeset' Linux kernel parameter, Unity launcher
icons can no longer be resized.
** Affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux-firmware (Ubuntu) => unity (Ubuntu)
--
You received this bug
Christopher, thanks for your time.
Please disregard comment #8, as I was just making a comparison between
two different machines - but probably that only added confusion.
Now, about the machine I reported the bug on:
* 12.04.0, 12.04.1, 12.04.2, 12.04.4: X does not start after boot, not even by
Tested with 12.04.5, kernel was "Linux ubuntu 3.13.0-32-generic
#57~precise1-Ubuntu SMP Tue Jul 15 03:51:20 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux".
Please let me know if you need further information.
Thanks,
MZ
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
You received
I confirm the very same bug also occurs in 12.04 LTS (just downloaded
12.04.5-desktop-amd64 and tested).
Thanks,
MZ
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't know: prior to 16.04 I used 12.04 which was bug-free, but running on
another laptop (no clickpad, only a "classic" touchpad with buttons and touch
area).
But I read online that this bug should be dating back to 14.04...
Thanks,
MZ
** Changed in: xorg (Ubuntu)
Status: Incomplete
Also I would suggest raising the importance a little, as this bug makes
the touchpad pretty unusable...
Thanks,
MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574667
Title:
Mouse pointer
The problem is still reproducible, even after the BIOS upgrade:
marco@filippo8:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
[sudo] password for marco:
1.1.9
03/01/2016
Thanks,
MZ
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
You received this
Public bug reported:
Sometimes the mouse pointer jumps directly to the bottom-left corner of
the screen, which results in opening the trash window when clicking.
This seems to be related: https://ubuntu-mate.community/t/mouse-pointer-
jumps-on-clicking-touchpad/2932.
Thanks,
MZ
ProblemType:
I can confirm this on my brand new Dell Inspiron 15 (5559)... a bit
annoying. :)
Thanks,
MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026046
Title:
Missing support for thumb resting on bottom
Sorry for the delay in answering, but I needed to test - and I can
confirm this bug has gone!
Thanks, MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285908
Title:
extended ascii characters not
Great news! There's a workaround which actually works, not only under X
but under console as well!
Full credits and thanks go to Vojtech Pavlik for a) taking time to
analyze my bug report and my output, b) describing the bug and finding
where the problem lies, c) suggesting me the workaround.
If
Vojtech Pavlik, the maintainer for the AT keyboard Linux driver, told me that
a way to force the keyboard in raw mode (which is what happens on buggy
boots) is to boot with i8042.direct=1. Unfortunately, there is not the
opposite option, i.e.: you cannot force the keyboard in translated mode
Public bug reported:
Binary package hint: network-manager
Hi,
it would be great if Network Manager could detect (and stop) roaming
UMTS/3G connections. That's because they are - at least in Italy -very
expensive.
Thanks, MZ
ProblemType: Bug
Architecture: i386
Date: Sat Sep 26 18:32:23 2009
Also tried with 9.10-alpha5 and the latest NetworkManager...
--
network manager has no umts roaming detector
https://bugs.launchpad.net/bugs/437265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32491658/Dependencies.txt
--
network manager has no umts roaming detector
https://bugs.launchpad.net/bugs/437265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0:
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/30977346/BootDmesg.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/30977345/AlsaDevices.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/30977347/Card0.Amixer.values.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/30977348/Card0.Codecs.codec.0.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Card0.Codecs.codec.1.txt
http://launchpadlibrarian.net/30977349/Card0.Codecs.codec.1.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: IwConfig.txt
http://launchpadlibrarian.net/30977351/IwConfig.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/30977353/Lspci.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/30977354/Lsusb.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/30977355/PciMultimedia.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/30977356/ProcCpuinfo.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/30977357/ProcInterrupts.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/30977358/ProcModules.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: RfKill.txt
http://launchpadlibrarian.net/30977360/RfKill.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/30977361/UdevDb.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/30977362/UdevLog.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/30977363/WifiSyslog.txt
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please note that my apport-collect uploads were taken with a live cd of
9.10-alpha4 (and the problem still persists), while I'm usually running
8.04.
Also, during the live cd experience, all proprietary drivers were NOT
loaded. The results, however, seem to be the same.
Thanks, MZ
--
extended
@Daniel:
no problem, thanks for your info... it seems everything works!
(I just got the keyboard hanged on one startup, but maybe that's a
coincidence...)
thanks, MZ
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug
I had to use i8042.reset i8042.nomux i8042.nopnp i8042.noloop instead
of just i8042.reset, otherwise my keyboard hanged up on cold boots 80%
of the times!
Hope this helps,
thanks, MZ
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received
no way: the keyboard still hangs up on cold boots most of the times...
:(
thanks, MZ
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi Daniel,
thanks, I'm trying this and I'll report if that's enough... :)
One question: shouldn't the option go in the #kopt line? by doing so, it
is automatically appended to *every* grub entry and also it is kept even
after a kernel upgrade...
thanks, MZ
--
extended ascii characters not
Hi,
isn't it possible to revert the kernel changes that were made and
originated the problem?
thanks, MZ
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is
2.6.24-23 still has the same problem (which occurs even more
frequently)...
thanks,
MZ
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
The default MySQL JDBC connector is installed in /usr/share/java, which
is not seen by Tomcat (unless you make a link from
/usr/lib/jvm/java-6-sun/jre/lib/ext/). It would be appreciated if this
could be done automatically...
Thanks, MZ
** Affects: mysql-connector-java
Hi,
I just made a diff sourcing the right dmesg output and the wrong
one, the results are:
WRONG boot (altgr not working):
[...]
input: AT Raw Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[...]
RIGHT boot (altgr working):
[...]
input: AT Translated Set 2 keyboard as
2.6.24-16-generic (the first kernel used by Ubuntu 8.04) was working
perfectly... the problem generated later, between 2.6.24-17 and
2.6.24-22...
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a
Hi,
since I'm running 8.04 (not intrepid) and bios 2.6.1 (if I remember
well), the problem lies in the kernel...
(Vostro 1000 is the work edition for Inspiron 152x)
thanks, MZ
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug
update:
reporting the showkey output when I press the AltGr key:
normally (i.e.: everything working fine):
0x64 (AltGr pressed)
0xe4 (AltGr released)
on problems:
0x00 0x81 0x94 (AltGr pressed)
0x80 0x81 0x94 (AltGr released)
thanks, MZ
--
extended ascii characters not displayed on cold
update: problem still occurs once in a while, but *much* more rarely
than a week ago (i.e.: before upgrading the kernel),
thanks, MZ
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of
it seems to me that the recent updates solved the problem!?
current kernel is 2.6.24-21
thanks, MZ
--
extended ascii characters not displayed on cold boots
https://bugs.launchpad.net/bugs/285908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
please close this bug report (I will open a specific one instead): I
discovered it's not an ALT-GR problem, but an extended-ASCII one: on
cold boots, every char between 0 and 127 is displayed correctly, others
aren't (the whole thing did not happen until a couple of weeks ago),
thanks, MZ
--
not an ALT-GR problem, but an extended ASCII one (so I'm going to open a
specific report)
** Changed in: ubuntu
Status: New = Invalid
--
altgr randomly not working
https://bugs.launchpad.net/bugs/283934
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Hi,
starting a couple of weeks ago, when I cold-boot my Dell Vostro 1000 laptop I
always find it impossible to press and display characters whose code is 127
(extended ascii), such as ì, è, ò, etc., and also @ (which requires alt-gr),
when I reboot the machine everything
It seems to me that the problem actually happens on cold boots rather
than after reboots (warm boots).
MZ
--
altgr randomly not working
https://bugs.launchpad.net/bugs/283934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Hi,
I use a Dell Vostro 1000 laptop with Italian keyboard, running Ubuntu
8.04,
starting about 10 days ago (I can't remember it it's connected to some
updates), the AltGr key began to NOT work randomly, which is: sometimes
everything is perfect, some other times the key
Thank you for your report. Is this still an issue for you?
yes, it is: just checked now...
thanks :)
Marco
--
seahorse plugin in evolution decrypts files in .evolution and leaves them there!
https://bugs.launchpad.net/bugs/176454
You received this bug notification because you are a member
Strange issue. Has it been solved already?
using 8.04 now: it doesn't happen so often anymore (actually, the bug
nearly disappeared),
thanks,
Marco
--
dvd drive occasionally opens by itself
https://bugs.launchpad.net/bugs/178109
You received this bug notification because you are a member of
So I'm closing this bug now but feel free to reopen it if you think it's
still happening. (And you don't press the eject button accidentally :) )
ok, thanks :)
Marco
--
dvd drive occasionally opens by itself
https://bugs.launchpad.net/bugs/178109
You received this bug notification because
I confirm that the bug has gone away. Using 8.04 here.
Thanks, MZ
--
OpenOffice Impress crash when closing
https://bugs.launchpad.net/bugs/90007
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks Ahmet and James, the scripts did work,
still reporting the bug, though, since it should work out-of-the-box:
but thanks for the temporary solution,
MZ
--
Brightness Control doesn't work on Dell Vostro 1000
https://bugs.launchpad.net/bugs/159255
You received this bug notification because
I'm sorry to report the bug is not fixed in Hardy (neither it was in
Gutsy): Evince still defaults all printers to US Letter, even if I set
the default paper size to A4 (by using CUPS).
(Note: my /etc/papersize is set to letter, but I tried to write a4
inside and nothing changed.)
--
evince
My experience:
- Gutsy: worked perfectly
- Hardy, default install kernel:
-- the wireless led works perfectly only after a few minutes of computer
activity
-- instead, it is always on (even if you turn the interface down) in the
first minutes
- Hardy, current 2.6.24-17-generic kernel (just
forgot to say: Dell Vostro 1000 with Broadcom Corporation BCM94311MCG
wlan mini-PCI (b43 driver)
--
[Hardy]b43 wireless driver: WiFi LED is out when interface up and vice versa
https://bugs.launchpad.net/bugs/175829
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi, using Hardy 8.04 here,
now the brightness keys show the brightness progress indicator at 100%,
but when I press the brightness up or brightness down keys the
progress bar is still at 100% (i.e: no way to lower that using the
keyboard),
thanks, MZ
--
Brightness Control doesn't work on Dell
Hi,
I noticed that the bug happens when the update-manager is downloading
upgrades in the background: could it be that it tries to access the dvd
drive, even if I disabled (#) the cdrom repository?
Thanks, MZ
--
dvd drive occasionally opens by itself
https://bugs.launchpad.net/bugs/178109
You
Hi, thanks for writing back,
Attached is the gpm.log file you required.
Please consider that I just tried pressing Fn+F1 (which should hibernate my
laptop) and now it does not work: which is correct, since I disabled it from
the Preferences Power management menu. So the bug is probably gone.
I'm using Ubuntu 7.10, all updates were correctly applied.
I disabled the eject key in the System Preferences Keyboard
Shortcuts menu. Now it seems the drive does not open by itself anymore,
but I still hear some noises once in a while (as if it tried to
eject).
Thanks, MZ
--
dvd drive
It just happened again.
I was just looking at the display, no keys were pressed at all, and all
of a sudden the drive opened!
I just re-enabled klogd and syslogd, hoping they give me some hint...
Thanks, MZ
--
dvd drive occasionally opens by itself
https://bugs.launchpad.net/bugs/178109
You
Public bug reported:
I have a Dell Vostro 1000.
Starting a few days/weeks ago (sorry I can't be more precise), the dvd
drive started to open by itself. This happens about 1-2 times per hour.
Please ask if you need some detailed specs about my computer.
Thanks,
MZ
** Affects: ubuntu
same here, using Ubuntu Gutsy,
but doing an echo -n VALUE /proc/acpi/video/VGA/LCD/brightness
works,
thanks, MZ
--
Brightness Control doesn't work on Dell Vostro 1000
https://bugs.launchpad.net/bugs/159255
You received this bug notification because you are a member of Ubuntu
Bugs, which is
confirming the problem EVEN when on AC power,
(also confirming that you can circumnavigate the problem by setting
hdparm -B 255 /dev/sda and entering the correct values in
/etc/hdparm.conf),
Dell Vostro 1000 (less than 2 weeks old, had about 1450 Load_Cycle_Counts on 13
hours of activity)
HD is
Do you think your problem is the same than this one?
https://bugs.launchpad.net/ubuntu/+source/mail-notification/+bug/2462
yes, as far as I can read, that's should be the same (mis)behaviour...
thanks,
--
Marco
--
mail-notification cpu
https://bugs.launchpad.net/bugs/164102
You received
Public bug reported:
Binary package hint: mail-notification
It often happens that the mail-notification applet increases the cpu load.
This usually happens when I have no email in my mailbox, but sometimes also
happens when I have some.
Right-clicking and uploading the state unloads the cpu.
editing my previous comment:
1) after editing /etc/usplash.conf I had to sudo update-usplash-theme
usplash-theme-ubuntu
2) vga=0 is not mandatory
ZM
--
[maybe initramfs-tools or usplash?] black screen during usplash. Ubuntu boots
fine
https://bugs.launchpad.net/bugs/68647
You received this
1 - 100 of 106 matches
Mail list logo
