Public bug reported:
When I use the new (24.04) settings and 'Online Accounts' to connect to
Microsoft 365, it authenticates, works well for about 5 minutes and then
disconnects.
I have to remove that account and redo it every time I want to use it.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Dag,
Can you confirm you mean 24.04 and not 22.04, please?
On Mon, 15 Apr 2024 at 17:25, Dag Bjerkeli <1875...@bugs.launchpad.net>
wrote:
> I've just tested this, and can confirm that there is a bug regarding
> keyboard layout in 22.04 beta. As this time the error also appears when
> you select
Hi guys,
I'm sorry to say that this bug is back in 24.04 Beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875062
Title:
[20.04] Keyboard layout changes during installation before typing
Changed from ding to nautilus after reading about nautilus gvfsd-trash
bug
** Package changed: ding (Ubuntu) => nautilus (Ubuntu)
** Summary changed:
- DING causes gvfsd 'Too many files open' error and fills syslog
+ nautilus causes gvfsd-trash 'Too many files open' error and fills syslog
**
Further reading would suggest that it's a bug in Nautilus and the way that
gvfsd deals with trash:
https://www.reddit.com/r/gnome/comments/l0gg32/a_helpul_tip_for_those_with_gvfsdtrash_hogging/
It runs out that I don't have ding installed, and also no references to
gvfsd.
Yet, if I do as the
Public bug reported:
My syslog is filled (to >30GB) regularly with these messages. I seem to
have this thing called DING going on, which maybe causing it?
Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068):
GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too
Public bug reported:
After following the instructions at:
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results
on the 20220523 daily build of Kinetic, I used the command
zsysctl show
and was met with the message:
~$ zsysctl show
Command 'zsysctl' not found,
No, It was a straight install with me present at the desktop computer
all the way through - no switching or even screen locking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967883
Title:
[snap]
Public bug reported:
From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox
(nightly) from Ubuntu Software (as snaps).
Neither of the two icons/graphics show up in the show applications window -
either in the thumbnails of the groups I have created, or the expanded windows
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577339/+files/Screenshot%20from%202022-04-05%2014-48-11.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577338/+files/Screenshot%20from%202022-04-05%2014-48-11.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568063/+files/acpidump.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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568061/+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/1964626
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568062/+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/1964626
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568060/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964626
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568059/+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/1964626
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568058/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568057/+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/1964626
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568056/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568055/+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/1964626
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568054/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964626
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568053/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964626
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568050/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568052/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964626
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568051/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964626
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1964626/+attachment/5568049/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964626
Title:
apport information
** Tags added: apport-collected
** Description changed:
I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple
of weeks and just updating and upgrading using apt.
When restarting the VM (VirtualBox), I get the screen in the screenshot
below. The
Public bug reported:
I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple
of weeks and just updating and upgrading using apt.
When restarting the VM (VirtualBox), I get the screen in the screenshot below.
The same thing happens if I select the 5.15.0-22-generic options
So I then manually changed the password to read Thanks#Brian by using
the US mapping of Shift+3 to get the # symbol as seen in the screenshot.
I let the installer run and logged in successfully using Thanks#Brian
directly as I normally would on my UK keyboard.
So, yes, it looks like Unity isn't
I've downloaded and installed using 20220129 which does have the eyeball
icon next to the password field.
As seen in the attached screenshot, the keyboard mapping at the password
stage doesn't go to UK as previously selected - I had tried to type
Thanks#Brian but the keyboard had given me
Hi Brian,
Using the latest daily build (20220126), I cannot see the option to
display the password? - see attached screenshot.
I can see your line of thinking as the # symbol is different on US & UK
keyboard mappings (much to the annoyance when I lived in the US for 6
years and had to retrain my
Unable to reproduce in VB environment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952515
Title:
QA Test Ubuntu 22.04 Gnome-shell Crashed
To manage notifications about this bug go to:
Bug not present in build 20211103
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949523
Title:
Disk Encryption Password Not Remembered
To manage notifications about this bug go to:
Public bug reported:
In two attempts at following the "Install (entire disk with lvm and
encryption) in Ubuntu Desktop amd64 in Jammy Daily" in the 20211102
build, the machine fails to recognise the full disk encryption password
set at install time.
I have tried "lemon" and "Lemon" as the
ubiquity-21.10.10
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: juglugs1974 seb128 ubuntuqa
> Launchpad-Bug-Reporter: Mark Smith (juglugs1974)
> Launchpad-Bug-Modifier: Sebast
The '@' character also does not work in any position of the string.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948714
Title:
After reboot, the password set at install time doesn't work.
To
Note: Booting into recovery and setting the password from the command
line allows the # character, so it's only in Ubiquity at install that
there is a bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've narrowed it down to a specific special character at any location in
the string, and after changing all of my passwords that included it, I
can reveal it to be the '#' character. So either pass#word or password#
fails.
I am now checking other special characters ('*' works).
Is there a faster
OK, so it appears that the bug is if you have a special character in the
original password. I don't really want to say which special character
and where in the password it appears in this public area, but if you
contact me, I'll let you know.
Also, please excuse my ignorance on all of this. I am
Clicking the 'Detect Keyboard Layout' button works fine, but not the
initial guess when going through the installation menus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948716
Title:
Proposed
New data point: Using build 20211028 and an alpha-character ONLY
password works. I'll now test the 21.10 build with that alpha password
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948714
Title:
Hi Leo,
Interesting. I ran the Ubuntu 21.20 iso through the same VM (used fresh
VDI) and I get the same fault. On my actual Ubuntu machine 21.10 was
installed with no problems.
So maybe it's a VirtualBox issue?
I don't understand (I mean I really am lacking the knowledge) why the keyboard
This is my first time testing daily builds - It has worked in previous releases
(I think).
There are some differences in the layout, e.g. the " and @ mappings are swapped
(Shift+2 for " in the UK, and Shift+2 for @ in the US).
I agree it's a low urgency/low importance bug, but it should be easy
Also exists in Jammy builds scripts for steps 3 & 4
3. Select your keyboard layout and click on continue
The 'Preparing to install Ubuntu' screen is displayed
4. On the screen Preparing to install Ubuntu, note the availability of the
following components.
Should be 'Updates and other software'
Also exists in 20211027 build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948716
Title:
Proposed Keyboard is Incorrect
To manage notifications about this bug go to:
Public bug reported:
The jammy daily testcase states:
"The proposed keyboard corresponds with your keyboard"
The proposed keyboard was English (US) and my keyboard is English (UK)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu
Same issue on 21.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881712
Title:
gnome-software says connection is metered while is not
To manage notifications about this bug go to:
Public bug reported:
To reproduce:
1. Start any application, e.g. Nautilus or Terminal
2. Click 9-dot grid in bottom corner fo screen.
3. The launcher (and it's app shortcuts) are hidden behind the application
windows that were opened in step 1.
Those open applications are tiled as if I had
Adding some cross-linking to help people who encounter this in the
future, and perhaps also help the devs:
This is discussed in the Ask Ubuntu post:
https://askubuntu.com/questions/1128164/no-suitable-destination-host-
found-by-cups-browsed
The solution there (which worked for me) is to `apt
ID = #3026
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3026
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Ubuntu 18.04
Sound Juicer 3.24.0-2
Operation:
Rip a single-disc album, with the "File name" preference set to "Number -
Title".
Expectation:
The filename should be something like "01 - My Song.mp3"
What actually happens:
The filename generated will be something like "Disc
Public bug reported:
The aspect ratio of the icon on the top left of the screen (Activites
bar?) is broken so it looks taller and thinner than normal.
See attached screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature:
Sorry, I should add that the pop-up window remained on top of all the others,
so it wasn't hidden behind anything else before I went to bed.
And although it was at the top, when I entered my password and the field went
grey, the window remained visible, but if I clicked anywhere in the window,
Not at that time - I had just gone to bed. I had changed them earlier that day,
and the error triggered. So I rebooted. This time the error came about without
me touching it.
Journal output attached.
The bug doesn't appear to be triggered by any steps in Software-Updater
** Attachment added:
I attempted to make a change to a repository by launching Software &
Updates and editing an unselected package from eoan to fossa - the
authentication window persisted at the top left of my screen throughout
- even after entering my credentials in the central authentication
window that popped up
Public bug reported:
I left the Beta of Focal Fossa running overnight and when I logged in
this morning, I found an open Authentication window with the message "To
change software repository settings, you need to authenticate" (see
attached screenshot).
I enter my password and the password field
Two network & volume indicators also on XFCE panel.
No change even after resetting the panel (xfce4-panel -r).
I guess two is better than none. ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I *might* have a possible clue for the gdebi gui crash in Bionic.
If I right click on a .deb file and tell it to install with gdebi the gui will
crash.
If I open a terminal in the same directory as the file and launch gdebi-gtk
*.deb the gui will install and uninstall the .deb file without
Public bug reported:
x11vnc will terminate abnormally on zesty with a **stack smashing
detected** error. Reverting to an x11vnc from an earlier Ubuntu version
appears to resolve this error. The error is generated by user activity,
it seems to be triggered by certain user input, such as a mouse
This turned out to be a problem with the user not being in the audio and
pulse-access groups. Also the back panel speaker out only has one
channel working, however the front panel headphone connector works fine.
So I just use the front panel headphone jack.
** Attachment removed: "AlsaInfo.txt"
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837338/+files/CurrentDmesg.txt
** Attachment removed: "JournalErrors.txt"
** Attachment removed: "PulseList.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837341/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I have no audio output with the following configuration:
*-multimedia
description: Audio device
product: MCP61 High Definition Audio
vendor: NVIDIA Corporation
physical id: 5
bus info: pci@:00:05.0
version: a2
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555147
Title:
package linux-image-extra-4.4.0-11-generic 4.4.0-11.26
It looks like sudo 1.8.12 made it into 15.10 finally. Excellent. Apple
went the other route and locked the clock back down.
(https://support.apple.com/en-us/HT205031)
The CVE associated with this bug seems to be about the TZ (seen on
RedHat's security site:
This appears to be a package dependancy problem because installing kio,
plasma-desktop and plasma-desktop-data fixed this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453162
Title:
Complete
** Description changed:
+ This is on Ubuntu 15.04.
+
This bug results in KDE crashing on login. This results in KDE being
completely nonfunctional, we are left with a blank screen. Any help is
appreciated.
With every login to Plasma, we get a plasma crash. Then KDE session does
not
Public bug reported:
This bug results in KDE crashing on login. This results in KDE being
completely nonfunctional, we are left with a blank screen. Any help is
appreciated.
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
** Description changed:
This bug results in KDE crashing on login. This results in KDE being
completely nonfunctional, we are left with a blank screen. Any help is
appreciated.
+
+ With every login to Plasma, we get a plasma crash. Then KDE session does
+ not continue, we are left with an
You can set the time with:
timedatectl set-time 2000-01-01 10:00:00
Wow. Yeah, that'll make exploiting this *much* easier on desktop.
Fortunately Ubuntu Server doesn't allow this without authenticating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Notice that only the SID changed though. That gives me a 1 in 32k
chance, and I can generate them basically at will with setsid. In my
testing so far, the inode of the TTY file for /dev/pts/0 has stayed 3
across several reboots. If it doesn't change, then it is moot from a
security standpoint.
To clarify: I reboot, log in, open gnome-terminal. The tty is always
/dev/pts/0, and ls -i /dev/pts/0 shows an inode of 3. This occurs even
if I shut down and power back on, though admittedly in a VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yup, I think so. while true; do setsid something to run sudo; done; or
the like. In my tests rolling through then all took about 5 minutes, and
that was in a crappy VM with 1 core and 30% CPU being used by compiz. I
haven't gotten it to pop an escalated shell yet, but I'll poke at it
more tonight
Oh, nevermind! You're talking about outside of the sudo instance. In the
case of Cron, etc: just let *the user* decide whether they want to be
asked after the first time. Make it an option to unlock the clock,
disabled by default but still available.
--
You received this bug notification because
Kay, the update to sudo (1.8.10) actually solves this by using the
monotonic clock. All that needs to happen is for Ubuntu to udpate to it.
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219337
Without rebooting, the tty, inode, sid should change for every
terminal you open.
When I tried this on 15.04, the tty and inode didnt: only the SID
changed. Closing a gnome-terminal and reopening it got the same tty and
SID. For *additional* terminals, they got new ttys and inodes, but if
you
Indeed. Trojaning those requires waiting for the user. Why lay a trap
and wait when you can just break down the door? If I can use dogtail or
similar to automate the clock and suddenly we're in drive-by territory.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Tyler,
it's great that this bug will be fixed. However, I have some concerns about the
mitigations factors.
1) Timestamp: Easily found in the auth.log, and easily bypassed due to
an unlocked clock.
2) TTY: The tty of the first gnome-terminal running is (as far as I can
tell) /dev/pts/0. That's
Congratulations, Ubuntu team. You have now fallen behind *Debian's
Stable Release* in a security update to sudo, despite several releases
in between. They even released their newest (24 month development cycle)
in the same month as you. This has been fixed, *fully fixed*, for over a
year now. Epic
Debian hasn't fixed this in squeeze or wheezy yet, it's fixed in
jessie because they have a recent enough version of sudo.
They haven't fixed it because they were never vulnerable: they don't
allow you to change the clock without a password.
We do plan on backporting monolithic timer support,
Really? If the terminal I last ran sudo in is open still on the machine,
and it's unlocked, I couldn't simply change the time back to the
previous sudo command an escalate?
Even if it's a remote chance, it's still an easy exploit.
/var/log/auth.log is certainly readable by a program that uses a
*** This bug is a duplicate of bug 1331654 ***
https://bugs.launchpad.net/bugs/1331654
But a Dell Inspiron 15R isn't an Dell Inspiron 1525. ;-)
Glad that script cures it, that script worked well until I installed the kernel
3.13.0-35.62 on our Dell Inspiron 1525.
--
You received this bug
It looks like linux-image-3.13.0-35-generic (3.13.0-35.62) contains the
fixes for this bug.
Yes it does, I deleted the band-aid fix script in my /etc/pm/sleep.d/
folder and upgraded from the recommended 3.13.0-24-generic kernel to
3.13.0-35 via the update manager in Mint 17 and our Inspiron 1525
Same here with two different network printers on Linux Mint 17 Qiana XFCE
desktop.
The xfce4-panel -r command in a terminal window removes it OK though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So I'm assuming that all the scripts in the sleep.d directory get
executed on a suspend/resume event?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305371
Title:
[Dell Inspiron 1525]
I have 3 files in that directory (sleep.d),
10_grub-common
10_unattended-upgrades-hibernate
novatel_3g_suspend
what would this script be called or is it appended to one of these files?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm running the 3.13.0-30-55 kernel on a 1525 laptop and unfortunately this
problem still exists.
Suspend always works, resume works maybe 80% of the time. It's the wife's
laptop so it's high visibility. ;-)
I can give more info if given specific instructions, thanks.
--
You received this bug
I loaded the 3.14.5-031405-generic kernel my Inspiron 1525 laptop will still
not resume from standby about 80% of the time.
Total lockup, must power off. (kernel 3.13.0-24 acted the same way) :-(
I'm running the XFCE desktop in Mint 17.
--
You received this bug notification because you are a
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129129/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129125/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328313
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129128/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
I'm on a Dell Latitude E7240 running 12.04 LTS and my touch pad acts
erratically. It happens because my middle and ring fingers accidentally touch
the top edge of the pad while my pointer finger is moving the cursor.
apport information
** Attachment added: Card1.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129131/+files/Card1.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129126/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328313
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129127/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328313
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129134/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328313
Title:
Alps
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129138/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129132/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328313
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129133/+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/1328313
Title:
apport information
** Attachment added: Card1.Amixer.values.txt
https://bugs.launchpad.net/bugs/1328313/+attachment/4129130/+files/Card1.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 189 matches
Mail list logo
