For reference I think it's likely the same issue as this one reported
in the RedHat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1884260
Package: cheese
Version: 3.38.0-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Open cheese and record a video.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Record a video. Stop the recording.
O Mér, 13-02-2019 ás 11:30 +, Simon McVittie escribiu:
> Control: tags -1 + moreinfo
>
> On Wed, 13 Feb 2019 at 11:51:08 +0100, Sergio Villar wrote:
> > gnome-shell is making my system unusable by completelly filling up
> > the /var partition due to the errors it s
Package: gnome-shell
Version: 3.30.1-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
gnome-shell is making my system unusable by completelly filling up the /var
partition due to the errors it spits into several log files like syslog,
user.log and messages. All
018 at 13:22:37 +0200, Sergio Villar Senin wrote:
> > Note that I've reproduced today this very same issue with lightdm
> > as
> > well, so I guess this is the confirmation that the bug is somewhere
> > else. Graphics drivers maybe?
>
> Yes, this sounds like a graphic
Note that I've reproduced today this very same issue with lightdm as
well, so I guess this is the confirmation that the bug is somewhere
else. Graphics drivers maybe?
> I basically started without plyumouth enabled and the screen becomes
black with the cursor in the top left corner of the screen.
I obviously meant _disabled_
BR
O Ven, 28-09-2018 ás 12:47 +0100, Simon McVittie escribiu:
> On Fri, 28 Sep 2018 at 11:01:09 +0200, Sergio Villar Senin wrote:
> > O Xov, 27-09-2018 ás 22:39 +0100, Simon McVittie escribiu:
> > > On Thu, 27 Sep 2018 at 23:16:05 +0200, Sergio Villar Senin wrote:
> &g
O Xov, 27-09-2018 ás 22:39 +0100, Simon McVittie escribiu:
> Control: tags -1 + moreinfo
>
> On Thu, 27 Sep 2018 at 23:16:05 +0200, Sergio Villar Senin wrote:
> >The background of the plyumouth theme is shown but the list of
> >users is not there as expected.
>
&
Package: gdm3
Version: 3.30.1-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
The problem appeared on 3.30 and is still a problem in 3.30.1
* What exactly did you do (or not do) that was effective (or
ineffective)?
O Xov, 20-09-2018 ás 17:22 +0200, Michael Biebl escribiu:
> On Thu, 06 Sep 2018 11:20:41 +0200 Sergio Villar Senin
> wrote:
> > Package: firewalld
> > Version: 0.6.1-2
> > Severity: normal
> >
> > Dear Maintainer,
> >
> >* What led up to the s
O Mér, 12-09-2018 ás 21:49 -0400, Jeremy Bicha escribiu:
> Control: tags -1 -moreinfo
>
> On Wed, Sep 12, 2018 at 8:06 PM Sergio Villar Senin <
> svil...@igalia.com> wrote:
> > What extra info would you need?
>
> In the View menu, try clicking Show Any.
Oh
O Xov, 13-09-2018 ás 02:59 +0200, Michael Biebl escribiu:
> You already filed the same issue as #908116
> No need to file a duplicate.
Oh I'm really sorry for that, my MTA was not working fine so I thought
I haven't sent it yet. Feel free to close as dup.
BR
O Mér, 12-09-2018 ás 19:58 -0400, Jeremy Bicha escribiu:
> Control: tags -1 moreinfo
>
> I can't reproduce this bug with the information you have provided.
>
> Note that seahorse continues to run in the background as a system
> service. I recommend logging out and logging back after upgrading
>
Actually I think the problem is worst than I thought as I cannot access
any of the enabled services in the machine with updated firewalld. I've
tried several, ssh, rdp, mdns... All of them are enabled in the active
zone and none of them is opened in the firewall.
I'd advice increasing the
Package: firewalld
Version: 0.4.4.6-2
Severity: important
Dear Maintainer,
* What led up to the situation?
Upgrade to 0.6.1
* What exactly did you do (or not do) that was effective (or
ineffective)?
Using avahi-discover to list discoverable services in my LAN
* What was
Package: seahorse
Version: 3.30-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Upgrading to 3.30
* What exactly did you do (or not do) that was effective (or
ineffective)?
Open seahorse. Click on the login keyring.
* What was the outcome of this
Package: libgtk-3-0
Version: 3.24.0-1
Severity: important
File: gtk
Dear Maintainer,
When you open a gnome-terminal and then switch to another window then the
blinking cursor is lost. You can recover it by switching tabs in
gnome-terminal. Apparently only Wayland sessions are affected.
Reported
These are the two missing files from the original report
---> firewalld.conf
# firewalld config file
# default zone
# The default zone used if an empty zone string is used.
# Default: public
DefaultZone=public
# Minimal mark
# Marks up to this minimum are free for use for example in the
Package: firewalld
Version: 0.6.1-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
Upgrading to sid's 0.6.1-2
* What exactly did you do (or not do) that was effective (or
ineffective)?
Multicast DNS (avahi) does not work at all with the new firewalld
O Mar, 24-07-2018 ás 18:41 +0200, Michael Biebl escribiu:
> On Tue, 17 Jul 2018 23:32:56 +0100 Mark van Rossum
> wrote:
>
> > Since the update to network-manager-config-connectivity-
> > debian:amd64
> > 1.12.0-4, and when I am connected via Wifi
> > Networkmanager is rapidly filling syslog
I'd raise the severity of this issue. In my particular case I got an
unusable system from fresh start after 5 minutes. I checked the syslog
and this is what I get
$ sudo grep "connectivity check failed" /var/log/syslog | grep "Jul 19"
| wc -l
10522249
10M records in just 5 minutes looks clearly
I'd raise the severity of this issue. In my particular case I got an
unusable system from fresh start after 5 minutes. I checked the syslog
and this is what I get
$ sudo grep "connectivity check failed" /var/log/syslog | grep "Jul 19"
| wc -l
10522249
10M records in just 5 minutes looks clearly
JFTR after some debugging we have verified that the problem is the VA-
API decoder not in webkitgtk
After enabling debug, we could see the following errors:
$ GST_DEBUG=3,webkit*:5 /usr/lib/x86_64-linux-gnu/webkit2gtk-
4.0/MiniBrowser
...
0x7fa5cc0f8770 ERROR vaapivideomemory
O Lun, 17-10-2016 ás 10:21 -0500, Jason Crain escribiu:
> On Mon, Oct 17, 2016 at 04:23:28PM +0200, Sergio Villar Senin wrote:
> > * What led up to the situation?
> >
> > Visit https://davidwalsh.name/demo/notifications-api.php and
> > click on &
Package: epiphany-browser
Version: 3.22.1-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Visit https://davidwalsh.name/demo/notifications-api.php and click on
"Show a notification" button
* What was the outcome of this action?
The browser crashed.
O Lun, 17-10-2016 ás 09:12 +, Debian Bug Tracking System escribiu:
> Thank you for filing a new Bug report with Debian.
I think we can safely close this. The bug is only affecting
accounts.google.com. They should have changed something on the server
side because the popup is shown for some
Package: epiphany-browser
Version: 3.22.1-1
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
* What led up to the situation?
Open a webpage for which you have previously saved a user/password pair
and set the cursor on the username field
* What was the
Package: libwebkit2gtk-4.0-37
Version: 2.14.1-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Open any youtube.com video in the epiphany browser.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Click on play.
* What was
Package: network-manager-openvpn
Version: 1.0.8-1
Followup-For: Bug #767549
Dear Maintainer,
It turns out that the bug still exists with version 1.0.8. As the
original reporter mentioned the routes are perfectly sent by the VPN
server because they're correctly set when starting the openvpn
Package: gnome-documents
Version: 3.18.2-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
1- Open gnome-documents
2- Click on search button
3- Type 1 letter
* What exactly did
En 24/05/14 17:03, Ritesh Raj Sarraf escribiu:
On 05/24/2014 03:57 PM, Sergio Villar wrote:
12:07:21 T:140323922204416 DEBUG: NFS: Context for
192.168.1.10/export/media not open - get a new context. 12:07:21
T:140323922204416 DEBUG: NFS: Connected to server 192.168.1.10
and export /export
Package: libnfs1
Version: 1.9.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I have two machines a client and a server. The server has a couple of NFS
shares. Working perfectly with libnfs1 1.3 and xbmc 12.3 in the client machine.
Package: distccmon-gnome
Version: 3.1-6
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Execute distccmon-gnome
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What
En 02/09/12 21:41, Salvatore Bonaccorso escribiu:
Hi
Looking at wheezy bugs to be fixed I stumbled over #657751 in
gdm3. Sergio, are you able to repoduce this with current version in
wheezy?
I'm running sid right now, and all I can say is that I am not able to
reproduce it with the current
Is this bug blocking the totem release? GNOME 3.6 is almost here and nor
even 3.2 landed in unstable/testing.
Can we help somehow with the release?
BR
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
You can close this bug as I found the answer here:
http://askubuntu.com/questions/73638/duplicate-icons-in-gnome-shell
Turns out that menu-xdg is the one showing the duplicate entries.
Uninstalling it fixes the issue.
BR
Package: gnome-shell
Version: 3.4.1-6
Severity: normal
Dear Maintainer,
* What led up to the situation?
Upgrading to gnome-shell 3.4.1-6
* What exactly did you do (or not do) that was effective (or
ineffective)?
Upgrading the package. Checking the ChangeLog there seem to be a couple
Is there any reason why this patch hasn't been applied yet? This is a RC
and there has been a patch available since March. 3.4 has been out for a
while right now and we got stuck in 3.0. I can help with debugging if
needed.
BR
--
To UNSUBSCRIBE, email to
Package: empathy
Version: 3.2.2-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
since I updated empathy to 3.2.2-1 version in unstable, I get no notifications
when a buddy is talking to me making empathy not usable as you don't know when
people is
En 29/11/11 19:38, Laurent Bigonville escribiu:
severity 650419 important
severity 650420 important
merge 650419 650420
thanks
Hi,
I've the feeling that this is an interaction issue between empathy 3.2
and gnome-shell 3.0.
Could you try to upgrade gnome-shell with the version from
Package: update-manager-gnome
Version: 0.200.3-1
Severity: important
File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ui.py
*** Please type your report below this line *** I have some available updates,
then I click on the update manager try icon and the program reports an error in
a dialog
42 matches
Mail list logo
