I have the same(?) problem on Jaunty with a ATI Mobility Radeon M6 LY.
Using the latest package from tormodvolden's PPA, after login I get
horizontal gray and black stripes and on the black stripes in some areas
every second pixel shows the desktop. I'll try to make a photo...
The interesting thin
Here's the "screenshot". This bug happens for some tormodvolden-builds
now. About a month ago these builds worked fine.
The bluish thing around the edges is "Gnome Do", which originally
appears at the center of the screen. The mouse cursor is rendered fine,
by the way.
** Attachment added: "P1010
@Timo Jyrinki:
On my Mobility M6 LY (16MB), EXA with both of your optimizations is still
slower than XAA. Using EXA, showing the selection list of "Gnome Do" (down
arrow) is presented in 3 hard steps whereas using XAA it is smoothly animated.
Same goes for expanding the playlist in VLC player.
Had the same problem with my old ATI M6 LY (as the original poster), see
http://ubuntuforums.org/showthread.php?t=1108844 . Today I upgraded my
PC at work, and got the same poor performance with a Radeon 9200 Pro.
Switching to XAA also brought back the performance I was used to in
Intrepid.
Is the
Also tried it. With the default screen size of 1024x768 (notebook TFT
panel) it's still nothing near the XAA speed. When switching to dual-
screen resolution 2304x1024, some options (like ColorTiling) get
disabled according to Xorg.log because the card can't handle it at this
resolution. And perfor
I have a similar problem with Jaunty. I played around on my netbook with
the "switch-desktop" tool and switched from netbook-launcher to normal
desktop, activated compiz, played around, deactivated compiz and went
back to the netbook-launcher. From there on, FUSA only shows a vertical
1px bar inste
I tried desktop-switcher yesterday on my netbook with Jaunty and
experienced this bug with the fast-user-switch-applet:
https://bugs.launchpad.net/ubuntu/+source/fast-user-switch-
applet/+bug/301309/comments/10
Additionally, it didn't restore the proper skin/window theme for the
netbook-remix.
-
Upgraded my Notebook today, 2.6.27-7 gives the kernel panic, the former
2.6.24-21 boots fine as usual.
IDE controller is an Intel 82801DBM (ICH4-M) 8086:24ca. The notebook is
a SONY VAIO PCG-Z1XEP, Centrino M.
--
Kernel Panic - not syncing: VFS after upgrade.
https://bugs.launchpad.net/bugs/1511
UPDATE: After adding uvesafb to /etc/initramfs-tools/modules and several
update-initramfs'es, the new kernel started to work. I'm not sure
whether I had the 0 Byte initrd-problem or not. When I read about this
problem, I already had some update-initramfs'es done and the file had a
normal size of ab
I have this while trying a svn-import:
$ bzr svn-import --verbose --all svn://localhost/Web/project
Importing branches with prefix /svn://localhost/Web/project/
bzr: ERROR: Must end write group before releasing write lock on
KnitPackRepository('file:///home/user/Development/www/co/project/.bzr/re
UPDATE: I now found out why FUSA only displayed as a 1px vertical bar:
the "desktop-switch" tool somehow set
desktop/gnome/lockdown/disable_user_switching to TRUE which caused FUSA
to this behavior. Since it is also used to set the current Pidgin state
and to Logoff, I guess this is not the desired
Public bug reported:
Binary package hint: fast-user-switch-applet
After toying around with the desktop-switch tool, it somehow set
desktop/gnome/lockdown/disable_user_switching to TRUE and when switching
back to the netbook-remix, the FUSA icon was missing. Instead I found a
grey vertical 1px bar
I now found out why the previously mentioned problem with the FUSA
appeared: desktop-switch somehow set
desktop/gnome/lockdown/disable_user_switching to TRUE which caused FUSA
to hide itself. I did NOT have this option enabled before using desktop-
switch.
--
Jaunty - Switch Desktop does not func
We had these problems with VMware ESX and a JeOS/Ubuntu Server
installation. Everything worked fine but after some kernel update, the
new initramfs was written beyond the 1024th cylinder and grub failed
(and this was inside a VM, so there's no BIOS update which could fix
this; shame on you VMware!)
For me it happens without ever touching the resolution settings. I have
a notebook with an external display attached (permanently!). The
resolution is already set correctly at the GDM login. But after login,
the applets are mixed up (panels are at their correct locations most of
the time). This eve
My preferred way would be to let the update-initramfs check that all
files are in the first 1024 cylinders of the disk. Maybe it could move
out-of-boundary-files more to the beginning of the drive using some
technique like e2defrag does.
--
/boot is on root partition by default
https://bugs.launc
Just wanted to add that for me (Jaunty, all updates as of today) X/GDM
won't start correctly if the tablet is plugged in. Also I got X crashing
when trying to start a new console (Terminator) while the tablet is
plugged in. And yes, unplugging the tablet also hangs and then restarts
X.
--
Unplugg
Forgot to add: I'm using an Aiptek SlimTablet 600U (Model WCK-C121) and
have NOT installed xserver-xorg-input-aiptek but xserver-xorg-input-
wacom (the tablet also uses the "wacom" kernel module). The problem
seems to be the same though. So it might have nothing to do with the
specific input driver
> I just installed the PPA version again and had a closer look. With and
> without XAA my Xorg defaults to VESA?!?
The latest xserver-xorg seems to not recognize this card anymore. To
force it to use the ati driver, add the line
Driver "ati"
to the Section "Device" in your /etc/X11/xorg.conf .
I now found out that the gray stripes have to do with the
"compositing_manager" option under /apps/metacity/general . When
enabled, I see the gray stripes. When disabled, I see my desktop but see
garbage in some apps e.g. the VLC window (might be all Qt interfaces
which fail).
--
[HD 3650] cannot
I didn't see this bug on Lucid for now. Looks fine. :)
--
Using Chromium crashed X and made kernel panic
https://bugs.launchpad.net/bugs/526757
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I noticed that this mostly occurs after having sent a mail. It rarely
happens when just browsing my mails but after sending one, it appears
almost for sure.
I have 3 IMAP accounts in Evo: Kerio Mailserver, Courier IMAP and Google
Mail.
--
Evolution hangs with "Formatting Message" after several h
Hi Alex,
As I updated today, the version is:
Installed: 5.0.336.0~svn20100224r39849-0ubuntu1~ucd1~karmic
So the version of the report was yesterday's version from the chromium-
daily PPA.
BUT: I got the same thing today while clicking around in Opera. So I
guess it has nothing to do with Chro
Public bug reported:
I'm on a Intel Q9400 using a ATI HD4670. GUI is Gnome, fglrx and Compiz.
Ubuntu is Karmic Koala as of today.
The machine was running fine for 2 days now. I just finished writing an
eMail using Chromium and my company's Webmailer. Upon clicking "Send", X
crashed (I saw the boo
The miro 3.0-0pcf1 package from their official Ubuntu repository also
fails to install because of a dependency to python-gnome2-extras. Is
there any chance to update this dummy package with correct dependencies
for Lucid?
--
python-gnome2-extras on lucid broken dependencies
https://bugs.launchpad
I also got the same device
(http://www.dizeg.net/digit/photo/caplior7/rimg1555.jpg) ... and with it
the same symptoms. Using alsamixer, going from 63.00 dB (max) gain
volume down to 11.00dB only slightly changes the volume (it's still very
loud at this point). Going one step down to 10.99dB comple
Public bug reported:
I just have a problem with Plymouth, GDM and an ATI HD4670 with the
fglrx driver. (Lucid as of 4 days ago now) I believe it has to do with
the fglrx (I'm using the just released one) not liking the "radeon"
kernel driver. Leaving everything as it is (i.e. everything installed
I had installed the 2:8.721-0ubuntu2 (amd64) package of fglrx by hand
(i.e. gdebi). (https://launchpad.net/ubuntu/+source/fglrx-
installer/2:8.721-0ubuntu2/+build/1569218) Maybe there was the
fglrx.conf contained ... I deleted it because I thought it was left by
the Karmic fglrx driver. ( I did a s
The 2:8.721-0ubuntu2 package for amd64 is missing the
/usr/lib/fglrx/ld.so.conf and thus it doesn't configure correctly. You
can fix this for now by creating that file with the contents
"/usr/lib/fglrx" (without quotes) and then doing a "dpkg --configure
-a". Worked fine for me.
--
Does not suppo
I just have the same problem with GDM and an ATI HD4670. (Lucid as of
now) I believe it has to do with the fglrx (I'm using the just released
one) not liking the "radeon" kernel driver. Leaving everything as it is,
I can see the splash (graphically) but it then goes all purple and
nothing more happ
@SolidSlash #21: I guess you have the same problem as I had: fglrx
conflicts with the "radeon" kernel module. You have to add "nomodeset"
or "radeon.setmode=0" to your kernel options, i.e. get into GRUB, edit
the parameters for recovery mode and add it manually to the kernel line.
After getting int
Public bug reported:
u-boot-rpi_2016.03+dfsg1-6ubuntu2 (armhf) loads the boot.scr to
0x0200 but the bootscr.rpi3 also expects the FDT to be at this
address.
Changing the bootscr.rpi3 (and /boot/firmware/config.txt) to have the
FDT at 0x02008000 and running flash-kernel afterwards makes the
Ra
** Also affects: u-boot (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791466
Title:
RPi3: fdt_addr_r conflicts with scriptaddr from u-boot-rpi
Public bug reported:
When dist-upgrading from artful to bionic, the upgrade of dma failed
with:
Setting up dma (0.11-1build1) ...
dpkg: error processing package dma (--configure):
installed dma package post-installation script subprocess returned error exit
status 128
Only after temporarily r
This might be related to this one: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=847659
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791471
Title:
Upgrading from 0.11-1 (artful) to 0.11-1buil
Public bug reported:
The current version of vte2.91 is 0.54.1 which breaks SCOSC/SCORC ANSI
codes for saving the cursor position and returning to it. (Aka. SCP and
RCP)
This is fixed in 0.54.2 as per
https://gitlab.gnome.org/GNOME/vte/issues/48 . Please update package for
cosmic.
** Affects: vte
This might be related to bug #1791466
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage notifications about this bug go t
Can we omit this u-boot dependency, please? The Raspberry firmware can
boot Linux kernels perfectly fine all on its own without the need of
u-boot. There's absolutely no need to add this additional layer of
potential problems, e.g. bug #1791466 .
--
You received this bug notification because you
Public bug reported:
The Raspberry Pi firmware can boot a Linux kernel perfectly fine with
these settings in config.txt:
kernel=vmlinuz
initramfs initrd.img followkernel
(Note that the space between "initramfs" and "initrd.img" is
intentional!)
So there's no actual need to use u-boot anymore. A
This was fixed in #1847163.
** Changed in: linux-raspi2 (Ubuntu Eoan)
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/1843207
Title:
Doesn't boot on Raspberry Pi 4
Public bug reported:
During upgrade on a Raspberry Pi 3 (armhf) from disco to eoan, the
upgrade of dma failed.
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: dma 0.11-2
ProcVersionSignature: Ubuntu 5.0.0-1025.26-raspi2 5.0.21
Uname: Linux 5.0.0-1025-raspi2 armv7l
ApportVersion: 2.20.11
I don't know what happened, but yesterday, all hotkeys worked for some
reason. After shutting down the PC over night and booting it up today
with no changes made - they DON'T work again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think I found a pattern: When I login immediately after GDM comes up,
the hotkeys seem to work. When I wait a bit at the user selection and
THEN login, the hotkeys DON'T work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
This is after waiting a few minutes at the GDM logon screen. I also
tested the media keys in GDM and they worked. But they DON'T work in
Unity.
https://pastebin.ubuntu.com/26222796/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to
missing kernel modules for the new hardware components. It would be nice
if these got included. Also it only boots the kernel when the Pi is
configured for 1GB RAM or less. (Then gets stuck on missing root FS
I'm booting my Pis without u-boot with this in my config.txt:
[pi4]
enable_gic=1
armstub=armstub8-gic.bin
total_mem=1024
[all]
kernel=vmlinuz
initramfs initrd.img followkernel
arm_64bit=1
gpu_mem=32
dtparam=eee=off
This exact setup works fine on my Pi 3B+
> Which release of Ubuntu are we talking about here?
This is a clone of my RPi3 system (disco, IIRC it started out as bionic)
that was upgraded to eoan (on the Pi3).
btw: I've upgraded(?) the EEPROM to the July version
(https://static.raspberrypi.org/files/rpi-boot-eeprom-
recovery-2019-07-15.zip
> I'd *guess* that's a limitation due to u-boot, but I'll try and find
> time to test the kernel alone to confirm that. Obviously it's
> something we'll want to sort out fairly quickly but I suspect it'll
> have to be post-release at this point.
For me, the Raspberry never leaves the rainbow scree
THANK YOU!!
I just made it boot (without u-boot ATM) with all 4GB RAM enabled. And
my problem was my own stupidity. Several weeks ago, when researching why
it wouldn't boot, I somewhere found the boot param
"modprobe.blacklist=sdhci_iproc" which I added to my command.txt.
Without that module, the
The DTB is also missing from the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843207
Title:
Doesn't boot on Raspberry Pi 4
To manage notifications about this bug go to:
https://bugs.laun
Public bug reported:
After upgrading my Raspberry Pi 4 from Eoan to Focal (arm64), it now
runs awfully slow with dmesg showing loots of these warnings:
[ 3821.602211] [ cut here ]
[ 3821.603018] WARNING: CPU: 2 PID: 25391 at drivers/mmc/host/sdhci.c:1101
sdhci_prepare
** Attachment added: "ubuntu-bug linux-raspi (gzipped)"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+attachment/5376655/+files/apport.linux-raspi.2ccw0izb.apport.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Downgrading to 5.4.0-1008-raspi fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880607
Title:
Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04
To manage notifications a
My cmdline.txt:
root=LABEL=rpi4-root rootfstype=ext4 rootwait verbose nosplash
console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 net.ifnames=0
dwc_otg.lpm_enable=0 dwc_otg.fiq_fix_enable=1 fsck.repair=yes
My config.txt:
[pi4]
# Route interrupts to ARM cores using legacy interrupt contro
A buddy is running a Pi 4 with the official 20.04 Pi image (freshly set
up) and with the 1011 kernel WITHOUT ISSUES. His config looks like this:
cmdline.txt:
root=LABEL=writable rootfstype=ext4 rootwait console=serial0,115200
console=tty1 net.ifnames=0 dwc_otg.lpm_enable=0 elevator=deadline fixrt
Kernel 5.4.0-1012.12 fixes the issue.
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => 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/1880607
Title:
Raspberry Pi 4 extrem
I have this, too, on a Raspberry Pi 3 with arm64 Ubuntu. However, I've
also upgraded my Raspberry Pi 2 with armhf and there, NetworkManager
still autoconnects just fine after boot. The configuration looks
identical on both machines.
--
You received this bug notification because you are a member o
Public bug reported:
Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco
arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41
CEST. About 12:36 the system froze. I was able to reset the system at
around 17:17. It froze again at around 17:55. Reset it again 19:09,
With 1.1.1b-1ubuntu2.3 it's a bit different. The system doesn't seem to
freeze anymore, but network traffic stops working. Happend about 1-2
hours after a fresh reboot (after applying updates). It still answered
to PINGs, but no other network traffic. Neither SSH, nor HTTP/HTTPS or
XMPP. After down
Public bug reported:
After updating flash-kernel from 3.90ubuntu3 to 3.90ubuntu3.18.10.1,
dpkg aborted with this error:
Processing triggers for flash-kernel (3.90ubuntu3.18.10.1) ...
Using DTB: bcm2710-rpi-3-b-plus.dtb
Installing
/lib/firmware/4.18.0-1009-raspi2/device-tree/broadcom/bcm2710-rpi-
The thing is: In the previous version, flash-kernel ignored if mkimage
was missing and just continued normally without throwing any error or
even showing any warning. Which is the behaviour I'd prefer.
The new version aborts and throws an error although there's no need to
run mkimage on my system
Same here while upgrading my Raspberry Pi 2 (armhf) from 17.10 to 18.04.
Upgrader finished with "Upgrade complete" but left hundreds of packages
in their old versions. I had to fix that with aptitude and now it's
actually finishing the upgrade.
--
You received this bug notification because you ar
The error message is:
Preparing to unpack .../bash_4.4-2ubuntu1_amd64.deb ...
Unpacking bash (4.4-2ubuntu1) over (4.3-15ubuntu1) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu15) ...
update-initramfs: deferring update (trigger activated)
dpkg: dependency
I have this problem in Ubuntu 15.10 and Guake Terminal 0.8.4 (from the
WebUpd8 PPA, as recommended on their homepage).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506166
Title:
Bracketed paste sh
Same here. The update to 1021 breaks the boot and the only way to
recover is to rename all *.bak files back so it boots the older kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
The actual problem happens earlier in the process than depicted in the
screenshot above:
Found U-Boot script /boot.scr
reading /boot.scr
412 bytes read in 13 ms (30.3 KiB/s)
## Executing script at 0200
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address co
It seems the FDT isn't loaded properly. I can boot the system if I load
the FDT manually and do the remaining steps from the boot.scr manually:
fatload mmc 0:1 0x0200 bcm2710-rpi-3-b.dtb
fdt addr 0x0200
fatload mmc 0:1 0x0100 vmlinuz
fatload mmc 0:1 0x0210 initrd.im
Downgrading the kernel or recently upgraded packages flash-kernel or
linux-firmware-raspi2 didn't work for me. But you can fix this
temporarily by editing /usr/share/flash-kernel/bootscript/bootscr.rpi3
and adding the line
fatload mmc 0:1 ${fdt_addr_r} bcm2710-rpi-3-b.dtb
after the line
Upon further inspection: The flash-kernel from the rpi3 PPA
https://launchpad.net/~ubuntu-raspi2/+archive/ubuntu/ppa-rpi3 is only
published for Xenial and there, the boot script sets the fdt address to
0x100 instead of 0x200. And that works without explicitly loading
the fdt.
So it seems I had
Also the official flash-kernel_3.0~rc.4ubuntu64_armhf.deb sets the fdt
address to 0x100 whereas 3.0~rc.4ubuntu64.1.1 from yakkety-updates sets
it to 0x0200. So it seems to be a regression in that package.
Downgrading to 3.0~rc.4ubuntu64 and running "sudo flash-kernel" works.
(Don't know why it
Could the missing fdt at 0x0200 be the reason, the RasPi now has a
different MAC address on each and every boot? Because I noticed this
after I got the boot process working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
4.8.0-1035 seems to fix the problem. (Didn't check -1034.) Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
To man
For the record: I upgraded to zesty and with kernel 4.10.0-1004
everything works fine, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic when using rtlwifi since 4.8.0-1
** Attachment added: "Screenshot of kernel panic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4824869/+files/IMG_20170223_0030047.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use
wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And
there's a RTL2838 DVB-T USB stick attached to monitor airplane positions
for Flightradar24.
After updateing the kernel from 4.8.0-1024, whi
apport information
** Tags added: apport-collected yakkety
** Description changed:
I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use
wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And
there's a RTL2838 DVB-T USB stick attached to monitor airplane positio
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825141/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Ti
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825136/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825138/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/166
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825137/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825140/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Ke
NOTE: The apport I sent was created with the WORKING 1024 kernel. IT IS
NOT from the here mentioned -1025 or -1026 kernel as there I can barely
login until the kernel panics.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you ar
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825135/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16671
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825139/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825134/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
*** This bug is a duplicate of bug 1726930 ***
https://bugs.launchpad.net/bugs/1726930
** This bug has been marked a duplicate of bug 1726930
System fails to start (boot) on battery due to read-only root file-system
--
You received this bug notification because you are a member of Ubuntu
Ah, I gave up after about 8 attempts without any luck - wanted to try
some more today. Glad you did it first. :)
After cleaning up different port numbers and IDs, the only obvious
difference between your logs seems to be something about the color-
plugin.
I've attached the cleaned logs.
** Attac
Today I was able to get media keys working about every 3rd restart of
unity-settings-daemon. I've saved 2 logs of each state. I suspect it has
to do with the order the plugins are loaded.
** Attachment added: "mylogs.zip"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1727842/+attachment
Just for the record: I had Ubuntu 17.10 (upgraded from 17.04 which was
upgraded from 16.10) running on my HP Spectre x360 just fine with GDM3
and Unity and when the screensaver kicked in or I locked the screen, it
turned to the GDM3 greeter.
A few days ago, I cleared my SSD and installed 17.10 fro
My Commands plugin was already disabled and the media keys still don't
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727842
Title:
Volume and Mute buttons on keyboard not doing anything in Un
After enabling it and disabling it again, the media keys work now for
some reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727842
Title:
Volume and Mute buttons on keyboard not doing anything
After a reboot, with nothing else changed, media keys are no worky
again. So it's NOT the Commands plugin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727842
Title:
Volume and Mute buttons on key
I see this during bootup with a fresh install of artful on a HP Spectre
x360 13-4104ng notebook. For me it's setkeycodes e057 and code 0xd7,
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16972
A few reboots later, I'm now able to unlock the notebook from the
LightDM lockscreen. There's no "switch to greeter" anymore, but a real
password entry field which works. However, I still don't know why I had
the GDM3 lockscreen before.
--
You received this bug notification because you are a memb
@Andrea: Yes, no "switch to greeter" for me anymore. But still I get the
LightDM lock screen (with working password field) instead of GDM3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
@Andrea:
@include common-auth
auth optional pam_gnome_keyring.so
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password f
Public bug reported:
After installing the "moc" package (2.5.0~alpha4+svn20120224-1ubuntu1)
incl. all dependencies, I get this when trying to run it:
$ moc
moc: could not find a Qt installation of ''
** Affects: moc (Ubuntu)
Importance: Undecided
Status: New
--
You received this
I just got access to that Raspberry Pi 3 again. I saw that the expected
fdt address now changed to 0x02008000 in the boot script.
In the config.txt, it was set as:
# set extended DT area
device_tree_address=0x100
device_tree_end=0x8000
So I changed it to:
# set extended DT area
device_tree_add
I don't have access to the RasPi3 at the moment (due to the changing MAC
screwing with DHCP and port forwardings). I'll see what I can do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Tested today with the -1028 kernel. The problem IS STILL THERE.
This time, I made a video of the problem:
https://www.youtube.com/watch?v=H_PxSXsgVQU
The error part starts with:
Unable to handle kernel NULL pointer dereference at virtual address 0034
pgd = afcfc000
[0034] *pgd=
1 - 100 of 145 matches
Mail list logo
